Website or web application — how to choose
In short
A marketing site convinces someone who does not know you yet. A web application lets someone who already knows you get work done. If your need is to sell, it is a site. If your need is to replace a spreadsheet, it is an application — or, more often than people expect, existing software.
Confusing the two is expensive in both directions. Companies pay for custom applications to solve a need three pages would have covered. Others spend two years cramming an entire business into a marketing site and a pile of spreadsheets.
The question that settles it
Ask this one: is the person using this tool logged in?
If the answer is no — the user is an anonymous visitor you are trying to convince — you need a site.
If the answer is yes — the user has an account, their own data, and actions to perform — you need an application.
The question looks simplistic, but it holds up under discussion. Everything else follows from it: security, backups, access rights, maintenance, cost.
What belongs on a marketing site
- Explaining what you sell and to whom.
- Showing proof: case studies, numbers, testimonials.
- Answering objections before the sales call.
- Capturing an enquiry.
- Publishing content so search engines can find you.
A good marketing site is a commercial tool. It is judged on one number: how many qualified enquiries it produces per month.
What belongs in a web application
- Tracking the state of something that changes: orders, cases, stock.
- Letting a customer do for themselves what they email you about today.
- Enforcing a business process with steps and approvals.
- Making two systems that do not talk to each other communicate.
An application is judged on the time it saves, or the errors it prevents.
The third option people forget
Before commissioning any development, list your ten main use cases and look seriously at three existing products.
If one covers eight of ten for €80 a month, take it. You will pay €960 a year instead of €30,000 once, plus maintenance. The two uncovered cases will cost you less in manual workaround than the custom tool will cost you in changes.
Custom only pays off in two situations: your process is genuinely different from your competitors' and that difference is what wins you work, or you are large enough that subscription costs exceed development costs.
The common case — both, in this order
Many businesses need both, but rarely at the same time.
The sequence that works: the site first, because it generates revenue and ships quickly. Then the application, funded by what the site brought in, once you know precisely what your customers need.
The reverse — building the internal tool first and redoing the site "later" — generally leaves a company with a fine tool and no new customers to use it.
Frequently asked questions
What is the difference between a website and a web application?
A marketing website presents an offer to anonymous visitors and aims to trigger contact. A web application requires a login and lets an identified user perform actions — view data, complete a file, track an order. The dividing line is authentication and per-user data.
Can we start with a site and add an application later?
Yes, and it is often the right sequence. A well-built marketing site can host a client area later without a rebuild, provided the initial technical choice allows it. State that intention during scoping.
Is a client portal a site or an application?
It is an application, even at three screens. As soon as there is a login, per-user data and access rights, you are in application territory — with the security, backup and maintenance questions that come with it.
How do I know whether off-the-shelf software would do?
List your ten main use cases and look for three existing products. If one covers eight of them at a reasonable subscription, take it. Custom is only justified when your process is a competitive advantage or when the workarounds already cost more than the tool.