What an MVP is, and what it is not
MVP stands for minimum viable product: the smallest version of your product that does a real job for real users. Not a slide deck and not a mock-up that only looks like software, but a product someone works with, pays for or comes back to. You find out whether that happens before your whole budget is spent.
We decide with you what goes into the first version, build it on a foundation that can grow, and after launch keep building or hand it over to your team.
Two products we built from scratch
We know the road from idea to first version from our own work:
- CaterFlow replaces spreadsheets and copy-pasted emails in festival catering. The organizer creates an event, the platform finds the matching food trucks, and each truck submits its offer through a personal link, without an account. The idea came from a client project with a food truck caterer.
- Ventus Invest replaces the spreadsheet business plan: pick an industry template, adjust the assumptions, send the plan as a PDF to a partner or a bank. Every business type runs on the same calculation core, covered by more than 600 automated tests.
What goes into the first version
An MVP contains the one workflow your users come for, from start to finish. For CaterFlow that is four steps: create the event, send it, compare offers, select a truck. Everything else waits until real users ask for it.
- In: the core workflow end to end, the data it needs, and everything a user needs on day one
- Later: roles and permissions for special cases, reports, extra settings, more languages, a separate app next to the web version
- Simpler: a personal link instead of a user account, an off-the-shelf service instead of custom code, an email instead of a built-in messaging system
Cutting the scope together
Most ideas arrive with a long list of features. We go through them with you one at a time and ask of each: does launch fail without it? If not, it goes on the list for later. You end up with a scope that fits your budget and a clear order for what comes next.
You can make the first cut yourself. The Project Wizard asks about your idea, suggests features and gives a rough budget and timeline. Our software development costs page explains what software costs and what drives the price. After that you talk directly to the developers who build your MVP.
Small in scope, solid underneath
What is small in an MVP is the scope, not the quality underneath. The data model (how your data is structured), automated tests and a delivery process that puts every change online without manual steps are there from day one. After the first success you keep building instead of starting over.
And it is yours. Code, cloud accounts and servers are in your name from the start. You can continue with another team at any time.
After launch
Launch is where the real work begins. Real users now show what is missing and what nobody needs. We keep building in the order their usage shows: from MVP to a subscription product, a platform or a tool for the whole team. Or we hand code and documentation over to your own team.
Frequently asked questions
What goes into an MVP and what stays out?
The one workflow your users come for, from start to finish. Whatever launch does not need waits: special cases, reports, more languages, an extra app. We write that list with you.
How much does MVP development cost?
It depends on the core workflow and the systems it connects to. The Project Wizard gives you a rough range in a few minutes. After that you see every part with its price before you commit.
Will the MVP have to be rewritten after the first success?
No. The data model, tests and automated delivery are there from the start, so the first version keeps growing. Only what real use proves wrong gets rebuilt.
What do we own at the end of the project?
Everything. Source code, domain, cloud accounts and servers are in your name. You keep developing the product with us or with another team.
Do we need a finished concept to start an MVP?
No. An idea and a picture of who will use it are enough to start. We work out the rest with you: the Project Wizard covers the key points, and in conversation we cut the scope from there.