How much does an MVP cost in the UK?

What published UK prices actually tell you#

A founder searching for an MVP price needs two things: a plausible starting reference and a way to understand why their proposal differs. The table below supplies the first. The model further down supplies the second. Neither substitutes for a written brief and a supplier’s response.

This is a deliberately small sample of visible offers, not a survey of the UK market. We did not purchase the services, inspect delivered projects or collect comparable quotations. Wall & Fifth publishes MVP Build and is therefore an affiliated supplier. Check tax, support, integrations and contractual scope before comparing totals. We have not inferred a market median from these prices.

Define the product you are pricing#

A clickable prototype, a concierge service and a production application answer different questions. A prototype tests understanding and interaction. A concierge service lets a person perform parts of the operation while customers experience the outcome. A production application must operate with real accounts, data, failure cases and ongoing ownership.

For example, “a booking platform” might mean a request form handled by staff, or live availability with payments, cancellations, refunds and several providers. The noun is the same; the work is not. Write the first journey and what happens when it fails before asking anyone to price it. The MVP scope guide provides a practical boundary.

Build the number from work and assumptions#

Use a work breakdown that makes omissions visible. Ask for estimated effort or a fixed deliverable price for discovery, design, engineering, integration, testing, release and handover. If a blended day rate is used, clarify which roles it includes. If the supplier sells a fixed result, ask for milestone scope and assumptions rather than treating an internal effort estimate as an entitlement to extra features.

An illustrative 15% reserve adds £4,500, producing £34,500 before tax and external costs. If running costs were £400 per month, the first 12 months would add £4,800. The combined planning envelope would be £39,300. Those assumptions are adjustable in the calculator; they are not recommendations for your project.

All worksheet inputs are illustrative assumptions chosen to show the arithmetic. They are not market rates, measured project averages or a quotation. Replace them with your team’s estimate. A team-day is one person’s working day: 40 team-days does not automatically mean eight elapsed weeks.

The decisions that move the quote#

• Users and permissions: an internal tool for one team differs from a product where each customer must see only their own information.
• Money movement: subscriptions, refunds, seller payouts and reconciliation need different flows.
• Integrations: access restrictions, incomplete documentation and inconsistent records can matter more than the number of APIs.
• Platforms: a responsive web journey differs from two app-store releases with device testing.
• Operations: support, moderation, recovery and administration still need a responsible person when the interface is small.
• Migration: cleaning, mapping and reconciling existing records can be a separate workstream.

Ask for a lower and upper effort estimate for uncertain items, plus a small investigation that could narrow the range. “CRM integration: unknown until sample data and API access arrive” is more useful than hiding the uncertainty inside a confident single number.

Compare two proposals without being misled#

Imagine an illustrative £24,000 proposal that excludes discovery, administration and deployment, next to a £32,000 proposal that includes them. The lower price is meaningful only after you identify who will do the excluded work and what that costs. Compare the same acceptance criteria, release responsibilities and support period.

• Send the same software development brief to each team.
• Mark each required outcome included, excluded or unresolved.
• Ask who will deliver and review the work, and when they are available.
• Confirm access to accounts, repositories, design files and documentation.
• Write down what triggers a change request and who approves it.

A fixed fee can make the commercial boundary clear, but it cannot make an undefined outcome precise. For work likely to change, compare the controls in our fixed fee, time and materials and retainer guide.

Make the budget smaller without making the release incomplete#

Reduce the first audience, geography or platform. Replace an infrequent back-office workflow with a documented manual process. Use an existing payment or identity service where it fits. Defer sophisticated reporting until you know which decisions it needs to support.

Keep the core result intact. A customer should not lose a payment because a notification failed, and an administrator should have a way to resolve a stuck record. If even a narrow dependable release is unaffordable, test the offer manually first. That can reveal whether a software build deserves the investment.

Ask each supplier to separate one-off delivery, external charges and ongoing operations. Request the currency, tax treatment, payment schedule, support period and exclusions in writing. A contingency is a reserve against named uncertainty; it is not an extra feature budget. Keep acquisition spend separate so you can see whether the product is affordable to build and affordable to operate.

Budget for the first operating year#

List infrastructure, email, paid APIs, monitoring, support and maintenance. Attach a usage assumption to each variable fee: active customers, stored files, transactions or AI requests. Ask what happens at expected usage and a higher scenario, and name the person who checks the bills.

Also distinguish a defect warranty from ongoing development. A supplier may fix an agreed feature that fails without including new features, third-party changes or unlimited incident response. Read the actual terms. Your budget is ready for a buying decision when delivery scope, remaining uncertainty and the operating plan are all visible.

Build your own budget#

Adjust the assumptions to see the arithmetic. These starting values reproduce the illustrative model above; they are not a quotation. The reserve applies to delivery effort, before external one-off costs. All amounts exclude tax.

Put this guide to work#

Frequently asked questions#

Sources and methodology#

This guide combines editorial analysis with the linked primary sources. Decision frameworks, worksheets and worked examples are our own; examples are illustrative unless explicitly identified as supplier claims or published research. We have not conducted original interviews, comparative supplier testing or a controlled experiment for this article.

1. Code23: published pricing bands ↗

   Supplier-advertised ranges checked 16 October 2026. These are not observed transaction prices or an industry average.

   Accessed 16 October 2026
2. Wall & Fifth: advertised MVP offer ↗

   Publisher-affiliated supplier. Headline price and scope checked 16 October 2026; confirm the final scope and any conflicting wording in a written proposal.

   Accessed 16 October 2026
3. GOV.UK: how the discovery phase works ↗

   Public-service guidance on understanding a problem before delivery, not a benchmark for startup duration.

   Accessed 16 October 2026

Source check: 16 October 2026. Platform documentation can change. Published as part of our editorial collection.

Expanded 16 October 2026 with practical decision material, downloads and topic-specific answers. Supplier and platform claims are identified by their linked sources.