Aisera After the Automation Anywhere Acquisition: Buyer Implications

Picture the renewal that lands eighteen months from now. A mid-market IT team signed Aisera in 2025 at a per-resolution rate, banking on agentic deflection to cut their service desk load. The renewal quote arrives on Automation Anywhere paper, the line items have changed names, the resolution definition reads differently, and the per-unit number is no longer the one they shook on. Nobody discontinued anything. The product just got folded into a bigger catalog, and the buyer who did not anchor their terms is now negotiating against a model they never agreed to. That is the scenario this article is built to prevent.

What actually changed when Automation Anywhere acquired Aisera?

Aisera, an agentic AI vendor for IT and employee support, was acquired by Automation Anywhere, an automation platform company. On paper the logic is clean: pair conversational AI resolution with process automation. For a buyer, the change that matters is not the technology story, it is the commercial one. Aisera has sold on a per-resolution basis, where you pay per issue the AI closes. Automation Anywhere has sold automation platform capacity. When two pricing philosophies merge, the acquired one usually bends toward the parent, and the bend lands on the customer at renewal.

Treat this the same way you would treat any AI vendor inside a larger portfolio. ServiceNow folding in Moveworks is the same shape of problem, and the same discipline applies. The full framework sits in our 2026 guide to agentic AI ITSM pricing and negotiation.

How does per-resolution pricing survive a platform-led parent?

It survives only if you write it down in a way the parent cannot quietly redefine. The risk with per-resolution pricing is not the headline rate, it is the definition of a resolution. A vendor can hold the per-unit price flat and still raise your bill by counting more events as billable resolutions: a clarifying turn, a handoff, a reopened ticket. After an acquisition, that definition is exactly the kind of fine print that gets re-drafted.

So nail the counting rules. What counts as one resolution, what does not, how reopens are treated, and whether deflected-but-unresolved sessions are billable. The buyer-side comparison of these models is in per-resolution vs per-seat AI ITSM pricing, and it is worth reading before you accept any restated definition.

What are the four buyer risks to price now?

What should you negotiate before the next renewal?

1. Lock the unit rate and the definition. Fix the per-resolution price and the exact counting rules in the contract, not the order form notes.
2. Cap the uplift. A single-digit annual cap, fixed for the term, so a platform premium cannot ride in on top.
3. Demand portability. If Aisera becomes an Automation Anywhere SKU, your rate, definition and cap travel to the successor product.
4. Win a re-price trigger. A material change to the commercial model gives you the right to re-price or exit without penalty.
5. Document the migration path. If you ever leave, you keep your conversation data and resolution history in a usable export.

This is the same playbook we run on any consumption-priced AI line. The discipline of not overbuying capacity you cannot yet forecast is covered in how to avoid overbuying AI assists in year one, and it applies directly to per-resolution commitments too.

When does this matter most?

It matters most if your Aisera renewal falls inside the next two cycles, because that is the window in which acquired products are typically re-packaged. If you are mid-term, use the time: get the portability and re-price language added now through a contract amendment rather than waiting for the vendor to set the agenda at renewal. We have run more than 500 ITSM engagements and average a 30% reduction, and the reductions that hold are the ones locked with terms, not just a one-time discount.

What to do next

Map your current Aisera terms against the four risks above, then decide whether to amend now or stage it for renewal. If you want a buyer-side read on your exposure and the exact clause language to ask for, the engagement runs through our AI cost control service on fixed fee or gainshare, and the platform-level context for ServiceNow-adjacent AI sits on the ServiceNow platform page.

Frequently asked questions

Does the acquisition change Aisera pricing immediately?

Not on day one, but it changes the trajectory. Acquired AI products get re-packaged into the parent model, so lock your unit rate, definition and cap now before a future re-bundle resets them.

What should an Aisera buyer negotiate now?

A fixed per-resolution rate with a written resolution definition, a capped uplift, portability of terms to any successor SKU, and a re-price or exit right if the commercial model materially changes.

Is Aisera at risk of being discontinued?

There is no signal of that, but every acquired product carries re-bundling and roadmap risk. The protection is contractual continuity language, not a prediction about the roadmap.