We wrote recently about AI assistants answering questions that used to be searches. There's a stranger shift a step behind it: agents that don't just answer, but act. Give an agent a task and a budget, and somewhere in the middle of that task it may need software. Transcription for an hour of audio. A geocoding API. A monitoring service for the thing it just deployed.
Which raises a question most SaaS companies have never had to ask: can a machine become your customer?
Today, mostly not. The signup flow has a CAPTCHA built specifically to stop it. The pricing lives in a JavaScript-rendered comparison table with a "Contact sales" button. The onboarding is a product tour it can't click through. Everything about the funnel assumes a human with a mouse, a credit card, and patience.
But agents with budgets are coming, in small numbers first, and the products they can actually buy will get a market the others can't see.
How an agent shops
It's worth being concrete, because an agent evaluates software nothing like a person does.
It doesn't watch your demo video or feel anything about your landing page. It reads the documentation, checks whether there's an API for the thing it needs, and quite possibly runs a test call before "deciding" anything. Clear docs, a real free tier or trial key, transparent per-unit pricing, and error messages that say what actually went wrong: to an agent, that is the product experience. Your beautiful dashboard is invisible.
It also doesn't forget. A human shrugs off a flaky afternoon. An agent that got three timeouts from your API has that in its context, or its operator's logs, the next time a similar task comes around. Reliability stops being a background virtue and becomes the entire brand.
What this asks of builders
If you run or are building a SaaS product, the practical list looks like this:
- Treat the API as the storefront. Everything the product does should be reachable without a mouse. The dashboard becomes a window onto the account, not the only door into it.
- Publish machine-readable facts. An OpenAPI spec, honest documentation, pricing stated in text rather than trapped in a design. An
llms.txtdescribing what the product does. If a machine can't find out what you cost, it can't choose you. - Rethink the bot wall. Fraud is real and CAPTCHAs exist for reasons. But "block everything that isn't human" now filters out paying customers. The emerging middle ground is agent identity: delegated credentials, scoped API keys, spending limits, and OAuth-style flows where a human authorizes what an agent may do on their behalf.
- Make billing programmatic. Usage-based pricing with hard caps fits agents naturally. "Book a demo" does not. If a purchase requires a Zoom call, agents will route around you.
- Write error messages like documentation. A human calls support; an agent retries, adapts, or leaves. The quality of your failure modes decides which.
The honest caveats
Nobody knows the timeline, and the hard problems are real: who's liable when an agent buys the wrong thing, how refunds work, how you distinguish a customer's agent from a scraper wearing a nice user-agent string. Anyone selling certainty about any of this is guessing out loud.
But notice the shape of the preparation list: a clean API, honest documentation, transparent pricing, reliable uptime, graceful failures. These are exactly the things that make software better for humans too. We've built enough SaaS platforms to know that list was always the assignment. The agents just grade it more strictly.
That's the quiet version of the future we'd bet on: not a robot economy overnight, but a slowly growing share of revenue arriving through the front door you built for machines. Products that have that door will barely notice the transition. Products that don't will wonder where the traffic went.