Website vs web app: which does your business need?

The straightforward distinction

A website presents information. A web application does something.

That’s the simplest version of the difference, and it holds up well enough for most purposes. A website tells people about your business, shows your services, and gives them a way to contact you. A web application takes input, processes it, and produces output — or manages ongoing data and interactions over time.

In practice, many digital products sit somewhere between the two. A website with a contact form is still a website. A system where users log in, manage records, submit requests and receive responses is a web application, even if it looks like a simple interface.

Examples of websites

• A business website presenting services, an about page and a contact form
• An e-commerce store where visitors browse and purchase products
• A portfolio or blog with regularly updated content
• A landing page for a specific campaign or product

These all present information and facilitate a relatively simple action — browsing, reading, purchasing, or getting in touch.

Examples of web applications

• A job management system where staff log jobs, update statuses and generate reports
• A client portal where customers log in to view their account, submit requests or track progress
• A booking or scheduling system with user accounts and calendar management
• An internal dashboard that pulls together data and presents it in a useful format
• A guest management tool for tracking RSVPs, dietary requirements and seating

The common thread is ongoing interaction with data, user accounts, or processes — rather than presenting fixed information.

Why the distinction matters practically

The difference isn’t just semantic. It affects how the project is scoped, how long it takes, how it’s built, and what it costs.

A straightforward business website can often be planned and built in weeks. A web application — even a relatively simple one — requires more careful upfront planning, because you have to work out the system's logic before building anything. Getting that wrong midway through is expensive.

It also affects maintenance. A website with a content management system is designed for non-technical users to update. A web application usually has more moving parts that need technical attention when something changes.

The grey area: websites that do things

Many business websites now include features that push them toward the web application end of the spectrum — booking forms, e-commerce functionality, member areas, or dynamic content. This is fine, and it doesn’t mean you automatically need a custom web application.

The question is whether the functionality you need is well-served by an existing platform — a WordPress plugin, a Shopify store, a booking system integration — or whether your requirements are specific enough that an off-the-shelf solution won’t fit properly.

If you find yourself working around the limitations of a platform constantly, or managing a spreadsheet to compensate for what the platform can’t do, that’s a signal that a custom solution might be worth considering.

How to work out which one you need

A few honest questions help here:

Does it need user accounts or logins?

If different people need to see different information, or if someone needs to log in to manage something, you’re moving into web application territory.

Does it need to store and manage data over time?

A contact form submits data once. A system that tracks jobs, customers, orders or requests over time, with the ability to update and report on them, is a web application.

Does it need to do something with input, not just receive it?

If the system needs to calculate, process, assign, notify or generate something based on what a user enters, it’s doing application-level work.

Would an existing platform handle it without constant workarounds?

If yes, a website with that platform integrated is often the more practical choice. If no, a custom build is worth considering.

What to do once you’ve worked it out

If you need a website, start with Website Design & UX/UI and Website Development — covering everything from planning through to a working, deployed site.

If what you need is closer to a web application — a custom system, a dashboard, a tool with logins and data management — Custom Web Applications covers that kind of work.

If you’re still not sure which category your idea falls into, the most useful thing to do is describe what you want the system to do, rather than what you want it to look like. That’s usually enough to work out the right approach.