Minimum viable product (MVP)
A minimum viable product (MVP) is the first, deliberately lean version of a piece of software that contains just enough features for real users to use it and give feedback.
Instead of working for months on a complete solution, an MVP goes into use early. This quickly shows which features are really needed — and which can be skipped.
An MVP is not a half-finished product: what it contains must work reliably. The difference lies in scope, not in quality.
Circle Lab develops custom software in stages: first a lean initial release, then expansion in clear steps based on real usage.
What to look out for
- Determine the one process that solves the biggest problem — and leave everything else out at first.
- Set measurable goals: how do we know the MVP works?
- Start with real users and collect feedback systematically.
- Choose a technical basis that can grow — lean does not mean disposable.
- Reprioritise after every stage instead of clinging to a rigid plan.
Common mistakes
- The MVP keeps growing until it is no longer an MVP and never goes live.
- Lean is confused with sloppy: bugs and security gaps “for later”.
- User feedback is collected but never evaluated.
Frequently asked questions
It depends on the core process it needs to cover. The goal is to start with real users as early as possible — we set the timeframe after the concept workshop.
Based on real usage, the software is expanded in clear stages: new features, interfaces and improvements where they deliver the most value.