Most founders do it backwards. They spend three months building, then wonder why nobody shows up. I've been there. Here's the framework that flipped the order and changed the outcome.
The core principle: validation is a sales process, not a research project. You're not gathering data. You're finding people willing to pay before you finish building.
Week 1: Kill Your Assumptions Before They Kill Your Startup
Before you write a single line of code, write down every assumption baked into your idea. Not the obvious ones — the sneaky ones.
- "Users will switch from [existing tool] because mine is better"
- "People will pay $X/month for this"
- "My target customer has this problem every week"
For each assumption, ask: What's the cheapest way to prove this wrong?
Then go find the cheapest way.
Reddit is your best friend here. Find the 3-5 subreddits where your target user lives. Don't post "I'm building X, would you use it?" — that's worthless. Instead, search for complaints. Real ones. Copy-paste 20 posts where people describe the exact pain you're solving. Read the comments. Notice what language they use. Notice what solutions they've already tried and abandoned.
In week 1, you're building a vocabulary, not a product.
Concrete deliverable: A one-page "customer voice" document with real quotes, real frustrations, real workarounds your potential users are already doing. This becomes your marketing copy later.
Week 2: The Fake Door Test (And Why You Should Feel Uncomfortable Doing It)
Build a landing page. Not a product — a landing page. Twenty minutes on Carrd or a simple HTML file. One headline, three bullet points, one call-to-action button.
The CTA should be an email signup OR — and this is the uncomfortable part — a payment form.
Yes. Charge people for something that doesn't fully exist yet. Be upfront: "We're launching in 6 weeks. Early access is $49. You'll get lifetime access if we don't ship on time."
This is the only validation that actually counts. A hundred email signups means nothing. Three credit card numbers means you have something real.
Where to get traffic without ads:
Twitter/X DMs — Find people tweeting about your exact problem. Send a message: "I saw your tweet about [problem]. I'm building a tool for this. Would 15 minutes of your time be worth free early access?" This is not spam. It's targeted outreach with genuine value.
Niche Slack groups and Discord servers — Every industry has 2-3 Slacks where practitioners hang out. Join them. Contribute for a week. Then mention what you're working on.
Your own network — Message 50 people in your phone. Not to sell them. To ask if they know anyone who deals with [problem]. Three degrees of separation works.
Goal for week 2: 100 conversations started, 10 discovery calls scheduled.
Week 3: Discovery Calls Are the Product
Run those 10 calls. Use the Mom Test framework: ask about their life, not your idea. "Tell me about the last time you [problem]. What did you do? What did you try first? How much time did it cost you?"
You're not pitching. You're listening.
After each call, write down:
- The exact phrase they used to describe the problem
- What they're currently using (your real competitor)
- What they said when you mentioned price
Three patterns will emerge. One of them is what you're actually building. It's almost never exactly what you thought.
At the end of the call: "Based on what you told me, I'm building [thing]. Would you pay [price] to be a founding member?"
If they hesitate, ask why. If they say yes, send them a PayPal link before they hang up.
Expected conversion: 2-4 paying customers from 10 calls. That's enough to build.
Week 4: Ship the Minimum Viable Version to Your Paying Customers
You have paying customers. Now you owe them something real.
Build the smallest thing that delivers the core value you sold. Not features — value. If you sold "faster invoicing," build invoicing. Skip the dashboard, the analytics, the team features, the integrations.
Ship it directly to your early customers. Not a public launch — a personal delivery. "Hey [name], here's the tool. I set up your account. Can we do a 20-minute walkthrough together?"
Watch them use it. Where do they hesitate? Where do they ask questions? Where do they succeed and look pleased? That session is worth more than any A/B test.
This is the part where most indie hackers bail — shipping something imperfect to people who paid real money feels terrifying. Do it anyway. Your early customers signed up because they have the problem, not because they expect a polished product.
The Scaling Phase: From 10 to 100
Once your first cohort is getting value, the acquisition math changes. Now you have:
- Real testimonials (ask for them explicitly)
- A clear before/after story
- Social proof for the next hundred people
Layer these distribution channels in order:
- Product Hunt — Only if your product is genuinely ready for public feedback. A botched PH launch is worse than no launch.
- SEO content — One article targeting the exact search query your customer would type when they have the problem. Not "best invoicing software" — "how to send invoices as a freelance developer without an accountant."
- Partner distribution — Find tools your users already use. Propose a simple integration or co-marketing. One email to the right founder opens more doors than six months of cold SEO.
- Your customers become recruiters — Build a referral mechanic early. One month free for each referral isn't expensive when your CAC is zero.
The 30-day timeline isn't magic. Some ideas need 60 days. Some validate in 10. The framework is the forcing function — it stops you from building in the dark.
What Most People Get Wrong
They treat validation as something you do before building, then stop once you start. Real validation is continuous. You're always asking: are we building the right thing, for the right person, at the right price?
The moment you stop doing discovery calls because "we have customers now" is the moment you start drifting from product-market fit.
Keep one call per week on your calendar forever. Not to sell — to listen.
The process above is exactly what I went through to build and iterate on my own tools. If you want the complete structured version with templates, scripts, and week-by-week checklists, I compiled everything into a practical guide: Idea Validation & First 100 Users Framework.
Build things people want. Charge for them before they're ready. Listen more than you pitch.