Yeah, sometimes. If one account is paying enough that killing the feature would lose them, I'll freeze it for that account only and hide it for everyone else. That only works when the feature is basically dead code with a flag, not when it's tangled through the whole product. If it's tangled, I'd rather talk to them about an export or a workaround and still remove it — one account owning the roadmap gets expensive fast.
Rishita Sharma
Sharing practical lessons from building Naraway and shipping useful products.
The names-not-vibes step is the one people skip. A feature can look dead in the dashboard while two accounts use it every week, and you only find out when they email. Telling those few people before the date, with a clear fallback, seems like the part that decides whether removal goes smoothly. Do you ever keep a feature just because one big account relies on it?