A large share of difficult digital projects start with the same misunderstanding. The client asks for a website. What they describe is an application. The quote is prepared for one and the expectations are set for the other, and the gap surfaces halfway through the build when it is expensive to correct.
The distinction is not about how something looks. It is about what happens after the first click.
The short version
A website presents information. Pages are largely the same for everyone, content changes occasionally, and the main job is to be found, read and acted on. A web application does work. It holds state, it has users with different permissions, and what one person does changes what another person sees.
A restaurant’s menu page is a website. Its table booking system is an application. They can live at the same address, but they are different pieces of work.
Four questions
1. Do people log in?
If different users need to see different things, you have an application. Accounts bring permissions, password resets, session handling, audit trails and a security surface that a brochure site simply does not have.
2. Does what one person does change what another sees?
If someone submitting a form updates a record that a colleague then acts on, that is a workflow. Workflows need states, notifications, and rules about what happens when two people act at once.
3. Is the content generated or authored?
Pages written by a person and updated occasionally are a website. Screens assembled from live data — stock levels, bookings, prices, availability — are an application, and the difficulty is in the data rather than the design.
4. What happens if it is unavailable for an hour?
If a website is down for an hour, you lose an hour of enquiries. If an application is down for an hour, work stops. That difference justifies a different standard of hosting, monitoring, backup and support — and it belongs in the budget from the start.
Why the answer changes the project
Websites and applications are scoped, priced and delivered differently:
- Websites can be specified fairly completely up front. Applications reveal requirements as people use them, so they are built in stages.
- Websites are mostly a design and content exercise. Applications are mostly a data and logic exercise, with design applied to it.
- Website testing is largely visual. Application testing has to cover permissions, edge cases and things going wrong.
- A website is usually finished. An application is a system you now operate.
The mixed case
Many projects are genuinely both — a marketing site with a customer portal behind a login, or a public catalogue with a trade ordering system attached. That is fine, and common. What matters is recognising it early, so the two halves are scoped and priced as what they are instead of being averaged into a single optimistic number.
The practical advice: before asking for quotations, write down what happens after someone logs in. If that paragraph is longer than the description of your public pages, you are commissioning an application.
We build both. If you are not sure which yours is, describe it to us and we will tell you honestly — see website design and development and web applications, or start a conversation.