A fill-in worksheet to define the smallest version of your product that tests your riskiest assumption, separating must-haves from later features and setting a clear success metric and timeline.
A minimum viable product (MVP) is the smallest thing you can build to learn whether your core assumption is right. It is not a smaller version of your final vision with every feature squeezed in. Work through this worksheet with your team before you write a brief for designers or developers.
Fill in each line in one or two sentences.
| Question | Your answer |
|---|---|
| Who is the target user? (be specific) | |
| What problem do they have? | |
| How do they solve it today? | |
| Why is the current solution not good enough? | |
| What evidence do you have that this problem matters? (interviews, pre-orders, waiting list) |
Every startup idea rests on several assumptions. List them with the evidence you have so far, then pick the one that would kill the idea if it were wrong.
Riskiest assumption: ______________________
Your MVP should be designed to test this assumption first.
Describe the single most important journey, from the moment a user arrives to the moment they get value. Aim for five to seven steps.
Anything not needed for this journey is a candidate for "later".
Sort every feature idea into one of three columns. Be strict: if you are unsure, it goes to "later".
| Must have (journey breaks without it) | Later (useful but not essential) | Not now (nice ideas, parked) |
|---|---|---|
Questions to challenge each must-have:
Choose one primary metric that tells you whether the riskiest assumption holds, plus a target and a time frame.
| Item | Your answer |
|---|---|
| Primary metric | e.g. users who complete the core journey twice in their first two weeks |
| Target | |
| Measurement period | |
| How you will measure it | |
| Decision if target is met | |
| Decision if target is missed |
Avoid vanity metrics such as total downloads or page views that do not show real value.
A common rule of thumb is to aim for a first usable version within roughly 4–8 weeks. If your scope does not fit, cut scope rather than extending the timeline.
| Week | Milestone | Owner |
|---|---|---|
| 1 | Scope and designs agreed | |
| 2–4 | Core journey built | |
| 5 | Internal testing and fixes | |
| 6 | First users onboarded | |
| 7–8 | Measure, learn, decide next step |
Budget available: ______ Team or freelancers involved: ______
If you plan to hire a freelancer or agency through the Foundly services marketplace, attach this completed worksheet to your brief. It makes estimates more accurate and reduces scope disputes.
A practical checklist for hiring and managing freelancers and agencies, covering scope, milestones, payments, IP ownership, access and credentials hygiene, and fair reviews.
OpenA ready-to-use script for customer discovery conversations, with the questions to ask, the traps to avoid, and a note-taking template so every interview produces comparable insights.
OpenA practical slide-by-slide outline for an early-stage pitch deck, with the question every slide must answer, what to include, and common mistakes to avoid.
Open