Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Product Marketing › Launches

Retiring a Feature or Product: Telling Customers

How to retire a feature or product with customers: who relies on it, the alternative, a phased timeline, messages by impact and every claim that must change.
Guideintermediate12 min readUpdated

Why retiring a feature is a launch in reverse

A launch adds something and asks customers to start using it. A retirement removes something and asks customers to stop, move their work, and keep trusting the product while they do. Most of the launch machinery applies in reverse: there is an audience segmented by impact, a message, a sequence of channels, internal readiness, and a set of assets to change. The launch planning and tiers guide supplies the plan format, the owners and the bill of materials; a retirement deserves the same discipline, scaled to how many customers depend on what is going. In the product life cycle, a retirement is how the decline stage ends, and the signals that come before it give product marketing time to prepare the telling.

The difference is the emotional direction. A launch gives customers a reason to be pleased; a retirement gives them a reason to look at alternatives. Customers who find out from a missing button, or from an email that buries the change under a list of improvements, conclude that the business does not respect their work, and that conclusion spreads to everything else it tells them. Customers who hear early, in plain words, with a credible way forward, usually accept the change even when they dislike it.

It also helps to be clear about what kind of decision this is. The one-way and two-way doors framework sorts decisions by how hard they are to undo. Inside the business, retiring a feature can look like a two-way door: the code could be restored. For a customer who depends on it, removal is a one-way door, because once they have rebuilt their process elsewhere they rarely come back. That asymmetry is the case for phasing the retirement, so that it stays reversible for as long as possible, and for spending more care on the customers who rely on it most.

Who relies on it, and for what

Before the decision is final, product marketing builds the picture of who will be affected. Start with usage: which accounts use the feature, how often, and how recently, broken down by plan, size and segment. Then add what usage alone does not show: which accounts bought because of it, which were promised it in a sales process, which have it written into a contract or a tender answer, and which rely on it for something they cannot easily do another way.

Usage says who; the job says why. The jobs-to-be-done framework reframes the question from who uses a feature to what progress they are trying to make with it. Two accounts can use the same feature for different jobs, and the job decides whether the replacement will serve them. A reporting feature used by one customer to check figures weekly and by another to produce the board pack each month is two retirements, not one. A handful of short conversations with heavy users, asking what they use it for and what they would do without it, usually reveals jobs the usage data hides.

The result is a short evidence note for the decision-maker: who uses it, for which jobs, which accounts carry commitments, and what each group would lose. It does not argue for or against retiring the feature. It makes sure the decision is taken with the cost to customers visible, and it becomes the basis of the segmentation used for every message that follows.

A replacement, a workaround or nothing

Customers losing a feature will ask one question first: what do I do instead? There are three honest answers.

AnswerWhat customers are offeredWhat the business must prepare
A replacementA new feature, product or integration that does the same job, sometimes betterProof that it does the job, a migration path, help content and, where it costs more, the price terms
A workaroundAnother way to do the job with what already exists in the product or elsewhereStep-by-step help for each job the feature served, tested by someone outside the team
NothingThe job is no longer supportedA plain statement, the reason, an export of the customer's data and work, and time to move

The answer must be true for each job, not just for the feature in general. A replacement that serves the most common job but not a rarer one is a replacement for some customers and nothing for others, and those customers need to be told which they are. Where the replacement costs more, or sits in a higher plan, the change is also a price change for the people affected, and the price change guide treats a withdrawn plan as one of its impact groups and covers the options, protected periods and notice that go with it.

Data comes with every answer. Customers need to be able to get their records, settings and work out of the feature in a usable form before it goes, and the export should be available, tested and documented before the first customer is told.

A phased retirement timeline

A retirement runs in phases, each of which can be paused or reversed if the evidence says the plan is wrong. The order below is common practice; how long each phase lasts depends on the contracts, the jobs involved and the effort customers need to move, and this guide sets no durations.

