From Idea to Validation: A 6-Week Founder Playbook (2026)

Founder playbooks · Priya Iyer · Updated 2026-04-25

A concrete 6-week plan to take a startup idea from notebook to paying pilot. Includes interview targets, prototype scope, kill criteria, weekly outputs and a calendar template.

Moving from idea to validation is less about building more and more about narrowing the unknowns. The goal of the first six weeks is not a product. It is evidence. The output is one of three things: a real invoice, a real verbal commitment, or a clear no.

I have run this sprint with 40+ founders over the past three years, both as an angel and as an operator. The version below has been refined down to the absolute minimum that still works. Skip a week and the structure collapses; add a week and the urgency dies. Six is the number.

The 6-week schedule at a glance

A 6-week validation sprint
Week	Theme	Output	Kill criterion
1	Sharpen the problem	8 interviews + 1-line problem statement	3 of 8 disagree on the problem
2	Find the wedge	Wedge brief + alternatives map	No painful workflow you can ship in 2 weeks
3–4	Concierge prototype	Manual delivery for 3–5 design partners	Zero design partners agree to pilot
5	Charge money	1 invoice + 2 verbal LOIs	No one is willing to pay
6	Decide and rewrite	Rewritten roadmap + kill list	n/a

Week 1: Sharpen the problem

The first week is brutal in its simplicity: book and run eight interviews with people who match your assumed ICP. Not friends, not advisors, not people who told you "this is a great idea" at a party. Real prospects who would buy if the thing existed.

8 problem-discovery interviews with your assumed ICP. Aim for 30 minutes each.
Write the problem statement in one sentence; iterate it after every call.
Kill criterion: if 3 of 8 interviews disagree on the problem, narrow the ICP before continuing.
Forbidden: pitching the solution. The first 25 minutes of every call is about their world, not yours.

Week 2: Find the wedge

By end of week one you should have a problem statement that survives contact with eight strangers. Week two is about choosing where to attack first. The wedge is the smallest possible workflow that is painful enough to pay for and small enough to ship in two weeks.

Identify the most painful workflow within the problem.
Map current alternatives, including spreadsheets, email and "doing nothing".
Pick a wedge that is small enough to ship in 2 weeks.
Write the wedge brief in under 200 words. If you cannot, the wedge is too wide.

Week 3–4: Build a concierge prototype

These two weeks are where most teams die because they reach for production code. Resist. The point is to learn what the system needs to do, not to build the system. A spreadsheet, a Zapier zap and a WhatsApp group is a perfectly valid v1.

Use no-code, manual delivery, or a clickable demo. Do not write production code.
Run the workflow for 3–5 design partners as a service.
Track time saved or revenue created: that is the value metric.
Charge if you can, even a token amount. Free pilots teach you nothing about willingness to pay.

Week 5: Charge money

Week 5 is the moment of truth. Until money changes hands, everything you have learned is theoretical. The invoice is the first piece of unambiguous evidence.

Send a real invoice to at least one design partner.
Collect a verbal LOI from two more.
If nobody pays, the wedge is wrong, not the pricing.
Pricing experiment: quote three prices to three different prospects. The variance teaches you more than the average.

Week 6: Decide and rewrite the roadmap

At the end of week 6, the question is not "is this working"; it is "what is the next 6 weeks?" Pythe rewrites the plan automatically based on the evidence captured along the way. Three outcomes are possible: green light (extend the wedge), pivot (change the ICP or the wedge), or kill (the problem is real but you are the wrong team).

A real example: Lakshmi's six weeks

Lakshmi (composite, real numbers) is a solo founder building a back-office tool for boutique manufacturing units in Coimbatore. Week 1: she booked nine interviews, of which seven repeated the phrase "GST reconciliation eats my Saturday". Week 2: she narrowed the wedge to that one workflow. Weeks 3–4: she ran the reconciliation manually for four units using a Google Sheet and a daily WhatsApp report. Week 5: two units agreed to pay ₹4,000/month for the service. Week 6: she rewrote the roadmap around productising the reconciliation. By month four, she was at ₹2.1 L MRR with no code in production yet.

Common mistakes during the sprint

Doing nine things at once instead of one thing per week.
Letting interviews drift into pitching the solution.
Building production code in week 3 because it "feels more real".
Skipping the invoice step because you are "not ready to charge".
Treating the kill criteria as suggestions rather than commitments.

What if I have a day job?

Halve the cadence. 12 weeks instead of 6. The structure does not change.

Do I need a cofounder for this?

No. Solo founders complete this sprint successfully every cohort. The bottleneck is interviews, not headcount.

How do I find 8 interviews in week 1?

LinkedIn cold outreach, founder communities, and your existing network, in that order. 30 messages typically produce 8 calls in the right ICP.

What if the wedge changes mid-sprint?

Allowed once. After the second pivot, restart the sprint at week 1. Two pivots usually means the ICP is wrong, not the wedge.