Core features live with the rest held back
Sounds familiar? I need a first working version to put in front of real users without building everything at once.
An MVP (minimum viable product) is the smallest version of your product that real users can sign up for and use. Its cost depends on which features make the first-version list and which systems they connect to, so the proposal is written from a discovery scope. Developers then build in short cycles, and you try each build on a private test copy of the app. A prototype made with an AI coding tool is reviewed first and kept only where the base is sound. At launch you get a handover of logins, files and documentation, with accounts set up for transfer to you where each provider allows.

What you get
- Build plan that splits the first-version scope from discovery into short cycles
- A working build at the end of each cycle, reviewed with you
- Test environment (a private copy of the app) where you try each build
- The core features on the first-version list, tested before release
- Deployment to live hosting, with accounts set up for transfer to you where the provider allows
- Source code, deployment notes and handover documentation
- Written list of the features held back for later versions
Is this right for you?
- You have a discovery scope and want the first version built
- You want real users on the product before you fund the full feature list
- You are launching a SaaS product (software customers subscribe to) and need a version early customers can use
- You built a prototype with an AI coding tool and need it reviewed and finished
What it changes
A first version people can use
The core features are live for real users. Everything held back sits on a written list for the next round.
Builds you tried along the way
Each cycle ended with a review, and you tried the build in the test environment as it arrived.
A base the next round can build on
With the code, deployment notes and documentation in hand, the next features can be built by us or by another team.
Scope and delivery
How we deliver it, what we need from you, what is not included. Timeline: Estimated after an assessment
How we deliver it
-
Confirm the scope and set up
Your discovery documents go to a technical lead, who checks them against what you want today. The code repository, where the code and its history are kept, is set up next, and the features are split into cycles.
-
Build in short cycles
Each cycle ends with a working build you try in the test environment.
-
Test each feature
Every cycle includes testing of what it added. A full pass over the first version follows before launch.
-
Go live and pass it on
The first version goes live. You receive the logins, files and documentation, plus a walkthrough for whoever runs it next.
What we need from you
- A written first-version scope, or time for discovery first
- Approved designs or a clickable prototype, if you have them
- A decision-maker who tries each build and answers questions quickly
- Logins for any hosting, domain and outside services you already pay for
- Sample data and content for testing
What's not included
Complex work that is estimated only after a technical or business assessment.
Not included
- A fixed price or dates before the first-version scope is written (see Product discovery & scoping)
- Features outside the first-version scope, which go on the later list and are quoted separately
- App store fees and third-party service costs, such as hosting, email or payment fees
Where it fits
What usually follows, what may already be in place, and what is planned alongside, with the reason for each.
This service: MVP development
6 connected services
After this
What usually follows once this is done.
-
Landing pages
A page that explains what shipped and collects sign-ups.
-
Analytics & conversion tracking
Measure what users actually do.
You may already have this
Skip it if it's already in place.
-
Product discovery & scoping
The first-version scope must be written first.
Keeps it running
Keeps it working after launch.
-
App support & maintenance
Fixes and updates once real users arrive.
Bigger version
When you need more than this covers.
-
Custom web applications
When the product outgrows its first version.
Part of these packages
-
Digital product & MVP launch
Build and test: The first version, or the portal or tool, is built in stages, each ending with a review, and tested before each release.
Read before you decide
Common questions
How is an MVP different from a custom web application?
An MVP tests a new product with real users, so it carries only the features that test needs. A custom web application suits a known process and known users, such as a client portal or an internal tool, and is usually more complete at launch.
Can you finish a prototype I built with an AI coding tool?
That depends on what the review finds. A developer checks how the code is organized, how data is stored and who can see what. If the base is sound, the build continues from it. If not, you get the reasons and a plan to rebuild the parts that won't hold. Code review & app rescue covers the review on its own.
Why is there no price before discovery?
An MVP's cost depends on the features, the systems it connects to and how users sign in. Until those are written down, any fixed price is a guess. Discovery produces the scope and an estimate range, and the build proposal follows from it.
What happens after launch?
The handover at launch covers logins, files and documentation, with accounts set up for transfer to you where each provider allows. From there, a landing page can explain what shipped and collect sign-ups, and analytics shows what users actually do. App support & maintenance keeps the live product updated. A custom web application is the usual step once the product outgrows its first version.