AR · July 2026 · 9 min read
How to choose an enterprise agentic AI vendor when none of them publish a price
Four platforms will make your shortlist and none will tell you what they cost. Here is what to compare instead, including which are likely to still be independent in three years.
Four platforms in this directory have been acquired since 2024. Zendesk alone bought Klaus, Ultimate and Forethought, the last of those closing fifteen days after it was announced.
If you are signing a three-year enterprise contract, that is not industry trivia. It is the most under-weighted variable in your evaluation.
You cannot compare on price, so compare on something else
Decagon, Sierra, Ada, PolyAI, Netomi and the CCaaS suites all price by negotiation. You will not get a number without entering procurement, which means shortlisting on cost is impossible and biases early evaluation toward whoever publishes.
So compare on the things that are knowable: capitalisation, architecture, and what happens when the agent is wrong.
1. Will they still be independent?
| Vendor | Position | Acquisition risk |
|---|---|---|
| Sierra | ~$950M round, valued above $15B | Very low |
| Decagon | ~$481M raised, $4.5B valuation | Very low |
| Ada | ~$174M raised, $1.2B valuation (2021) | Moderate |
| Cognigy | Acquired by NICE | Already happened |
| Forethought | Acquired by Zendesk, March 2026 | Already happened — no longer standalone |
Sierra and Decagon are capitalised well enough that few plausible acquirers exist. That is a genuine procurement consideration, not a vanity metric.
2. Procedures or improvisation?
The two most credible independents reach the same architectural answer from different directions. Decagon configures explicit operating procedures. Ada forces the AI through no-code business rules step by step before it resolves anything.
Both are choosing constrained execution over free generation. For anything touching money or compliance that is the correct choice, and a vendor that cannot show you the constraint mechanism is telling you something.
3. Voice, or only chat?
Sierra is the only platform here treating voice and chat as one agent with one configuration. If phone volume is material, that is the single strongest differentiator available and comparing Sierra's rate against chat-only tools is not comparing like with like.
If phone is not in scope, you are paying for breadth you will not use, and Decagon or Ada is the better shape.
4. What does the pricing model do at your volume?
Sierra charges per resolved interaction at a reported $1.50, negotiated. Fin publishes $0.99. Outcome pricing sounds aligned and is, but it also means costs rise as the agent improves. At 10,000 monthly resolutions a $1.50 rate is $15,000 a month, and you are negotiating that against one of the best-funded companies in the sector.
5. Questions for the call
- What event triggers a billable resolution, and what happens when a customer abandons mid-conversation?
- Show me the mechanism that stops the agent improvising outside policy.
- What is your resolution rate confirmed by the customer, not inferred from silence?
- What is the implementation timeline, in weeks, with named dependencies on our side?
- Who owns you in three years?
Funding figures are drawn from press reporting and company announcements, cited below. We have not tested any enterprise platform — they are sales-led and we do not accept vendor-configured environments.
The short version
You cannot shortlist enterprise agentic vendors on price because none publish one. Shortlist on independence, on whether the architecture constrains the agent to your procedures, and on whether voice is in scope. Sierra if phone matters and budget is not the constraint. Decagon if auditability matters most. Ada if you need channel and language breadth with a no-code owner. And ask every one of them who owns them in three years.
Frequently asked
Why does no enterprise AI support vendor publish pricing?
Because it is negotiated per customer against support volume and integration scope. The practical effect is that you cannot shortlist on cost, which disadvantages vendors who do publish.
Which enterprise vendors are least likely to be acquired?
Sierra and Decagon. Sierra has raised at a valuation above $15 billion and Decagon around $481 million at $4.5 billion — few plausible acquirers exist for either.
Sierra or Decagon?
Sierra if phone volume is material — it is the only one treating voice and chat as one agent. Decagon if auditability and procedural control matter more than channel breadth.
What should I ask on an enterprise sales call?
What triggers a billable resolution, what stops the agent improvising outside policy, what the confirmed resolution rate is, the implementation timeline with dependencies, and who owns them in three years.
Tools mentioned
Full reviews, pricing tiers and where each one breaks.
Sierra
Bespoke enterprise builds with unusually natural conversation, and the only one in this group that handles voice properly too.
Decagon
Enterprise agent with deep configurability. Sales-led, so expect a procurement cycle rather than a signup form.
Ada
Multi-channel agent that predates the current wave, with the enterprise footprint that implies.
Forethought
ZendeskSelf-learning support agents, now folded into Zendesk. No longer separately buyable.
You can also look into
What is agentic customer support AI? A definition that survives contact with a sales deck
Every vendor now calls their product agentic. Most of them mean a chatbot with a better model behind it. Here is the distinction that actually holds.
Somebody claims 93% autonomous resolution. Here is what that number can hide.
Vendors publish autonomy rates between 30% and 93%. The range is that wide because they are not measuring the same thing.
Per-resolution pricing punishes you for making the AI work
The billing model most of this category adopted has a structural flaw: the better your AI performs, the more you pay.
How to handle customer support at scale with AI without breaking what works
Scaling support with AI is mostly a sequencing problem. Teams that automate in the wrong order end up with more escalations than they started with.
SOURCES
WRITTEN BY AR · UPDATED 2026-07-28
I run the testing here. Every platform on this site gets the same ticket set, the same escalation cases, and the same billing period — and I publish the invoice, not the marketing number. Where I have not tested something, the page says so.