The first version of your product, in real hands.
Test your product idea with an MVP: a working first release focused on one core user problem. We help you choose essential features, agree the scope and build a version people can actually use. Bring your target audience, budget and launch goals; we will help define what to build first.
- A free 5-day audit comes first
- We sign an NDA before we see anything
- A fixed price before you commit
- You own all the code
MVP release
Example
Release 1: the first users
- Built sign-up and the one job the product is for
- Tested with 5 people from your waiting list
- All 5 finished the job without asking for help
Open it to the rest of your waiting list?
An example with made-up figures. The buttons send nothing.
How MVP development works.
We cut it to one job
Together we pick the one job your first users need done, and the smallest version that does it well. Everything else waits for a later release.
Real users try it
The first version goes to a small group of real users, often from your own waiting list. What they do with it decides what gets built next.
It grows instead of being thrown away
The base is built to carry the full product, in widely used tools any team can take over. The second and third releases add to it rather than start again.
MVPs we build.
Start from where you are today. Each tab names the problem you have now and what we build to fix it.
- Today
A deck, a waiting list and nothing to show
What we buildA product your first users can sign up to
We turn the deck into the one job the product does, then build that with sign-up from the start. Your waiting list gets a real product to try, and you learn what they will pay for before you spend on the rest.
Real usersinstead of a slide deck
Start a project - Today
A new line of business you want to test before committing
What we buildA small product to test the market, not a new division
An established company wants to know whether a new service sells before it hires for it. We build the smallest version that lets real customers buy or book, kept apart from your main systems until it proves itself.
Provenwith customers before you hire for it
Start a project - Today
A first attempt that never reached users
What we buildRebuilt on what the first attempt taught you
The last build ran out of money or time before anyone used it. We take what it taught you, cut the scope to what users must have, and ship a version you can put in front of them, on a base that will not need a third attempt.
Shippedthis time, to real users
Start a project - Today
An internal tool other companies keep asking about
What we buildYour own tool, packaged for its first outside users
We take the tool your team relies on and add what the first outside user needs: sign-up, a space of their own for their data and a way to pay. A few friendly companies try it before you decide whether it becomes a product.
Separatedata for each outside company
Start a project
How you stay in control.
Handing your first version to an outside team should come with clear terms. Ours are these four, written into every MVP we build.
Your users see only what you approved
Every change is tried on a test copy first. It reaches your users when the person you name says yes, and not before.
- You approve every release
- A release can go to a few users first
- Any release can be rolled back
Your product, in your own accounts
The MVP runs in your own cloud account and its code lives in your own repository, under your name, from the first day. An NDA is signed before we see anything.
- Runs in your own cloud account from day one
- NDA before anything, plus MSA and DPA
- Code in your own repository under your name
Built to grow, not to be thrown away
The MVP is written in widely used tools on a base that carries the full product. Payments, email and sign-in come from services you already know, and a mobile app can be added on the same back end later.
- Connects to payments, email and sign-in you already use
- A mobile app can be added on the same back end
- Documented for the next developer, yours or ours
You see progress, spend and usage
Each week you see what we finished and what we spent against the fixed price. After launch you also see how users move through the product, so the next release comes from what they really do.
- Progress against the plan, every week
- Spend shown against the fixed price
- Usage figures to decide what comes next
MVP project timeline.
You can stop after any stage. By week three you are already showing a clickable version to the people you want as first users.
01 · Week 1
Audit
We agree on who the first users are, the job they need done and the smallest version that proves it.
You end withA plan and a fixed price.
02 · Weeks 2 to 3
Prototype
A clickable version of the main screens. You put it in front of a few target users before any real building starts, while changing the plan still costs nothing.
You end withScreens your first users have seen.
03 · Weeks 4 to 8
Build
We build the first version with a working demo every week: sign-up, the one job it is for and the admin view you need to run it.
You end withAn MVP ready for real users.
04 · Weeks 9 to 10
Launch
A first group of users starts using it. We fix what they find and track what they use.
You end withReal usage, and a plan for the next release.
Once the MVP has found its users, the product stage begins: an account for each customer company, billing, permissions and audit logs. That is our SaaS development service, and it continues from the same code.
Start with a free first step.
Bring the deck, the idea or the first attempt. On day five you know who the first users are, the smallest version worth building for them and what that costs.
What you hold when it ends
Free, 5 days
- Who the first users are, and the job the MVP does for them
- The smallest first version worth putting in front of them
- A fixed price and a timeline for it
Take the plan to your investors or to another team. It is yours either way.
What our clients say.
From clients in the US, Portugal, New Zealand and the UK.
MVP development questions.
What it costs, how long it takes, MVP against SaaS, and whether you will have to throw it away.
How do we choose which features belong in the MVP?
Choose one target user and the main problem the product must solve. Include the features needed to complete that journey and learn from real usage. Defer secondary workflows until there is evidence they matter, and agree how feedback will inform the next release.
How much does MVP development cost?
The price moves with what the first version must do, whether users pay inside it, and the tools it connects to. That is why we keep it small. The free 5-day audit fixes the price, and you decide whether to go ahead once you have seen it.
How long does an MVP take?
Our stages add up to about ten weeks: a week of audit, two weeks of clickable prototype, about five weeks of build with a demo every week, and two weeks with the first users. A bigger first version takes longer, and the audit gives you the real timeline before you commit. You can stop after any stage.
MVP or SaaS development, which page is for me?
This page, if you have no product yet and need a first version in front of real users to learn from. Our SaaS development page, at /saas-development/, is for the stage after that: a product with users that now needs accounts for each customer company, billing, permissions and the audit logs enterprise buyers ask for. One continues from the other, on the same code.
Will we have to throw the MVP away later?
No. It is built in widely used tools, in your own accounts, on a base the full product grows from. What does get thrown away is the features your users turned out not to want, and finding that out cheaply is the point of an MVP.
Can you build an MVP for an established company, not only a startup?
Yes. A company testing a new line of business needs the same thing a founder does: the smallest version real customers can use, before anyone is hired for it. We keep it apart from your main systems until it proves itself, then connect it to them.
Who owns the MVP and its code?
You do, from the first day: the source code in your own code repository, the running product and its data in your cloud account, and the documentation. Should we part ways, it all stays with you and you owe nothing extra.
From the blog.
Plain-language notes from our engineers on this kind of work, written for the owner who signs the check.
Free project estimate
Start your MVP project.
Pitch it to a founder in 30 minutes. You leave knowing what the first version should include, roughly what it would cost and when the first users could try it. If an MVP is the wrong first step, we say so.
What you get back
- An indicative budget range
- A realistic timeline
- What moves the cost up or down
- A reply within 4 business hours
- Answered by a founder
- NDA on request, before you share details
Tell us what you need
A few lines is plenty. You get a number before any call.