Moving a product onto a subscription usually gets discussed as a pricing decision, and every guide presents it that way: recurring revenue is worth a multiple of one-off revenue, each customer is worth more over their lifetime, and 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 length attached, and the same sum that makes it look attractive also tells you how long you have agreed to keep working.
The same number, read two ways
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 number sets both the revenue and the length of the commitment.
At two percent monthly churn, a subscriber is worth fifty months of the price. Everyone quotes that number. It also says, unavoidably, that the average customer expects the product to be alive and looked after for about four years. Low churn isn't just a better business. It's a longer commitment, described in the language of revenue so that it sounds like a benefit instead of a duty.
This is why the number feels so good and reads so badly. Everything you would do to make \(c\) smaller, which means everything that works the product deeper into someone's routine, also lengthens the period in which walking away from it would be a betrayal rather than a business decision.
What you are actually selling
A one-off purchase sells the thing as it is. Both sides know where they stand: the buyer has what they paid for, and if nothing else ever arrives, no promise was broken. A subscription sells the future, and the future has to be delivered.
In practice that means a standing commitment to keep the product working while the world moves underneath it: operating systems that change every autumn, devices that didn't exist when the code was written, dependencies that stop being maintained, a support inbox that never empties. None of it is optional, and none of it shows up in the pricing model. It shows up later, as the part of the year that is already spoken for before any new work starts.
The honest test isn't whether people will pay monthly, because plenty will. It's whether the product really keeps giving, month after month, in a way you would be embarrassed to bill for otherwise. A tool that syncs, hosts or does work for you every month passes easily. A tool that was finished eighteen months ago and now mostly just opens does not, whatever the churn number says.
How we price
So the first question we ask isn't what a product could charge. It's what the product is promising, and for how long. If it really does work continuously, a subscription matches what we're taking on, and a recurring price is the honest one. If the value was delivered once and in full, we would rather sell it once, take less, and owe less.
We accept a smaller number on the spreadsheet for this. A one-off price will always look worse next to what recurring revenue is valued at, and a portfolio built this way grows more slowly than one that puts everything behind a monthly paywall. What we get for it is being able to say a product is finished and mean it, without that being a broken promise to somebody who is still paying every month.
The trade is worth stating plainly. A subscription turns a product into a relationship, and relationships are worth more than one-off sales. That is exactly why you should only start one when you have something real to keep giving. Charging monthly is fine. Charging monthly for something that quietly stopped needing to be built, and then treating the revenue as proof that it was the right call, is where it goes wrong.