Framework
Sprint Zero
Before writing code, conduct a discovery phase that audits pirate metrics, forces explicit assumption validation, and produces a 1–1.5 month validated roadmap. Sprint Zero converts founder conviction into actionable direction. Almost every founder arrives with a three-month roadmap and no data to support it. Sprint Zero surfaces what is real and what is assumption — and the roadmap that comes out is one the team can build against with confidence.
How it works
- 1Audit pirate metrics first: retention, referral, revenue. Identify whether the numbers being reported are real signals or vanity metrics (signups, views, downloads that spike with PR).
- 2Force every roadmap item to answer the same question: what specific business metric will this move, and what data supports that assumption? Almost no founder can answer this without the audit.
- 3Record customer conversations and analyze them for what customers actually mean — many say 'yes' in research but don't intend to purchase. Convert signal to insight, filter out noise.
- 4The output is a 1–1.5 month roadmap, not a 3-month one. Short enough to be grounded in current knowledge; long enough to give the team direction.
- 5Sprint Zero is not optional: every unicorn Wednesday has worked with started as something materially different from what it became. The founders who found PMF were searching for demand, not protecting a thesis.
Hear it on the podcast
Hours Are Worthless, Replace Them with ThisListen to the episodeMore from this episode
The Founder's FourAt MVP/pre-PMF stage, founders should only do four things: marketing, sales, customer conversations, and fundraising. Anything else is not value. A founder at this stage is at a developmental milestone — and these four activities are the only ones where their presence creates leverage that no one else can replicate. Technical execution is delegated; everything else is a distraction or a delegation failure.Specialist-First HiringHire specialists, not generalists, especially in early stage. The generalist role — run experiments, figure out what sticks — belongs to the founders. When you need something done well, bring in someone who has dedicated years to that area. A specialist runs fast, clean, high-signal experiments. A generalist in a specialist's seat produces ambiguous results and wasted sprints.
Get the next framework first
One email a week with the frameworks, tools, and founder stories from the podcast. Free.
More frameworks for Building the Product
Prototype and PruneAI is a proxy for skill, not taste. Generate multiple enterprise-appropriate prototypes using real design system context, then let a human with taste prune down to the right one. Coined by Jules at Meta, reinforced by Scott Belsky. The bottleneck moves from production to curation — and curation is the irreducible human job.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.Design Systems ThinkingStop designing individual screens. Start designing systems of experiences. Every interface element is a pattern with explicit rules and constraints — not a one-off creative decision. This shift from instance-level to system-level abstraction is what enables consistent product experiences at scale and makes AI generation enterprise-appropriate.The Whole Person DiagnosticEffective diagnosis requires integrating three data streams that no specialist silo currently combines: longitudinal medical records (what the healthcare system has captured), wearable data (continuous biometrics between clinical encounters), and life story — the mind-body layer of trauma, stress, and relational context that the research literature documents as medically relevant but that EHRs structurally exclude. Consumer ownership of the record is the architectural enabler: the patient integrates across institutions because the institution won't.Meet Consumers Where They AreDo not build a new interface and ask customers to learn it. Identify the medium where your target customers already interact with this type of service — email, text, phone call — and build the product to operate entirely in that medium. The lower the adoption friction, the higher the trust, and the faster the referral loop. No app to download, no portal to navigate, no new UX to learn means less resistance at every stage of acquisition.Requirements-First DevelopmentThe CTO's core job is not writing code — it's translating business objectives into technical requirements, then ensuring the code solves the right problem. Start there. Generating code before generating requirements produces something technically functional that solves the wrong problem. The 70% wall is the symptom; deferred requirements are the cause. Requirements elicitation — guided prompting to extract what you actually need — is what separates MVPs from prototypes.