Ask HN: Why is everything a SaaS product?

141 points by kevivni ↗ HN
I understand the advantages of Saas - transparent updates, cloud based, redundancy, subscriptions, scaling, unicorns etc.

Why don't we have more businesses following the JetBrains model specially if the product is not a service that needs to run 24/7. I buy the product once and use it for perpetuity. If I want updates, I pay more.

As a consumer, my data does not leave my perimeter, my data is not sold or used for ads and I am not hooking into a subscription that I am going to forget soon.

1) Personal photos and videos backup and viewer. - Just give me a cheap cloud for backup and a desktop app for viewing. 2) Personal budget - Just give me a desktop app that connects to my different accounts and gives me overview.

186 comments

[ 0.24 ms ] story [ 285 ms ] thread
Jetbrains can offer a perpetual license[1] in theory because old versions don't continue getting updates. They spend (relatively) little on "supporting" old versions -- mostly just the cost of the download servers.

The two use cases you described don't work that way. Both of them have cloud components, which means they need frequent security patches, and they likely also need bug fixes and other updates.

"Connects to my different accounts" by itself is a huge undertaking that most people outsource to Plaid or a similar vendor.

So to answer your question: a lot (not all, but most) SaaS products are services because they are services. They are updated incessantly by developers and have rolling updates.

1. https://sales.jetbrains.com/hc/en-gb/articles/207240845-What...

To me, the keep your old version forever was a thing Jetbrain did to "soften" the blow when going from buy once, use forever.. to buy every single month.

Still, one of the most valuable softwares I pay for.

A lot of people really didn't like the fact they were going from having a perpetual license to having a subscription. The reality is, the way it worked out is basically the same as before but I could pay monthly. Since I paid for my own license instead of allowing an employer to buy it (so I could get IntelliJ for all languages instead of getting a language specific version) that was nicer.
Jet brain moved to subscription first.

The reason is that you do not want to start over each month sales wise.

Again, as a consumer you can "consume" what is offered in the market.

I.e. if you have an option to not buy, the seller has the option to maximize its profit.

> Jet brain moved to subscription first.

This is why I stopped using their software.

Because people pay for it and companies like money, it's a bit of a dismissive answer but it's just what it is really.
It’s a model that makes money printer go brrrrr

Most customers like it, it keeps the company able to push newer features and maybe up sell them.

Because having a constant cash flow fits better the model of a software company since you need to keep a dev team in perpetuity.

You can't hire devs per project like in construction. Developing commercial software requires maintenance, knowing the codebase, etc.

The difference is software companies hire programmers while companies that sell physical goods hire engineers. Engineers work hard to get it right the first time while programmers are constantly fixing their mistakes.
This is a dumb take, product recalls happen all the time if the issue is bad enough, otherwise everything else flies under the radar. All physical goods eventually need upkeep, too.
(comment deleted)
You probably don't understand how either of them work. Do you remember for how long Apple was trying to fix problems with their butterfly keyboards?
Are they fixing mistakes or constantly adapting to new/expanding requirements?

Try adding an extra bedroom or 3 mid-construction on a house that had perfectly designed plans. One might be doable, seem easy even but 3 might require a new foundation or something to carry the load (scale).

What if the ask is to pivot to a commercial property. Now you have to physically move it to piece of land that is zoned appropriately. Or maybe just tear it down and start over (refactor).

Those aren't mistakes, they just weren't planned when construction began yet have insane implications to the builders. Planning and expanding software never ends like it would when you complete a tangible finished good.

> Are they fixing mistakes or constantly adapting to new/expanding requirements?

Fixing their mistakes. Constantly adapting to new/expanding requirements doesn't require SaaS.

But the way it's worked out is that SaaS lowers production costs because code can be shipped fast -- with minimal testing and before there's any real reason to have confidence in it -- on the theory that you can just push out updates later for any bugs that customers find too annoying.

It's a bit of everything. Sure there are mistakes, but OTOH the complexity also grows exponentially.

And it's literally impossible to make software without mistakes. Doesn't matter how much money you throw at it.

True. However, companies used to engage in comprehensive testing before release. SaaS removes the need to do that, saving a lot of money in exchange for a lower-quality product.
Non-SaaS still exists. Why does my OS update every week?
(comment deleted)
I’m not saying you’re wrong, but you can absolutely hire devs per project. My employer has done it many times. I was in a project that scaled up from 10 scrum teams up to 120 over a year and a half, and then once the product was launched, down to ~25 teams again for the maintenance part of the product cycle. This would have been impossible without contractors.

That said, your first argument is sound.

> I’m not saying you’re wrong, but you can absolutely hire devs per project

You're right of course. I should have written a more nuanced comment that I had time for :)

My point was only that in other types of businesses it's possible and common to hire the whole team per project or season.

