An MVP first, or the full build?
An MVP tests one assumption with the people you invite; the full build serves a need you already know.
| An MVP | The full build | |
|---|---|---|
| What it starts from | One assumption you have not tested yet. | A need you already know, such as a process you run every day. |
| What gets built | Only what the test needs, with its database and thorough testing. | All the software your process needs, in one build. |
| Who uses it | Only the people you invite, behind a login. | Everyone it is made for, once it is live. |
| The risk it removes | Building everything for an idea that does not hold. | Running a process you know on tools that do not fit it. |
| How the price is set | A fixed price in a written offer, for the first version. | A fixed price in a written offer, for the whole scope. |
| Before people use it | We test it thoroughly before your users get access. | It runs in a test version you can try, and goes live only when everything works. |
| What you have at the end | Working software behind a login, and a clear result: pivot, persevere or stop. | Software in daily use; once it is live, we check it every hour, as a service you book with us. |
| What comes next | If the answer is yes, the full product, built as custom web software. | Changes as your business needs them, each priced before it is built. |
The differences that matter.
One assumption, or a known need.
An MVP is for an idea you have not tested yet. Before any design or code, its riskiest assumption is written down, with one metric and a threshold. The full build is for a need you already know, such as a process no standard tool covers.
What the first version leaves out.
An MVP keeps only what the test needs, and the rest waits. It never leaves out the database or thorough testing: minimum scope, never minimum quality.
What happens after launch.
An MVP stays private behind a login, and it ends with a clear result: pivot, persevere or stop. The full build goes live, and once it is live, we check it every hour, as a service you book with us.
What each option covers.
An MVP
Working software with a database, kept private behind a login and used only by the people you invite. It tests one assumption against one metric and its threshold. If the answer is yes, the full product is built as custom web software.
The full build
Custom web software made for the way your business works, built in one project. It first runs in a test version that you can try, and it goes live only when everything works.
Which fits your situation?
Start with an MVP when an idea has to prove itself; start with the full build when you already know what your business needs.
See custom web software
Frequently asked questions.
Can the MVP grow into the full product?
The MVP gives you the answer; the full product comes after it. If the result says persevere, it is built as custom web software, shaped by what the people you invited showed you.
What if the result says stop?
Then you have your answer from a first version, before building everything. That is what an MVP is for: a clear result, measured against the threshold you set.
What does each cost?
It depends on what your software has to do. Once that is written down, you get a fixed price in a written offer, and nothing is built until you agree to it. Any change beyond the agreed scope is priced before it is built.
Tell us about your project. Send us a message and we will get back to you.