is 30 days notice enough to kill a paid b2b tool or am i being rude Customer Notice
Small scheduling tool, 60 accounts, $12-$40/mo, mostly single-room clinics and studios. I am done with it.
Plan was: email today, service ends in 30 days, exports available the whole time and for a month after.
A friend says 30 days for something businesses run on is "a bit hostile" and I should do 90. Ninety days is three more months of a thing I am actively trying to stop thinking about.
What is actually normal?
@kombucha_kai · 7mo ago · 2 replies
It depends on one thing: does your data have a future in it.
A $19 notes app, 30 days is generous. A scheduling tool for a clinic has rows dated after your shutdown date - appointments people have already promised to patients. That is not "your service ends", that is "their next quarter needs rebuilding somewhere else, by hand, while they are working".
Practical version of the test:
select max(starts_at) from appointments. Whatever that date is, your read-only date should be after it, or you should give people enough runway to move the future-dated rows. For most scheduling tools that lands somewhere between 60 and 90 days, and it is not about politeness.Reply
Report
@wrangler_dev_jo · 7mo ago
Never seen it put that way and it is immediately obviously right. Anything with future-dated rows - bookings, invoices, renewals, scheduled sends - has to outlive its own furthest row or you are handing the customer your problem.
Reply
Report