We shut down a product years ago. This year we rebuilt it and the first paying customer came from the old user list.
Years ago we shipped AutoSync, a small tool that pushed Stripe data into Google Sheets. It worked, sort of, and then we let it go.
The thing that always bothered us: it polled Stripe by creation date. So anything that changed later — a refund, a subscription update, a dispute — never made it into the sheet. People's reports went stale without them realizing it.
This year the three of us rebuilt it properly on Stripe's event stream, as SyncStaq.
What we did before writing code: interviewed 6 teams who'd either used the old tool or had the problem. 4 of the 6 described the same job unprompted — calculating commissions or partner revenue share, and struggling to net out Stripe fees and refunds. We thought we were building a sync tool. We were building a payout tool.
Then the first paying customer after launch came from a single email to the old AutoSync user list. Not SEO, not ads, not social - a list that had been sitting there for years.
The lesson we keep relearning: your dead product's user list is worth more than a new audience.
Happy to answer anything about the rebuild or what came out of the interviews.
How are you using the rest of the old list now: inviting them into interviews, segmenting them by prior use case, or sending everyone the rebuilt offer? The non-buyers may be just as useful as the first customer for determining whether payouts are the core market or only the first niche.
This is one of the strongest customer acquisition insights. It flips the startup narrative completely - we're trained to think cold audiences matter (social, ads, growth hacking), but the users who already saw value in version 1 are infinitely warmer than strangers.
The Stripe data point is huge too. Going from simple sync to understanding the actual job (payout calculation) only happened through talking to users. Most teams skip that and rebuild what they think the problem was.
The strongest insight here is that the product changed when the customer problem became clearer.
How are you deciding whether the payout/revenue-share workflow is the wedge to build around, versus keeping SyncStaq broader as a Stripe data automation layer?