Look up "SaaS is dead" and you'll get a list of posts and videos mostly agreeing with the claim. This has been going on since at least late 2024, when Satya Nadella's comments on a podcast were (mis)interpreted into the headline "SaaS is dead."
Almost two years later, SaaS is still very much alive, and so is the trend of reading its eulogy.
What's worse is that this claim keeps getting conflated with the idea that software engineering as a profession will collapse. It's not just that SaaS is dead. It's that nobody needs software engineers anymore, because AI will build their tools for them.
Only time will tell whether either headline proves true. Until then, I, for one, don't think SaaS is anywhere near dead. Nor do I think software engineering is. If anything, software engineers are poised to thrive.
What's on its way out is charging money for trivial solutions.
Weekend builds vs. engineered products
AI has made it remarkably easy to build something that works. A weekend and a few prompts, and you have a tool that solves some specific problem.
However, "works for me on a Sunday" is a long way from a product, and agents can't easily fill that gap. What they can do is replace a subscription to an app that does one small thing.
The sieve
"Solve your own problem first, then sell it" has always been a proven route to a product. AI doesn't just make that route faster. It tightens the sieve on what makes it to market.
A real itch used to be a product idea even when it was easy to scratch, because only engineers could build the fix. Now almost anyone can. So, if your weekend build solves the problem completely, it will be hard to sell. A micro-SaaS that can be replaced by an n8n workflow, or a skill on your favorite AI assistant, won't cut it anymore. The niche isn't the issue; the simplicity of the solution is.
If you keep hitting walls, however, pay attention. Edge cases, scale requirements, messy data, reliability... Each wall is a reason someone might rather pay you than build it themselves.
Walls don't guarantee sales. You still need other people who have the same problem.
Even so, the sieve works in everyone's favor. The products that pass through it are the ones worth paying for, and the competition to build them leads to better products, lower prices, or both. If you're the one selling, lower prices sound like bad news. But price wars happen where building is easy. The harder your product is to build, the fewer people can undercut you.
SaaS ≠ code
The last letter in SaaS stands for "service," and that's the part that gets lost in the "SaaS is dead" conversation. Customers don't pay for your code. Most of them will never see it. They pay for the walls you've already climbed:
- the app is up when they need it,
- it complies with standards and regulations,
- it stays fast as their data grows,
- their data is safe, backed up, and not leaking,
- updates ship without breaking their workflow,
- and someone handles it when something goes wrong.
Code is cheap now, but it was never the product. That's why "I can rebuild that in a weekend" can be both true and beside the point.
Why engineers come out ahead
I'm not a leader in the field. I'm just a career switcher who loves programming, but I truly believe that engineers come out ahead in all this.
Software engineers are the ones with the skills to give agents real system requirements. They're the ones who can discuss architecture with an agent and, when they're not being lazy, review its output instead of letting an unmaintainable monstrosity grow from layers of agentic patches.
Software engineers are also the most able to scratch their own itches. So they get to practice what most of them love to do — building solutions — at an unprecedented rate.
And when a problem turns out to be hard enough, they're the ones best equipped to evolve a toy project into a viable product.
Easy itch or hard problem, engineers win either way.
Top comments (0)