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.
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.
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.
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.
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.
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.
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".
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.
but they don't want to. and they will be replaced, as it's good and well.
I feel like there's an interesting story in there.
Since when does stock price / valuation have to match actual business realities?
I was surprised when I saw the numbers from Bloomberg myself as well!
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.
> 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
??? Do you mean biased or do you mean impartial?