Scoping and estimating a website project

Scoping is the stage where what was learned in discovery gets turned into a written, itemised description of exactly what will be built — and an estimate or quote is only meaningful once that description exists. A number without a scope behind it cannot be compared to any other number, because there is no way to know whether the two suppliers are pricing the same thing.

What a scope document for a website project actually contains

A proper scope is specific enough that both sides could hand it to a different supplier and get a comparable price. That means it states, at minimum:

Scope item	Why it has to be explicit
Number of unique page templates	Ten pages using one template costs far less than ten pages each designed separately
Number of design concepts and revision rounds	The most common source of “scope creep” disputes later in the project
Who writes the content	Whether the supplier is writing copy or only loading content the client supplies changes both cost and timeline
Platform	WordPress, Shopify, Squarespace and a custom build carry different licensing, hosting and maintenance implications
Functionality beyond static pages	Booking systems, ecommerce, membership areas or third-party integrations are priced separately from page design
What is explicitly excluded	Ongoing SEO, copywriting, photography and paid advertising are commonly assumed included and commonly are not

The last row is where most disputes originate. A scope that only lists what is included, without stating what is deliberately excluded, leaves the door open for both sides to have a different mental picture of the same project.

Estimating versus quoting

An estimate is a range, produced early, against a scope that may still move — useful for budgeting, not for signing. A quote is a fixed figure against a scope that has been written down and agreed by both sides. Confusing the two is a common source of dispute: a client who received an early estimate and treats it as a binding quote later feels misled when the final figure differs, even though the scope itself changed in the interim (more pages requested, a booking system added, a platform switched).

A supplier who is candid about this distinction will label an early figure “estimate, subject to a written scope” rather than presenting a round number as though it were final. If a supplier’s first figure arrives before any scope conversation has happened at all, it is a guess dressed as a quote, and it should be treated accordingly.

How estimating actually works

Most suppliers estimate against a rate per page template, adjusted for complexity, plus fixed costs for anything functional (a booking system, a payment gateway, a custom search). A ten-page brochure site using one or two templates is priced very differently from a ten-page site where every page has a unique layout, even though the page count is identical — because the design effort is what scales, and effort is what a supplier is actually trying to calculate, not the page count on its own.

Timeline estimates follow the same logic in reverse: a supplier estimating how long a build will take is really estimating how long content collection, design rounds and revisions will take, because the actual build work is comparatively predictable once scope is fixed. This is why timeline estimates are usually wrong in the direction of underestimating — the variable that is hardest to estimate (how quickly a client will supply content and feedback) is treated as fixed. See content collection for why this specific stage is the most common cause of a blown timeline, independent of how well the original estimate was made.

What “scope creep” actually is, stated plainly

Scope creep is any addition to the agreed scope that is not accompanied by an adjustment to the price or the timeline. It is not inherently a client problem or a supplier problem — it happens on both sides. A client adding “just one more page” without expecting to pay for it is scope creep. A supplier who quietly absorbs extra revision rounds to avoid an awkward conversation, then makes it up by compressing quality assurance later in the project, is also scope creep, and it is the less visible kind because the client never sees it happen.

A written scope document is the actual defence against both directions, because it gives both sides a fixed reference point to point back to when something is proposed that was not in it.

Comparing pricing and quotes from different suppliers

Two quotes cannot be honestly compared unless the underlying scope is comparable. Before comparing a dollar figure, check: the same number of pages counted the same way, the same number of design concepts and revision rounds, whether content writing is included in both or neither, and whether the same platform is assumed. A lower quote that includes fewer revision rounds or excludes content writing is not necessarily the cheaper option once the excluded items are added back in elsewhere. General information on what the resulting figure is actually paying for, once scope is defined, is on what drives the cost of a website — this page covers how the scope behind that figure gets defined, not what the figure itself should be.

Where scoping and estimating sits in the project planning sequence

Scoping and estimating follows discovery and precedes everything else — wireframing, design and build are all conducted against the scope agreed here, which is why a scope revisited mid-project reliably pushes every stage after it. See discovery for what happens immediately before this stage, and content collection for the stage that most often tests whether the scope’s timeline assumptions were realistic.