When to fire your website
There’s a moment in the life of a bad website when patching it stops being thrift and starts being denial. Every business with an aging site eventually faces the question — fix it again, or fire it and start over? Get it wrong in one direction and you torch a perfectly salvageable platform; get it wrong in the other and you pour money into a hole forever.
After fifteen years of inheriting other people’s websites, here are the five tests we actually use.
1. The repair-to-value test
Old-car logic. Add up what you’ve spent on fixes in the last twelve months, plus the quotes you’re looking at now. If the total approaches half the cost of building the site right, the math has already voted — every additional patch is buying time on a platform you’ve outgrown, at a premium. The sneaky part is that hourly patches arrive in small, individually reasonable invoices, so nobody ever sums them. Sum them.
2. The foundation test
Some problems live in the paint; some live in the foundation. Slow pages from bloated images: paint. A site built on an abandoned page builder, a theme from a developer who vanished, or a proprietary platform you can’t export from: foundation. Paint problems are always worth fixing. Foundation problems mean every future dollar is invested in a building that’s slowly sinking — that’s the situation Huntington Hospital was in with a failing proprietary CMS, and the answer wasn’t another patch; it was a rebuild on ground they owned.
3. The embarrassment test
Do people at your company avoid sending prospects to the website? Watch for the tells: sales reps who lead with a PDF instead of a link, “don’t look at the site, it’s being redesigned” said for the third consecutive year, the owner who winces at their own homepage on a conference projector. A website that your own team routes around isn’t neutral — it’s actively taxing every deal. No patch fixes shame.
4. The capability test
List the three things the business needs the site to do next — sell seats to teams, gate member content, take bookings, pass a security review. Can the current platform do them with configuration and reasonable development? Or does each one require fighting the architecture? When the answer to “can we?” keeps being “sort of, with duct tape,” you’re not maintaining a website anymore; you’re subsidizing its limitations. (This is the trap behind a lot of sites that just keep breaking — the breakage is the architecture objecting.)
5. The hostage test
Could you leave? If your content, your customer data, or your design can’t come with you — proprietary builder, vendor-locked platform, developer who holds the only keys — then you don’t own a website, you rent one, and the rent always goes up. Sometimes firing the website is really about firing the lock-in.
The fear that keeps bad websites alive
Let’s name the real reason businesses keep paying the patch tax on sites they already know are doomed: the rebuild feels riskier than the rot. What about our Google rankings? Our content? The forms wired into the CRM? Better the devil you know — said every owner of a slowly failing platform ever.
The fear was earned a decade ago, but it’s overpriced today. A competent migration preserves your URLs or redirects them one-to-one, carries content over programmatically rather than by intern-with-a-clipboard, and rebuilds integrations on purpose instead of by accident. Done right, rankings don’t just survive a rebuild — they usually improve within a quarter, because the new platform is faster and cleaner than the one Google had been tolerating. The risk worth fearing isn’t the move; it’s the unmaintained status quo, which fails eventually with no migration plan at all.
If it’s a fix: fix it properly
Plenty of “hopeless” sites fail every test except the foundation one — and those are rescues, not rebuilds. Stabilize, patch the real holes, then put the site on a care routine so it never decays again. That’s a few weeks of work, not a few months, and it’s exactly what our site rescue is for.
If it’s a firing: make the next one boring
If the site fails the foundation or hostage tests, stop investing in it today — every patch dollar is sunk. But learn from the autopsy: the next site should be built on an open platform you own outright, by a team that sticks around to run it, with the maintenance plan in place from day one rather than bolted on after the first crisis. Websites don’t die of old age; they die of neglect and bad foundations. Solve both and you never have to fire one again.
Not sure which side of the line your site is on? That’s literally what our free systems review answers — a plain-English verdict, fix or fire, with the reasoning shown. We’ll tell you the truth even when it talks us out of a bigger project.