# MVP development

> An MVP is the smallest product that tests the assumption most likely to sink the idea. We build it fast, put it in front of real users and help you read what they do.

Every new product rests on a few assumptions: that people have the problem, that they will try your answer, that they will pay for it. One of them is usually the riskiest, and an MVP exists to test it before you spend on everything else. We work out with you which assumption that is, then build the smallest product that gives a clear answer. Sometimes that is an app, sometimes a single page with a waiting list. Where the idea is still unclear, a discovery phase comes first. After release, real use decides what gets built next.

Bitmason: https://bitmason.dev/en/services/mvp/

## What you get

- **The riskiest assumption, named**: A short statement of what must be true for the idea to work, and which part the MVP will test first.
- **A product real people can use**: A working first version, released to real users rather than shown in a meeting.
- **A deliberately small scope**: Only the features the test needs. Everything else waits until the answer is in.
- **Measurement built in**: The events and questions that show whether the assumption held, set up before release.
- **A decision you can defend**: A read of the results with you: build on it, change course, or stop before the cost grows.

## How it works

1. **Find the riskiest bet**: We list the assumptions behind the idea with you and pick the one that most needs proof.
2. **Design the test**: We decide the smallest product that can answer the question, and what result would count as a yes.
3. **Build and release**: We build it quickly, keep the scope tight and put it in front of real users.
4. **Learn and decide**: We read what users did with you and plan the next release, the change of course, or the stop.

[Scope your MVP](https://bitmason.dev/en/contact/?service=mvp)