Web app vs website – what's the difference and which do you need?

The short answer

A website communicates information: who you are, what you offer, how to get in touch. A web application lets users act: log in, store data, manage processes – it's a program in the browser. The distinction has practical consequences: different technologies, a different build process and budgets that can differ by an order of magnitude. If you're planning a project and don't know which path is yours, this article will help you decide before you talk to any vendor.

What a website is

A website presents content: your offer, articles, contact details. The user reads, looks around, perhaps fills in a form. Websites are built for search visibility and fast loading, and their content is managed through a CMS. A typical company website costs €2,500–6,000; a larger site €6,000–18,000 – we break this down in detail in our website pricing guide.

What a web application is

A web application is a tool: the user has an account, works with data, completes tasks. A client panel, a booking system, an invoicing tool, an analytics dashboard – all of these are web applications. Underneath run business logic and a database, and besides the interface you design user roles, permissions and security. Smaller internal tools start at around €10,000, and an MVP of a commercial SaaS product typically costs €20,000–60,000.

Examples: which is a website and which is an app?

The difference is easiest to feel on concrete cases.

• Website: a service company's presentation site, a site with an offer and a blog, a campaign landing page, a restaurant's site with a menu and a map, an architecture studio's portfolio.
• Web application: a client panel with order history and invoices, an appointment booking system with a calendar, a document workflow tool, a production configurator quoting from a price list, a sales data dashboard.
• In between: an online store (it works like a website for the shopper and like an application for the back office), a site with a quote calculator, a site with a client area.

If your idea lands in the "in between" category, that's good news: it can usually launch in stages, starting with the cheaper part.

Technologies: what websites and applications are built with

This difference explains a large part of the price difference. A company website is built on a CMS such as WordPress or on a static site generator like Astro; editors manage the content, and technically what matters most is loading speed and search visibility.

A web application has two layers. The frontend, the interface in the browser, is usually built with libraries such as React. The backend, the business logic with a database, runs on a server, for example in Node.js. On top come the things invisible on mock-ups that consume a real share of the budget: user accounts and permissions, data security, backups, integrations with payment or ERP systems, and test environments. That's why a "simple panel" can cost more than an extensive website: there's simply more machinery to design, build and maintain underneath.

PWA: the third path between the browser and the app stores

A PWA, a progressive web app, is a web application enriched with features associated with mobile apps: a home-screen icon, push notifications, offline use. It needs no App Store or Google Play release, and one codebase serves every device. It's a sensible middle ground when users return to the tool daily but the budget or timeline doesn't yet justify a separate mobile app. You'll find a cost comparison of both paths in our article on mobile app prices.

Five questions that settle the choice

1. Will users log in? Accounts, data and action history mean an application. Presenting an offer means a website.
2. Does the product store and process user data? If so, it's an application, with consequences for security and GDPR.
3. Where will users come from? From search engines, for content: a website. From a "log in" link in their daily work: an application.
4. How often does the content change? Updated pages and a blog are CMS territory. Data changing in real time means an application.
5. What's your starting budget? If it's under €10,000, start with a website that validates the idea before you invest in a product.

The middle ground: a website with app features

The boundary blurs. A site with a product configurator, a quote calculator or a client area is a hybrid – and a frequent, sensible first step. You start with a website plus one app-like feature, measure whether users touch it, and only then build the full product. We often recommend this path to clients who come "for an app" and discover at the workshop that something half the price will test their hypothesis.

Increasingly often that first app-like feature is AI: a chatbot answering customer questions, a search box that understands natural questions, or automated handling of sales enquiries. We describe such projects in our article on AI agents for business; from an architecture point of view, this is exactly the moment a website starts turning into an application, because business logic and data processing appear.

SEO and maintenance: the differences continue after launch

A website you look after mostly through content: it's public, search engines index it, and development means publishing and optimising. Maintenance comes down to updates and hosting.

An application runs largely behind a login, so search engines see only its public layer: the product page with features and pricing. That's why SaaS products run a separate marketing site alongside the application itself. After launch an application also needs more care: monitoring, backups, dependency updates and feature development based on usage data. When you plan the budget, count not just the build but the upkeep, because an application without a caretaker ages faster than a website.

What this means for your budget

The most common mistake is buying an application when you need a website (you overpay several times over), or a website when you need an application (you get a shell you'll throw away anyway). The second trap: quoting an application without a scoping workshop. "A web application" says as much as "a building" – without a feature list, any figure is fortune-telling. That's why we start product builds with a workshop and an MVP that leaves you with a concrete scope and budget. How to plan the scope of a first version, we describe in our MVP planning guide.

Not sure which side of the line your idea is on? Describe it to us and we'll advise honestly – including when the answer is "a website is enough".