Andrew Crossley

How much does an MVP cost in the UK?

SHORT ANSWER

In the UK, a focused commercial MVP with one core user journey typically costs about £12,000–£25,000 with a product-led, AI-assisted build. A clickable or lightweight validation prototype can cost roughly £3,000–£8,000. Multiple user roles, complex integrations, RAG or agentic AI, specialist compliance or premium design can move the project above £25,000; larger agency builds can reach £60,000–£150,000.

Answered by Andrew Crossley, AI Product Consultant & Product Partner · Updated 2026-08-22

Why it matters

Founders often compare prices for completely different scopes. A prototype, a focused commercial MVP and a multi-role production product should not share one price label.

Budgeting only for version one creates a second problem: there is no money left to respond to what real users teach you after launch.

How it works in practice

  1. 1

    Decide whether you need a prototype or an MVP

    A prototype proves the flow or helps validate demand. A commercial MVP handles real accounts, real data, analytics and a real conversion or payment path. They are different jobs and should have different budgets.

  2. 2

    Cost the core journey first

    Price the one user journey that creates value before adding admin, settings, additional roles or secondary workflows. Those additions are where a focused MVP becomes a larger product.

  3. 3

    Separate build cost from run cost

    Hosting, model inference, email, monitoring and support continue after launch. Model the recurring cost per active user or successful task before usage grows.

  4. 4

    Reserve the iteration budget

    Hold back roughly 20-30% of the available product budget so the first customer evidence can change the product instead of merely producing a report about what went wrong.

Common mistakes

  • Treating a £3,000 prototype and a £20,000 commercial MVP as if they are competing quotes for the same deliverable.
  • Adding a second user role, admin surface or several integrations without acknowledging that the scope has changed.
  • Underestimating AI inference and support costs after launch.
  • Spending the full budget on version one and leaving no room for post-launch iteration.

FROM EXPERIENCE

Three useful budget shapes

£3,000–£8,000: a prototype or narrow validation build designed to test the journey and customer response, not to carry the full operational burden of a mature product.

£12,000–£25,000: a focused commercial MVP with one core journey, accounts where needed, analytics, a conversion path and a launchable product surface.

£25,000–£60,000+: a broader product with multiple roles, harder AI, several integrations, bespoke design or specialist operational requirements. A traditional agency structure can push the same category of work higher again.

Frequently asked

Can I build an MVP for under £5,000?

Yes for a prototype, a founder-built AI-assisted test or an unusually narrow validation product. That is not automatically the same deliverable as a production-capable commercial MVP handling real customer accounts, data and payments.

How much does an AI MVP cost in the UK?

For a focused AI MVP, use roughly £12,000–£25,000 as a planning band when the product has one core journey and controlled complexity. RAG, agentic workflows, sensitive data, multiple roles or several integrations can move it above that range.

Why are agency MVP quotes often higher?

An agency price usually includes a multi-person delivery structure, project management, design and engineering capacity. That can be appropriate for a broader defined specification, but it is often more process and capacity than a single-journey founder MVP needs.

How much should I keep for post-launch changes?

A useful planning rule is to keep roughly 20-30% of the available product budget uncommitted so real usage can determine the next version.

IN SHORT

  • Prototype or validation build: roughly £3k–£8k.
  • Focused commercial MVP: typically £12k–£25k.
  • Multiple roles, harder AI, integrations or specialist requirements can push beyond £25k; agency builds can reach £60k–£150k.

AI app development in six weeks

A validated, instrumented first product in front of real users.

AI app development in six weeks

THE FRAMEWORK

The Crossley Method: idea to first revenue in seven stages

See the full method
  1. STAGE 1DiscoverWeek 1
  2. STAGE 2ValidateWeek 2
  3. STAGE 3PrototypeWeek 3
  4. STAGE 4Build MVPWeeks 3-4
  5. STAGE 5LaunchWeek 5
  6. STAGE 6First RevenueWeek 6
  7. STAGE 7ScaleOngoing

MORE ANSWERS

Idea to MVP

How do you build an MVP?

Build an MVP by picking one job a specific user will pay to have done, designing the single shortest flow that completes it, and shipping only that. Validate demand before building — interviews plus a paid or committed signal. A focused build can take four to six weeks; allow roughly six to twelve weeks from idea to public launch when validation, pilot users and fixes are included.

How do you build an AI MVP?

Build an AI MVP by choosing one task where being right 80% of the time is still useful, wrapping a hosted model rather than training your own, and designing the interface around correction — users must be able to see, edit and accept output. Set an evaluation set before launch, measure task success and human-override rate, and only consider fine-tuning once the workflow itself is proven.

Can a non-technical founder build an AI app?

Yes. A non-technical founder can build and validate an AI app in 2026 using tools such as Lovable, Cursor or Bolt without first hiring a full engineering team. The founder still needs to own the customer problem, scope, accounts, data access, AI quality, costs and launch decision. Use specialists for the parts where a mistake creates real security, reliability or commercial risk.

What happens after building an app with Lovable?

After your Lovable app works, do not automatically rebuild it. First validate that real users want the core journey, then audit authentication and data access, billing, error handling, backups, monitoring, AI quality and cost per user. Fix launch blockers in risk order and add analytics before public release. Rebuild only when the existing architecture genuinely cannot support the business you have evidence for.