The Short Answer
Sometimes a focused refresh delivers 80% of the value at 30% of the cost. Sometimes it just delays the inevitable. The expensive mistake is choosing a rebuild when a refresh would have done, or the reverse. A short audit tells you which side of the line you are on.
What a Refresh Includes
A refresh keeps the existing foundation and improves the layer visitors actually experience. In practice that means new copy on the highest-traffic pages, an updated visual layer within the existing structure, speed work, accessibility fixes and repaired conversion paths. It is fast, low-risk, and often delivers most of the perceived improvement.
When a Refresh Is the Right Call
A refresh fits when the CMS is modern and supported, the pages load acceptably on mobile, the content can be edited by your team, and the structure already works. The goal is to improve the presentation and the conversion paths without touching the platform. It typically takes weeks, not months.
What a Refresh Cannot Fix
A refresh cannot rescue an abandoned CMS, add a mobile layout where none exists, or make unstructured content translatable. If the foundation is the problem, repainting the front door does not help. Knowing the boundary of a refresh is what prevents the half-measure.
What Demands a Rebuild
A rebuild is necessary when the foundations are the problem rather than the presentation. Abandoned CMS platforms, no mobile layout underneath the styling, content that cannot be structured or translated, and integrations that block any meaningful improvement all fall into this category. Trying to refresh a broken foundation produces a site that looks new and behaves old.
The 15-Minute Test
Open your site on a phone. Try to edit a paragraph in your CMS. Check whether it loads in under three seconds on a normal connection. Then ask whether it would accept a second language without a rebuild. If you can answer all four confidently, you are a refresh candidate. If any one of them is embarrassing, start planning the rebuild.
What Does the 15-Minute Test Reveal?
The four questions cover mobile, editing, speed and multilingual readiness. Each maps to a foundation layer: the front end, the CMS, the hosting performance, and the information architecture. A fail on any one points to the layer that must change, not to a vague redo.
Can I Combine Both?
Yes. A common and sensible path is a phased rebuild: refresh the highest-traffic pages now to stop the bleeding, then rebuild the foundation in a second phase. The phased approach controls risk and spreads cost, while avoiding the site-that-looks-new-but-behaves-old trap.
Cost and Timeline: Refresh vs Rebuild
A refresh typically costs a fraction of a rebuild and takes weeks, while a rebuild costs more and takes two to three months. The decision is not really about price; it is about whether the foundation blocks your goals. If the foundation is sound, paying more for a rebuild wastes budget. If it is rotten, a refresh is a delay that still costs money.
What If I Choose Wrong?
The good news is that both paths are reversible in stages. A refresh that under-delivers can be followed by a rebuild; a rebuild scoped too small can be extended. The worst outcome is choosing the expensive option for the wrong reason and then discovering the root cause was never addressed.
Conclusion
Neither option is universally correct, and the expensive mistake is choosing the rebuild when a refresh would have done, or the reverse. A short audit will tell you which side of the line you are on, and we are happy to run one before you commit budget.