Adonis appointed Alison Bloom-Kiefer as chief product officer and promoted Doug Pickett to chief revenue officer on Aug. 19, 2026, following a $40 million Series C round and what the company said was more than 4x revenue growth over the prior year. The C-suite additions signal that the AI revenue cycle management vendor is shifting from pilot projects toward platform-based operating models, which typically means more structured product roadmaps and a harder push to demonstrate value to health systems.
For hospital revenue cycle and IT leaders, the personnel moves are less about org-chart housekeeping and more about what comes next: larger, more repeatable deployments that demand tighter product execution and a more formal commercial operating model.
Why a CPO role matters for RCM buyers
A dedicated CPO usually appears when a vendor needs to make hard choices about what gets built and what gets integrated next. Adonis said Bloom-Kiefer will lead product strategy and execution and help "sharpen roadmap priorities" while reducing operational burden and recovering more revenue.
For operators, that tends to translate into clearer answers to the practical questions that stall enterprise rollouts: which queues get automated first, which edits remain human-controlled, what gets written back into the EHR or billing system, and how exceptions are handled.
Once an AI RCM tool moves beyond pilots, the hardest question becomes governance: who is allowed to change the workflow, and how does the system prove what it did and why?
What the first CRO appointment changes
Pickett becomes Adonis' first chief revenue officer after joining nearly three years ago as SVP of Sales. CRO appointments usually indicate the sales motion is being industrialized: tighter packaging, more standardized implementation services, and more disciplined renewal playbooks.
None of that is inherently good or bad. It does, however, change how buyers should structure evaluation and contracting. If Adonis' commercial organization is being scaled, health systems should expect more explicit definitions of "value" and, potentially, more pressure to align on baseline metrics early.
In AI-assisted RCM, those baselines are often where projects succeed or stall: denial rates by payer and reason code, underpayment recovery timing, and the labor time spent on rework. The vendor's ROI narrative only holds if the data definitions and extraction methods are locked down across facilities.
Epic Connection Hub availability
Adonis also announced it is available in Epic Connection Hub. For Epic-heavy providers, that can shorten the initial discovery process for integration pathways and give security and IT teams a familiar starting point for assessing how a third-party tool will interact with Epic and related systems.
But Connection Hub availability is not a substitute for integration diligence. AI RCM platforms still live or die on data latency, write-back boundaries, and workflow ownership. For systems operating with fragmented payer portals, multiple clearinghouses, or decentralized billing teams, "orchestration" often becomes an integration project as much as a product purchase. That's where the CPO's roadmap priorities and the CRO's implementation standards will be felt first.
Questions to put on the table before the next AI RCM contract cycle
- Roadmap and workflow ownership: Which specific denial and underpayment workflows will Adonis productize in the next two quarters, and where does the system stop and a human queue begin? Ask for a workflow map that names system-of-record fields and handoffs.
- Integration and auditability: If deploying alongside Epic, what data moves through standard Epic interfaces versus custom feeds, and what is the audit trail for each AI-recommended action? Require a description of write-back behavior and exception handling.
- Baseline metrics for value: Before signing, agree on the exact denial and underpayment baselines, time windows, and payer segmentation used to measure impact. Ensure multi-facility normalization is part of the plan if the rollout spans hospitals or physician groups.
- Commercial packaging: With a first CRO in place, clarify what is included in implementation services, what is optional, and how changes in claim volume or facility count affect pricing and renewal terms. Ask for a template SOW early.
Why this matters for healthcare revenue cycle leaders
The most useful benchmark in AI RCM isn't a demo. It's whether a vendor can commit to measurable change in denials and rework using your data definitions across all facilities. Adonis' new executive structure suggests the company is preparing for that level of scrutiny - and health systems should prepare their baseline metrics and governance requirements before entering negotiations.
Your membership also unlocks:
