- 1. Call the accounts that matter before anyone else hears
- 2. Bring the replacement, not the news
- 3. Set a last-time-buy window with a hard date and a quantity
- 4. Close the door the same day
- 5. Watch the accounts for two quarters
Long notice does not protect an account. It just gives the customer more time to run a full sourcing exercise, and once that exercise starts, everything else you sell them is on the table too.
The standard advice says the opposite: give plenty of warning, be transparent, let people plan. The intent is right and the mechanism is backwards. A form letter announcing that a product ends in six months, with no replacement named, tells a purchasing manager that their supplier has become unreliable and hands them half a year to act on it. Meanwhile your own organization treats the deadline as distant and does nothing until month five.
What works instead is a short, controlled sequence: the accounts that matter hear from a person before anyone hears from a letter, every conversation arrives with the replacement already chosen, the last-time-buy window is tight and firm, the product leaves your systems the same day it leaves the catalog, and somebody watches the affected accounts for two quarters afterward. Five steps, and they only work in order.
Who counts as an account that matters is a separate piece of work, covered in how much revenue you will actually lose in a SKU cut. Do that classification first. This sequence assumes you already know which customers carry the exposure.
1. Call the accounts that matter before anyone else hears
Every customer you classified as a basket risk gets a phone call or a visit from someone they know, before any general notice goes out. Not an email. A conversation, in which they hear it first and can say what it breaks on their end.
The order is the whole point. A large customer who learns from a mass email that a part they build into their product is ending has learned two things: the part is going, and they were not worth telling. The second one does more damage, and it is the one that starts the sourcing exercise.
Keep the list short enough to be real. If two hundred customers all supposedly need a personal call, the classification was not done properly and the calls will not happen.
2. Bring the replacement, not the news
Show up with the substitute already chosen: which product, at what price, with what lead time, and what the customer has to do to qualify it. A retirement with a migration path is a routine supplier conversation. A retirement without one is an invitation to go shopping.
Deal with the qualification burden explicitly, because that is usually what the customer is actually worried about. Offer the samples, the documentation, the test support, and the timeline. If the substitute needs approval on their side, the migration plan has to fit inside their approval cycle rather than yours, and that is a fact worth knowing before you set any dates.
When there is genuinely no substitute in your line, say so directly and help them find one elsewhere. You will lose the item either way. Handling it straight is what keeps the other thirty-nine items in the basket.
3. Set a last-time-buy window with a hard date and a quantity
Publish one window, with a closing date for orders and a cap on quantity, and hold both. Then build to the orders you receive, not to the demand you imagine.
A short window concentrates the decision and gets you real information about who depends on the product. A long one guarantees that most customers file the notice and call you the week after it closes, which is how retirements turn into emergency extensions that undo the whole exercise.
The most common way a rationalization loses its savings is a final production run sized for optimism.
Size the final run against the orders in hand. Adding a comfortable margin on top leaves you holding exactly the slow-moving inventory the retirement was supposed to eliminate, except now it belongs to a product with no future orders at all.
4. Close the door the same day
On the day the product leaves the catalog, it leaves the price book, the quoting tool, the configurator, the website, and the sales collateral. All of it, that day.
Leave any one of those live and somebody sells it again next month in good faith, and a retired product returns with a new part number and a customer expectation attached. That is not a hypothetical failure mode. It is the normal outcome when the systems work is treated as cleanup to be done after the announcement.
Prepare the internal side before the external one. Customer service needs the script and the substitute details before the first call arrives, and anyone quoting new business needs to know the product is gone. A customer who hears about a retirement from a confused service representative costs more goodwill than most retired products were ever worth.
5. Watch the accounts for two quarters
Track total revenue from every affected account for two quarters after the last shipment, not just their purchases of the substitute. The signal you are looking for is a customer quietly buying less of everything.
That is what a failed migration looks like in the data. It rarely arrives as a complaint. It arrives as a basket that shrinks by ten percent a month while nobody notices, because each individual order still shows up. Compare each account against its own prior run rate and the drift is obvious early enough to fix with a call.
Check your predictions against what happened, too. The customers you classified as basket risks either moved or did not, and that record is what makes the next round’s estimate better and the argument for it shorter.
So the question is not how much notice to give. It is how fast you can get every affected customer from the news to a working replacement, with the least time spent in between wondering whether you are still a reliable supplier.
About the Stagnation Assassin
Todd Hagopian is a Fortune 500 transformation executive who has generated $3B in shareholder value across Berkshire Hathaway, Illinois Tool Works, Whirlpool, and JBT Marel, where he serves as Global VP of Product Strategy and Marketing. Known as The Stagnation Assassin, he is the author of two published books: The Unfair Advantage: Weaponizing the Hypomanic Toolbox and Stagnation Assassin: The Anti-Consultant Manifesto. His blog is published in 15+ languages and read by operators worldwide. Bring him to your stage via his speaking page or connect with him on LinkedIn.
Retiring products one at a time is usually a sign the portfolio decision behind them was never made. Request a free 15-minute 80/20 Portfolio Performance Audit and I will show you which of your product lines is generating the retirements.
See also: 3 Places Revenue Goes After a SKU Cut