How we scope a website before quoting it
What a useful website scope needs to settle before a quote means anything: pages, content, evidence, systems, responsibilities and the commercial job.
/ In this article:
Quoting a website from a page count is like quoting a building from the number of rooms. It says nothing about what needs to happen inside them, what already exists or who is responsible for supplying the missing pieces.
A quote is only as useful as the scope behind it
Before we attach a number to a project, we need to understand the commercial job, the audiences, the pages, the content and the systems involved. Otherwise, the number is either padded for uncertainty or low enough to become a problem later.
A redesign will not fix a weak argument. It made the design work faster, because there was nothing left to argue about.
/ TITANMATTER
The scope turns those unknowns into decisions. It shows what is included, what is not, what we need from the client and which assumptions would change the price if they turn out to be wrong.
What we check first
Four questions come up every time:
- What must the site change for the business?
- Which audiences and decisions does it need to support?
- Which content, proof and integrations already exist?
- Who owns feedback, approvals and delivery on each side?
What a scope document contains
A scope we are willing to quote against names the pages, the argument each page makes, and the evidence that argument needs. It is usually two or three sides of A4. If it cannot be written that briefly, the project is not understood well enough to price.
Pages and their jobs
Every page gets one sentence describing what a visitor should be able to do or believe by the end of it. Pages that cannot be described this way are usually pages nobody needed.
Evidence
Claims need proof: case studies, numbers, named clients, screenshots of real work. Gathering that is often the longest part of a project, and it is the part most likely to be discovered late if nobody scoped it.
Why this is worth doing first
Scoping properly costs a week. Discovering mid-build that the site needs eleven case studies nobody has written costs a month, and it arrives at exactly the point where everyone has run out of patience.
In short
Decide what the site has to prove. Write down how each page proves it. Then, and only then, design something around that argument — because the design will be faster, cheaper and better when there is nothing left to argue about.
