Moving a product to a subscription is usually discussed as a pricing decision. It is presented as one in every guide: recurring revenue is worth a multiple of one-time revenue, the lifetime value of a customer goes up, the business becomes predictable. All of that is true and none of it is the interesting part.
The interesting part is that a subscription is a promise with a duration attached, and the arithmetic that makes it attractive is the same arithmetic that tells you how long you have agreed to keep working.
One number, read twice
Take a monthly price \(p\) and a monthly churn rate \(c\), meaning the fraction of subscribers who leave each month. The expected revenue from one subscriber is the familiar result:
The same denominator sets the revenue and the length of the obligation.
At two percent monthly churn a subscriber is worth fifty months of price. That is the number everyone quotes. It is also, and unavoidably, a statement that the average customer expects the product to be alive and looked after for about four years. Low churn is not merely a better business. It is a longer commitment, described in the language of revenue so that it sounds like a benefit rather than a duty.
This is why the metric feels so good and reads so badly. Everything you would do to make \(c\) smaller, which is to say everything that makes the product more deeply woven into someone's routine, extends the period during which walking away from it would be a betrayal rather than a business decision.
What is actually being sold
A one-time purchase sells a thing as it is. Both sides know where they stand: the buyer has what they paid for, and if nothing further arrives, nothing was broken. A subscription sells the future, and the future has to be delivered.
What that means in practice is that a subscription is a standing obligation to keep a product working against a world that keeps moving: operating systems that change every autumn, devices that did not exist when the code was written, dependencies that stop being maintained, a support inbox that never empties. None of this is optional and none of it is visible in the pricing model. It shows up later as the amount of the year that is already spoken for before any new work begins.
The honest test is not whether people will pay monthly. Plenty will. It is whether the thing genuinely keeps giving, month after month, in a way that would embarrass you to bill for otherwise. A tool that syncs, hosts, delivers or otherwise does work on your behalf every month passes it easily. A tool that was finished eighteen months ago and now mostly launches does not, whatever the churn number says.
How we price
So the question we ask first is not what a product could charge, but what it is promising and for how long. If a product genuinely does continuous work, a subscription is the format that matches the obligation, and the recurring price is the honest one. If the value was delivered once and completely, we would rather sell it once, take less, and owe less.
The consequence we accept is a smaller number on the spreadsheet. A one-time price will always look worse next to the multiple that recurring revenue attracts, and a portfolio built this way grows more slowly than one that puts everything behind a monthly wall. What it buys is the ability to say a product is done and mean it, without that sentence being a broken promise to somebody paying every month.
That is the trade, and it is worth naming plainly. Subscriptions convert a product into a relationship. Relationships are more valuable than transactions, which is exactly why they should only be entered where there is something real to keep giving. The mistake is not charging monthly. It is charging monthly for something that quietly stopped needing to be built, and calling the resulting revenue proof that it was the right idea.