Customer Communication When Closing Your Startup

When you decide to shut down, the hardest part isn't the decision — it's telling people. Here's how to do it across every channel your users might encounter.

Email: Your most important channel

Email reaches your users directly. It's where most people expect important account communications. This should be your first and most thorough announcement.

Who to email:

• All active users (logged in within the last 6 months)
• All registered users, even inactive ones (they may have stored data)
• Paying customers separately — they deserve a personal message and refund confirmation

What to include:

• Shutdown date
• Data export instructions and deadline
• Refund timeline for paid users
• Alternative recommendations
• Contact information

When to send: Send the initial announcement 30–60 days before shutdown. Follow up at 14 days, 7 days, and 24 hours before.

For the final email, consider a plain-text format. It reads more personal than HTML email and tends to feel more human for this kind of message.

Your website and app: The passive channel

Your website continues to receive visitors after your announcement. Make sure every visitor gets the message:

Homepage banner: A persistent, prominent notification that the service is shutting down. Don't hide it below the fold.

App notification: For logged-in users, show an in-app banner or modal with the shutdown date and data export link. This is especially important for users who don't check email.

Documentation: Update your docs to reflect the shutdown. Mark APIs as deprecated, add a notice at the top of every docs page.

Login page: After the shutdown date, your login page should show the shutdown notice rather than the login form. Don't let users try to log in to a service that no longer works.

Social media: The public record

Social media announcements serve a different purpose than email. They're public, searchable, and permanent. Many of your past users — people who've moved on and unsubscribed from your emails — may still follow you on social.

What to post:

• The shutdown announcement (immediately after your first email)
• Responses to user questions and reactions
• Reminders as deadlines approach
• A final farewell post

Tone: Be human. The best shutdown social posts read like messages from real people, not press releases. They acknowledge the product's impact, thank the community, and leave on a note of genuine warmth.

On Twitter/X in particular: Consider pinning your shutdown announcement. People who find your account through search or old links will see it immediately.

For developer products: Additional channels

If you have an API, a developer tool, or any kind of programmatic interface, you have additional communication responsibilities:

API responses: Return deprecation warnings in your API responses well before shutdown. A Deprecation header or a warning in your response body gives developers time to migrate.

Webhooks: Send a final webhook event to all active webhook endpoints announcing the shutdown date.

Developer documentation: Add prominent deprecation notices to your API docs. If you have OpenAPI specs, add deprecated: true to your endpoint definitions.

Developer newsletter: If you have a separate developer newsletter or forum, announce the shutdown there specifically.

The people you often forget

Users who left before the announcement

Former users still have accounts. Some may have data stored in your product. They deserve notification even if they haven't logged in in a year.

Integration users

If your product integrates with other platforms (Zapier, Slack, a marketplace), notify users through those channels too. People who set up integrations may not be regularly visiting your app directly.

Your community

If you have a Slack community, Discord server, forum, or subreddit — announce the shutdown there too. These communities often contain your most engaged users.

Press and analysts

If your product was covered by press, consider a brief note to the journalists who wrote about you. It's a courtesy that's often appreciated, and it allows the public record to be updated accurately.

After the shutdown: Keep one channel open

Once the service goes offline, you still need a way for users to reach you. Minimally, this means:

• Keeping your contact email active for several months
• Maintaining a shutdown page that includes that contact information

Users will have questions after shutdown. Data export issues. Refund questions. "Was my data actually deleted?" questions. Keep a channel open for them.

Your shutdown page is part of your communication strategy — the permanent, always-on message for anyone who reaches your domain. Create one at ExitPage.one.