Web Development
Website or web app? Knowing what you are actually commissioning
The two cost different amounts for good reasons. How to tell which one you need, and the questions that shape the price.
Codexan
5 min read
"We need a new website" can mean a five-page brochure or a booking system with customer accounts and payments. Those are different projects with different budgets, and confusing them is the commonest reason quotes for the same brief vary by a factor of ten.
The difference
A website presents information. Visitors read, look and get in touch. Everyone sees roughly the same thing.
A web app lets people do something: sign in, save data, pay, book, upload, manage. What each person sees depends on who they are and what they have done before.
Many projects are both: a public website with an application behind a sign-in.
Why the app costs more
A page that displays text has one state. A feature that stores data has many, and each needs a decision:
- What if the form is half filled in and the connection drops?
- Who is allowed to see this record, and who can change it?
- What happens to a booking when the customer's account is deleted?
- How is the data backed up, and for how long is it kept?
None of this is visible in a design mock-up. All of it has to be built, tested and maintained. That is where the cost lives.
Questions that shape the price
Before asking for a quote, try to answer these. Even rough answers make estimates far more accurate.
- Do users sign in? Accounts bring password resets, permissions and data-protection duties.
- Does money change hands? Payments add a provider, refunds, receipts and reconciliation.
- What other systems are involved? Each integration with a CRM, accounting package or stock system is a small project of its own.
- Who updates the content? If your team edits pages, they need an editing interface that suits them.
- How many people will use it at once? Fifty and fifty thousand are different engineering problems.
- What must never go wrong? The answer tells the team where to spend the testing budget.
Start smaller than you think
The most reliable way to control cost is to launch the smallest version that is genuinely useful, then extend it using what real users do. A booking system might start with one service, one location and email confirmations. Calendar sync, multiple staff and reminders can follow once people are using it.
This is not cutting corners. Software built in stages, each one in real use, almost always ends up better than software built in one long stretch from a long specification.
What to ask for at the end
Whoever builds it, make sure you finish with:
- the source code, in a repository you control
- hosting, domain and third-party accounts in your company's name
- written notes on how to deploy and how to restore a backup
- a clear statement of what ongoing maintenance costs
A project delivered that way can be picked up by any competent team later, including your own. That freedom is part of what you are paying for.
- web
- full-stack
- planning
- product