/s
Although it does sort of put pressure on the developers to actually refine their product and continue to deliver tangible improvements. Nobody is going to pay for a UI that's been re-arranged a bit.
I can't think of a single subscription service I use that doesn't continue to deliver new updates and value on a regular basis, and other than Adobe's bullshit "annual masquerading as monthly" drama I haven't come across something I wished was still packaged.
With a subscription model, there’s a point where the consumer has paid you “too much” and they will either cancel or find another solution. This is also known as churn. If your avg customer pays you for 8 months, this is a pretty good indicator of how much customers are willing to pay, but you can likely charge more for a one-off cost, sometimes 2-5x more.
Since you are likely combatting churn by finding new customers, switching to a one-off model means you can just find new customers and not worry about churn since it doesn’t exist.
Don’t get me wrong, sometimes subscription models make a lot of sense. Most of the time they don’t unless you’re selling something that has an infinite cost anyway (like immediate access to “all” movies ever made like Netflix) and would be an infinite cost for the consumer to do it in some other way. But if I can pay a contractor to build your app for less than infinite money, then it shouldn’t cost an infinite amount to use your product.
For scale, I've been using VIM for almost thirty years. Twenty years is not an exaggerated number.
It might make the software prohibitively expensive though.
How about for maximum flexability we do a per user rolling monthly license.
Softwares can't sell like hardwares. When you buy a toaster for example, after the warranty expires you pay for every time you take it out for repairing. With softwares customers expect a life time of warranty, bug fixes and improvements.
Sell it as is, or with a very short one year support window. Exactly like all sorts of companies used to profitably do until they realized they could extract more value for the same work with a subscription.
Rent-seeking in the most literal form...
The stores also lack (and still do) an easy way to sell new versions, so here we are. Subscriptions.
Jetbrains has very good model in that regard. Hope they will not ruin it (new pricing for self hosted Spaces is bit concerning).
The problem is that a lot of things that aren't a service are being rebranded "as a service" just to extract free revenue.
I would argue that it has been proved that this model doesn't work, because it unalgins incentivess between the developer and the user: the developer will look tho maximize revenue, catering to better paying ads and more clicks/interaction with them, while the User will try to get more usage from the main app.
I want applications that give me an EXE that I can use forever , even if the company disappears. And then the option to pay yearly or monthly for updates to said Exe (even as replacement EXEs) that give me more functionality, bugfuxes and secfixes .
The opposite effect is you are pressured to keep using the product and I feel my friends are losing valuable time because of their Netflix subscriptions.
Pay-per-use might also be a similar option, and I'm happy with many web services working this way.
I was thinking monthly as that is the usual billing interval. Minimum 1 month subscriptions, then pause the next month if you want to be busy for example. Maybe even weekly or 24 hours would do.
I’d love to say pay for a feature set that I really like and pay a “lower” subscription for it for ever. Even if at some stage I am forced to upgrade because developers have too many versions that they need to maintain.
1. Every SaaS business should be compelled to offer both a subscription price and perpetual license at a fixed price.
2. The fixed price of a perpetual license should not be more than 10x or 20x (?) of the monthly subscription price.
3. If a user has opted for subscription payment, they should get a perpetual licence after they have paid a certain subscription amount over a period that is not more than 2x or 3x of the fixed price of the perpetual license.
4. SaaS businesses should not be allowed to hold users data hostage if the user decides to end the subscription. (This can be tricky if the data is in some proprietary format).
5. As much as possible, the SaaS should be able to run offline on a user's computer without needing to offload computing to servers.
Ofcourse, most of the above are practical only for software that you can actually run on your computer and don't require massive computing powers from data centers that some services may need. But then again, that's exactly the kind of software that don't need to be SaaS at all in the first place, as the article too points out.
I still think this has much more to do with market interventions enabling 'artificially' large economies of scale. Infrastructure, police, subsidies/grants, IP protections--all played and continue to play a massive role in shaping markets today.
Regulation, on the other hand, does tend to lead to rent seeking behavior as incumbents use those laws to their advantage and forcibly block new companies.
It’s much easier to overcome high costs than bad laws.
And that's only because of current regulations and anti-competition laws. Turns out "free market" is only "free" when the giants are asked to behave and punished for bad behaviours.
1. Free = problematic with the lack of money
2. Freemium = looks good if the balance is right
3. Ads = Mostly works but the model is flawed and skewed
4. Subscription = Love/Hate currently trendy but too relied on
5. Pay-what-you-can = Fans provide the service for everyone
6. Premium only = Only what it's worth, when it's worth
7. Enterprise = S'ok because my company/org pays for it
8. Tokenised = S'ok because the next person pays for mine...
9. Charitable / foundation = Someone more wealthy pays
10. None of the above = For now somehow it works
There are probably 10 more models already, 10 more out there and 10 more coming soon. Get thinking, stop complaining.