Prior authorization & UM · AI utilization management
Xsolis
Xsolis is an AI utilization-management platform for providers and payers. It supports status determination and collaboration so UM teams can reduce manual review friction. It is not a consumer telehealth brand or a basic fax prior-auth portal.
Strong fit
- Health systems and payers that want AI-assisted utilization management and status determination
- Teams measuring avoidable days and concurrent review workload
- Organizations willing to connect clinical data for model-assisted decisions
Weak fit
- Groups that only need a fax portal for occasional prior auth forms
- Buyers with no appetite to change UM nurse workflows
- Organizations that cannot share the clinical data the models need
Bottom line
Xsolis earns a Recommend for mid-market and enterprise buyers modernizing utilization management with AI-assisted status and collaboration between providers and payers. Outcomes look strongest when UM leaders track avoidable days and review workload. Projects stall when the tool is a side dashboard. Product depth is among the stronger marks in this new prior-auth and UM station. Implementation needs clinical data access and change management for review staff. Pricing is enterprise-opaque. Score leads this station's first board.
Score breakdown
Weights: Outcomes 35% · Product 30% · Implementation 20% · Pricing clarity 15%.
Xsolis applies AI and clinical data to utilization management so providers and payers can move status decisions with less manual friction. It belongs in the prior-auth and UM station, not in general claims RCM.
Define metrics up front and train review staff to trust and challenge model output. Projects fail when the software is installed and concurrent review habits stay unchanged.
On this station's opening board Xsolis leads Agadia and Silna on overall score, with the usual enterprise pricing opacity.
Competitor landscape
| Vendor | Overall | Ease of implementation |
|---|---|---|
| Xsolis | 7.8 | 7.3 |
| Agadia | 7.6 | 7.2 |
| Silna Health | 7.3 | 7.1 |
| Availity | 7.5 | 7.3 |
Pricing
| Item | Detail |
|---|---|
| Model | Enterprise or mid-market software contracts for UM / status platforms. |
| What usually drives cost | Facilities or covered lives, modules, and integration scope into EHR and payer systems. |
| What to ask in diligence | Year-one cost at your volume, what data feeds are required, and success metrics for avoidable days. |
| Published pricing | Public list price: not published. Expect a custom quote. |
Prerequisites for purchase
| Need | Why it matters |
|---|---|
| What you need to get Xsolis to function | |
| Clinical data access for UM models | Without feeds, AI status suggestions starve. |
| UM leadership willing to change review workflows | Dashboards alone do not free days. |
| Payer or provider collaboration agreements where needed | Network value needs both sides engaged. |
| Success metrics such as avoidable days or review turnaround | Unmeasured programs drift. |
| IT capacity for EHR and analytics integration | UM platforms are data projects. |
| What will maximize your value | |
| Pilot on high-volume service lines first | Trying every service line at once hides signal. |
| Calibrate nurse trust in model output with override tracking | Blind trust and blind distrust both fail. |
| Share outcome dashboards with finance | Avoidable days need a CFO audience. |
| Revisit criteria packs when policies change | Stale criteria recreate manual work. |
| Budget change management, not only licenses | Workflow adoption is where these programs stall. |
| Deal-breakers | |
| You only need occasional fax prior auth forms. | |
| You cannot provide clinical data access. | |
| UM leadership will not change concurrent review habits. | |
| No one owns avoidable-day or turnaround metrics. | |
| IT cannot integrate for the next two quarters. | |
Value creation time frame
| # | Stage | Typical range |
|---|---|---|
| 1 | Contract signed → kickoff | 4-8 weeks (security, data mapping, pilot units) |
| 2 | Kickoff → first live workflow | 3-6 months for a meaningful UM pilot |
| 3 | First live workflow → steady value | 4-8 months of tuning before multi-facility expansion |
Methodology
| Weight | Factor | What it measures |
|---|---|---|
| 35% | Customer outcomes | Whether buyers get measurable operational or clinical-workflow results after go-live |
| 30% | Product | Capability depth, reliability, and fit for the job the category actually buys |
| 20% | Implementation | How hard it is to stand up, integrate, train, and stabilize |
| 15% | Pricing clarity | Whether a buyer can model total cost without a mystery quote |
| Label | Meaning |
|---|---|
| Highly recommend | Strong outcomes and product with manageable caveats |
| Recommend | Solid fit for the right buyer; know the tradeoffs |
| Conditional | Only with a specific use case or heavy caveats |
| Not recommended | Avoid for most buyers in this category |
Read our full methodology for how we weight scores and assign recommend labels.