Every startup eventually has to kill something. A feature that never found its audience, an integration nobody maintained, a whole product line that made sense at Series A and stopped making sense by Series C. The build is always covered in a launch post. The ending almost never is.
Pull up the last ten “sunset” or “deprecation” emails a company has sent and they read the same way: a subject line that buries the news, a body that opens with “as part of our continued commitment to delivering the best experience,” and a deadline mentioned once, in passing, three paragraphs in. It is written to survive a legal review, not to be read by a person who built a workflow around the thing that is about to disappear.
That is backwards. A launch email is read by someone who is already curious. A sunset email is read by someone who is already annoyed, actively looking for the part where you admit what this costs them, and deciding in real time whether to trust you with the next product you ship. There is no softer audience for a hard message.
What the good version actually does
The companies that handle this well share three habits, and none of them require legal sign-off to change.
They name the deadline in the first line, not the last. If a customer has ninety days to export their data or switch workflows, that number belongs in the subject line, not buried under three paragraphs of context they have to read to find it.
They say why, briefly, without pretending it is good news. “This feature had too few active users to justify the maintenance cost” is a sentence a reasonable adult can respect. “We’re incredibly excited to streamline our platform” is a sentence that tells the reader you think they are stupid.
And they tell the customer exactly what to do next, with a link that works, not a support address that routes to a queue. A sunset email with no clear next action isn’t a notice. It’s a countdown with nowhere to go.
Why this is a brand decision, not an ops one
Most founders file this under “customer success will handle it” and never read the email before it ships. That is the exact moment it becomes a brand document instead of an operational one. The customer who gets a badly handled sunset email doesn’t file a complaint against your support team. They file it against your company’s judgment, and they carry that judgment into the next renewal conversation, the next upsell call, the next time a competitor pitches them.
The irony is that a well-handled ending is one of the few trust-building moments a company gets without spending a rupee on it. The customer isn’t comparing your sunset email to your competitor’s launch video. They are comparing it to every other vague, evasive corporate email they have ever deleted. The bar is on the floor. Clearing it is cheap, and almost nobody bothers.