An MVP is the smallest credible product that can answer an important business question. It is not every planned feature in rough form. The question may concern demand, activation, workflow, willingness to pay, retention, or technical feasibility; scope follows that question.
What actually matters
Write the decision that evidence will inform before choosing features. Build one complete path to the intended outcome, recruit representative users, and define success and failure thresholds in advance.
Factors to evaluate
Riskiest assumption
Identify what could invalidate the product or operating model.
Credible journey
Deliver one useful end-to-end outcome, including necessary trust and support states.
Evidence
Combine behavior, interviews, support signals, and commercial response.
Next decision
Expand, change, pause, or stop according to evidence rather than sunk cost.
A practical next step
Write down the current workflow, people involved, records exchanged, exceptions, and the decision that a better system should improve. That evidence gives a development team enough context to challenge assumptions and define a credible first release. Learn more aboutMVP development.
Avoid a false shortcut
A launch without instrumentation and a learning plan is only a small release. Avoid vanity metrics; observe completion, time, abandonment, repeated use, objections, and what users do without assistance.
Frequently asked questions
Should MVP code be production quality?
Critical security, data integrity, and operability should be credible. Scope can be reduced; essential quality should not be faked.
Turn the question into a clear project decision
Share the workflow, constraints, and outcome you need. We can help define a responsible technical path without inventing scope or promising certainty before discovery.