The feature request that was actually a refund request

A customer emailed support on a Tuesday asking, very politely, whether the product could do one specific thing. The CSM logged it as a feature request, thanked them, and moved on. Six weeks later the customer canceled. The exit survey said not the right fit anymore.

It was the right fit ten weeks ago. The feature request was not roadmap input. It was a verdict.

Customers rarely churn loudly. The dramatic cancellation email with bulleted grievances is a myth told by product managers who need a clear villain. Real churn is quiet: one polite request, two weeks of declining logins, an auto-renewal toggle flipped on a Sunday night. By the time the renewal email goes out, the decision is months old.

The honest translation of most late-stage feature requests is not please build this. It is the product I have today is no longer enough to keep me, and I am giving you one chance to prove otherwise before I stop paying. The customer is being generous. They are telling you, in a tone calibrated not to embarrass either party, that they are leaving.

The diagnostic is simple and almost never run. When a request comes in from an existing customer, look at their usage for the next fourteen days. Steady or growing means real roadmap input from someone invested. A drop means exit interview wearing business-casual.

Shipping the feature after the customer has mentally left almost never retains them. The decision was made before the email was sent. What the email tested was whether you were paying attention. You weren't. They were already gone.

This does not mean ignore the request. It means read it correctly. The right question is not can we ship this in time to save them? It is how many of our next ten customers are about to send this same email, and what would it take to make sure they don't?

The customer who churns is not your problem. The product that produced the request is. Fix the product. The next ten will not need to write.