How to build an MVP in 6 steps: prototype, Discovery, design, build, launch, iterate. Timeline, team, what to include and UK costs from £10,000.
Short answer. Build an MVP in six steps: a working prototype of the core flow (5–10 working days), a Discovery sprint that fixes scope and price (2 weeks), design for the MVP scope only (1–2 weeks), build in weekly sprints (4–6 weeks), QA and launch (1 week), then measure and iterate. That is roughly two to three months from first call to live users. In the UK an MVP built by an agency like Magora starts from £10,000, and most cost £10,000–£25,000.
This guide is for founders and product owners about to build a first version. It covers each step, what to include and leave out, the team, the technology choices, how to measure the result and the mistakes that cost the most.
Last checked: 2 November 2026.
The six steps
| Step | Time | What happens | Output |
|---|---|---|---|
| 1. Prototype | 5–10 working days | Your brief becomes a clickable core flow, so the first conversation is about something you can click | A prototype to test with users |
| 2. Discovery | 2 weeks | User roles, the one metric the MVP must move, a prioritised feature list and a costed architecture | A fixed-price quote |
| 3. UX and design | 1–2 weeks | Wireframes and UI for the MVP scope only, tested with a handful of target users | User flows and a UI kit |
| 4. Build | 4–6 weeks | Weekly sprints with a demo every week; authentication, payments, admin and analytics first | Working software in your repository |
| 5. QA and launch | 1 week | Automated and manual testing, store submission or web release, monitoring switched on | A live product |
| 6. Measure and iterate | After launch | Read the analytics, fix what blocks activation, plan the next release from real usage | A roadmap based on data |
The process we use on our MVP development projects.
What to include, and what to leave out
An MVP answers one question: will people use and pay for this? Argue every feature against that question.
| Usually in the MVP | Usually later |
|---|---|
| Sign-up and login | Social features and referrals |
| The one core workflow the idea depends on | Secondary workflows and edge cases |
| Payments, if the business model needs them | Several pricing plans and coupons |
| A simple admin panel for your team | Self-service reporting and dashboards |
| Analytics on activation, retention and conversion | Personalisation and recommendations |
| One platform, unless both are essential | iOS, Android and web all at once |
Founders almost always ask for more than the first version needs. Every extra feature delays the moment you learn whether the idea works.
The team you need
| Role | What they do | Share of effort in our estimates |
|---|---|---|
| Product owner | Owns scope and priorities, writes acceptance criteria, keeps the MVP small | 20% of development time |
| Designer | User flows and UI for the MVP scope, tested with users | Mostly in weeks 1–2 |
| Developers | Backend, web or mobile, and the infrastructure | The estimate itself, in developer-days |
| QA | Manual and automated testing, regression, launch support | 30% of development time |
That works out at about £520–£570 per developer-day including QA and product ownership. Source: software development cost UK 2026.
Hiring this team in-house for a first release is slow and expensive. The alternatives are an agency, freelancers or a fractional CTO; we compare them in fractional CTO vs agency vs freelancer and vibe coding vs freelancer vs agency.
Technology choices
- Choose mainstream technology your next hires already know: React or Next.js on the web, React Native or Flutter for mobile, Laravel, Node.js or Python on the backend, PostgreSQL for data.
- Cross-platform for mobile unless the product needs native features: one codebase, both stores.
- Production-grade from day one: real authentication, a proper database, CI/CD and hosting you own, so the MVP does not need a rewrite when it works.
- No-code when it fits. Internal tools and simple products can be tested faster with no-code. It gets expensive with custom logic and integrations; see our low-code MVP guide.
- AI features with evaluation and cost limits from the first release. See AI development cost in the UK.
We help founders scope, build and launch an MVP real users can try, starting with a free working prototype in 5–10 days. First release in 6–8 weeks.
How to measure the MVP
Decide before launch what success looks like, and ship the tracking with the first release:
- Activation: how many sign-ups complete the core action.
- Retention: how many come back in week two and week four.
- Conversion: how many pay, or take the step that predicts paying.
- Qualitative signal: short interviews with users who stayed and users who left.
What it costs to build an MVP in the UK
| Stage | Typical time | Magora band (GBP) |
|---|---|---|
| Free working prototype | 5–10 working days | £0 |
| Discovery: scope, architecture, fixed-price quote | 2 weeks | From £3,000 |
| First release (MVP) | 6–8 weeks | From £10,000 |
| Full production system | 3–6 months | £25,000–£60,000 |
| Regulated or integration-heavy system | 5–8 months | £80,000–£120,000 |
| Support after launch | Monthly | From £1,000 a month |
Rates behind the bands: from £49 an hour per developer, and £65–£70 an hour for a full team with QA and product ownership. Source: Magora UK software development pricing, 2 November 2026. Figures exclude VAT.
In the 12 project estimates we wrote for UK clients in 2026, first releases cost £11,000–£34,000, with a median of about £25,000, and took 6–8 weeks. What moves the price: user roles, integrations such as payments and banking, the number of platforms at launch and any compliance work. More in how much an MVP costs in the UK, or price your feature list in the app cost calculator.
Mistakes that cost the most
- Skipping the prototype. Testing with a clickable flow is free; changing built software is not.
- A fixed price on a vague brief. Without Discovery, either the price is padded or the budget runs out.
- Building for every platform at once. Start where your users are.
- No analytics at launch. Without data, the next release is guesswork.
- Not owning the code. Make sure the code is in your repository and the IP transfers to you.
Ready to build? Send us your idea: we will build a free working prototype of the core flow in 5–10 working days, then a two-week Discovery turns it into a fixed-price quote. More about our MVP development.
Frequently asked questions
How long does it take to build an MVP?
Typically 6–8 weeks of build after a two-week Discovery, or roughly two to three months from first call to live users. Products with regulated data, several user roles or heavy integrations take longer.
How much does it cost to build an MVP in the UK?
At Magora an MVP starts from £10,000 and most cost £10,000–£25,000. In the 12 project estimates we wrote for UK clients in 2026, first releases cost £11,000–£34,000 with a median of about £25,000.
What should an MVP include?
Usually sign-up and login, the one core workflow the idea depends on, payments if the business model needs them, a simple admin panel, and analytics to measure whether the idea works. Everything else waits.
Who do I need on the team to build an MVP?
A product owner, a designer, developers for the platforms you need, and QA. In our estimates QA is sized at 30% and product ownership at 20% of development time.
Should I build my MVP with no-code?
Sometimes. No-code is a good fit for internal tools and simple products where you need to test demand quickly. It becomes expensive when you need custom logic, integrations, performance or ownership of the code.
Can a non-technical founder build an MVP?
Yes, with a partner that turns the idea into a written scope, explains decisions in plain English and shows working software every sprint. Most of our MVP clients are non-technical founders.