MVP and prototype development
Learn first, then scale
The most expensive software is the software nobody needs. An MVP – a minimum viable product – is the smallest version of your product with which real users solve a real problem. It answers the questions no concept paper can: Do customers use the product? Will they pay for it? Which feature really matters, and which one did nobody miss?
We help you choose the right stage and stay focused – even if that means deliberately leaving features out. At the same time, we build an MVP so that it can be developed further. If you have to rewrite everything after the market test, you lose exactly the head start the MVP was meant to give you.
Prototype, proof of concept or MVP?
Clickable prototype. A realistic design of the interface that you can click through on screen or on your smartphone – ideal for testing processes with future users, convincing investors or sharpening requirements. Find out more under Prototyping and design systems.
Proof of concept. A technical feasibility check for the riskiest part of your idea: Can the device be controlled, can the legacy system be connected, does the AI model deliver usable results?
MVP for pilot customers. A lean, working version with the core features that real users rely on in their daily work – including sign-in, data storage and operation.
Market-ready product. Expansion based on what you learned in the pilot phase: subscription model and payment, roles and permissions, multilingual support and operations that grow with your user numbers.
We know both sides
We do not only develop for clients, but also build our own products. We built Inventary, a digital guest guide for holiday rentals, ourselves – from the product idea and subscription model to day-to-day operation. In doing so, we face the same questions as our clients: What has to go into the first version, what can wait, and what does operation cost each month?
This experience feeds into your project. We ask about your business model and target group, not just about features, and suggest what can be tested with little effort. Technically, we rely on proven tools such as Ruby on Rails, which let you achieve a lot in a short time – and which still hold up after the market test.
From our projects: from idea to platform
In 2015, there was no ready-made way to bring photos live from a professional camera to the guests at an event. Together with PicturePartners, we developed the first version of the platform from scratch – back then with a custom camera box based on embedded Linux. Over more than ten years, this idea has grown into the platform on which the ClicClic brand is built today. The same team is still developing it. Find out more in the ClicClic case study.
How much does an MVP cost?
Based on our cost model, a clickable prototype costs about €7,000–13,000, an MVP for first pilot customers €27,000–50,000 and a market-ready product €70,000–125,000 – all net, including project management and quality assurance.
What determines the price is explained in our guide How much does custom software cost?. For an estimate for your idea, the project cost calculator takes just a few minutes.
How we get your idea off the ground
- Free initial consultation: clarifying the idea, target group and key assumptions
- Defining the scope of the first version – as small as possible
- Prototype or MVP in short iterations with regular progress reviews
- Evaluating the pilot phase and planning the next expansion
- Free initial consultation: clarifying the idea, target group and key assumptions
- Defining the scope of the first version – as small as possible
- Prototype or MVP in short iterations with regular progress reviews
- Evaluating the pilot phase and planning the next expansion
Frequently asked questions about MVPs and prototypes
What is the difference between an MVP and a prototype?
A prototype shows how a product should look and be used – it looks real, but usually does not store any data. An MVP, by contrast, is working software that real users use in their daily work. The prototype tests usability and processes; the MVP tests whether the product is actually used and paid for.
How long does it take to develop an MVP?
A clickable prototype usually takes a few weeks. For an MVP that pilot customers use in their daily work, you should expect a few months, depending on the scope. The biggest lever is in your hands: the more strictly the feature set is limited to the essentials, the sooner you get feedback from the market.
Can the MVP later be expanded into the finished product?
Yes, that is exactly what we build it for. We develop an MVP with the same technology and care as the later product, just with fewer features. Clickable prototypes and often proofs of concept are different: they are meant for learning quickly and are usually not reused.
Do I need a complete requirements specification for an MVP?
No. To get started, a clear description of the problem, the target group and the key assumptions you want to test is enough. We work out the scope of the first version together with you. A specification covering every eventuality would even be a hindrance for an MVP, because many assumptions are only confirmed or disproved in the market test.
App or web app – which is better for an MVP?
For many MVPs, a web application is the faster and more affordable route: it runs on every device and can be updated at any time without a store review. A native app pays off when the camera, offline use or other device features are at the core of the idea.
Didn't find your question?Get in touch
Let us work out together how you can test it on the market with little effort.