A few weeks ago I was setting up a new project and needed to do the usual dance: create a Notion doc, spin up a Linear board, invite the team to Slack, and set up a couple of Zapier automations to connect them all. It took me most of an afternoon.
That's when it hit me — I wasn't actually trying to "use" any of these tools. I just wanted the outcome. I wanted the project set up. And somewhere between the fifth Zapier trigger and the third failed webhook, I found myself thinking: why am I the one gluing all this together?
That question is basically the whole thesis behind this post. AI agents aren't just a new feature category bolted onto SaaS. They're starting to eat the reason SaaS exists in the first place.
The old deal: software rents you a workflow
Traditional SaaS sells you a workflow, not an outcome. You pay for Notion, and Notion gives you a very nice, very rigid shape to pour your thoughts into. You pay for HubSpot, and it gives you a CRM shape. You pay for Zapier so you can awkwardly stitch the shapes together.
This worked great for twenty years because the alternative was building everything yourself. SaaS was the shortcut. But the shortcut came with a tax: you had to adapt your work to fit the tool, and when you needed two tools to talk to each other, you had to become a part-time integrations engineer.
The new deal: software does the workflow for you
An AI agent flips that relationship. Instead of "here's a tool, go operate it," it's "here's the outcome, go figure out how to get there." You tell an agent "onboard this new client" and it can read the contract, create the folders, send the welcome email, schedule the kickoff call, and post a summary in Slack — using whatever tools it has access to, without you clicking through five different dashboards.
That's the part that's easy to miss if you only think of agents as "chatbots with extra steps." A chatbot answers questions. An agent does multi-step work:
That loop — plan, act, observe, adjust — is the real unlock. It's the difference between a search bar and an employee.
_Why companies are building agents instead of "just" chatbots _
1. Chatbots hit a ceiling fast. A support chatbot that can answer FAQs is nice, but it doesn't reduce headcount. An agent that can actually issue a refund, update a database, and close the ticket does. Once companies realized the ROI of "does the task" versus "describes how to do the task," the incentive to go further became obvious.
2. The interface itself is becoming the product. If an agent can competently use ten different tools on your behalf, the value shifts away from any single tool's UI and toward whoever orchestrates the agent. That's a scary position to be in if you're a SaaS company whose entire moat was a nice dashboard. So a lot of these companies are racing to build the agent layer themselves before someone else builds it on top of them.
3. Retention math changes completely. SaaS pricing has always been "pay per seat, per month, forever." Agents change the unit of value to "task completed." That's a much harder thing to price, but it's also a much stickier thing to build a moat around — whoever owns the agent that actually finishes the work owns the relationship with the customer, not whoever owns the interface.
None of this means chatbots are dead. It means chatbots were the training wheels, and a lot of companies are quietly removing them now that the model is good enough to hold the handlebars itself.
This isn't hypothetical anymore
You can already see the shape of this in the wild:
The common thread isn't "AI is involved." It's that a human used to be the glue between steps, and now something else is.
The uncomfortable part
I don't think this trend is purely good news, and I'd be lying if I pretended otherwise. A few things worth sitting with:
I bring these up because I think a lot of "AI is replacing X" content skips straight to the exciting part and ignores the friction. The friction is where the real engineering problems — and honestly, the real opportunities — are.
So what happens to "software" as a category?
My honest guess: software doesn't disappear, but the thing you pay for shifts up a level. Right now you buy access to an app. Increasingly, you'll buy access to an outcome, and the agent will decide which apps (if any) to touch along the way. The apps themselves become more like tools in a toolbox than destinations you visit.
If you're building products right now, I think the practical takeaway is this: don't ask "how do we add a chatbot to our SaaS." Ask "if a customer never opened our dashboard and just told an agent what they wanted, would our product still be the one doing the work?" If the honest answer is no, that's worth losing some sleep over. Curious how others here are seeing this play out — are you building agent-first products, or still bolting AI features onto existing SaaS? Would genuinely like to hear how it looks from inside different companies.