Rebuild or refresh? How to tell the difference.
Not every site problem needs a full rebuild. But sometimes a refresh is just delaying the inevitable. Here's how I make the call.
When someone tells me their website isn't working for them, my first question isn't 'what should I build?' It's 'what's actually broken?' Because the answer changes everything about what I'd recommend, and how much of your money I'd spend getting there. Plenty of people walk in asking for a full rebuild when a good refresh is all they need. Every so often it's the other way around.
Signs a refresh is enough.
If the bones of the site are sound, the navigation makes sense, the content is organized logically, and the checkout or contact flow works, then most problems can be solved with a design refresh. Update the visual language, fix the typography, tighten the mobile layout, rewrite the copy that's been sitting there untouched since 2019. A refresh done well can feel like a brand new site without the cost and the risk of starting from scratch.
Refreshes work best when the underlying platform still fits the business. If you're on Shopify and it's doing what you need, there's no reason to move. Same with a WordPress site that's only gone visually stale. You'd be surprised how far new photography, a calmer grid, faster load times, and honest copy will carry a site people had already written off. Fix what's broken, not what isn't.
Most of the time, when a shop tells me the site 'feels old', it isn't old. It's slow and cluttered. A couple of weeks on images, layout, and speed, and it reads like a different business. A full rebuild would have cost several times as much and solved exactly the same problem.
Signs a rebuild is necessary.
A rebuild is the right call when the platform is wrong for where the business is going. When the codebase has been patched and modified so many times that adding one new thing breaks two others. When the site is structured the wrong way for the content it now holds: a blog glued onto a landing-page template, a webshop crammed into a CMS that was never built for commerce, a booking system held together by plugins that each need their own update schedule and occasionally fight each other.
The tell I look for is compounding cost. On a healthy site, a small change is a small job. On a site that needs rebuilding, every small change turns into an archaeology dig: you touch one thing and lose a day working out what else depended on it. When maintenance starts costing more than the feature is worth, the foundation is the problem, not the feature.
A refresh on a broken foundation is just expensive wallpaper.
The questions I actually ask.
When I can't tell from the outside, I work through the same short checklist. You can run it yourself before you call anyone.
- Can you add a normal new page or product without something else breaking? If yes, the foundation is probably fine.
- Is the platform something a normal developer can pick up, or a custom system only the original builder understands?
- Is the thing you hate about the site visual, or structural? Ugly is a refresh. Wrong-shaped is a rebuild.
- Picture the business in two years. Does the current setup still fit, or are you already working around it?
- How often are you paying someone to fix things that used to work? Rising maintenance bills are the foundation talking.
There's usually a middle path.
It's rarely all or nothing. Often the right move is to refresh now to stop the bleeding, then plan a rebuild for when the budget and the timing line up. Or rebuild the one part that's genuinely broken, the checkout, the product pages, the CMS, and leave the rest alone. You don't have to burn the whole house down because one room is on fire. A good plan sequences the work so you never pay to build something you'll throw away in six months.
The honest conversation.
I'll always tell you what I actually think. If a refresh will solve the problem, I'll say so, even when a rebuild would be more money for me. Trust is the only thing that makes this work over the long run, and it's a small industry: the fastest way to kill a business like mine is to sell someone a rebuild they didn't need and let them find out later.
If a rebuild is genuinely necessary, I'll explain why in plain language: what the current site can't do, what a new one will, and what the realistic cost and timeline actually look like. No upselling features nobody asked for, no jargon to scare you. You'll understand the decision well enough to explain it to someone else, because it's your money and your site.