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

An app in the UK can now cost almost nothing or well into six figures. AI design and build tools have pulled the bottom of the range right down. A studio build still costs tens of thousands, and ours are fixed: £25k, £60k or £100k, excluding VAT. The real question is which end your idea belongs at.

The price on the quote is rarely what sinks a founder. What sinks them is building the wrong thing, or the cheap thing twice. Below is what each end of the range buys you, where the middle ground sits and what you’ll pay once you’re live. To put your own idea through the numbers first, try the app cost estimator.

Has AI changed what an app costs?

Yes, at both ends. AI tools can now turn a written description into working screens, a database and a login in an afternoon. A founder with no code can get further alone than ever before.

AI has changed the expensive end too, just less visibly. Good studios use it to write, test and review code faster. That moves the money away from typing and towards judgement: what to build, how it fits together and what happens when it breaks.

So the gap isn’t between “AI” and “no AI”. It’s between who owns the decisions, and who answers for the product once real people depend on it.

How far can AI-built apps get you?

Further than most agencies will admit. For a lot of first products, an AI-built version is the right place to start.

What the cheap end does well

• Clickable demos. You can show investors and customers something real, not a slide.
• Internal tools. A tracker or a booking form for your own team rarely needs more.
• Testing demand. A landing page with a working sign-up tells you whether anyone cares.
• Your own thinking. Building a rough version forces you to decide what the product actually does.

The cost is mostly your time, plus a monthly subscription to the tool. That’s a fraction of any studio quote.

Where it runs out

The limits show up when the product meets the real world:

• Security and data. Generated code can expose customer data in ways a non-engineer won’t spot.
• Payments and integrations. Connecting to banks, CRMs or legacy systems needs someone who can read what broke.
• App stores. Apple’s guidelines expect apps to go beyond a repackaged website, and reject apps that generation services submit for their clients.
• Change. Each new prompt can quietly rewrite something that worked yesterday. Without tests, nobody notices until a customer does.
• Ownership. Some tools host your app on their platform. Check you can export the code and run it elsewhere.

None of that makes the cheap end wrong. It makes it a starting point. If your AI-built version is getting real use, that’s good news. It means you’ve learned what to build properly.

When is the expensive end worth it?

Paying a studio makes sense when getting it wrong would cost more than the build. That usually means one of these:

• People will pay you, or trust you with health, money or personal data.
• The product has to connect to other systems and keep working when they change.
• You need native iPhone and Android apps that pass review and stay current.
• Buyers will ask for security and compliance evidence before they sign.
• You need it live, on a date, without managing developers yourself.

At that end you’re buying senior judgement and accountability, not lines of code. We use AI throughout our own work. Senior engineers review and own everything that ships, which is the part a tool can’t sell you.

Is there a middle ground?

Yes, and it’s bigger than it used to be. If you already have a logo, a brand system or a clear visual identity, much of the design work is done.

Design normally takes a real share of a build. A founder with an established identity can skip the brand exploration and go straight to applying it. That leaves more of a fixed budget for the product itself.

The same goes for an AI-built prototype. If you’ve already tested screens with real users, bring them. Discovery moves faster when it starts from evidence rather than a blank page.

What actually drives the cost of an app?

Price follows decisions, not screens. Two apps with the same number of screens can differ in cost several times over.

A native app is built specifically for iPhone or Android and installed from an app store. A web app runs in the phone’s browser, and costs less to ship and maintain. Plenty of first products don’t need native.

The last row matters most. Overspend usually comes from changing direction mid-build, not from the original plan.

Why budgeting for an MVP is the wrong goal

MVP stands for minimum viable product: the smallest version that proves people want your idea. It sounds sensible. In practice, it often leads founders astray.

Cutting an idea down to its smallest size doesn’t make it launchable. It makes it small. A product with half a journey, no analytics and no plan for feedback rarely tells you much. Users try it, shrug and leave, and you can’t tell why.

What matters more than size is what happens in the weeks after launch:

• A launch plan. Who hears about it, through which channel, on which day.
• Feedback cycles. Analytics and user conversations built in, so you learn what to change.
• Room to adapt. Foundations that let you change direction without a rebuild.

That’s why LaunchPad is about launching a successful product, not building an MVP. The budget covers the first version and the means to improve it once real users arrive.

Where does each LaunchPad tier sit?

Starter, £25k

