Ending a product properly.
WHY IT DESERVES CARE
Customers built their work on it, and their data is in it.
WHAT TO DECIDE
The date What happens to data Whether refunds are due What customers should move to
WHAT NOTICE TO GIVE
As much as possible. Months, not weeks.
WHY
Customers need to select an alternative, migrate, and retrain.
WHAT TO COMMUNICATE
That it is ending When What they must do How to export everything
WHAT TO BUILD BEFORE ANNOUNCING
A complete export.
WHY
The first question will be how to get their data out.
WHAT TO REFUND
Anything paid for a period you will not serve.
WHY
It is right, and failing to do so produces claims and lasting reputational damage.
WHAT TO CONSIDER
Recommending alternatives honestly Helping migrate, where feasible Open-sourcing, where possible
WHAT TO KEEP RUNNING LONGEST
Data export.
WHAT TO DO ABOUT DATA AFTERWARDS
Delete it, as stated, and confirm.
WHAT TO ATTEND TO
Obligations in contracts, which may survive shutdown.
WHAT TO TAKE ADVICE ON
Liabilities, and the proper process.
WHAT TO PROTECT
Your reputation, which outlasts the product.
