Skip to main content

How Much Does a Web App Cost in the UK? Platform Prices, Stages and What Moves Them

In this article

A web app, or web platform, is a website that does something: customers log in, pay, generate documents, book, manage accounts, or run part of your business through it. In the UK a platform like that costs from roughly £15,000 for a first version built around one journey, to well into six figures for a product with several kinds of user and connected systems, and the honest answer to "how much" is a price per stage rather than a single figure.

This guide explains what moves the number, how a staged build keeps the first invoice small, what you keep paying after launch, and what to have ready before you ask anyone for a quote.

The short answer

  • First version: roughly £15,000 upwards across the UK market, for one journey working end to end, delivered in weeks rather than months.
  • What moves it: how many kinds of user the platform has, whether it takes payments or subscriptions, what it has to produce (documents, emails, reports), and which systems it connects to.
  • How it is priced: a written quote for the first stage before any work starts, then a price for each later stage before it begins. Our own platforms are quoted after a free 30-minute call and built in stages.
  • After launch: hosting, maintenance and monitoring as a monthly plan, plus new features priced as they are added.

What "web app" covers, and why the price range is so wide

The same two words cover a booking page that takes a deposit and a multi-user system with trade accounts, invoicing and a warehouse feed. The first is a few weeks of work; the second is a product that grows for years. That is why a quote from a one-line brief is a guess. The useful question is not "how much does a web app cost" but "how much does the first version of mine cost", and that has a real answer once the first journey is written down.

Three examples from our own work show the spread. UK Name Change started as one journey: fill in a form, pay, and have a legally valid document generated, which the business then prints and posts. A self-serve booking site for accommodation is one journey too: check availability, book and pay. A platform for landlords with rent collection, compliance tracking and a tenant portal is several journeys and several kinds of user, which is a different scale of build.

What moves the price

Kinds of user. One kind of user with one journey is the simple case. Each extra role, such as customers, staff, trade accounts and partners, brings its own screens, permissions and edge cases.

Payments and subscriptions. Taking a one-off card payment through Stripe is routine. Subscriptions, deposits, refunds, invoicing on account and anything where no payment must ever be taken twice need careful design and testing, because mistakes here cost money and trust.

What the platform produces. Generated documents, automated emails and reminders, PDFs, exports and reports each need building and testing. UK Name Change's whole value is the document it generates, so that part of the build was the heart of the project.

Integrations. Accounting software, calendars, CRMs, stock systems, Open Banking and third-party data feeds each need an integration written and kept working as the other side changes.

Data you already have. Replacing a spreadsheet or an old system means moving its data in, checking it, and often running both side by side until you trust the new one.

Design and content. A platform customers use every day needs its screens designed for the job, and the copy, help text and emails written. Supplied content costs nothing; writing it is work.

How a staged build keeps the first invoice small

The expensive mistake is specifying every feature before anything is built. A staged build does the opposite: the first stage is the one journey that makes or saves money, working end to end, on a staging site you can try as it takes shape. Later stages add the next journey, the next kind of user or the next integration, each priced before it starts and built on the same codebase.

You pay for what the business needs now, see it working, and decide the next stage with real users behind you. Our guide to planning a custom web app shows what a good first conversation covers, and our guide to building a SaaS MVP covers the same approach for a product business.

What we charge

Our web platforms are quoted after a free 30-minute call and built in stages: as a rough guide, a few weeks for a first version built around one simple journey, and a few months for one with several kinds of user or connected tools. You get a written quote for the first stage before any work starts, and once the project is paid for the code, the database, and the hosting, domain and payment accounts are yours, with no per-user licence fees and nothing rented. If a business website or an online shop would do the job, we say so, because both cost less.

Running costs after launch

  • Hosting. A platform with logins, a database and background jobs needs more than a static brochure site, but for most platforms it is a modest monthly cost.
  • Maintenance and monitoring. Security updates, dependency upgrades, daily backups that are restored for real to prove they work, uptime and error alerts, and a developer who knows the code. Budget for this from day one; a platform with no maintenance plan becomes risky to change within a year.
  • Third-party services. Payment processing, email delivery, SMS, maps or document signing are charged by their providers as you use them.
  • New features. The platform will grow. Each addition is priced before it starts, on the same codebase, so the cost of change stays visible.

How to get quotes you can compare

  1. Write down the one journey the platform must handle end to end, as the steps actually happen, with the exceptions.
  2. List the kinds of user and what each one needs to see and do.
  3. Say what the platform must produce: payments, documents, emails, reports.
  4. List every system it must connect to, and where the data lives today.
  5. Separate the must-haves for the first version from everything that can wait.

Then ask each quote the same questions: what is in the first stage, what the platform will cost to run each month, who owns the code and the data, and what happens in the first month after launch. Our guide to choosing a development agency lists the rest.

Questions people ask

How much does it cost to build a web app in the UK?

Roughly £15,000 upwards for a first version built around one journey, with no fixed ceiling, because a platform with several kinds of user, payments, documents and integrations is a product that grows in stages. The first stage is the figure to ask for, in writing, before any work starts.

How long does a web app take to build?

As a rough guide, a few weeks for a first version built around one simple journey, and a few months for one with several kinds of user or connected tools. Building in stages means something useful goes live early and the rest follows on the same codebase.

What is the difference between a web app and a website?

A website shows: pages, services, contact details, a blog. A web app does: customers log in, pay, book, generate documents or manage their own data, and staff run part of the business through it. The price difference follows from that, which is why we will say so if a website or an online shop would do the job.

Can I start small and add features later?

Yes, and you should. A staged build puts the one journey that matters live first, then adds the next journey, user type or integration as a priced stage on the same codebase. It keeps the first invoice small and lets real use, rather than a specification, decide what comes next.

Where to start

Write the one journey down today, step by step, with the exceptions. That page is what any developer needs to tell you whether a platform makes sense and what the first stage would cost. Our web platforms page sets out how we build them, and a free 30-minute call is the quickest way to get a figure for yours.