AI Is Killing B2B SaaS
22 points
1 hour ago
| 17 comments
| nmn.gl
| HN
harundu
5 minutes ago
[-]
Sure, vibe coding has impacted user's expectations. They know you can ship a new update easier and faster than before - and you actually can.

But, not sure which successful SaaS companies just stopped shipping any updates to the product, never talked to their customers and never added any new features to win over major new accounts - and still managed to survive and thrive?

And the author actually confirms this:

> AI isn’t killing B2B SaaS. It’s killing B2B SaaS that refuses to evolve.

reply
re-thc
1 minute ago
[-]
> Sure, vibe coding has impacted user's expectations. They know you can ship a new update easier and faster than before - and you actually can.

Can you though? With major bugs? We've been getting more and more crashes, downtime, issues etc lately and a lot of it has had to do with vibe coding.

The whole point of these B2B SaaS is meant to be quality.

i.e. it's set users' expectations but in the wrong way.

reply
epolanski
23 minutes ago
[-]
> How to keep asking customers for renewal, when every customer feels they can get something better built with vibe-coded AI products?

Wrong take. You don't need to build something better, you only need something good enough that matches what you actually need. Whether you build it or not and ditch the SaaS is more of an economic calculus.

Also, this isn't much about ditching the likes of Jira not even mentioning open source jira clones exists from decades.

This is more of ditching the kind of extremely-expensive-license that traps your own company and raises the price 5/10% every year. Like industrial ERP or CRM products that also require dedicated developers anyway and you spend hundreds of thousands if not millions for them. Very common, e.g. for inventory or warehouse management.

For this kind of software, and more, it makes sense to consider in-housing, especially when building prototypes with a handful of capable developers with AI can let you experiment.

I think that in the next decade the SaaS that will survive will be the evergreen office suite/teams, because you just won't get people out of powerpoint/excel/outlook, and it's cheap enough and products for which the moat is mostly tied to bureaucratic/legal issues (e.g. payrolls) and you just can't keep up with it.

reply
zdragnar
2 minutes ago
[-]
Having participated in the build of an inventory system / system of record for a large national retail company, I can't see vibe coding helping anything more than the prototyping in the discovery / requirements gathering parts of the process.

The sheer volume of data, the need for real time consistency in store locations, yada yada means that bad early decisions bite hard down the road.

Lots of drudge work can be assisted by AI, especially if you need to do things like in ingest excel sheets or spit out reports, but I would run far away from anything vibe coded as hard as possible.

reply
JaggedJax
33 minutes ago
[-]
Maybe it's mostly from AI, maybe it's mostly general economic cutbacks. I also feel like these "wrapper" style SaaS products are the first ones companies are dropping when they are looking to cut costs, and I think a lot of companies are looking to cut costs. I do agree with the overall conclusion either way, that System of Record products/companies are the most likely to survive. There are a lot of SaaS companies with questionable long-term businesses who are getting hit, but that was bound to happen.
reply
namanyayg
32 minutes ago
[-]
System of Records especially for boring industries is the way to go. What kind of wrapper SaaS are you seeing getting dropped?
reply
JaggedJax
11 minutes ago
[-]
Analytical systems. I see a lot of add-on services that will add intelligence/analytics/etc and companies try them out to solve some issue they have and bounce off them frequently due to growing costs. I can only assume as mentioned that over time these are also easier for companies to in-house vibe-code as well, I just haven't seen a ton of that yet, but people are definitely trying which still shrinks the available pie.
reply
jboggan
16 minutes ago
[-]
I don't think it is killing SaaS. I have definitely had to extend my sales cycle when a potential customer vibe-coded a quick fix for a pain point that might have triggered a sale a few weeks earlier, but eventually the benefit delivered by someone else caring about the software as their entire mission really wins out over a feature here and there.

If you are selling SaaS consider that a vibe-coding customer is validating your feature roadmap with their own time and sweat. It's actually a very positive signal because it demonstrates how badly that product is needed. If they could vibe code a "good enough" version of something to get themselves unstuck for a week, you should be able to iterate on those features and build something even better in short order, except deployed securely and professionally.

Everyone's going to talk about how cool their custom vibe-coded CRM is until they get stuck in a failed migration.

reply
d_watt
1 hour ago
[-]
I think one of the interesting things here is that AI doesn't need to be able build B2B SaaS to kill it. So much of the overhead of B2B SaaS companies is thinking about multitenancy, intergrating with many auth providers and mapping those concepts to the program's user system, juggling 100 features when any given customer only needs 10 of them, creating PLG upsell flows to optimize conversions, instrumenting A/B tests etc...

A given company or enterprise does not have to vibe code all this, they just need to make the 10 features with the SLA they actually care about, directly driven off the systems they care about integrating with. And that new, tight, piece of software ends up being much more fit for purpose with full control of new features given to company deploying it. While this was always the case (buy vs build), AI changes the CapEx/OpEX for the build case.

reply
bdcravens
57 minutes ago
[-]
And in many cases, it's 12 features, with 2 of the features not even existing in the big SaaS.

I'm pretty sure every developer who has dealt with janky workflows in products like Jira has planned out their own version that fits like a glove, "if only I had more time".

