You're probably being sold one thing and shipped another. The slide says autonomous: an agent that acts on your behalf while you get on with your day.

Then the thing arrives, and it's a very capable assistant: it drafts, it suggests, it summarises, and then sits there politely until a person tells it what to do next. Useful, often genuinely so, but not quite what you thought you'd bought. That quiet disappointment is sitting underneath a lot of enterprise AI right now.

The word doing the damage is "agentic", and it's worth being precise about it. An agent acts: it initiates, it decides, it carries a task through without a human in the loop for every step, and (the part the vendors skate over) it owns the outcome. An assistant responds: you ask, it answers; you point, it moves, and there's always a hand on the button. The difference isn't how clever the model is, because the same frontier model can power both. It's whether the vendor will let the software act without you pressing go, and whether they'll stand behind what happens when it does. Right now, almost none of them will.

Agentic is a tense, not a capability

The trick, and it's rarely even a cynical one, is that when a vendor says their product is agentic, they're usually describing a roadmap in the present tense. The autonomy is real on a slide, in a closed beta, in the demo environment where the data is clean and the awkward edge cases have been removed. What's sold as "does" is very often "will do". The verb is carrying the whole sentence, and it's pointing at next year.

You can see it in the naming if you look. When SAP unveiled its "Autonomous Enterprise" at Sapphire this spring, the headline suite was described as more than fifty Joule Assistants, orchestrating a couple of hundred specialised agents underneath. Read that back. Even the company building the most ambitious version of all this calls the things you'll actually touch assistants. Salesforce will tell you Agentforce resolves the large majority of customer queries with nobody human involved (85%, by its own count), and for a narrow, well-bounded job like first-line support, that's plausibly true. Press past the headline and the same shape appears everywhere else: real autonomy in one well-lit lane, and a supervised assistant doing the rest. The reporting that's followed (early adopters wrestling with data quality, inconsistent behaviour, and pricing nobody could explain) is what that gap feels like once the contract's signed.

The technology is real. The marketing has simply run a year or two ahead of the engineering, which is what happens in every adoption cycle. How long the gap lasts, I'm not sure; maybe the engineering closes on the marketing faster than these cycles usually allow. Either way, it only becomes your problem if you buy on the marketing's timeline and then plan your business on it too.

Why the difference lands on you

If all this amounted to was a slightly grander word than warranted, it wouldn't be worth writing about. But the agent-versus-assistant line is also the accountability line, and that's where it gets expensive.

Deploy a genuine agent and you've got to answer some uncomfortable questions before you switch it on: which decisions it's allowed to make, what it does when it's unsure, who owns the result when it's wrong. Deploy an assistant dressed as an agent and those questions get skipped, because everyone assumes a human is still in the chair, right up until the day the thing does something consequential and you find that nobody ever decided who was responsible. You've taken on all the risk of letting software act on its own, while still doing all the supervising yourself. The worst of both, paid for at the price of the better one.

This is the supply-side mirror of something I've written about before from the buyer's end: most organisations want agents but can't yet support them. The two halves feed each other. Buyers who aren't ready can't easily tell roadmap from running product, so they reward the grander slide; vendors, sensing that, sell the grander slide. And both bets come due at the same place: the moment something goes wrong and nobody can say who owned it. For a smaller business that sting lands harder, because you don't have the spare process, the legal cover, or the slack in the budget that lets a large enterprise shrug it off.

How to tell, in the room

There's no need to become a sceptic about AI to protect yourself here. You just have to drag the verb back into the present tense. A handful of questions does most of the work, and you can ask all of them in a single meeting:

  1. Show me the autonomous part running. Not a video, not a sandbox, but the actual product, doing the actual thing, on data that looks like mine. If the demo always has a human clicking "approve" between steps, you're buying a faster co-pilot, not an agent.
  2. What does it do when it isn't sure? A real agent has an answer to this: it escalates, or it pauses and flags the gap for a person. A relabelled assistant just hands the whole problem back to you and calls it a feature.
  3. What's generally available today, and what's roadmap? Make them sort the slide into things you can use this quarter and things you're being shown to close the deal. The honest vendors will do it without flinching.
  4. Who's accountable when it gets something wrong, and how do I undo it? Watch what happens to the word "autonomous" the moment liability and rollback enter the conversation. It tends to shrink.
  5. What am I actually committing to? Pricing that assumes autonomy you won't have for a year, integration work that quietly lands on your team, lock-in that's hard to reverse. The cost of the roadmap is usually paid on today's invoice.

If you want a sharper sense of what you're being sold versus what you're being shown, it's worth knowing where the agentic maturity scale actually tops out before you walk in. Most products selling level five are shipping level one or two, and that's fine, as long as you know which one is landing in your account.

Buy the assistant, just buy it on purpose

An assistant isn't a con, and that's the part worth holding onto. For most small and mid-sized businesses, a good assistant (one that drafts the proposal, reconciles the invoices, answers the first-line query) is exactly the right tool for where you actually are. The value is real and it's available today, not next year.

The mistake isn't buying one. It's paying agent prices for it, and building agent-shaped plans around it — the headcount you were going to redeploy, the process you were going to leave unsupervised — for something that still needs you in the chair. That's how you end up disappointed by software that was, on its own terms, working perfectly well.

So when the next slide says agentic, treat the word as a question rather than a claim, and make the vendor earn it before you pay for it.