MVP development
The smallest working version of an idea, built to test it.
What this is for
Deciding whether the whole thing is worth building at all. An MVP is not a cheaper version of the finished product — it is an experiment with one question in it, built far enough to answer that question with real users rather than opinions. Anything that does not affect the answer is deliberately left out, including things that will obviously be needed later. The outcome is a decision, and a decision not to continue is a successful one.
What it covers
- Scope cut to the core
One assumption is chosen as the thing being tested, and every proposed feature is measured against whether it helps test that.
- Cut to what proves it
Features that would make the product complete but do not change the answer are written down and postponed, so they are not argued about twice.
- Real users on it
Put in front of people who would plausibly pay for it, rather than colleagues and friends, who will be kind about it.
- A path to version two
What was built to last and what was built to be discarded is recorded, so a second version starts from a known position rather than an archaeology exercise.
What you end up with
- The smallest version that proves the idea
Working software rather than a prototype — people can use it for the thing it claims to do.
- Real users on it
In front of people outside the business, with what they actually did recorded alongside what they said about it.
- What it showed, written down
The result stated plainly, including the places where the evidence is thin.
- A route to version two, or a reason not to
Either the next build, scoped from what was learned, or a clear account of why continuing would not be worth it.
What we need from you
- The one assumption you are testing
Written as something that could turn out to be false. An assumption that cannot fail is not being tested by anything.
- Access to people who would actually use it
Introductions to real prospective users are the one input we cannot supply on your behalf.
- What result would stop you
Agreed before the build starts, because it is considerably harder to agree once money has been spent.
How a project runs
Fixed scope first, a design you approve before any code, and everything in your name.
We work out what you need, what it has to do, and what it will cost.
- Scope written down
- Fixed quote
- Agreed timeline
Get in touch
Every one of these reaches us directly, and is answered by a person.
A new project, a quote, or a question about one that is running.
- Reaches us at
- +355 69 752 2209
- Carries
- Messages