Starter is for founders who need one thing live: an app or a website. It suits a product with one main user journey and few outside systems. It includes discovery, design, an interactive prototype, the build, analytics and launch.

Growth, £60k

If you need a website and an app, Growth is our answer. It adds the second product, single sign-on and third-party integrations. Single sign-on lets people log in with an account they already have, like Google or Microsoft.

Most two-sided products land here. Think of a customer portal on one side and a staff app on the other.

Scale, £100k

Scale is for products where the hard part is depth rather than breadth. It adds a fully custom interface and brand system, advanced integrations and long-term product planning. It also includes a certification gap analysis: what you’d need to change to pass a security standard.

Why we fix the price

Overruns are the thing founders fear most, with good reason. A fixed price means both of us agree scope before the build starts. If an agreed feature takes us longer, that’s our cost, not yours.

Discovery sets the scope within the tier you pick. If the plan isn’t right after Discovery, you get your money back. You pay in stages, with each phase invoiced in advance. You own the code and IP.

The price covers everything up to launch. That includes developer accounts, hosting, licences and the third-party services the build needs. The pricing page lists what’s in each tier.

Where do app budgets quietly leak?

Budgets rarely vanish on the features founders asked for. They leak into places nobody puts on the quote.

• Hand-built admin tools. Your team needs a back office, but off-the-shelf tools already do this well. Spend on what customers touch.
• Scale you don’t have yet. Architecture built for millions of users solves problems you don’t have. Pay for scale when your users force you to.
• Cheap foundations. Shortcuts in the foundations make every later change slower and dearer. The most expensive app is the cheap one you replace a year later.
• Code you don’t control. On a rented white-label platform, even a logo change can wait on the vendor. On code you own, it’s a quick job.
• Your own time. Expect a few hours a week on feedback and decisions. Slow answers stretch any timeline.
• Change mid-build. New ideas after design sign-off cost money with any supplier. Park them for the next cycle.

What does an app cost to run after launch?

The build is a one-off cost. Running costs aren’t, and most quotes leave them out.

Apple’s 15% rate is for developers with under $1 million a year in proceeds, and you have to enrol. Store commission only applies to digital goods and services. Physical goods and real-world services, like deliveries, pay none.

New personal Google Play accounts must run a closed test with 12 testers for 14 days before launch. Registering as an organisation is usually the better route for a company.

Or hand the running to us

Support isn’t optional. Apple and Google update their operating systems regularly, and apps that aren’t kept up start to break.

You can run all of this yourself. Or we can run it for you with TotalCare, for a fixed monthly price. That covers hosting, the app store accounts, third-party services and support. You don’t chase renewals, juggle supplier bills or wake up to a broken release. You get on with scaling the business.

Either way, the accounts, hosting and code are yours at launch. An AWS setup is a whole AWS account, and it can move out to you. App Store and Google Play apps transfer between developer accounts, and so do GitHub repositories.

Do UK app development prices include VAT?

Usually not, so always check. Our prices exclude VAT, as most business-to-business quotes do. The standard UK VAT rate is 20%, so Starter is £30k including VAT. Growth comes to £72k and Scale to £120k.

If your company is VAT registered, you can normally reclaim VAT on business costs. Registration becomes compulsory once taxable turnover passes £90,000 in a rolling 12 months. Some pre-revenue founders register voluntarily so they can reclaim it.

Once registered, you can usually reclaim VAT on services bought up to six months before. Ask your accountant before you sign anything.

When shouldn’t you spend £25k yet?

Don’t spend studio money if you haven’t spoken to potential customers. Twenty conversations and a landing page cost almost nothing. Our guide to validating an app idea shows you how.

Don’t build custom if an existing tool would do. And if an AI-built prototype can answer your next question, build that first. Come to us when people are using it and you need it to hold up.

What does this look like on a real project?

Pristine Condition came to us with software almost nobody used: under ten percent adoption. We rebuilt it as an app that assesses lifting technique in real time on an ordinary phone camera. It works with no internet connection, even on old handsets.

Around 150,000 warehouse staff now use it worldwide, and usage is up around 9,000%. That’s a Scale-shaped product, where a native app earns its extra cost. It needed offline working, AI running on the phone and a reporting hub for managers.

The lesson for your budget is simple. A product people don’t use is expensive at any price. Whatever end of the range you start at, plan for what happens after launch. Then talk to us, and we’ll tell you which tier fits, or whether to spend nothing yet.