Five factors move a website rebuild budget more than any other: the page count, the state of existing assets, the state of the copy, the integrations that have to keep working, and the search foundations that get rebuilt alongside the site. Two rebuilds with the same page count can demand very different work once those five are named.
Buyers usually ask for a number before anyone has named the work. The useful sequence runs the other way. Name the factors, shape the scope around them, and the conversation becomes about defined work instead of estimates attached to a page count.
Use the five sections below to read your own situation before you talk to any studio.
Page count decides how many things get made
Every page in the route plan needs copy, design states, responsive behavior, metadata, and review. The page count also drives what surrounds the pages: navigation, internal links, redirects, and launch checks all grow with it.
A rebuild that keeps ten routes is a different project from one that consolidates forty routes into twelve, even though the final counts look similar. Consolidation means deciding what dies, mapping the old paths, and writing the redirects. Keyframe0's website work starts with the route plan and message hierarchy before any page gets built, because the route plan is where the real size of the project lives.
Existing assets decide how much gets made twice
Rights-cleared identity, photography, and source files shorten the work. Missing, expired, or unlicensed assets turn into production: new art direction, new imagery, new exports, and new approvals for all of it.
Three questions settle this factor. What exists? Who owns it? Can it be handed over as source files rather than screenshots? A logo as a flattened image is a different job from a logo as a source file, and the second one is smaller.
The state of the copy decides whether the message gets rebuilt
Copy state is the factor buyers underestimate. If the business facts are settled and the writing is close, the rebuild carries the message across. If pages contradict each other, or the offer changed and the site still explains the old version, the message system gets rebuilt first.
A message rebuild runs through everything: the copy on every page, the metadata, the structured data, and the questions the intake asks. The rebuild decision guide covers how to tell a message problem from a page problem.
Integrations decide what has to be carried and tested
A form that feeds a CRM, a login, payments, a required platform, a domain structure that must survive the launch: each of these has to move across the rebuild and get tested in the finished site.
Integrations rarely add visible pages. They add care, testing, and boundary-writing in the scope, and every one of them should be named as a fixed constraint before work starts. What a website rebuild should include lists where these belong in a complete scope.
Search foundations decide whether the rebuild preserves what works
Titles, descriptions, structured data, the sitemap, discovery files, and the direct answers on your pages: a rebuild either carries these forward deliberately or loses them at launch. Redirects for every changed path belong in the plan too.
If the current foundations are thin, the rebuild is the right moment to build them, and the scope should say so. Keyframe0's SEO and AI-search work builds visible answers, structured data, discovery files, metadata, and internal links from facts the business can support.
Ranking, traffic, and virality guarantees stay outside the work. Nobody honest sells those.
How the factors compound
The five factors rarely move alone. Ten pages with settled copy, clean assets, and no integrations is a small scope. The same ten pages with a rebuilt message, missing sources, and two integrations is a larger one, and the difference is invisible in a page count.
This is the honest answer to why two rebuilds of similar size produce different scopes. The page count is one factor of five, and rarely the largest.
What shrinks the scope
Decisions made before production shrink work in every lane: settled business facts, rights-cleared source files, one approver, and constraints stated in writing. The Website Rebuild Scope Mapper turns your answers on these five factors into a written brief you can hand to any studio.
Work with us to send the page count, what exists, the state of the copy, the integrations, and the fixed constraints in writing, and get the scope back in writing too.