PhaseWhat changesWho is toldStill reversible?
Decision and preparationNothing customers can see; replacement, export and help content are readiedInternal teamsYes, fully
No new usersThe feature is no longer offered to new customers or new accountsSales, support and the heaviest users in personYes; existing customers are unaffected
AnnouncementEvery affected customer is told the date, the reason and the optionsAll affected customers, by impact groupLargely; the date can still move
MigrationCustomers move to the replacement or workaround with help; exports are openReminders to those who have not movedPartly; dates can be extended for groups that need it
Read-onlyThe feature can be viewed and exported but not used to create new workRemaining users, directlyPartly
RemovalThe feature is gone; exports may remain for a stated periodA final confirmationNo

Two habits keep the timeline credible. Every date published to customers is a date the business intends to keep, so the announcement waits until the replacement and the export work. And the move between phases is a decision, taken by a named owner against what was planned: how many affected accounts have moved, what support is hearing, and whether any group needs more time. Watching churn rate among affected accounts against the rest, as the churn and retention metrics guide sets out, shows early whether the retirement is costing more customers than expected. The same phased approach applies at a larger scale when a business withdraws from a whole country, which the guide to pausing or closing a market works through.

Telling customers by how much it affects them

The sequence follows the price change guide: internal teams first, then the most affected customers, then everyone else, with high-value and contracted accounts hearing in a conversation before any written notice. What differs for a retirement is how the groups are drawn. Impact is measured by dependence, not by revenue alone.

  • Depends on it daily, for a job with no easy alternative. A conversation first, from the account manager or customer success, with the replacement or workaround walked through and help offered to move. Then the written notice.
  • Uses it regularly, and the replacement serves their job. A written notice with the date, the reason, the replacement and a migration guide, followed by reminders during the migration phase.
  • Used it rarely or not recently. A short notice so the change does not surprise them, and the export link.
  • Contracted for it. Whatever the contract says governs. Read the contract and take legal advice before saying anything about what the customer is entitled to; this guide does not cover contract terms.

Every written notice answers the same questions near the top: what is changing, when, why, what the customer can do instead, how to get their data, and where to get help. The reason should be specific and one the business can stand behind, such as the cost of maintaining something few customers use or a better way to do the same job.

The notice is a service message. The guide to promotional and transactional email explains that the UK regulator's direct marketing guidance separates service messages a customer needs from marketing a business wants to send, and that purpose and content decide which a message is. A notice that a service customers use is changing passes that test, so it goes to every affected customer whatever their marketing preferences, as transactional email does. It stays a service message only if it carries no selling. An upgrade pitch, a discount on a paid replacement presented as a deal or a newsletter block belongs in a separate message to people who agreed to receive marketing. This is educational guidance, not legal advice.

Record the change in the changelog too, labelled as a removal and placed where readers will see it. The release notes tutorial treats the note as the record of the change, not as the way customers are told.

Removing the feature from every claim

A retired feature lives on in places nobody thinks to check: the pricing page and plan comparison, product pages, help articles, onboarding emails, adverts still running in accounts nobody reviews, sales decks, proposal templates, security and procurement answers, partner listings, comparison pages, case studies and battlecards. Each of them becomes a claim that the product does something it no longer does.

That matters beyond embarrassment. The messaging hierarchy and proof points guide records that the Advertising Standards Authority's codes require objective claims to be capable of substantiation before they are made, and it lists a capability removed in a release among the usual ways proof decays. A page that still promises a removed feature is a claim the business can no longer substantiate. For consumers, the pricing and packaging guide records that in the UK the Competition and Markets Authority enforces consumer protection law covering misleading pricing practices, so a plan still sold on the strength of a feature it no longer includes is worth checking with whoever handles compliance. What customers who paid for the feature are entitled to is a question for the contract and for legal advice, not for this guide.

Build the list before the announcement, give each item an owner, and change it on the date the phase requires: new sign-up pages when new users stop, everything else by the removal date. Messaging comes first. If the feature supported one of the value pillars, the hierarchy needs a new proof point or a revised pillar before the copy can be fixed, and the pricing page needs to show what each plan now includes.

Sales, support and the competitor's version of the story

Sales and support hear before customers do, with the date, the reason, the options for each impact group, the export, and answers to the questions customers will ask. Support also needs a route for the cases that do not fit: a customer whose job the replacement does not serve, or who cannot move in time. When customers complain, the service recovery and complaints guide covers handling the complaint and finding the root cause, and a pattern of similar complaints is evidence for the owner deciding whether to extend a phase.

