There is a peculiar kind of problem that only shows up when you're paying attention. A testimonial on your homepage is doing exactly what a testimonial should — it names a specific thing your product does, in a customer's own words, and it lands. The catch is that the specific thing it praises is a feature you've already decided to retire. Maybe you're folding it into a bigger workflow, maybe usage never justified it, maybe it's being replaced by something better. The decision is made internally; the sunset just hasn't happened yet. And so you have a quote that is completely honest today and will become quietly misleading on a date you already have in your calendar.
This is a better problem to have than most, because you've caught it early. The usual version of this — dealing with a testimonial that praises a feature you've already removed — is a cleanup job you do after the fact, often after a prospect has already clicked a link that goes nowhere. Catching it before the deprecation ships means you get to decide what happens on your own schedule, calmly, instead of scrambling. The whole point of handling it now is to never end up handling it later.
Why "leave it until launch" is the wrong instinct
The tempting move is to do nothing until the feature actually goes away. The quote is honest right now, the reasoning goes, so why touch it early? Deal with it on sunset day like everything else.
The problem is that sunset day is the worst possible day to be editing testimonials. You'll be busy shipping the change, updating the docs, answering the support tickets from customers who also liked the feature, and writing the changelog. A quote buried three sections down your homepage is exactly the kind of thing that gets forgotten in that scramble — and forgotten testimonials are how you end up with social proof that praises a button no one can find. Worse, if the testimonial links to the feature's page and that page 404s, you've turned a trust signal into a broken promise at the exact moment prospects are most likely to be evaluating you.
Handling it early costs almost nothing and removes the entire failure mode. You're not editing under pressure; you're editing with a clear head and a known date.
First, sort what the testimonial is actually doing
Not every quote that mentions a doomed feature needs the same treatment. Before you touch anything, figure out which of these you're holding:
- The feature is the whole point of the quote. "The one-click export is the reason we switched — it saved us an entire afternoon every week." Take away the export and there's no testimonial left. This one needs real handling.
- The feature is mentioned in passing. "The team is responsive, the pricing is fair, and the export is handy." The export is one item in a list; the quote survives without it. This is a light trim, not a crisis.
- The feature is being replaced, not deleted. The customer praised something that's becoming a better version of itself under a new name. This isn't a loss at all — it's an update, and the same logic as placing a testimonial next to the feature it praises still applies once you know the new name.
The mistake is treating all three as the same emergency. Most testimonials that mention a deprecated feature fall into the second bucket and need nothing more than a small, honest edit outside the quotation marks.
The options, from lightest to heaviest
Once you know what you're holding, pick the lightest move that keeps the quote honest.
Trim the mention (for passing references). If the feature is one item in a list, you can cut it — as long as cutting it doesn't distort what the customer meant. Removing "the export is handy" from a three-part compliment leaves a true, if slightly shorter, quote. Stitching the two remaining fragments into something more enthusiastic than the customer said does not.
Add a dated note outside the quote (for central praise you want to keep). If the feature is the quote and the customer's words are too good to lose, you don't have to rewrite them — you leave them exactly as said and add your own honest framing beside them: "— from 2025, when export was a standalone feature; it's now built into Reports." The customer's words stay theirs. The context that keeps a prospect from chasing a dead link comes from you, not from putting new words in their mouth.
Swap in a different testimonial (for central praise you're ready to retire). Sometimes the cleanest answer is that this quote has done its job and it's time to feature a different one. If the deprecation is a good moment to refresh your social proof anyway, retire the quote to an archive and promote one that praises something you're keeping. No edit, no note, no risk.
Reach back out (when the customer might re-testify). If the customer who praised the old feature is likely to love the replacement, the deprecation is a natural reason to ask for an updated quote. "We're rolling the export you liked into a bigger Reports feature — would you be open to a quick line on how the new version's working for you?" A yes gets you a current testimonial for a current feature. A no costs you nothing you weren't already going to lose.
The one thing you must never do
Do not edit the feature name inside the quotation marks to point at the replacement. It feels harmless — the customer would probably like the new version too, so why not update "export" to "Reports" and keep the quote alive? Because they didn't say "Reports." They praised the thing that existed when they spoke, and rewriting their words to endorse a feature they never used is a small forgery, even when your intentions are good. If you need to connect their praise to the new name, do it in brackets or in a note outside the quote — "the export [now part of Reports]" — never by silently changing what appears between their quotation marks.
The line is the same one that governs every testimonial edit: you may change how a quote is framed, but not what the customer claimed.
A simple pre-deprecation checklist
Before the feature ships its sunset, run every testimonial that mentions it through three questions:
- Does the quote survive without the feature? If yes, trim or leave it. If no, it needs a note, a swap, or a fresh ask.
- Does it link anywhere that's about to break? Any testimonial pointing at a feature page that will 404 must be re-pointed or unlinked before the page goes down, not after.
- Is this a moment to refresh instead of repair? If the quote was aging anyway, the deprecation is a clean excuse to promote something newer.
Do this in the same sprint as the deprecation itself, and the testimonial never gets a chance to become a liability. The whole advantage of catching it early is that "handle it later" never has to happen — the quote is honest the day before the feature leaves, and still honest the day after, because you did the small thing while it was still small.