How to scope a website rebuild before you ask for quotes

Separating what's changing from what's staying the same

You've probably already been told, or told yourself, that the site needs a rebuild. What hasn't happened yet is deciding exactly what "rebuild" means for your particular site. That gap is precisely where scoping starts, before anyone else gets involved.

Go through the current site and sort it into two piles: what's staying roughly as-is, and what's genuinely changing. Maybe the blog stays untouched, but the homepage gets rebuilt from the ground up. Maybe every page changes visually while the content underneath stays the same. Writing that split down, even loosely at first, is the real first step.

This doesn't need to take long. Twenty minutes with a notebook or a blank document is enough for most small sites. The point is having it written, not making it perfect.

Don't worry about getting the split exactly right on the first pass. It's a working document. You can move something from one pile to the other once you've thought about it more.

Taking an inventory of the current site first

Before anyone can quote you accurately, they need to know what actually exists right now. That means a real list: how many pages, what kind of content sits on each one, which pages carry forms or other functionality, which pages barely get any visitors at all.

This feels tedious, and honestly, it is a little. It's also the difference between a quote based on your actual site and a quote based on someone's rough guess at what a typical small business site tends to look like.

Open your site's admin panel or click through it page by page if you don't have that access. List each URL in a spreadsheet with one line of notes. It's slow work, but it's work only you can do accurately.

The content side of this inventory, deciding what gets kept, merged, or cut, connects directly to what happens to your old content during a website redesign, worth reading alongside this step.

Listing features, not just pages

Pages are the visible part of a website. Features are the part people forget to mention until halfway through a project, when it's already more expensive to add them. A booking calendar. A payment form. An email signup that feeds into a separate marketing tool. A photo gallery pulling from another platform automatically.

Each of those is a distinct piece of work, and each one is something anyone quoting your project genuinely needs to know about upfront. Leaving them out of the scope doesn't make them free. It just means they show up later as a surprise, usually with a price tag newly attached.

List every tool your current site talks to, even the small ones. A chat widget. A review plugin. A newsletter signup. Small pieces add up to real work for whoever's building the new site.

How a fuzzy scope turns into a fuzzy price later

Think about what actually happens when three different people read the words "redesign the site" with nothing else attached. A vague scope doesn't produce an average price. It produces a wide spread of prices from different people, because each one is quietly quoting a different imagined project in their head.

One quote assumes five simple pages and no booking tool at all. Another assumes twelve pages and a full calendar integration, because that's what their last similar client happened to need. Neither person is wrong exactly, because neither was actually told what you want. The spread in the quotes you eventually get back often just reflects the spread in what each person guessed.

A tighter scope narrows that spread considerably. It won't make every quote identical, since people still price their own time differently, but it stops the gap from being pure guesswork.

How scope specifically drives price upward is its own topic, covered fully at what drives the cost of a website.

Writing it down before the first conversation with anyone

Once you've got the inventory and the feature list assembled, put it all into one short document. It doesn't need to be formal or polished. A page or two covering what's changing, what's staying, what features are needed, and roughly what the current site looks like today is genuinely enough.

Send that same document to everyone you're getting a quote from, without editing it between conversations. That single habit does more to make quotes comparable than almost anything else in this whole process. It also saves you from repeating yourself on every single call.

Keep a copy for yourself too. When the project is underway and someone asks whether a feature was ever agreed to, the original document settles it quickly and without an argument. Store it somewhere you'll actually find again, not buried in an old email thread nobody can search.

Using the scope to compare quotes evenly

With a shared scope document in hand, differences between quotes finally start meaning something concrete. If one number lands far below the others, ask what's been left out rather than assuming it's simply a better deal. A lowball quote and a genuinely lean, honest one can look identical on paper until you actually ask what's included.

A finished scope also becomes the thing you use to evaluate who to hire, not just what to pay them. Ask each person how they'd approach the specific items on your list, not just for a total number. Their answer tells you more than the price does, since anyone can name a number but not everyone can walk you through a plan.

That evaluation process is covered at how to choose who builds your website, and this whole scoping step sits inside the larger picture laid out at how to redesign a website without losing what works.

More from the blog

All posts