Suki AI 2026: HCA, Trinity Health, Memorial Hermann Deployments

The Deployment That Defined the Month

Suki produced one of the more consequential April 2026 announcements for healthcare buyers. The platform changed shape, the pricing model evolved, and a wave of named enterprise customers committed publicly. Together those signals reshape the vendor shortlist for any team running a healthcare AI agent RFP this quarter or next.

This post breaks down what shipped, what's now in production, what the contract looks like, and what to do about it as a buyer or a competing vendor.

What Customers Are Actually Paying

The pricing math for healthcare AI agents in 2026 has settled into three patterns that show up in nearly every deal we've reviewed:

1. Per-seat with AI add-on — the legacy CX vendor approach. Typically $80-180 per agent per month plus a $50-120 per-seat AI module fee. The model that's losing share fastest.
2. Per-conversation or per-resolution — the Decagon-led model. $0.40-$1.20 per resolved conversation, sometimes tiered with volume discounts kicking in at 100K and 1M monthly conversations. The model gaining share.
3. Per-outcome — Sierra's signature model. The platform charges only on resolutions confirmed by the customer or measured against a defined success criterion. Effective pricing lands between $1.50 and $3.00 per fully resolved ticket depending on intent complexity.

Enterprise buyers are increasingly demanding hybrid contracts — a small platform fee plus per-outcome usage — to align vendor incentives with customer success without runaway exposure to top-line conversation volume variability. The smartest contracts include caps, floors, and explicit definitions of "resolved" written in plain language.

What's Bundled, What's Add-On

The unbundling pattern across healthcare AI agent platforms in 2026 is consistent:

• Bundled in the base tier: agent runtime, conversation logging, basic analytics dashboard, standard model access (mid-tier reasoner), single-channel deployment, basic CRM connectors
• Add-on at meaningful cost: voice channel, premium model access (Claude Opus 4.7, GPT-4.1), custom guardrails, advanced analytics with cohort breakdown, dedicated customer success, compliance certifications beyond multi-region deployment
• Negotiable at signing: SSO report delivery cadence, data residency, custom integrations, training-data ownership clauses, IP indemnity, termination terms

The economics for the vendor are heavily weighted toward the add-ons. Most enterprise contracts end up 60-70% bundled and 30-40% add-on by spend. Your starting position in negotiation should be 90% bundled, with the explicit understanding that you'll concede on some add-ons but not all.

Healthcare-Specific Risk and Reward Math

For healthcare buyers, the risk-reward calculation in 2026 looks different than horizontal SaaS:

• Reward upside is large because the manual cost base in healthcare is large — labor is expensive and the operational hours are real
• Risk downside is also large because regulatory and reputational risk is amplified in regulated verticals
• The right deployment posture is staged: narrow intent coverage first, expand only after months of stable operation and demonstrated quality
• Vendors who push aggressive expansion timelines should be asked why — the right answer is "because the metrics show it's safe," and there should be data behind that
• Internal stakeholder management (clinical leadership, general counsel, compliance, security) takes longer than the technical integration

The vendors and customers winning are the ones with patience and discipline about scope expansion.

What's Driving Vendor Choice

Three forces shape vendor selection in this segment in 2026, in roughly this order of importance:

1. Existing CRM, CX, or ITSM platform — buyers default to bundled options unless the agent quality gap is significant. The gravitational pull of incumbent platforms is strong and getting stronger.
2. Compliance posture — vendors without HIPAA BAA, or ISO 27001 are screened out at procurement, regardless of how good the agent itself is
3. Reference customers in the same vertical — abstract capability claims lose to concrete deployments at peer companies. Vendors who can name three customers at the buyer's revenue band always win the close.

Vendors winning new business in 2026 lead with reference architecture diagrams from named customers, not feature checklists. The shift in sales motion is visible across every category.

Frequently Asked Questions

What is the typical time-to-deploy for an enterprise healthcare AI agent in 2026? Four to ten weeks for a tier-1 intent. Most of the time is in knowledge base curation and escalation rule definition, not the model integration itself. Teams that have done it before move faster on the second use case.

What's a reasonable per-conversation cost for a production healthcare AI agent? Between $0.20 and $1.50 depending on model choice, conversation length, tool-call complexity, and channel. Voice agents typically run 2-3x chat agents on a per-conversation basis because of the speech-to-text and text-to-speech overhead.

Should we build or buy an agent platform in 2026? For most teams, buy. Build only if you have a five-plus engineer AI platform team and a 24-month commitment. The reference architecture, model routing, observability, and compliance work in a buy is more than most teams realize until they try.

How do we evaluate vendors apples-to-apples in an RFP? Insist on a 30-day pilot with your real data, your real intents, and your real evaluation criteria — not the vendor's standard pilot. Most vendors will agree if you push. The ones that won't, drop from the shortlist.

Sources

• Suki primary — https://suki.ai
• www.wsj.com coverage — https://www.wsj.com
• www.cnbc.com coverage — https://www.cnbc.com
• techcrunch.com coverage — https://techcrunch.com
• Industry analyst report — https://www.gartner.com