Account managers face the retirement at renewal. The expansion and renewal marketing guide covers supporting renewals; for an account that used the retired feature, the renewal conversation should start from how the move went, not from the new price.

Competitors will tell their own version: the business is cutting back, the product is shrinking, customers who relied on the feature should switch. The competitive battlecards guide keeps cards current when something changes. Update the business's own cards so sellers can answer that story with the reason and the replacement, and remove the retired feature from any comparison in which it still appears. If a competitor still offers the feature, say so honestly on the card and give sellers the questions that show whether the prospect actually needs it.

Finally, watch retention. The customer retention strategy guide covers diagnosing why customers leave and winning them back; for a retirement, the useful reading is churn among the accounts that used the feature, compared with similar accounts that did not, over the months after removal.

A project software retires its timesheets (illustrative)

Illustrative example — not a real result

Ostrivel Projects retires its built-in timesheets

Ostrivel Projects, an invented project software for architecture practices, decided to retire its built-in timesheets in favour of an integration with dedicated time-tracking tools. Usage showed 340 of its 1,200 practices had logged time in the previous quarter; conversations with 12 of the heaviest users found two jobs: tracking hours against fee stages, which the integration served, and producing a monthly invoice backup, which it did not. The product marketer split the affected practices into 60 daily users, 210 regular users and 70 occasional users. The feature stopped being offered to new customers first. Account managers then called the 60 daily users before any email, walked through the integration and a spreadsheet export for the invoice backup, and offered help to move. Written notices followed in two waves, with no upsell in either, and exports stayed open after removal. The claims list found the timesheets still promised on the pricing page's plan comparison, in two help articles, in a proposal template and in a battlecard against a competitor that offered timesheets, which was rewritten with the integration and the reason. After the read-only phase, 9 of the 340 practices had cancelled, against 4 among a similar number of practices that had never used timesheets.

Common mistakes

  • Deciding without the evidence. A retirement decided on usage alone misses the jobs, the contracts and the promises made in sales.
  • Announcing before the replacement or export works. Every date published must be one the business can keep.
  • Treating it as a two-way door. For a customer who has moved their work elsewhere, the removal is final; phase it so it stays reversible for longer.
  • One email for everyone. The customers who depend on it daily need a conversation first, not the same notice as people who used it once.
  • Selling inside the notice. A service message stays free of promotion; offers go separately to people who agreed to receive marketing.
  • Forgetting the claims. Pricing pages, adverts, decks, proposals, comparisons and battlecards keep promising the feature until someone changes them.
  • Guessing at entitlements. What contracted or paying customers are owed is set by their contract and the law; read it and take advice.
  • Leaving sales without an answer. Competitors will tell their version; sellers need the reason and the replacement before they hear it.

Frequently asked questions

How much notice should customers get before a feature is retired?

This guide does not state a period, because the sources it relies on do not set one. The minimum depends on what customers agreed to and on the law where they live, so check the contract terms and take advice where the position is unclear. Above that minimum, notice is a choice: long enough for the customers who depend on the feature to move their work, and given in phases so that the heaviest users hear first and in person.

Is a retirement notice a marketing email?

It should not be. Under the purpose test that the site's guide to promotional and transactional email takes from the UK regulator's direct marketing guidance, a message that tells customers about a change to a service they use is a service message they need whatever their marketing preferences. It stays that way only if it carries no selling. An upgrade offer, a paid replacement promoted as a deal or a newsletter block turns it into promotion, so those go separately to people who agreed to receive marketing.

Who decides to retire a feature: product management or product marketing?

Product management decides, because it owns what the product does and what it costs to keep. Product marketing contributes the evidence before the decision, who relies on the feature, for which job and what they would lose, and owns the communication after it: the timeline customers see, the messages, the claims that must change and the briefing for sales and support. A decision made without that evidence often underestimates who will be affected.

Terms used on this page

Frameworks

Where this page is used

Sources

  1. Competition and Markets Authority — GOV.UK
  2. Advertising Standards Authority — ASA
  3. Direct marketing guidance — Information Commissioner's Office (UK)

Related