I sold ITSM platforms for years, so let me be blunt about the move. When a buyer with three or four service providers walks in, the instinct on the sell side is to price the complexity, not the usage. Federation sounds technical and scary, so it gets quoted as if every connected provider needs its own bundle of paid seats. It usually does not. The Xurrent model is genuinely simpler than that, and the savings live in refusing to pay for the complexity story. The full pricing picture sits in the Xurrent pricing guide for 2026; this piece is about the SIAM-specific cost traps.
How does Xurrent license a multi-provider environment?
Xurrent charges for paid Specialist seats, the people who actively work records: agents, fulfillers, change and problem managers. Basic users who only raise requests, approve, or read are free. That model does not change because you run SIAM. Connecting a managed service provider's Xurrent instance to yours through federation does not, by itself, add a per-provider license fee. What adds cost is each provider needing paid Specialists to act inside your data, plus any account structure you stand up to keep them separate.
The seat-by-seat mechanics that decide who is paid and who is free are in Xurrent Specialist vs Basic user licensing explained. Read that first, because in SIAM the same misclassification error multiplies across every provider you onboard.
Where does the cost actually land in SIAM?
Three drivers, in order of how much money they move. First, the total count of paid Specialists across all parties working in your instance. Second, whether you federate separate provider accounts or share one, since separate accounts can carry their own minimums and platform terms. Third, the professional services to set up federation, integration and the SIAM process model. Everything else is noise next to these three.
| Cost driver | What the vendor will argue | What to counter with |
|---|---|---|
| Paid Specialists per provider | Each provider needs its own block of seats in your instance | Provider fulfillers should sit on the provider's own license and federate in; only pay for Specialists who must act on your records |
| Account structure | Separate accounts per provider for clean isolation | Shared account with trust relationships where governance allows, to avoid duplicate minimums |
| Federation and integration services | Fixed scoping package, per connection | Fixed-fee statement of work with acceptance criteria, not time and materials that drift |
| Annual uplift | Standard increase at renewal | Capped uplift locked before you scale provider count |
Should each provider have its own Xurrent account or share yours?
This is the decision that quietly sets your cost for years, so do not let it be made on the implementation call. Federating separate provider accounts gives clean isolation and lets each provider own its seats, which usually lowers your bill but can introduce per-account minimums on their side. Sharing a single account is simpler to stand up but tends to pull every Specialist onto your paper. The right answer depends on who owns the fulfilment work and where governance requires data separation. Model both before you sign, because switching later is a migration, not a setting.
Whatever you choose, the count you negotiate against has to be the real one. Benchmark the per-Specialist rate and the federation services against deals of similar shape using how to benchmark a Xurrent contract, so your target sits on market data rather than the vendor's opening number.
Our gated 2026 ITSM Negotiation Benchmark Report shows the discount ranges by deal size that anchor a credible Xurrent target in a multi-provider deal.
Model your SIAM seat count first.
We reconcile every paid Specialist across providers, settle the account structure, and cap the uplift before you scale. Fixed fee or gainshare.
Book a contract negotiation review →What are the mistakes that cost the most?
The first is paying for the complexity story. Federation is not a per-provider license event, so do not accept a quote that prices it that way. The second is letting provider fulfillers land on your license. If a managed service provider works your tickets, push their seats onto their own Xurrent entitlement through federation wherever the contract allows. The third is signing the account structure on the implementation call, which bakes in cost before anyone has modeled it. The fourth is scaling provider count under an uncapped uplift, so each new provider compounds an increase you never agreed to.
None of these require leaving Xurrent. They require negotiating the SIAM model deliberately, the same way you would benchmark and right-size any other estate. The discipline that ties it together is in our guide to ITSM renewal negotiation, and the firm has run this sequence across more than 500 engagements and $420M+ in ITSM contract value, averaging a 30% reduction by rebuilding the seat count from need.
How does federation change your leverage at renewal?
It strengthens it, if you understand the model. In a single-provider deal the vendor knows you are unlikely to rip out the platform, so the leverage is mostly about right-sizing. In a SIAM environment you have an extra card: where provider fulfillers sit. If those seats are on your license today, moving them onto the provider's own Xurrent entitlement through federation is both a cost reduction and a credible threat the vendor would rather avoid, because it shrinks your paid count without you leaving the platform.
Use that deliberately. Going into a renewal, model the count both ways, with provider seats on your paper and with them federated off it, and bring the lower number as your target. The vendor has to engage with a structure that is real and available rather than a vague demand for a discount. That is the difference between asking for a better price and presenting one.
What to do next
Map the paid Specialists by provider, decide the account structure on cost not convenience, and cap the uplift before you onboard the next party. When you are ready to run it, the engagement goes through our contract negotiation service on fixed fee or gainshare, and the wider context lives in the Xurrent pricing guide.
Frequently asked questions
- Does Xurrent charge per connected provider in a SIAM model?
- No. It meters paid Specialist seats, not federated accounts, so connecting another provider does not by itself add license cost. Confirm federation and account terms against your order form, as structure varies by deal size.
- What drives Xurrent cost in a multi-provider environment?
- The total paid Specialists across all parties, whether you run separate or shared accounts, and federation setup services. Basic users who only request or approve are free.
- How do you stop SIAM coordination from inflating the bill?
- Reconcile every Specialist against real fulfilment, push provider seats onto the provider's own license through federation, and cap the uplift before scaling. We average a 30% reduction by rebuilding the count from need.
Book a Xurrent review.
Map the seats, settle the account model, benchmark the rate, close capped terms before provider count grows. Fixed fee or gainshare.
Book a contract negotiation review →