Website vs web app: what is the difference, and which do you need?

A website publishes information that is the same for every visitor: pages about a company, its services, its articles. A web app lets each user log in and create, store and change their own data: an invoicing tool, a booking system, a client portal, a SaaS product. The practical difference is state. A website mostly reads from a fixed set of pages; a web app reads and writes data for each user, and has to keep that data correct, private and available.

That one difference drives everything else: what it costs, how long it takes, how it is tested, how it ranks on Google and what it needs after launch. It is also why our web app and SaaS development work starts by asking which parts of a project really are an app.

How do websites and web apps compare?

The build times and costs above are typical for a small studio as of October 2026. How much a website costs and how much a web app costs give the full ranges. As a rough rule, the same number of screens costs three to ten times more as an app than as a site, because every app screen has to handle permissions, validation, errors and edge cases that a page of text does not.

Where is the line blurry?

Many projects are a website with an app inside it, or an app with a website in front.

• An online store. Product pages are a website. The cart, checkout and order history are an app, supplied ready-made by Shopify or WooCommerce.
• A booking system on a clinic site. Mostly website, with one app-like workflow, usually handled by an embedded tool.
• A SaaS product. Mostly app, with a marketing website in front of it for pricing, features, the blog and sign-up.
• A members' area. A website with a login. If members only read content, it is still a website. If they submit, track or edit things, it has become an app.

A useful test: if a user can make a mistake that affects their own data, you are building an app. That is the point where you need validation, permissions, audit trails and backups that you can restore for one customer.

Why does a web app cost so much more?

Because most of the work is invisible. A website page is done when it looks right on every screen size and loads fast. An app screen is done when it also:

• shows only the data this user is allowed to see, and refuses everything else;
• validates every input, on the server as well as in the browser;
• handles the empty state, the error state, the slow-network state and the "two people edited this at once" state;
• writes to a database that is backed up and can be restored;
• is covered by tests, because a bug in an app loses someone's work, not just a paragraph.

On top of the screens sit accounts, password resets, emails, billing, an admin area for your team and monitoring. None of this shows in a design mock-up, which is why quotes for apps vary so widely. We include these in the first estimate, because leaving them out is how cheap quotes become expensive projects.

Do you need a website, a web app, or both?

You need only a website if visitors read, compare and then contact you, call you or buy through a standard checkout. Most service businesses, manufacturers, consultancies and agencies are here. WordPress vs a custom website covers how to build one.

You need a web app if any of these are true:

• Customers or staff need to log in and do work, not just read.
• The same task is done repeatedly with data that changes, such as orders, jobs, bookings or claims.
• You are replacing spreadsheets or email threads that several people edit.
• You are selling software as the product.

You need both if the app is the product and you need customers to find it. In that case build the website first. It can go live in a few weeks, test your message, rank for the problems you solve and collect a waiting list while the app is built. Estimate the website side with our website cost calculator before committing to the app budget.

Sometimes you need neither. If an existing SaaS tool covers 80 percent of the workflow, paying for it is cheaper than building, and custom software vs off-the-shelf is the guide for that decision.

Can a web app rank on Google?

The parts behind login cannot, and should not. Search engines cannot sign in, and you do not want customers' data indexed. What ranks is the public layer: the marketing site, feature pages, pricing, help articles, and any public tools or pages the app generates.

Two technical points matter for the public layer. First, pages should be rendered on the server or at build time, so their content is in the HTML. Google can render JavaScript, but its own JavaScript SEO guidance explains the extra step and the ways it fails. Frameworks such as Next.js handle this by default, which is one reason we use it for both sides; why we build with Next.js explains the rest. Second, keep the app on its own subdomain or path, block its logged-in routes from indexing, and keep the public site fast and crawlable.

What changes after launch?

A website after launch needs content updates, security patches and occasional design work. A few hours a month is common.

A web app after launch is a product with users. It needs bug fixes, support, new features, dependency updates, monitoring and backups that are tested. Budget for a team, part-time at least, for as long as the app is in use. What to log and monitor from day one covers the minimum, and the pillar guide on building a SaaS product shows how the first version fits into the rest of the work.