Experity

Overview

RCM vendor, dominant in the urgent care space. Medallion partner for roughly 3–4 years. Experity originally built its own credentialing + enrollment team ~5 years ago (circa 2021); it grew faster than they could staff it, which is what drove them to bring Medallion in as the back-end enrollment engine. Used by Medallion sales as the canonical reference case for RCM-partner resale models (cited to both Sunbound and Raintree in March 2026).

Key Contacts

• None captured in current sources (relationship discussed by Medallion staff externally; no Experity participants in-call).

Active Work / Processes

Resale partnership model

• Medallion contract sits at the Experity enterprise level (not with Experity’s sub-customers).
• Experity buys a bucket of enrollment applications per year from Medallion (e.g. ~500 or ~1,000 apps per Mallory’s description to Raintree).
• Experity’s sales/revenue team pitches Medallion credentialing as a value-add to their own clinic customers; if a customer opts in, they get added into Medallion via API.
• Medallion does the credentialing + enrollment work directly (submissions, follow-ups, revalidations); Experity is the client-facing “white glove” layer and the point of billing to the end clinic.
• Experity bills its own customers on a consumption basis (per application) with an upcharge on top of the Medallion rate.
• Systems connected via API between Experity platform and Medallion.

Platform footprint

• As of 2026-03-19, Experity had 87 unique customer instances inside the Medallion platform (sub-customers scoped under the Experity enterprise account), each with its own organizational access — used as the canonical example of how Medallion isolates RCM-partner sub-customers (shown by Scott Everline during Sunbound BVA demo).
• Medallion does not charge per instance for RCM-partner sub-customers; pricing is facility/transaction-based.

Pain Points / Open Issues

Custom-payer-name on-hold lines surfacing as unassigned (2026-03-30)

During the PE weekly ops review, Nicole called out that 57 “unassigned” rows in Sigma included Experity items — on-hold lines where a custom payer name had been entered, which doesn’t auto-assign via the payer distribution list and falls through to manual assignment. Custom payer names can no longer be created going forward, but legacy ones still pull into this bucket. Source: 2026-03-30 Weekly PE Operating Review.

Decisions & Commitments

• (none captured in current sources)

Key Facts

• Vertical: urgent care RCM
• Partnership length: ~3–4 years as of March 2026
• Deal structure: enterprise contract + bucket-of-enrollments + API integration + Experity resells on consumption basis
• Scale inside Medallion: 87 customer sub-instances (2026-03-19)
• Events: Experity runs an annual conference that Medallion has attended multiple times (Mallory Smith mentioned attending “a couple of” Experity conferences)

Source History

• 2026-03-19 — Medallion & Sunbound II — Scott Everline used Experity’s 87-instance Medallion footprint as a demo example of RCM-partner architecture.
• 2026-03-20 — Medallion <> Raintree Reconnect — Mallory Smith described the full Experity resale model as a template Raintree could adopt; “3–4 years” partnership; “they built their own cred team ~5 years ago, grew too fast, came to us.”
• 2026-03-30 — Weekly PE Operating Review — Experity on-hold custom-payer-name lines causing Sigma unassigned-bucket noise.