Scoping guide
How to scope a software MVP
6 min read·Published by ODOOVATIONS, October 2026
An MVP is the smallest product that lets real users complete the job you are betting on. Scope it as a short list of complete user journeys, each with its users, states, data and acceptance test, and an explicit list of what is not in this phase. Price follows the journeys, not the screens.
A worked example (synthetic)
A fictional company wants an app where traders upload a price list and their customers place orders from it.
| Journey | User | Accepted when |
|---|---|---|
| Upload a price list | Trader | A spreadsheet becomes a product list; errors are shown per row |
| Place an order | Customer | Order confirmed, trader notified, totals correct |
| See orders | Trader | List with status; nobody else sees them |
For every journey, write down
- Who does it, and what they may see.
- Empty, loading, error and success states.
- The data it creates or changes.
- Any outside system it touches.
- The test that proves it works.
Out of this phase
- Payments, unless a journey needs them.
- Native mobile apps, if a web app will do.
- Admin dashboards beyond what the journeys need.
Related services
Questions
Our MVP builds start at USD 3,500 for one end-to-end journey, USD 7,500 for three and USD 15,000 for six, confirmed after scoping.
Ready to talk through your project?
Send a voice note, spreadsheet or a plain description of where your business is struggling. We’ll help you find the right next step.

