Owners say “we need a redesign” when they mean “the website is not making the phone ring.” Those are different jobs. A redesign changes how the current pages look. A rebuild changes the platform, the URLs, the templates, and usually the CMS. Choosing wrong wastes a quarter.
Redesign when
- The stack is maintainable and fast enough.
- The information architecture still matches how people buy.
- Search Console does not show a crawl or indexing disaster.
- The problem is voice, hierarchy, and the first screen — not the pipes.
Rebuild when
- Nobody on the team will edit the CMS without breaking it.
- The theme / plugin pile is the reason you are slow or hacked.
- Important pages are client-rendered empty shells.
- You need new templates (services, locations, journal) the old system cannot grow.
- You are merging brands or moving off a vendor who owns your content.
A simple test
Time how long it takes a non-developer to update a price and publish. Time a quote form on a mid-range Android phone. Look at the top ten landing pages in Search Console. If two of those three make you wince, you are in rebuild territory. If only the homepage looks dated and the rest converts, spend the money on the pages that already work — that is a redesign, and it should be cheaper.
The risk is always in the CMS and the redirects, not the design.
Our web modernization practice assumes rebuild unless discovery proves otherwise. The audit in week one is how we keep you from buying the wrong project.
Continue in the practice: related service.