Explore gave you a team, a finalized category, and a pain point tested against real conversations. Validate takes that raw material and forces it into a rigorous startup idea report, then puts that report in front of real industry feedback, not just internal confidence.
This stage is not about writing a nice document. It is about finding out, with real evidence, whether your idea survives contact with people who were not in the room when you built it. If you are in Kolhapur, the Industry Feedback Loop happens live at Founder Night. Anywhere else, run the same 14 days and submit your report for async mentor review.
Progress is measured by what you have tested and confirmed with real people, not by how confident you feel about the idea.
Adapted from the Build-Measure-Learn loop, Eric Ries, The Lean StartupYou confirm the problem is real before you confirm the solution works, and you confirm the solution works before you scale anything.
Adapted from Customer Development, Steve BlankFeedback only counts when it comes with a specific commitment or a hard critique, not a polite "sounds good."
Adapted from The Mom Test, Rob FitzpatrickYour report follows the same core questions serious investors have asked founders for two decades: problem, solution, market, model, team, why now.
Adapted from Sequoia Capital's founder pitch framework13 sections that force real thinking, built over 13 days, with 2 full days for the numbers
Real industry mentors score your report, twice
Weekly community checkpoints that keep the whole thing honest
Same rhythm as Explore. It continues here because a builder should never have to wait a week to ask for help.
Open, drop-in doubt-clearing with community founders. Bring a stuck section, a shaky number, or a report that just is not coming together.
Peer-level feedback on your report draft, before it ever reaches an industry mentor.
The formal night. Industry mentors, unaffiliated with this cohort's Founder Nights, review your finished report live, section by section, for the first time.
Thirteen sections. Answer them honestly and you will have a real, working validation of your idea, not just a document. The day-by-day guide below walks you through building each one.
Startup name, your name and role, date
Overview, mission, vision, key highlights
The core problem, who faces it, why it matters
What you offer and your USP
TAM, SAM, SOM, trends, competitors
Revenue, pricing, go-to-market
Design, features, roadmap, early prototypes
Channels, acquisition, positioning
Workflow, team structure, logistics
Costs, projections, break-even, funding ask
3, 6, 12 month roadmap and KPIs
Key risks and mitigation strategies
Why now, why this idea, why your team, call to action
Pull directly from your Explore stage: your finalized category, your validated pain point, your research documents, and your team. This week turns all of that into sections 1 through 6.
The executive summary is the only part most readers finish. It has to carry the whole idea in a few honest lines.
Under the Mom Test principle, your problem statement should be built from what people actually said and did during Explore, not from what you assumed going in.
Pull directly from your Week 3 Explore conversation log. If a claim here is not backed by something a real person actually said, flag it and go find the evidence.
A solution only matters in relation to the problem it addresses and what makes it different from what already exists.
Sequoia's framework asks one blunt question here: is this a big enough market for the outcome to matter? Your numbers need to answer it honestly.
A good problem and a good solution still fail without a business model that actually generates revenue.
Share sections 1 through 6 with other founders. This is peer review, not industry review, so the goal is catching obvious gaps and confusing language before Week 2.
Fold in Founder Night feedback before starting Week 2's sections.
Sections 7 through 13, then the report meets real industry mentors, twice. The Financial Plan gets two full days here, not one, because most first-time founders cannot honestly produce cost estimates, projections, and a break-even analysis in a single evening. The final three sections are light enough to finish the same morning as Founder Night 2.
This is where the idea stops being abstract. Even a rough sketch shows a reader you have actually thought about the thing itself.
A great product with no path to customers is not yet a business.
Investors and mentors both want to know the business can actually run day to day, not just exist as an idea.
Numbers are where most first-time reports fall apart. Nobody expects certainty, but they do expect honesty, and honest numbers take more than one evening.
A funding ask with no method behind it is either embarrassingly low or invented out of thin air. A simple heuristic beats a guess.
The final three sections are shorter individually but together they answer the question every reader is really asking: should I trust this team with this idea? Finish these before this evening's Founder Night, since the full report goes in front of a mentor tonight.
The formal round. Mentors are unaffiliated with this cohort's Founder Nights and are reading your report for the first time tonight, so the review stays independent of any peer feedback you got on Day 6. See the full mechanism below.
Under Customer Development's own logic, if validation does not hold up, you go back and fix it. You do not carry a flawed section forward and hope nobody notices.
Built on two ideas that already have a track record: Customer Development's rule that you validate in stages and go back when something fails, and the Mom Test's rule that a compliment is not evidence. Mentors are asked to score, not encourage.
A three-point scale is only rigorous if every mentor applies it the same way. These definitions are fixed, mentors do not set their own bar.
Niche mentor coverage is the hardest part of this to guarantee, so the matching process has a defined fallback instead of assuming a perfect match will always exist.
One mentor's read should never be the only gate on two weeks of work. Any team can request a second opinion within 48 hours of their Round 2 verdict. A different mentor or panel reviews the same report independently, without seeing the first mentor's scorecard. If the two reviews disagree, a short call with both mentors and the team resolves it. This does not apply to reopen a Validated verdict, only to challenge a Back to Explore or a contested Needs Work call.
Every section holds up. Ready to move into Stage 2 and start building.
The core idea holds, but specific sections need real rework before building starts.
The problem or market itself is not holding up. Better to find this out now than after building.
This is not the end of the road, it is a defined re-entry, chosen by the team, not decided for them.
Founder Night keeps its shape from Explore: the whole community gathers, no one goes through this alone. In Validate, it takes on a second job. Day 6 is peer-level, the same informal energy as Explore's Founder Nights, run entirely by fellow builders. Day 13 is where industry mentors, deliberately kept separate from the peer community that gave feedback on Day 6, show up to run the Feedback Loop live. Keeping the two nights separate is intentional: peer encouragement and independent industry critique should never blur into the same voice. Founder Room continues underneath both, Tuesday and Thursday evenings, for anyone stuck on a section between the two nights.
Bring what you built in Explore. Leave with a mentor-reviewed report and an honest verdict on whether it is ready to build.
Start Validating