“Web development services” is a category that hides enormous variation. It covers a five-page brochure site and a system that handles payments, inventory and user accounts for thousands of people. Both get quoted as “a website”, and the gap between them is where most budget disputes begin.
This sets out what the different kinds of web development work actually involve, which one fits which problem, and what to settle before a project starts.
Key Takeaways
- Brochure sites, content-managed sites and web applications are three different projects with different costs, timelines and risks.
- The technology choice should follow who maintains the site afterwards, not what is currently fashionable.
- Integrations with systems you already use are the most commonly underestimated part of any build.
- Maintenance is not optional. Software that is never updated becomes a security problem rather than staying still.
What Kinds of Web Development Are There?
A brochure site
Fixed pages that rarely change: what you do, who you are, how to reach you. No login, no database of your own, nothing calculated.
Suits professional services, trades and small businesses whose content is stable. These can be built as static sites, which removes most maintenance and security burden entirely, at the cost of being less convenient to edit.
A content-managed site
The same, plus the ability for non-technical people to add and edit content: a blog, a news section, a growing set of service or location pages.
This is what most businesses need, and it is what WordPress and similar systems exist for. The trade-off is ongoing maintenance: a content management system is software, and software needs updating.
An e-commerce site
Selling online adds products, stock, payments, tax, shipping rules, and customer accounts. Each is a source of complexity that a brochure site never touches.
The decisive question is usually not the storefront but what happens behind it: whether stock and orders need to reach an existing system, and who fulfils them.
A web application
Software that happens to run in a browser: a portal, a booking system, an internal tool, a dashboard. Users log in, data is stored, things are calculated, permissions matter.
This is a genuinely different discipline from building a website, and it is the category most often underestimated. The visible screens are a fraction of the work; the rules underneath them are the project.
How Do You Choose the Technology?
By asking who maintains it, not which framework is currently admired.
A stack that is excellent and obscure becomes a liability the moment the person who built it is unavailable. A stack that is ordinary and widely known can be picked up by any competent developer. For most businesses, the second is worth more than any technical advantage of the first.
Three questions settle it in practice:
- Who will update this in two years? If the answer is “whoever we can find”, choose something common.
- Does anyone non-technical need to change content? If yes, it needs a content management system, and that constrains the choice.
- Does it need to talk to systems you already run? Existing systems usually dictate more than preference does.
What Gets Underestimated?
Integrations
Connecting a new site to an accounting system, a CRM, a payment provider or a supplier feed is almost always harder than it sounds. The other system’s limits are discovered during the work, not before it, and they are outside your supplier’s control.
If a project depends on an integration, it is worth investigating that first rather than last, because it is the part most likely to change the plan.
Content migration
Moving hundreds of existing pages or products is a real piece of work, and it is where old URLs get lost. Anything with history needs a URL map so old addresses still resolve.
The states nobody designs
Empty states, error messages, what happens when a payment fails, what a user sees when they have no data yet. These are invisible in a design review and they are what people actually encounter on a bad day.
Browsers, devices and accessibility
A site has to work on an old phone on a poor connection, and for people using a screen reader or keyboard navigation. Retrofitting accessibility is far more expensive than building with it in mind.
Why Does Maintenance Matter More Than People Expect?
Because software does not stay still while you ignore it.
A content-managed site runs a platform, a theme and a set of plugins, each of which receives security updates. A site left unattended for a year is not the same site you launched: it is an older, more vulnerable version of it. Most compromised small-business sites were not targeted; they were running something known to be exploitable.
Maintenance also covers the quiet failures. The most common one we see is a contact form that stopped delivering email months earlier, which nobody noticed because nobody was watching the one thing the site existed to do. Whatever arrangement you make, make sure something checks that the form still arrives.
That ongoing work is what maintenance and security cover, and it is worth deciding who owns it before launch rather than after an incident.
What Should Be Agreed Before Work Starts?
- Scope, and what counts as done. Ambiguity here becomes a dispute later.
- How changes are handled. Scope will change. The question is whether there is an agreed way to price and schedule it.
- Who owns the code, domain, hosting and accounts. This should be you, in writing, from day one.
- What happens after launch. Support, updates, and who to contact.
- Where it will be hosted, and by whom.
Frequently Asked Questions
What is the difference between a website and a web application?
A website presents information. A web application does work: users log in, data is stored and changed, and rules are applied. The difference is not visual, and it is the biggest driver of cost and timeline.
Is WordPress a serious choice for business?
Yes, for content-led sites and many e-commerce ones. Its strength is that anyone can edit it and most developers know it. Its cost is ongoing maintenance, which is a real commitment rather than a formality.
Do I need a custom build or an off-the-shelf platform?
Off-the-shelf almost always wins when it fits, because someone else maintains it. Custom development earns its place when your process is genuinely different from the assumptions the platform makes, not when it is merely inconvenient.
How much does web development cost?
It depends entirely on which of the four categories above the project falls into, and on how much is genuinely unknown at the start. Any figure quoted before the scope is understood is a guess, which is why we scope before quoting.
What happens if my developer disappears?
This is why ownership matters. If you hold the code, the repository, the domain and the hosting, another developer can pick it up. If you do not, recovering the project can cost more than the original build.
Scoping a Build?
The most useful early conversation is not about technology. It is about which of these categories your project actually is, because that decides everything else.
See our named work in the portfolio, browse what we offer, read how we scope on our process page, or get in touch.
