Website or Web App? What the Difference Actually Means for Your Budget

A client once came to us wanting "a website" with a customer login area, a booking calendar that checked real-time staff availability, and automatic invoice generation after each job. It is a website in the sense that it runs in a browser, but it is not a website in any way that a typical web developer's quote for "a website" would price up. It is a web application, and the difference between those two words had already cost this client two wasted quotes before they got to us.

This mix-up is common, and it is one of the main reasons website quotes can vary by a factor of ten for what sounds, on paper, like the same project. Knowing which one you actually need, before you ask anyone to quote it, will save you time and get you a number you can trust.

What a website is actually for

A website's job is to present information. Someone lands on a page, reads it, maybe fills in a contact form or clicks through to another page, and that is largely the end of the interaction. A brochure site, a portfolio, most restaurant or tradesperson sites, and the majority of small business sites in the UK fall into this category. They can look polished and still be, structurally, a website: pages of content, a contact form, perhaps a blog.

The technology behind a website is relatively simple and well understood. A content management system like WordPress, or a static site built with a modern framework, can handle almost everything a typical business site needs. That is also why websites are the cheaper, faster thing to build. There is less to go wrong because there is less happening.

What actually makes something a web app

A web app is software that runs in a browser instead of living on your desktop or phone. The test is not how it looks. It is whether it remembers who you are, stores and changes data specific to you, and does something different depending on who is using it.

A customer portal where clients log in to see their own invoices and job history is a web app. A booking system that checks real availability against a calendar, holds a slot while payment is taken, and then updates a staff rota, is a web app. An internal tool where your team logs stock levels, raises purchase orders, and sees automatic reorder alerts when something runs low is a web app. So is a quoting tool that takes a customer's inputs and calculates a live price based on your own rules, rather than just showing a static price list.

None of these need to look complicated to a user. A booking calendar can look like a single, clean page. What makes it a web app is what is happening underneath: a database tracking real state, logic deciding what to show different users, and often other systems it needs to talk to, like your accounting software or a payment processor.

A quick way to tell which one you're actually briefing

Ask yourself one question about the thing you want built: does it need to remember something between visits, or behave differently for different people? If a visitor sees the same page regardless of who they are and nothing they do changes stored data, you are almost certainly describing a website, even if it has forms, animations, and a few clever design touches.

The moment you add "and customers can log in to see their own," or "and it should calculate this automatically based on," or "and staff need a dashboard showing," you have crossed into web app territory. That is not a bad thing. It just changes what the project actually involves, and what it should cost.

Why the cost gap is so wide

This is where the confusion gets expensive. A straightforward business website in the UK typically runs from around £2,000 for a simple small-business site up to £10,000-£15,000 for something larger with custom design and more pages. A web app starts in a different place entirely.

A simple internal tool, covering one core workflow with basic data handling and minimal integrations, tends to sit somewhere around £8,000-£20,000. Add user accounts, a payment integration, and a proper admin dashboard, and mid-complexity projects commonly land between £20,000 and £60,000. Anything with multiple user roles, several third-party integrations, and more involved business logic can run well beyond that, and ongoing maintenance for a web app typically costs 15-20% of the build price per year, because there is more underneath it that needs looking after: databases, security patching, and the integrations that can break when another tool updates.

None of this means a web app is a poor investment. A well-built customer portal or internal tool often earns back its cost quickly in admin time saved or in jobs you can now take on that you could not handle manually. But asking three agencies to quote "a website" when you actually need a web app, and then comparing the numbers side by side, will leave you comparing things that are not the same, and wondering why one quote is five times another.

You rarely have to choose once and be stuck with it

Plenty of businesses start with a straightforward website and add app-like features later, once there is a clear reason to. A trades business might launch with a simple site, then add a customer portal a year later once enough clients are asking "can I just check the job status online?" A retailer might start with a brochure site and add an online booking system once in-person appointments become the bottleneck.

The practical approach is to build the website properly first, on a platform that will not fight you when you want to bolt on a login area or a booking system later, rather than trying to guess every future feature on day one and paying for complexity you might not need for another two years.

What to actually do with this before you ask for a quote

Write down, in plain language, what you want the finished thing to do, focusing on anything involving logins, data that changes, or calculations specific to a user. Then say explicitly in your brief whether you think it is a website or whether it needs to behave more like software. An agency that knows what they are doing will tell you if you have got that wrong, but starting the conversation with the right word saves everyone time, and it means the quotes you get back are actually comparable.

If you are not sure which side of that line your project sits on, that is a genuinely normal position to be in, and it is exactly the kind of conversation we have with new clients all the time at Digital Hand. We will tell you honestly if what you are describing is a simple site, a web app, or something that could start as one and grow into the other. You can book a free 15-minute consultation and we will help you work out which one you actually need before you brief anyone.