When does a redesign become a rebuild from a cost perspective?

A redesign becomes a rebuild when the required design changes force rewrites of the underlying codebase, backend architecture, or CMS infrastructure. There is no single dollar threshold; the tipping point is technical, not financial, though the cost implications follow immediately once the scope crosses that line.

Redesigns stay in scope when updates are limited to visual and layout changes on an existing, functional backend. They cross into rebuild territory when the project requires a new CMS, significant code refactoring, new database architecture, or performance overhauls that the current platform cannot support. Agencies sometimes blur the terminology, calling rebuilds "redesigns" to make scope sound less intimidating, which creates budget misalignment. A practical test: if the existing backend and CMS will remain intact after launch, it is a redesign. If new architecture is required, it is a rebuild. The cost overlap zone ($15,000 to $75,000) is where most projects live when scope has not been clearly defined, and phased approaches that spread cost across incremental releases reduce the risk of a redesign quietly expanding into a full rebuild.