← Revenue weighted voting

Churn cost calculator, for the request you did not build

Four numbers about one request. Nothing is sent anywhere.

Worth a month when they asked
Gone, a month
Gone, a year
Still paying, still waiting

Askers times price is what the request was worth. Leavers times price is what has gone, times twelve for the year. The rest is what is still there to keep. No rate, no model, no benchmark.

Does this prove they left because you did not build it?

No, and a calculator that hands you a savings figure is quietly claiming it does.

People leave for reasons that have nothing to do with your roadmap. Read this number as a ceiling: the most the request could have cost you, with the truth somewhere between that and nothing.

What it is good for is comparison. Run it on two requests. If one is carried by customers who have mostly left and the other by customers who are all still here, those two are not tied whatever their vote counts say.

Where do the numbers come from?

Your billing system, and whatever holds your requests.

On a board that knows who pays, the first two are already on the request: the voter list names everybody who voted, with what each pays on their own row. The third one, who has since churned, is the awkward one, and the API answers it in a single call.

Related reading

Churn rate, and how many of your askers already left Customer retention, and what your board says before they go Weight feature requests by what the customer pays