Medallion aiwiki

Sunbound

4 min read

Sunbound

Overview

Senior-living RCM company (sunboundhomes.com). Active Medallion prospect as of Q1 2026, in the BVA (business value assessment) phase. Use case is facility-level enrollment for senior-living communities — not individual provider credentialing. Referred by Brigade (existing Medallion customer). Zach, Manny, and Anh have prior Medallion exposure via customers (SeniorDoc, GeisMed) and/or prior employers (Weight Watchers).

Key Contacts

Sunbound (external)

  • Manny Cominsky — (manny@sunboundhomes.com) — leadership / deal sponsor; provided the underlying numbers for the BVA
  • Amy Raymond — Chief Operating Officer, amy.raymond@sunboundhomes.com — RCM, onboarding, pay-ops all report up to her; new to Sunbound, wrapping up old contracts
  • Zach Miller — Revenue Cycle Team Lead, zach@sunboundhomes.com — day-to-day cred/enrollment work; currently ~25% of time on credentialing (was higher before new hire)
  • Anh Tran — Lead Product, anh.tran@sunboundhomes.com — background in health-tech RCM, prior auth platforms, consumer health; prior Medallion exposure via Weight Watchers

Medallion (internal)

Active Work / Processes

Business Value Assessment (in progress, as of 2026-03-19)

Medallion ran through a BVA deck with Manny, Amy, Zach, and Anh. Open adjustments committed:

  • Revise the FTE scaling estimate down from 9 to ~7.5 (originally used 0.75 FTE per 150 NPIs bucket; Amy pushed back that the math was inflated because enrollment is at the facility/community level, not per-provider)
  • Re-cut the revenue-at-risk math to reflect Sunbound’s cut of their customers’ revenue, not gross customer revenue (Scott offered to share the algorithm so Sunbound can compute their own cut)
  • Pricing not yet attached — BVA is validation-only at this stage

Scope clarified

Sunbound deals with facility enrollment (enrolling senior-living communities with payers), not primary-source verification on individual providers. Scott confirmed that maps to Medallion’s facility-enrollment flow (facility profile + W9/TIN/NPI + taxonomy + accreditations + licenses → enrollment requests + follow-ups + revalidation tracking). A future expansion into provider-level PSV / CAQH maintenance is a potential follow-on use case per Amy, but not in the current scope.

Sub-account architecture

Sunbound wants each of its customers (senior-living operators) to have their own organizational instance inside Medallion so customers can’t see each other’s data — matches the model Medallion already runs for Experity. Sunbound as the admin/super-user has full visibility across. Medallion doesn’t charge per user seat; fees are per facility seat + per enrollment transaction.

Availity fallback

Not all Sunbound communities have Availity set up. Scott confirmed Medallion can submit directly to the payer (form-mapping from Medallion data) when Availity isn’t available. Fax submission is the only method Medallion explicitly won’t do.

Pain Points / Open Issues

Manual cred tracking today

Spreadsheets + an in-house “scraper tool” are the current system — drives denials, rework, and customer frustration per Nave’s recap. Credentialing gaps are estimated to cause 1–3 months of billing delay.

Customer TINs/NPIs sometimes unknown

Manny flagged that Sunbound’s customers often don’t know their own TIN or NPI at onboarding; Sunbound built an internal fuzzy-match engine for NPI. Medallion doesn’t fill the TIN-discovery gap; they expect the W9 submitted as part of facility info to carry the TIN.

Customer cost sensitivity

Amy noted the $3K/facility add-on SKU is likely above most of their customers’ pricing tolerance. She’s exploring a lighter-touch value-add use case where Sunbound helps customers organize cred docs without doing the full enrollment work — ROI would be softer than hard FTE-savings numbers.

Decisions & Commitments

  • 2026-03-19 — Medallion to revise the BVA deck (FTE count, revenue-at-risk math) and send to Manny’s email, cc’ing the rest of the team. Source: Medallion & Sunbound II.
  • 2026-03-19 — Manny confirmed that once enabled, credentialing would not be a one-year experiment — Sunbound sees this as a core ongoing offering. Nave will present 1 / 3 / 5-year pricing options once BVA is validated. Source: same.
  • 2026-03-19 — Next meeting tentatively same time next week (2026-03-26). Source: same.

Key Facts

  • Current scale: ~120 NPIs
  • 5-year target: 1,500 NPIs (12×), 150 logos
  • Revenue model assumption used in BVA: ~2M–$4M)
  • Credentialing delay impact: 1–3 months → 10% claim impact estimated
  • Add-on pricing (Sunbound → their customers): $1–3K per community/facility, ad-hoc; tied to Medicaid/commercial app count
  • Credentialing scope: facility/community level only (at current phase)
  • Referrals/prior exposure: Brigade referred them; Amy knows Medallion via SeniorDoc and GeisMed; Anh knows it via Weight Watchers
  • Segment: senior living (distinct from hospital/provider groups — Amy repeatedly flagged senior living as its own world)

Source History

  • 2026-03-19 — Medallion & Sunbound II (BVA walkthrough) — initial intro of Amy/Anh, BVA deck walkthrough, scope clarification (facility vs provider), sub-instance architecture match-up to Experity, Availity fallback.

Graph View

Backlinks