Framework
Pre-MVP Concept Validation
Before writing code, test the concept: a landing page, a waitlist, a single-function prototype, or direct customer questions. Confirm the problem is real and users want to interact with it the way you imagine before committing engineering resources. Most founders skip this step and build the wrong thing at full cost. Fake it until you make it is not a launch strategy — it is a validation strategy.
How it works
- 1The MVP should really be an MVP — but before the MVP, you should validate the concept with the lowest possible investment: a landing page, a single question, a manual demo.
- 2Most founders roll out a no-code MVP and start marketing without knowing which problems are real, which features matter, or how users actually want to interact.
- 3Asking 'how would you log in?' before building auth is the whole point: if everyone says Google and Facebook and you build Telegram login, you've wasted time on something nobody needed.
- 4The validation step is also when market timing becomes visible. You cannot control timing, but you can assess it — and a product launched into the wrong moment will fail regardless of quality.
- 5The cockroach strategy: not lucky (right timing), but durable (built on real validated problems). Most founders need to be cockroaches, not lottery winners.
Hear it on the podcast
Why Your Great Idea Is Quietly Killing Your StartupListen to the episodeMore from this episode
The Third-Party Truth AuditHave a neutral outsider interview users, observe them using the product, and deliver a prioritized action list of bottlenecks blocking revenue. Founders cannot get honest feedback directly: customers soften criticism to protect the founder's feelings, and founders get defensive and hear what they can manage rather than what is being said. A third party removes both distortions and surfaces the real picture.Engine + NLP + AutomationModern product development converges three capabilities: an existing engine (platform, open-source framework, or no-code tool), natural language AI (NLP you can prompt rather than program), and trigger-based automation (API integration that has existed for 15 years and is now commercializing at scale). Build around the right engine and connect components rather than coding from scratch. In 2025, building from zero is immature.
Get the next framework first
One email a week with the frameworks, tools, and founder stories from the podcast. Free.
More frameworks for Finding & Validating Ideas
Stop, Listen, RelaunchBefore rebuilding in a complex domain, spend serious time — months, not weeks — doing nothing but listening to the people who live inside the problem: customers, practitioners, adjacent experts. Technology is the easy part. The hard questions — who do you serve, how do you make money, why does this product deserve to exist — must be answered first. Building before you have those answers is borrowing against a debt you will repay at maximum cost.The Three Checkbox FrameworkBefore building any AI product, three boxes must all be checked: (1) distribution on the cap table — equity to people already inside your target market's networks, (2) defensible IP — proprietary data, SOPs, or formulas that cannot be replicated with another model call, and (3) an industry expert involved. If you cannot check all three, the project does not start. Not pauses — does not start.The Founder's Three GuardrailsBefore investing time in any idea, run it through three filters: Is it fun? Does it make money? Is it of service? Add a fourth: Can I be best in the world at this? If any answer is definitively no, stop and move on.The 10 Uncomfortable Conversations RuleYou do not deserve to write a single line of code until you have survived ten customer conversations where you genuinely tried to be told no. Validation is evidence that bruises — not vibes that confirm what you already believe.The Tight Circle Photo Sharing ThesisPeople share photos freely when the social environment is tight, secure, and trusted — not because the product is good, but because the people around them feel safe.The 'Have To' Startup TestDon't start a company to start a company. Wait for the observation you cannot not pursue. That's the one you'll have the most fun with and the best shot of building well.