"It still works" is the hardest objection to argue with, because it's true. The site loads. Forms submit. Nobody's shouting about it. That's exactly why the case for a rebuild has to be made on numbers the objection doesn't cover, not on taste.
Most rebuild pitches lose right here, arguing that the current site looks dated or the CMS is annoying. Both might be true and neither moves a director. "Still works" is a real answer to "does it work". The case has to answer a different question: what is it quietly costing to keep working this way.
The objection is correct, and incompleteWhat "still works" doesn't measure
A site that hasn't fallen over has three things it doesn't tell you. What conversion rate it would get if it matched what a rebuilt version typically achieves. What every recent campaign actually cost in dev-ticket time to launch a page that a modern setup would have shipped same day. And what got quietly dropped from the roadmap because nobody wanted to fight for a release slot. None of that shows up as an incident. All of it shows up on a spreadsheet, if someone builds one.
Not "the site is old." "We spent 340 dev hours on landing pages last year that a rebuilt setup would ship in a day each." One is an opinion. The other is a number a director can put next to a budget line.
The three numbers worth having in the room
Cost per page shipped, right now. Add up dev hours, delayed launches, and any external help called in, across the last six to twelve months of pages and campaigns. Divide by pages shipped. That's your baseline.
Cost per page under a fixed alternative. A Sprint pack or a Replatform quote gives you a comparable number priced by the page, not by the hour, so it sits next to the baseline without translation.
Time-to-market lost on the campaigns that mattered. Not every delayed page costs the same. The one tied to a product launch or a seasonal window costs more than a slow blog update. Pick two or three real examples from the last year and put a number on what the delay itself cost, not just the build.
How to actually present itOne slide, one number, then the evidence
Whatever the deck looks like, the first slide should carry the whole story: the payoff number and the recommendation, together. If the only slide anyone reads is the first one, they should still know what you're asking for and what it's worth. Every slide after that is proof, not build-up. Starting with context, or with the plan, buries the number the director actually needs to make the call, and gives the "it still works" objection room to land unchallenged before you've made your case.
Lead with the cost of staying still, not the appeal of moving. "Here's what inaction cost us last year" argues with a number. "Here's how nice the new one would be" argues with a feeling, and feelings lose to "it still works" every time.
Nobody signs off a rebuild because the old site looks tired. They sign off because staying still has a number attached to it now.Where this case falls apart
Don't skip the honest version
Sometimes the numbers genuinely don't support a rebuild yet. Low page volume, a small campaign calendar, or a CMS that's clunky but rarely actually blocks anything, and the fixed-cost alternative doesn't clear its own bar. Building the same three numbers and finding they don't justify the move is a useful outcome too. It's a better answer than guessing, and it's the answer that keeps the case credible the next time the numbers do add up.
"It still works" is a fact about the present. The case for a rebuild is a fact about the cost of the last twelve months. Bring the second one, not an opinion about the first.
Keep reading: How a website redesign works · Website and CMS migration