Foundation Sprint Worksheet
Work through a lighter Foundation Sprint: define the problem, the customer and your value proposition, then list assumptions, metrics and experiments.
The interactive tool loads here when JavaScript runs.
About this toolWhat is the Foundation Sprint Worksheet?
The Foundation Sprint Worksheet walks a founding team through four steps before anyone writes code: Problem Definition, Target Customer, Value Proposition and Validation Plan. Each step is one tab with a prompt, a few coaching tips and a text box. The last tab collects three lists you can grow line by line: Key Assumptions, Success Metrics and Validation Experiments.
It is a worksheet, not the full two-day workshop that Jake Knapp and John Zeratsky describe. There is no timer, no voting and no facilitator script. What you get is a structured place to write down the decisions a foundation sprint is meant to force, with a summary underneath and a Text, Image or PDF export you can send to a co-founder or adviser.
Answers are saved in your browser's local storage under the key foundation-sprint, so you can close the tab and come back later on the same device. Nothing is sent to a server, and clearing site data removes the draft.
- Four guided steps with prompts and coaching tips
- Editable lists for assumptions, success metrics and experiments
- Positioning template for the value proposition
- Text, Image and PDF export of the summary
- Autosaves in your browser; no account and no upload
Updated
How to use the Foundation Sprint Worksheet
- Open the Problem Definition tab and describe the problem in the customer's terms, without naming your product.
- Click Next and fill in Target Customer: who has the problem, how often, and what they use today.
- On Value Proposition, write one paragraph using the positioning template shown under the box.
- On Validation Plan, add Key Assumptions, Success Metrics and Validation Experiments with the Add buttons; use Remove to drop a line.
- Check the Foundation Sprint Summary below the tabs, then download it with the Text, Image or PDF button.
- Click Load Sample at any time to see a filled-in example (a curated freelancer marketplace for small businesses).
Worked example
Turning a vague idea into testable assumptions
Input
Problem: SMB owners waste hours finding reliable freelancers for urgent work. Assumption: SMBs will pay a 15-20% premium for pre-vetted freelancers. Metric: 80% of job posts get a qualified applicant within 24 hours. Experiment: hand-match 20 projects manually (concierge test).
This is the shape of the built-in sample. Each assumption has a number attached and an experiment that could prove it wrong within a few weeks. If the concierge test cannot find 20 paying projects, the premium assumption is in trouble before any code exists.
Background and insight
The Foundation Sprint comes from Jake Knapp and John Zeratsky, the pair who ran design sprints at Google Ventures and wrote Sprint (2016). Through their venture firm Character Labs they started running a shorter exercise with early-stage teams, and they published it in the 2025 book Click. Where a Design Sprint tests a specific solution with customers, a Foundation Sprint happens earlier: it asks who the customer is, what problem you solve, what advantages the team has, who you compete with and why you would win. The output is a Founding Hypothesis, a single sentence of the form: if we help this customer solve this problem with this approach, they will choose it over these competitors because of these differentiators.
This worksheet covers the same ground in a lighter way. The Value Proposition tab offers the classic positioning template from Geoffrey Moore's Crossing the Chasm ("For [target customer] who [statement of need], our [product] is a [product category] that [key benefit]. Unlike [primary competitive alternative]..."), which is close in spirit to a founding hypothesis. The Validation Plan tab turns the hypothesis into things you can check: the assumptions that must be true, the numbers that would prove it, and the cheapest experiment for each.
The most common failure in this kind of exercise is writing a solution into the problem statement. "Small businesses need an AI scheduling app" is a solution. "Owners of 5 to 20 person salons lose two or three bookings a week to no-shows" is a problem you can count. The tips under each box push in that direction.
Common use cases
Pre-build alignment for a new team
Two or three founders fill the tabs together in one sitting and leave with the same written problem, customer and value statement.
Preparing for customer interviews
The Key Assumptions list becomes the question plan for discovery calls, one assumption per question.
Accelerator or grant applications
Problem, customer and value proposition answers map directly onto most application forms.
Restarting a stalled project
Rewrite the four steps for the current product to see whether the original problem still holds.
Tips and limitations
- Keep the problem statement free of your product name. If you cannot describe the pain without your solution, you may not have found the pain yet.
- Write assumptions so they can be false. "Users will love it" cannot fail; "30% of trial teams invite a second member in week one" can.
- Pick experiments that take days, not months: landing pages, concierge tests, pre-sales and interviews come before building.
- The PDF and Image exports capture the summary section, which shows the problem, customer and value proposition; the Text export also lists your assumptions, metrics and experiments.
- Load Sample replaces your current answers, so export your own draft first.
Sources and further reading
- Click: How to Make What People Want, Character. Knapp and Zeratsky's 2025 book that sets out the Foundation Sprint and the Founding Hypothesis
- Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days, Character. The 2016 book on the five-day Design Sprint that a Foundation Sprint comes before
Frequently asked questions
What is a Foundation Sprint?
A Foundation Sprint is a two-day exercise by Jake Knapp and John Zeratsky, described in their 2025 book Click, that helps a founding team agree on customer, problem, advantages, competitors and approach. It ends with a one-sentence Founding Hypothesis that later experiments and Design Sprints can test.
How is a Foundation Sprint different from a Design Sprint?
A Foundation Sprint decides what to build and for whom; a Design Sprint tests one specific solution with customers. The Foundation Sprint runs about two days and produces a hypothesis. The Design Sprint runs five days and ends with a realistic prototype in front of five customers.
Does this worksheet run the full two-day Foundation Sprint?
No. It covers the core questions in four tabs (problem, customer, value proposition, validation plan) but has no timers, voting, differentiator chart or facilitator script. Use it to capture decisions, or as prep and follow-up for a facilitated session.
How do I write a good value proposition for a startup?
Name the customer, the need and the one benefit that matters, then say what you replace. The template under the box (For [customer] who [need], our [product] is a [category] that [benefit]. Unlike [alternative]...) forces those parts. Cut adjectives; keep anything a customer could check.
Where are my Foundation Sprint answers stored?
In your browser's local storage under the key foundation-sprint. They stay on this device and browser until you clear site data. Nothing is uploaded, so export a Text or PDF copy if you want to share or back it up.
How many assumptions should I list before validating an idea?
Three to six is usually enough. List the beliefs that would sink the idea if wrong, such as willingness to pay, how often the problem occurs and whether you can reach buyers, then test the riskiest one first with the cheapest experiment you can design.
Is there an in-depth guide to the Foundation Sprint Worksheet?
Yes. “Design Sprint vs Foundation Sprint: How the Two Knapp Sprints Work” covers the background, how it works, common pitfalls and worked examples. Read the full guide.
Related Tools You May Like
Free, in-browser tools that pair well with this one.