How Much Does a Business Website Really Need to Do?
Every website brief is really a scoping decision. Getting that decision right matters more than any design choice you will make afterwards.
Oaktree Technologies
The brief that grows
A business asks for a simple website. By the third meeting, the list includes a blog, a customer login area, an online store, live chat, a quotation calculator and a careers page. The project stalls. Nothing gets launched.
This is the most common way website projects fail: not through bad design or bad code, but through a scope that quietly outgrew the business it was meant to serve.
Three jobs, in order
Almost every business website exists to do three things. They are worth separating, because they cost very different amounts and they are not equally urgent.
1. Be found
Someone is looking for what you sell. Can they find you, and do they land somewhere that makes sense?
2. Be believed
They have found you. Do they trust you enough to make contact? This is about clarity, evidence and tone — not about volume.
3. Be used
They want to act: book, buy, enquire, request a quote, download something. Can they do it without friction?
Most businesses need all three, but not all three at the same depth. A professional services firm might need the first two done extremely well and the third to be a simple form. A retailer might need the third to be a full checkout. The depth is the decision.
Match the site to the stage of the business
The right scope for a business that is still finding its first customers is not the right scope for a business with steady demand and a growing team.
A young business usually needs clarity more than capability: a site that explains what it does, for whom, and how to start. Speed of launch matters more than completeness, because the site's real job is to start conversations and gather evidence about what customers actually want.
An established business usually needs capability more than clarity: systems that remove manual work, handle volume, and connect to how the business already operates.
Building the second when you need the first is expensive. Building the first when you need the second is frustrating.
The features that rarely earn their place early
Some things sound essential in a planning meeting and turn out to be premature.
A blog is valuable when someone will genuinely write it. A customer login area is valuable when customers need one, not when it sounds professional. Live chat is valuable when someone is available to answer it. An online store is valuable when the business is ready to process orders at volume and handle returns.
None of these are bad. They are simply not first. Adding them before the foundation is set usually means the foundation gets less attention.
How to judge a quote
A price is only meaningful next to a scope. When you receive a quote, the useful question is not "is this expensive" but "what exactly is being built, and what is it expected to achieve".
A useful quote should tell you:
- what pages and features are included
- what is explicitly not included
- how content will be produced
- how long it will take
- what happens after launch
If a quote cannot answer those, the number is not really a price. It is a guess.
What you are actually paying for
There is a version of website work that is essentially assembly: a template, some colours, the client's text dropped in. It has its place, and it is cheap for a reason.
There is another version that is closer to business work: understanding what the business needs to communicate, deciding what to build and what to leave out, writing content that sounds like a human being, and making sure the thing is fast, findable and maintainable.
The second version costs more and usually earns it back faster. The first version is often the more expensive decision in the long run, because it has to be redone.
The discipline of leaving things out
The most valuable scoping skill is subtraction. A site that does three things properly will outperform a site that does twelve things badly, and it will launch months earlier.
That means agreeing in advance what this version will not include — and writing it down. A deferred feature is not a failure. It is a decision made deliberately, and the next version will be better for it.
A simple way to decide
Write one sentence: what should a visitor be able to do after spending five minutes on this site?
If the answer is "understand what we do and contact us", you are describing a focused, fast, affordable website. If it is "place an order and track it", you are describing a product. Both are legitimate. They are simply different projects with different timelines, and confusing the two is what makes budgets go wrong.
Decide the sentence first. Everything else follows from it.