In January 2025, a project management SaaS with 3,200 paying customers shut down. The founders ran out of funding, couldn't find a buyer, and decided to close. They sent an email to customers giving 30 days notice.

That's the good version. Plenty of startups don't even manage that.

The bad version: the company stops paying its hosting bill. The app goes down. Customers try to log in and get a 502 error. They email support. No response. They check Twitter. The last tweet was 4 months ago. They check LinkedIn. The founders have new jobs.

Their data, their workflows, their integrations, gone. No export option. No goodbye. No explanation.

The Support Void

When a company dies, support is the first thing to disappear. Agents are laid off or they quit when they see the writing on the wall. The help desk subscription lapses. The support email bounces.

The customers, who don't know the company is dying, keep submitting tickets. Into a void. For days or weeks.

"I can't log in. Is the site down?" "I need to export my data before my quarterly report." "I was just charged $49 for a product I haven't been able to use in two weeks."

These tickets sit in a dead inbox. The customers get increasingly frantic. Some charge back their recent payments. Some post on social media. Some just lose their data quietly.

How to Shut Down Responsibly

If you're shutting down a product (or your whole company), support is part of the wind-down. Treating it as an afterthought guarantees the worst possible ending for your customers and your reputation.

Communicate early and clearly. Give at least 30 days notice. 60 is better. 90 is ideal for enterprise customers who need time to migrate. The email should include: what's happening, when, what customers should do (export data, find alternatives), and who they can contact with questions.

Provide data export. Before anything else shuts down, give customers a way to get their data out. A one-click export, a bulk download, an API endpoint that stays active for 90 days after shutdown. Your customers' data belongs to them. Trapping it in a dead product is a legal and ethical failure.

Keep support running through the shutdown period. Even if it's just one person answering emails for 30 days. The wind-down support agent handles: data export help, refund requests, questions about alternatives, and "what happens to my account?" queries.

Process refunds proactively. If customers paid for a period they won't receive, refund the unused portion. Don't make them ask. Don't make them fight. The company is already dying. Generating chargebacks and BBB complaints on the way out is pointless.

Keep the status page or website up with a notice. Don't just let the domain expire. Put a page that says "This product has been discontinued as of [date]. For data export, email [address]. We're sorry and we appreciate everyone who used [product]." Leave this page up for at least 6 months.

The Reputation Afterlife

Founders of dead startups often start new companies. The way you shut down the last one follows you.

If customers remember a respectful wind-down (clear communication, data export, proactive refunds), they might become customers of your next product. If they remember being ghosted, their data trapped, their money gone, they'll tell everyone about it. And when they see your name on a new launch, they'll remember.

The startup ecosystem is small. People talk. A founder who shut down responsibly gets empathy. A founder who ghosted 3,000 customers gets blacklisted.

The In-Between: Sunsetting a Feature or Product Line

Full company shutdown is the extreme case. More common: sunsetting a product line, retiring a feature, or discontinuing a service tier within an ongoing business.

The support principles are the same but the stakes are lower and the resources are greater.

Give notice. Provide migration paths. Keep support staffed for the transition. Proactively refund if the customer paid for something they can no longer use.

The biggest mistake companies make when sunsetting: they announce the sunsetting and then stop investing in support for the sunsetting product. "It's being retired, why spend money on it?" Because the customers still using it deserve support until the day it actually goes away. Abandoning support before the shutdown date is a betrayal.

AI During Wind-Down

Even a skeleton support operation benefits from AI during a shutdown.

Configure an auto-responder for the most common wind-down questions: "When does the product shut down?" "How do I export my data?" "Will I get a refund?" "Can you recommend an alternative?"

These four questions will make up 80% of shutdown-period support volume. Auto-responding to them instantly reduces the load on your skeleton crew while ensuring every customer gets a fast, accurate answer.

Supp can handle this at minimal cost. Configure auto-responses for the shutdown-specific intents. The classification runs at $0.20 per message. Even at 500 messages during the wind-down period, that's $100 for consistent, instant communication with every affected customer.

The difference between a "clean" shutdown and a messy one is preparation. A day of setup (communication email, data export tool, auto-responder, refund process) is the difference between "they handled it well" and "they disappeared and took my data."