reply
gritspants
20 minutes ago
[-]
Pretty much. My employer was looking to cut costs and they were spending ~500k a year on a product that does little more than map entra roles/groups to datasets and integrated with a federated query engine through a plugin. Took a couple days to build a replacement. The product had only a few features we needed.
reply
namanyayg
1 hour ago
[-]
Exactly, a lot more focus -- and most importantly specific domain knowledge -- allows the end-user to build exactly what they need, fast.
reply
pagwin
5 minutes ago
[-]
Something notable for SaaS which this article doesn't mention is that in some cases the reason to buy rather than make yourself is due to needing to handle a bunch of different regulations which LLMs don't threaten (barring businesses which would rather have lawsuits than pay for a SaaS).
reply
vemv
17 minutes ago
[-]
It's not and I really doubt it will, for true SaaS platforms. A desktop .gif recorder (frequent example I've read about) is not a SaaS, even if you charge monthly for it.

Let's put an example an exception-tracking SaaS (Sentry, Rollbar). How do the economics of paying a few hundred bucks per month compare vs. allocating engineering resources to an in-house tracker? Think development time, infra investment, tokens, iteration, uptime, etc. And the opportunity cost of focusing on your original business instead.

One would quickly find out that the domain being replaced is far more complex and data-intensive than estimated.

reply
insane_dreamer
4 minutes ago
[-]
There are many cases where the company might only use a fraction of the features (and therefore complexity) of the SaaS and so only need to develop and maintain those features they actually need. That's when ditching the SaaS can make sense if you can easily develop/maintain what you specifically need on your own with AI assistance.
reply
avereveard
7 minutes ago
[-]
here's the secret saas can vibe code features too on top of their paid well developed and secured api. they can get off their ass and vibe code a mcp wrapper, so user can use the ai tooling they pay for to interact with their saas. and they'd be called visionary hero of the agentic revolution.

but they don't want to. and they will be replaced, as it's good and well.

reply
raunaqvaisoha
12 minutes ago
[-]
Focus is a currency and you have a limited amount of it, if all SaaS is built internally, teams would go bankrupt. There's likely always going to be a band of experts focused on solving a problem and everyone pays them to solve it for them, because they do it better and can handle the hassle of maintaining it.
reply
pjmlp
43 minutes ago
[-]
Not sure about that, however agents in low code tools are certainly taking over old school integrations.
reply
namanyayg
34 minutes ago
[-]
Nice, what kind of agents and integrations are you seeing being used?
reply
pjmlp
18 minutes ago
[-]
Platforms like Boomi, Workato, Optimizely Opal,
reply
chaitanyya
25 minutes ago
[-]
Well it definitely killed mine so I can't say this is not true
reply
lelanthran
19 minutes ago
[-]
> Well it definitely killed mine so I can't say this is not true

I feel like there's an interesting story in there.

reply
tiffanyh
19 minutes ago
[-]
I'm sorry to hear that ... if not too painful, would you mind sharing more (so others can learn).
reply
namanyayg
24 minutes ago
[-]
Oh no...
reply
morgango
18 minutes ago
[-]
Be a System of Record, not just a Wrapper™ is excellent advice.
reply
semiquaver
16 minutes ago
[-]
I know this is petty but I stopped reading when I saw the “c-t” ligature in the article headings. Obnoxious and pretentious.
reply
re-thc
28 minutes ago
[-]
Are B2B sales actually impacted or is the stock market just randomly predicting AI will impact B2B and selling off?

Since when does stock price / valuation have to match actual business realities?

reply
guywithahat
30 minutes ago
[-]
I didn't realize B2B SaaS products were in freefall like his numbers suggest. I'm not convinced customers are leaving to vibe code their own products but I do believe we're seeing a major shift in the market, pushed by the sudden relative ease of coding. There are a lot of B2B SaaS products which are outdated and I wouldn't be surprised if they're supplanted by much faster competition
reply
namanyayg
29 minutes ago
[-]
Yup it's definitely not because _customers_ are coding solutions, but the trend and motivation seems to come from the fact that customers are realizing there's something else possible except being tied into expensive recurring yearly subscriptions.

I was surprised when I saw the numbers from Bloomberg myself as well!

reply
fogzen
29 minutes ago
[-]
Having worked in enterprise B2B SaaS for a long time, almost every feature I built could have been a simple spreadsheet or some emails. So I'm highly skeptical AI is going to change anything.

Enterprise sales basically works like this: A non-technical sales team aggressively promises everything to win a deal to a non-technical procurement or exec team. When the deal is won, the SaaS sales team tells engineers "go build this" regardless of how stupid it is. And the customer tells their employees "you now have to use this SaaS" regardless of whether it makes sense.

reply
dotdi
35 minutes ago
[-]
This immediately lost credibility for me with this quote:

> And vibe coding is fun. Even Bret Taylor, OpenAI’s chair, acknowledges it’s become a legitimate development approach.

Color me shocked! Bret, who directly profits by how his product is perceived, thinks it's legitimate???? /s

reply
namanyayg
34 minutes ago
[-]
Good point -- removed for being biased and partial. Thanks for the feedback!
reply
lelanthran
17 minutes ago
[-]
> Good point -- removed for being biased and impartial. Thanks for the feedback!

??? Do you mean biased or do you mean impartial?

reply
warkdarrior
19 minutes ago
[-]
"biased" and "impartial" are antonyms. Pick one or the other.
reply
namanyayg
18 minutes ago
[-]
Edited, allow me blame it on my ~12 hour workday today :^)
reply