FREE MVP SCOPE PLANNER
Draw the line
before you build.
Turn an early product idea into one user, one job, one critical journey, and one testable release boundary.
Build a practical MVP brief around what is in, what stays out, and what must be tested before the release expands. The free planner creates a local result you can copy, download, or print without submitting your answers.
01 / DRAW THE BOUNDARY
Define one credible release.
Use short, non-sensitive descriptions. Your answers stay in this browser unless you choose to copy, download, print, or share the finished brief.
02 / METHOD
Test the uncertain part first.
The planner adapts two problem-first ideas from the GOV.UK Service Manual. Its discovery guidance says teams should understand users, the problem, constraints, and success measures before committing to a build. Its alpha guidance recommends prototypes that are only complex enough to test the riskiest assumptions.
Blancc applies those ideas to commercial product planning by separating a first useful journey from later scope, then pairing the boundary with one primary risk and an observable evidence signal. The wider Service Standard also keeps accessibility, the complete user problem, appropriate technology, measurement, reliability, and ongoing operation visible.
GOV.UK guidance is written for public services. This planner is an independent adaptation for early product conversations; GOV.UK does not endorse the tool, and the government phases or timescales are not presented as a universal commercial delivery model.
03 / LIMITS
A boundary is not validation.
The generated brief is a planning aid, not a specification, quotation, schedule, delivery promise, demand forecast, market validation, technical assessment, or proof that a product should be built. A responsible project still needs evidence from representative users and review by the people accountable for accessibility, privacy, security, data, operations, commercial viability, and relevant regulation.
The result reflects only the descriptions and options entered. It cannot inspect existing systems, resolve competing stakeholder priorities, establish a baseline, test an assumption, or judge whether the selected evidence is sufficient. Treat every output as a conversation draft with explicit unknowns.
04 / QUESTIONS
Before you use the brief.
What belongs in a first MVP release?
A useful first release gives one defined user a complete way to perform one important job. It also includes the dependencies, controls, failure states, measurement, accessibility, and support needed to test that journey responsibly. Everything else needs an explicit reason to enter the boundary.
Is this an MVP cost or timeline calculator?
No. Cost and timing depend on validated scope, delivery responsibilities, technical discovery, data, integrations, assurance, release obligations, and team availability. The planner makes those unknowns easier to discuss; it does not turn them into an invented estimate.
Does the generated brief validate product demand?
No. The brief records a proposed boundary and an evidence signal. Product demand requires appropriate research and observed behaviour from representative people. The result is not proof of desirability, usability, feasibility, viability, safety, or regulatory acceptability.
Does Blancc receive the text I enter?
The form does not submit your answers. The planner builds the result locally in your browser, and opening the contact page does not attach it. Copied, downloaded, or printed briefs contain your text, so do not enter confidential, personal, or sensitive information.