Do You Need a Website or a Web Application?

Whether you need a website or a web application depends on what people do when they arrive. If they read about your business and then contact you, book or buy, you need a website. If they log in to create, manage or track their own information, such as quotes, orders, jobs or documents, you need a web application. Many businesses actually need a website with one application-like feature, and recognising that saves a lot of money.

Website vs web application: the difference

Signs you need a website

• Visitors want to understand what you do and whether to trust you
• The main action is an enquiry, a call, a booking or a straightforward purchase
• Content is the same for every visitor
• Your team mainly needs to edit pages and publish updates

That describes most small businesses. The business website development guide covers how to plan one.

Signs you need a web application

• Users need accounts and see information specific to them
• People create or edit records: quotes, orders, projects, applications
• Different users have different permissions, such as customers, staff and admins
• The system replaces a manual process, spreadsheet or email chain
• It connects several systems and shows the combined result
• Two groups of users interact through it, as in a marketplace

A B2B marketplace connecting buyers and suppliers is application territory. The Kontractz B2B marketplace case study shows what that kind of build involves: trade leads and requests for quotation, separate buyer and vendor dashboards, deal rooms with documents attached to each stage, paid membership tiers with automatic billing, and an admin layer to moderate it all. It was built in Next.js with a relational database, because none of that is content. It is logic, permissions and data.

A quick test

Answer these five questions about the project you have in mind:

1. Will most users need to log in?
2. Will two users see different information on the same page?
3. Will users create or change records that other people then act on?
4. Does the system need different roles with different permissions?
5. Would the business stop working properly if the system went down for a day?

No to all five: a website. Yes to one or two: a website with an application-like feature. Yes to three or more: a web application, and it should be planned and budgeted as software.

The common middle ground

Many projects sit between the two. A website with:

• An online booking calendar
• A quote calculator
• A members-only resources area
• A simple customer login to download documents

Each of these is an application-like feature inside a website. Off-the-shelf tools or plugins often cover them well. On WordPress, booking and membership sites are a mature category. On a framework such as Next.js, a single custom feature can be built into an otherwise ordinary site.

The expensive mistake is treating a website-with-one-feature as a full application, or the reverse: trying to bend a website platform into a full application with a stack of plugins.

How cost and process differ

A website project is mostly design, content and templates. A web application project is software development:

1. Requirements. Who the users are, what each can do, what data exists.
2. Data model. How records relate to each other.
3. Authentication and permissions. Who can see and change what.
4. Interfaces. Screens for each user type, plus admin tools.
5. Integrations. Payments, email, CRM, accounting.
6. Testing and security. Far more paths through the system to check.
7. Ongoing development. Applications grow with use.

That is why applications usually cost several times more than a website and need a longer relationship with a developer. How much does a website cost in the UK covers where websites sit; applications are priced on features rather than pages.

What changes after launch

A website, once launched, mostly needs content updates and routine maintenance: software updates, backups, security checks. A web application needs all of that plus ongoing development, because users find edge cases, ask for features and depend on the system working every day.

Plan for:

• Support. Someone users can contact when something does not work for them.
• Monitoring. Errors logged and noticed, not discovered by an unhappy customer.
• Data responsibilities. Accounts and personal data bring UK GDPR obligations, including security and retention.
• A development budget. Applications that stop being developed tend to fall behind the businesses they serve.

Start smaller than you think

If you are sure you need an application, build the one workflow that matters most first. For example, customers submit a job and track its status, before adding invoicing, reporting and messaging. Real use will tell you which features are worth building next, and which you only thought you needed.

For the technology choice, Next.js vs WordPress explains why frameworks usually suit application work better.

If you are not sure which side of the line your project sits on, describe what users need to do and send it through the website development service page. Working that out is the first part of any quote I give.