Every struggling site eventually collects a rebuild quote. Sometimes it’s right. Often it’s the lazy answer priced as the only answer — “rebuild it” requires no diagnosis, and diagnosis is work.

When rescue wins

The site’s structure is sound but its care lapsed: an unpatched but well-built platform, a solid content model under a dated coat of paint, problems that itemize into a fix list. Rescue-and-stabilize typically runs a fraction of rebuild cost and ships in weeks — and preserves the things rebuilds quietly lose: URLs and their search standing, integrations, years of content structure.

When rebuild wins

The platform is a dead end (a proprietary CMS, an end-of-life version where migration is the honest path), the business outgrew the architecture, or accumulated hacks-upon-hacks mean the foundation itself is the problem. Real rebuild cases exist; the tell is that the recommendation comes with a diagnosis attached.

Spotting the ransom quote

Three tells: it arrived without anyone examining the current site; it’s urgent (“this can’t wait”) in ways the facts don’t support; and it bundles you into their accounts and platform going forward. A rebuild quote from someone who can’t tell you what’s wrong with the current build is a bid, not advice.

The cheap way to certainty

A fixed-price assessment prices both roads in writing — what stabilization costs, what migration or rebuild costs, and which one the evidence supports. The fee credits toward whichever you choose, and the report is portable to any developer. Deciding with a diagnosis costs $1,500; deciding without one costs whatever the wrong road costs.