Capitalism, baby! Companies have figured out they can take more of your money if they extract it little by little instead of in chunks.
1. Easier to manage updates. If you control the service you can ensure it's up to date. If everyone is using their own version you have to deal with bug reports for bugs that have been fixed.

2. As many point out, subscriptions are best for a business because it's recurring revenue and you can grow. One off sales makes this harder.

3. The Jetbrains model is basically subscription model now. They only allowed you to have perpetual license because of backlash. However, I liked their approach of you can have a peretual license for the version that was available 12-months before your subscription ended. It's what I'm going to be using with my product with a slight modification.

4. As you point out, you're likely to forget about a subscription therefore the company makes money while basically providing nothing.

5. Overall, the problem is that everyone is accepting the current setup and paying for subscriptions instead of buying things so more companies are getting in on the gig.

OP here: Those are fair points.

I get it from the business' perspective and also from a software developer's perspective.

Its unfortunate that there is so little option for a consumer here when they are just wanting to just simplify their lives without sharing their personal data and/or subscribing to a service.

Technically speaking, you could totally imagine a SaaS software that does not require you sharing your data. These two things are fairly orthogonal.
How so? At the very least, you need to have some sort of payment method on file with the company.
Only for automatically recurring subscriptions. If subscribers are willing to to manually renew every pay period, the payment methods don't need to to stay on file (outside of the bare minimum required for tax purposes).
You claim that the consumer has it better with the desktop app, but you're ignoring the number of people who want quick access to their photos or finances from their mobile device, or from the computer at their friend's house when their computer dies. SaaS also implies universal access to a system.
As someone who built a SaaS for your 2nd use case (Homechart: https://homechart.app, lifetime license available!), the real reason is any kind of software that integrates with other things has an ongoing maintenance cost that needs to be paid by all of the users to keep it working. Like connecting to your bank accounts, that's not a one and done thing typically.
I really dislike the subscription model and avoid it wherever I can. It serves the software publisher at the expense of the user. If I can't license your product, I'll pay by usage of resources or usage of minutes or hours. I won't pay for access. I will pay to use the product.
Because businesses with a recurring revenue/subscription model are valued far higher than comparable "buy" businesses.

And of course, the more guaranteed revenue you can demonstrate, the more valuable your business is going to be for potential acquirers. “Because a high percentage of the revenue of a subscription-based business is recurring, its value will be up to eight times that of a comparable business with very little recurring revenue,” claims Warillow.

https://www.techradar.com/news/how-recurring-revenue-can-inc...

My pet theory is that the rise of SaaS in the 2010s is largely a function of the low prevailing interest rates. Standard pricing says that if interest rates are 0.5%, an annual recurring payment of $100 is worth $20,000; but if interest rates are 5%, like in the 90’s, it is only worth $2,000. With the fed increasing rates, maybe we’ll see a return to pay-once software?
Are you saying that because for the SaaS company, $100 in income can service $20,000 in debt?
That’s one way of looking at it. From the investor (and thus valuation) point of view, you need to pay $20,000 lump sum to obtain a recurring interest payment of $100.
Money and power. It lets companies squeeze more cash out of their customers over time and it lets them make whatever changes they want to something people have already paid for, leaves the door open for things like continuously collecting their user's personal data, and can help make it more difficult for users to migrate away from their product.

It's terrible for users who value their money, security, and privacy, but vastly more profitable for companies so most companies will offer it increasingly leaving users with fewer options for anything else.

Even if we disregard the recurring-monthly-fee part of SaaS, which is popular because it makes more money, I think the "cloud" part is a main reason there are so many. Nobody wants to deal with creating installable business software, and businesses mostly don't want to deal with installing software across their systems. It's much simpler for a small dev team to have the software live inside a website, and it's relatively simple to bolt on a monthly fee for access to a website.
This is the big one. It's far easier for both sides to use the "cloud hosting" model. The seller only has to worry about deployments on their own systems, and the buyer doesn't have to worry about deployments at all. It really is a win-win.
> businesses mostly don't want to deal with installing software across their systems

And now they have to deal with cloud leaks of sensitive data that they no longer control and various SOC2/ISO "certifications" increasingly look like security theater and a "feel good" measure because they don't guarantee anything.

What is there to deal with? No one cares about leaks, and at most you give out some cheap credit reporting nonsense. A data breach is hardly news anymore.
Time for an anecdote. I have recently witnessed a medium large company with a paranoid CEO, obsessed with business security, owning physical servers only for internal needs, hosting every single needed service, hoarding all the data. And just overnight they started switching these services to SaaS based one by one.

Why? Lack of on-premise and offline based software. Consequently, the innovation today is almost exclusive to SaaS based products. On-premise and offline client software is just becoming an optional expensive side-product of every SaaS product.

But it's a pretty logical step forward. As for the value, SaaS eliminates administration, installation, hardware, technical support and security hastle and majorly cuts the costs for a client company. As for the price, we always praise the always blooming software industry, successful startups, awesome jobs with so many perks and benefits, but someone has to pay for it. I think people don't consider that software is just getting very valuable and too expensive to make and it just makes more sense for companies to rent it then to own it forever.

Completely understand the comments around valuation of a recurring revenue business and ongoing maintenance. Those are all true and accurate.

I've also been thinking about this from an ecosystem standpoint that it is now very difficult to develop a software product that is not SaaS.

If everyone else is SaaS, and you are not, your business will be:

- Valued lower than equivalent revenue SaaS businesses, because revenue is lumpy and comparatively unpredictable

- Have greater difficulty raising capital, because investors aren't used to valuing non-SaaS businesses any more

- Have greater difficulty hiring engineers, as they know the next job they have will likely be SaaS related

- Slower sales cycle due to higher upfront price required (IE - Doesn't automatically fit on an employee card for land and expand)

- Higher customer acquisition costs, as most customers, other than those on HN, are used to the subscription model and prices, and would encounter sticker shock at the high prices required to make a one time purchase work

> most customers, other than those on HN, are used to the subscription model and prices, and would encounter sticker shock at the high prices required to make a one time purchase work

This one has basically come full circle last year. [1] Many "customers, other than those on HN" have been burned by subscriptions in the past and are rightfully using pricing models assuming a 10x service spike in the future. We've found it easier to sell one-time units for $25000 than subscriptions of $250/mo

[1] https://news.ycombinator.com/item?id=28372532

(comment deleted)
So we have settled on one model that VCs understand and manufactured consent to be ruled by that model by relying on VCs

So much for being risk takers and disruptors. Sounds a whole lot like the opposite.

What’s old is new again. Why do we continue to value people who do not do real work but, like a preacher, latch onto a meme that has others work for them?

I don't get it. It used to be software licenses were being sold for like $10 or $20 dollars. Now $.99 a month is somehow more palatable than $20 for life? I don't believe it. I think perhaps organizations got too large in their bureaucracy. Times were probably leaner for the business folk when software were sold for $10 and $20 or even $120 dollars for Adobe products.

All that being said, it stands to reason you could structure your business to be lean enough to ask for $10 or $20 or $120 licenses again, because it worked fine a decade ago, and nothing significantly changed to make it not work now other than all the sexier corporate real estate these companies have invested into across the US and expanding administrations.

You could take a share of that profit from license sales after paying your immediate overhead to set up some sort of trust that can pay out maintainers for that software long into the future. It can even be structured to outlast the development company if done correctly.

I know a lot of small business owners love SaaS that reduce their IT department to someone who can buy a new iPad and log into the apps again.

Payroll, POS, inventory, backup, etc and the owners can keep track of everything remotely. Setup a backup mobile internet solution, and your biggest IT problem becomes regional loss of electricity.

Nothing for employees or others to steal, nothing to spend on tech support labor, and being up and running again is just a matter of replacing the iPad.

It’s also very easy to justify. As long as the product generates more value than it’s monthly price, it doesn’t matter what it costs. And it’s so low risk since you can cancel any time.
In general SaaS vertically scales to increase demand which means factors of increased revue with no new work.
It's best to think of it as three loops.

1. The loop of just regular maintenance. How long is that version of Node supported? 2 years? Alright assuming you did literally nothing, no bugs, nothing else your software is already needing to be tested against a new major version in just 2 years.

2. External loops, integrate with XYZ platform? Oh version 1 is EoL in 2 years? Guess you need to get on upgrading to API version 2!

3. Someone uses your out of date software and runs into an issue, now they email you, tweet at you, complain that your software sucks and you should support it better. (My first job would get this all the time for software we released 6+ years ago) Oh you fixed that bug in the new version? "I should get it for FREE!!"

Who is going to do this work for free?

Even if you cut the support emails down to a minimum, that alone costs money to automate...

Another favorite of mine was complaining about price, "$5,000 for a perpetual license?!"

Even tech people became like the old school folks complaining about charging for fixing a computer or the ol' "$500 for a website!?".

People get spoiled with so many free services and content provider around them and never consider that someone has to actually pay for it. Even tech people live in this ever-blooming software industry with above average paychecks, perks and benefits, but never think about who is really covering for that.

Software development is expensive, value it can provide is high, businesses provide SaaS to enable companies to attract them and pay for the value they use and get. There will always be attempts at price manipulations, but if software is used and business is profitable - the price is reasonable.

Rental fees, so to speak.

Software as a service becomes a rental property and owners can milk consumers for more money over time as well as introduce features to encourage lock-in. Basically, you're teaching frogs to boil themselves.

Jetbrains wanted to go full subscription too but their userbase revolted.
"You will own nothing, and be happy."

I don't know about the second part, but they sure are trying to push the first. As many others here have noted, the reason is money, or more precisely, greed and control.

I won't elaborate on the very real pessimistic comments because those are addressed from others.

What I haven't seen mentioned are scenarios with non-technical customers. In the extreme use case of resource intensive software with completely non-technical customers, who is going to man the ship? It's like selling someone a car who is incapable of driving.

Even if you provide an on-prem system turn-key, who is going to manage and maintain the system? Yes, you can sell perpetual licenses with support agreements, but the delimitation of responsibilities will be difficult for non-technical customers to understand.

SaaS essentially allows customers to outsource their IT operations.

Exactly, as much as we love open source in many ways it's also kind-of destroyed the mid-segment of fixed-software sales(the dBase, Lightwaves, Turbo Pascals,etc) and we really need a way to find back to it.

Because not only is people not gaining income from their work (even if for example the Blender foundation exists.. how many people can live off it?) but we're also straining a lot of open source developers with support that really needs to be paid-for in some fashion.

I don't fault Stallman in this instance(not a fan in general), the GPL always allowed re-sales and I think he did see something akin to the shareware world even with free software, but what happened was the combination with the Internets ubiquity made everyone just jump to the source (kind of rightfully due to bad shenanigans by middlemen actors like SourceForge or worse) leaving potential supporting middlemen screwed.

Stallman would probably be happy with the idea of paying an expert who used open tools. It's no different from taking a bus, or hiring a taxi if you don't know how to drive.

My impression is that the key aspect revolves around freedom to participate in society. In theory anyone can run their own email, irc, matrix, etc servers. Anyone is free to use an off the shelf open source product, a paid product, or even write their own if there is need.

Ms exchange and aws, azure come to mind. The cost of paying $10
There's a deep and rich ecosystem of IT consultancies that sell, operate and maintain shrink-wrapped software and appliances from the likes of Microsoft, Cisco, VMWare, Citrix. These consultancies sell "SaaS" in the form of, like, we'll have a technician drive to your site, get the keys to the server closet, and spend N hours checking on and maintaining things every month. You can make a living as the SQL Server guy for Duluth or the Cisco phones guy for Milwaukee.

It's hilariously inefficient compared to cloud/SaaS, and no surprise that cloud and SaaS are eating this world's lunch.

People have already mentioned all the technical aspects, or blamed capitalism... but I really think it's just the best fit for the benefits that software delivers. It provides lower barriers to try for consumers and higher long term rewards for the company that builds the software. You can certainly find companies that have a flat rate or fixed price, but the incentive to build those projects from the beginning is usually outcompeted by the incentive to build a subscription product.
> I really think it's just the best fit for the benefits that software delivers.

How so? The only "benefit" you cite for the user is lower cost of entry, but the total cost of using the software over time is higher, so that's not a clear benefit.

From a user's point of view, SaaS does have some other benefits, certainly, but it also comes with some rather large drawbacks. So it seems to me that, on the whole, it all just adds up to software costing more.

Personally, I find it a lot easier to address bugs on the producer side of SaaS. Back in the Bad Old Days where I worked on a proprietary database delivered to a customer to run on their servers with general-purpose staff, getting high quality bug reports and working our way to resolution was a major issue, and a very expensive part of the development process.
There are a few reasons:

1. Higher total revenues. If you compare the subscription fee with the sale fee and how often sales happen.

2. More predictable revenue. There are many reasons people want that.

3. The more information (metadata/telemetry) they have on you the more they can use that for something else. That could be details on how you use the app. If they host your photos they may use those photos to train an AI. Things like that.

4. Finding and tracking unlicensed users is easier to stop and manage. Everything is tied to a SaaS. Less stealing software which cuts into revenue.

There are other reasons, too.

In a capitalistic society where the goal is constant revenue growth, SaaS provides a means to do that more effectively. Look at the goals.

I’d also add: it’s easier to operate and iterate.

If you have a thousand different installs that you need to provide support for, that makes for a very challenging support and maintenance responsibility. People need to be able to operate the software themselves, and may not upgrade when you want them to.

SaaS on the other hand means you, the vendor, are in full control. Sure, it means you need to be able to scale it, but you and only you completely own the infrastructure, which makes things so much simpler.

>I understand the advantages of Saas - transparent updates, cloud based, redundancy, subscriptions, scaling, unicorns etc.

You answered your own question.

One reason is that SaaS pricing is an easy way for people to "hack" corporate spending restrictions. You need accounting approval for that perpetual $10000 software license, but a $500 monthly subscription payment is totally at your discretion, even if you end up spending more of the company's money in the end.
I am not in accounting/finance, but the world has been on SaaS for so long that it's hard to imagine that the department responsible for controlling spending hasn't caught on and plugged this loophole.
Yeah this is less true than it used to be but it's a big part of how SaaS initially came to be the only game in town.