You're refreshing your testimonials wall and you hit one that stings a little: "The automated weekly digest is the single best thing about this product — I forward it to my whole team every Monday." It's specific, it's warm, it names a real person at a real company. It's also praising a feature you sunset two quarters ago. The digest is gone. And now you have a decision that feels like it has no good answer: pull a great piece of social proof, or leave up a quote that promises something a new signup will go looking for and never find.
Most founders resolve this by instinct, and the instinct is usually wrong in one of two directions. Some leave every legacy testimonial untouched because "it's what the customer actually said" — and quietly accumulate a wall of quotes describing a product that no longer exists. Others panic-delete anything that mentions a specific feature, and strip their best, most concrete proof down to generic "great tool!" mush. The right move isn't a blanket rule. It's a two-question test.
The two questions that decide it
Before you touch the quote, ask these in order:
- Would a prospective customer, reading this today, expect to get the thing the testimonial praises?
- If they signed up expecting it, would its absence make them feel misled?
If the answer to both is yes, the testimonial is now a claim you can't fulfill, and it has to change or come down. If the praise is about something that still exists in a different form — or something general enough that no one would go hunting for a specific missing button — you have room to salvage it.
The distinction is the same one that governs a testimonial that makes a specific claim you can't substantiate: the risk isn't the enthusiasm, it's the specific, checkable promise riding along with it. "Best thing about this product" is opinion. "The automated weekly digest" is a factual pointer to a feature. When the feature is gone, that pointer is now a broken promise on your marketing page.
Three situations, three moves
The feature is gone entirely, with no successor. The digest doesn't exist and nothing replaced it. This quote can't stay as-is — a prospect will feel baited. Your options, in order of preference: ask the customer whether the reason they loved the digest still holds ("Do you still get value from how the product keeps your team in sync?") and get a fresh quote about what remains; or trim the testimonial to the part that isn't feature-specific, if a clean, honest fragment survives; or retire it. Don't rewrite the customer's words to praise a feature they never mentioned — that's the line you can't cross.
The feature was renamed or folded into something else. The digest became part of a broader "Monday briefing" dashboard. Here you often can keep the sentiment, but you should update the reference so it points at what actually exists now — and only with the customer's sign-off, because you're changing their words. A light-touch edit like "the weekly summary" instead of the old product name keeps the quote true without misrepresenting them. Keep a record of the approval; consent to the original quote isn't consent to your revision.
The praise is general and the feature was incidental. "This team actually ships improvements — they added the digest I asked for within a month." The star of that quote is your responsiveness, not the digest. The feature is an example, not the promise. You can usually leave this, or trim the clause, because no prospect reads it as "I am guaranteed a weekly digest." Use judgment: if the specific feature is load-bearing to the quote's appeal, treat it like the first case.
What not to do
- Don't silently rewrite the customer's words to name your new feature. Putting praise for a product they never used into their mouth is fabrication, even if you're "just updating it." Any change to a real person's quote needs their okay.
- Don't leave it up and hope no one notices. Someone will — usually a prospect on a sales call who says "I signed up for the weekly digest I saw in your testimonials." That's a worse conversation than a slightly thinner testimonials wall.
- Don't treat this as a one-time cleanup. Features churn continuously. The real fix is a process, not a purge.
Build a light audit into your release process
The reason legacy testimonials rot is that nobody owns re-reading them. Tie it to something you already do: whenever you sunset or rename a feature, grep your testimonials and landing-page copy for the feature name as part of the deprecation checklist. It takes five minutes and catches exactly this problem at the moment it's created, instead of two quarters later during a random refresh. This is the same maintenance discipline behind knowing when to retire a testimonial from your website — social proof is not a write-once asset, it's inventory that ages against a moving product.
The bottom line
A testimonial praising a dead feature isn't automatically trash and isn't automatically fine. Run the two-question test: if a prospect reading it today would expect the thing and feel misled by its absence, it's now an unfulfillable claim and must be refreshed, trimmed, or retired. If the praise survives without the missing feature — because the feature was incidental, renamed, or replaced — salvage the sentiment, get the customer's okay on any wording change, and keep your best proof honest. The goal isn't a wall that's frozen in time. It's a wall that still tells the truth about the product a new customer will actually get.