Why a 7-day sprint?
Most founders waste months building products no one wants. The point of a 7-day validation sprint is to compress the discovery loop: by the end of the week you should know whether a real, paying audience exists for the problem you want to solve — or whether to move on. The seven days are not arbitrary. They are short enough that you cannot fall in love with the idea, and long enough to talk to humans rather than guessing.
Day 1 — Write down the hypothesis
Frame your idea as a single sentence: "[Audience] struggles with [problem] and would pay [price] for [solution]." Be specific. "Marketers" is not an audience; "B2B SaaS marketers at companies with 50–200 employees" is. The narrower the hypothesis, the easier it is to falsify. Write the hypothesis at the top of a doc and keep updating it through the week — by Day 7 the wording should be very different from Day 1.
Day 2 — Map the existing alternatives
List 5 ways your target audience solves this problem today, including spreadsheets, Notion templates, freelancers, and "doing nothing." If they are not actively spending time or money on a workaround, the pain is not strong enough to justify a new product. Pay particular attention to spreadsheets and "I just live with it" answers — those are the strongest signals that there is room for a focused tool.
Day 3 — Find 20 prospects
Use LinkedIn Sales Navigator, niche subreddits, Slack communities, and Twitter to identify 20 specific people who match your target audience. Save their names and how you found them. This becomes your discovery interview shortlist. The act of finding 20 specific humans is itself a validation step: if you cannot list 20 people in a day, your audience is too vague or too thinly distributed.
Day 4–5 — Run discovery interviews
Reach out to all 20 with a short, no-ask message: "I'm researching how [audience] handles [workflow]. Could I ask you 4 questions over a 15-minute call?" Aim for 8–10 conversations. Ask about the last time the problem hurt, what they tried, and what they paid (if anything). Do not pitch your solution. The single most useful question is "walk me through the last time this happened" — concrete past behavior beats hypothetical future intent every time.
Day 6 — Score the signal
After interviews, score each prospect on three axes: pain severity (1–5), willingness to pay (1–5), and reachability (how easy will it be to find more like them). If the average pain × pay score is under 12 across all interviews, the wedge is too weak. Pay attention to outliers too — a single 5×5 prospect with a credit card in hand is often the seed of a profitable niche, even when the average is mediocre.
Day 7 — Write the kill-or-build memo
In one page, document the hypothesis, what you heard, the score, and your decision. If you are building, your memo doubles as the brief for the MVP. If you are killing, you saved yourself months of wasted code. Either outcome is a win — the goal of the sprint is decision velocity, not a guaranteed yes.
Common failure modes
Founders who run this sprint badly tend to make three predictable mistakes: they pitch instead of listen, they only talk to friends who are too polite to push back, and they conflate excitement with willingness to pay. If you catch yourself in any of these patterns mid-week, restart the day with a friend in the room as a "did they actually say that?" referee.
Key takeaways
- A 7-day sprint forces decision velocity and prevents months of building the wrong product.
- A sharp, falsifiable hypothesis is the foundation — vague audiences kill the sprint on Day 1.
- Discovery interviews focused on past behavior, not pitches, are the only honest signal.
- A pain × willingness-to-pay score under 12 is a kill signal even if the idea feels exciting.
- The output of the sprint is a one-page memo — kill or build, never "let's keep thinking about it."
What to do next
If validation passes, run our First 100 Users Planner to design the early acquisition motion, then use the Vibe Coding Time Estimator to scope the MVP. Pair the sprint with the Confidence scoring methodology to compare your hypothesis against the patterns we see across 1,000+ generated blueprints, and read Idea to MVP in a weekend once you are ready to build.