Discovery suggests that staff need a clear unresolved-enquiry queue, but the proposed MVP includes automated calling, dispatch, billing and a mobile app. The scope has grown beyond the question the research actually supports.
For founders planning the first build, use findings to identify the smallest useful workflow and the uncertainty it should resolve. A smaller MVP can produce clearer evidence when its completion boundary is explicit.
What does evidence-based MVP scope include?
It includes an intended user, a concrete task, the constraints required to complete it and a reviewable outcome. It separates essential workflow steps from speculative features and future automation.
Research does not automatically determine technical feasibility. A valuable task may depend on integration access that needs separate inspection before implementation is estimated.
Map findings to a bounded experiment
Use a fictional missed-enquiry study to create the proposed scope table below. These are example decisions, not findings from a real client project.
| Evidence or uncertainty | Possible first-build boundary |
|---|---|
| Staff cannot identify unresolved requests | A shared queue with clear ownership |
| Follow-up is inconsistently recorded | A simple outcome update |
| Automatic calls remain untested | Keep follow-up manual initially |
| CRM access is uncertain | Run a narrow feasibility review |
| Buying authority is unclear | Continue commercial discovery separately |
The manual step should be an intentional operating choice with an owner and visible effort. Calling unfinished automation a manual pilot after failure does not create the same clarity.
Define acceptance around the user outcome
Specify what the user can do and what evidence proves the workflow works. For a queue, that may include creating a request, assigning responsibility, updating its state and reviewing unresolved work with appropriate access.
Avoid measuring success only by the number of screens built. A polished dashboard without an owned next action can leave the original problem unchanged.
The assumption ledger keeps solution beliefs visible. The research export guide helps carry source context into the engineering brief.
Keep deferred scope connected to later decisions
Record why each feature was deferred and what evidence would justify adding it. This prevents a backlog from becoming an unexamined promise to build every suggestion eventually.
My StackFlight case study describes an independently built research product. It does not claim that discovery eliminates product risk or guarantees demand for the next MVP.
Use the external technical brief when commissioning a feasibility or implementation review. Keep customer evidence, technical findings and commercial assumptions distinct so the next milestone answers the right question.
Does smaller scope mean an incomplete customer workflow?
Aim for one complete useful path, with manual steps and limitations explicitly owned rather than hidden.
Should every requested feature enter the MVP?
Prioritise the evidence and uncertainty relevant to the first decision instead of treating suggestions as automatic commitments.
What should we commission first?
Define the user outcome, acceptance evidence and unresolved dependencies in the product engineering discussion.