How to Find Your Ideal Customer Before You Launch: A 4 Week Pre-Launch Playbook

There are two kinds of launch day. In the first, you press publish and refresh an empty dashboard. In the second, the people who are about to buy already know your name, because they have been filing bug reports for six weeks.

One founder in this series has had both. His first app, Screenshot Swipe, launched into silence and was eventually abandoned. His second, GainFrame, launched with more than 100 test users behind it and did over $250 in subscriptions on day one.

Nothing about the second launch was luck. This is the playbook, drawn from him and six other founders who each got a paying customer without an ad budget.

Why pre-launch discovery beats post-launch iteration

Post-launch, every wrong assumption costs you a rebuild and a chunk of your remaining motivation. Pre-launch, it costs you a conversation.

DraftKit had a working prototype in a weekend, built in Lovable. It was wrong. Its founder had built it around a calendar because scheduling was the problem she personally felt. Three weeks of talking to Substack writers and watching them use it revealed that what they wanted was a place to write together. She caught it early enough that it cost weeks instead of a year.

She Shapes Digital cut even earlier. One of the founders sent a message to a Slack community inviting women to join a prototype, explicitly saying it would not be perfect and that she wanted feedback rather than money. Eighteen people signed up within days.

Week 1: pick the room and go quiet in it

Before you recruit anyone, find where your problem already gets discussed and read for a week without pitching.

CheckVibe came directly out of this kind of observation. Its co-founder was shipping fast with AI coding tools and noticed nobody was checking what got deployed. People were pushing real apps with Supabase keys in the frontend and row level security wide open. The code worked, so they assumed it was safe.

Week 2: recruit a small group with an honest ask

Now you go in, and the framing matters more than the offer.

GainFrame's founder found testers on Reddit and built a small mailing list, then ran TestFlight before the App Store. He ended up with 100 plus testers, of whom roughly 25 were highly active, submitting bugs and feature requests continuously. That group shaped his roadmap instead of him guessing at it.

PocketHog was posted on the PostHog subreddit well before it was polished, and its founder says the feedback from real users shaped V2 more than any amount of solo iteration would have.

Week 3: watch them use it, do not ask them about it

Interviews give you opinions. Observation gives you behavior, and behavior is what you can trust.

The blunt version, from Narrareach: it is uncomfortable watching users use your product, and you learn a lot. Every major improvement came from watching creators get frustrated at a specific point.

Instrument the same week you invite people in. PocketHog replaced its API key signup with OAuth because users were dropping off, and then analytics showed the new OAuth flow failing 20% of the time. Analytics caught a bug that no user would have thought to report, because from their side it just looked like the app did not work.

CheckVibe's recommendation is to wire up analytics and billing from day one, because you cannot fix conversion or churn problems you cannot see. GainFrame's is to invest in analytics earlier than you think you need to.

Week 4: test willingness to pay before you finish building

You are not testing whether they like it. You are testing whether the problem is expensive enough for money to change hands.

• •Free intro session plus a code. She Shapes Digital hosted free intro sessions and handed everyone who showed up a discount code. Their first paying customer came straight through that funnel.
• •Show the problem, charge for the fix. CheckVibe lets anyone scan and see how many issues they have, and only charges if there is something to fix.
• •Credits instead of subscriptions. DraftKit sells credits for features like AI drafting while its founder works out the permanent model.
• •The prototype that is a person. She Shapes Digital ran a five week program with Canva, Claude, and a GitHub hosted site. No app required.

What good pre-launch signal looks like

• •Someone pays before you have properly launched. CheckVibe's founder had written a few TikTok comments that got two or three likes when the first payment landed.
• •Testers file bugs unprompted and keep coming back after the novelty has worn off.
• •Someone recommends it for you. When DraftKit's founder and another writer published a post built together in the tool, he mentioned it in the comments without being asked.
• •You are using it yourself daily. PocketHog's founder never nearly quit, because she was using it on her phone every day.

What to ignore

Compliments. Signups with no usage. Feature requests from people who have never opened the product twice. And your own embarrassment about how rough it looks, which is the least reliable signal of all.

The four week summary