When is a website enough, and when do you need a web app?
Four levels from an information site to a custom web app, what drives the cost at each step, and what to ask about maintenance and ownership.
By Daniel Aideborn · Published 17 September 2026 · 3 min read
Short answer: a website is enough for as long as a visitor only needs to understand, compare and get in touch. The moment somebody has to sign in, see their own records or set something off inside your business, it is a web app, even when it looks like a page.
Between the two sits a step that is often forgotten: letting an existing service handle booking or payments, and simply connecting it. That is almost always the cheapest, and it carries further than most people expect.
Four levels
| Level | What the visitor does | What gets built |
|---|---|---|
| Information site | Reads, compares and gets in touch | Pages, forms, measurement |
| Site with a connected service | Books or pays inside an external service | Pages plus the service's configuration |
| Customer portal | Signs in and sees their own | Accounts, permissions, data, views |
| Custom web app | Works in the tool daily | Own data model, roles, flows, admin |
The levels cost different amounts to build, but above all different amounts to own. The first needs almost no maintenance. The fourth needs somebody to keep it alive.
Signs that a website is no longer enough
- You send the same details back and forth by email because the customer cannot see them.
- Somebody types the same information into two systems every week.
- You need to show different things to different customers, behind a login.
- A spreadsheet has become business-critical, and several people edit it at once.
- You turn customers away because the flow does not scale, not because the work is missing.
One or two of those usually mean an existing service is enough. Four or five mean the work already exists, and that it is being done by staff instead of by a tool.
What drives the cost of a build of your own
- Accounts and roles. Sign-in, password resets, and who is allowed to see what.
- Data. Where it is stored, how it is backed up, and how mistakes are corrected once something has gone wrong.
- Flows with exceptions. The normal case is rarely the problem. The exceptions are.
- Integrations. Every system you connect is its own set of failures to handle.
- Administration. Somebody on your side has to be able to correct, add and remove without calling a developer.
Maintenance and ownership
A web app is not a project that finishes; it is something you will own. What decides how cheap that ownership is turns out to be how simple the build is, not how advanced.
- Who owns the code, and where does it live?
- Who owns the data, and how do you get it out if you change supplier?
- Which accounts are in your name: domain, hosting, database, email?
- What do fixes look like after launch, and what do they cost?
- What happens if the person who built it becomes unavailable?
The answers to those matter more than the choice of technology. A simple build you own beats an advanced one you rent.
How to choose
- Write down, in one sentence, what the visitor or the colleague should be able to do.
- Check whether an existing service already does it, for a monthly fee.
- If it does: connect it, and spend the money on the content instead.
- If it does not: describe the three most common cases and the two most awkward ones, and ask for a price on those.
If you want my answer on which level your need sits at, describe the flow in the contact box on the home page. The packages and what they cost are under pricing, and what a larger build includes can be opened there. If the problem is recurring manual work rather than a missing page, What can a small business automate? is nearer the question.
Related services: Web apps