How do you start a white-label RCM service line?
Decide which workflows you will sell and which you will keep in-house, pick a client pricing model that matches how your production partner charges you, build per-client unit economics, put a BAA in place with each client and a subcontractor BAA with your partner, write branding and contact rules, then pilot on one client before selling broadly. You own the client and the accountability; the partner supplies production capacity.
How the white-label RCM model works
Three parties are involved, and most launch problems come from being vague about who owns what. The practice contracts with you. You contract with a production partner. The practice should only ever experience your company.
| Criteria | The practice (your client) | You (the brand) | Production partner |
|---|---|---|---|
| Contract | Signs with you | Signs with the client and the partner | Signs with you only |
| HIPAA role | Covered entity | Business associate | Subcontractor business associate |
| Pricing | Pays your rate | Sets the client price | Charges you its rate |
| Client communication | Talks to you | Owns every client conversation | None, unless you design it |
| SOPs and decisions | Sets policy (write-offs, collections) | Owns SOPs, approvals, escalations | Follows your SOPs |
| Production and QA | — | Reviews QA results, owns quality | Works the queues, runs sample QA |
Who this model fits, and who it does not
White-label solves a delivery problem. It does not create demand. It works best for companies that already have client relationships and need more production than they can staff.
- Fits: billing companies adding workflows such as denials, posting, or prior auth to existing accounts
- Fits: practice-management and EHR vendors that want to attach billing services to their software
- Fits: MSOs and healthcare consultants whose clients keep asking who can run the back office
- Fits: RCM companies whose sales pipeline is ahead of their hiring
- Poor fit: no client base yet. You will be paying for capacity while you look for accounts
- Poor fit: clients whose contracts prohibit offshore access to PHI. Check this before you sell, not after
Decide what to white-label and what to keep
Not every workflow should be white-labeled. High-volume, rules-based work suits a production partner. Judgment calls and client-facing work should stay with you, because that is the value your clients are paying you for.
| Workflow | White-label it? | Why |
|---|---|---|
| AR follow-up | Yes | High volume, repeatable, easy to measure by aging bucket |
| Denial rework | Yes, with your appeal rules | Production-heavy; you keep the appeal-or-write-off decision |
| Payment posting | Yes | Rules-based, auditable against ERAs, EOBs, and deposits |
| Eligibility and prior auth | Yes, if coverage hours fit | Time-sensitive; the partner must work during your clients' scheduling hours |
| Coding | Only with qualified coders | Needs credentialed staff and your own audit before you resell it |
| Write-off and appeal approvals | No | Financial decisions stay with you and the client |
| Client reporting and reviews | No | This is your relationship; the partner feeds you the data |
Choose a client pricing model that matches your cost
The most common margin mistake in white-label RCM is a mismatch between how you charge clients and how your partner charges you. If you bill a percentage of collections but pay your partner per dedicated seat, you carry all of the collection risk. When a client's payer mix gets worse, your revenue drops and your cost does not.
Percentage of collections
Easy to sell and aligned with client outcomes. Risky if your partner cost is fixed, because slow-paying months hurt only you.
Per claim or per transaction
Predictable and simple to reconcile against partner per-unit pricing. Clients may push back on paying for denied or reworked claims.
Dedicated seat, billed monthly
Maps cleanly onto an FTE-based partner cost. Works best for larger clients who want named capacity.
Fixed-fee project
Suited to backlog cleanups with a defined inventory and exit. Scope the inventory first or the fee will not hold.
Build unit economics before you quote
Work out margin per client, not per claim. The partner's rate is only one line. The costs that erode white-label margin are the ones you still carry yourself.
A simple check: client revenue minus partner cost, minus your own account-management and QA time, minus tools, minus onboarding spread over the expected life of the contract. If that number only works at full volume, the deal is fragile.
| Cost line | What to include |
|---|---|
| Partner production | Seats or per-unit fees, plus any minimums or ramp charges |
| Your account management | Hours per client per week for calls, reviews, escalations, and reporting |
| Your QA review | Time spent reviewing partner audit results and spot-checking work yourself |
| Onboarding (one-time) | Access setup, client-specific SOPs, payer playbooks, first-month rework |
| Tools | PM or EHR seats, clearinghouse fees, reporting and ticketing tools |
| Ramp period | Lower productivity in the first weeks while the partner learns the account |
Set up the BAA chain correctly
Under HIPAA, each practice you serve is a covered entity and you are its business associate, so you sign a BAA with every client. Because your production partner will access PHI on your behalf, it is your subcontractor business associate, and you need a separate BAA with it (45 CFR 164.502(e) and 164.308(b)). The practice does not usually sign anything with the partner directly.
The key rule is flow-down. Anything you promise the client in your BAA, such as breach notification timing, access controls, or return of data at termination, must also appear in your agreement with the partner. Otherwise you are promising something you cannot enforce. Have healthcare counsel review both agreements. This section explains the structure; it is not legal advice.
- Breach notification: the partner's deadline to notify you must be shorter than your deadline to notify the client
- Access: least-privilege logins per client, with a documented process for revoking them
- Offshore disclosure: some client contracts, payer agreements, and government programs restrict or require disclosure of offshore PHI access
- Termination: how PHI is returned or destroyed, and how fast access is removed
- Non-solicitation: the partner may not contact, solicit, or take on your clients directly
Launch sequence: from first client to a repeatable offer
Do not build a service catalogue before you have run the model once. Launch on one workflow with one client who trusts you, fix what breaks, and only then package it.
- 01
Pick one workflow and one client
Choose a queue with clear volume, such as AR follow-up, at a client who will give you honest feedback.
- 02
Write SOPs and branding rules
Document payer playbooks, note templates, how specialists identify themselves, and who may contact the client.
- 03
Sign the BAAs and provision access
Client BAA, subcontractor BAA with flow-down terms, then least-privilege access per client.
- 04
Baseline the KPIs
Record Days in AR, AR over 90 days, denial rate, or posting lag before work starts so you can show movement.
- 05
Run a bounded pilot
A defined window with agreed QA sample rates and continue, fix, or stop criteria set in advance.
- 06
Build the client-facing report
Turn partner output into your branded weekly report. If you cannot explain it in a client review, it is not ready.
- 07
Package and price the offer
Only now write the service description, pricing, and SLA you will sell to the next client.
Questions your clients will ask, and how to answer them
Decide your disclosure policy before the first sale. White-label keeps the partner behind your brand; it does not mean misleading a client who asks directly. Some contracts require you to disclose subcontractors anyway.
- "Who is actually doing the work?" Your team, supported by a production partner under your SOPs and QA
- "Where is our PHI accessed?" Answer accurately, including offshore access, and point to your BAA terms
- "How do you check quality?" Describe the sample audit cadence and what happens when an audit fails
- "Who do we call when something goes wrong?" Always you, with a named contact and response hours
- "What happens to our data if we leave?" Your termination and data-return terms, backed by the partner agreement
Where Salt HealthOps fits
Salt HealthOps works as the production partner behind white-label RCM offerings. We work inside your systems, follow your SOPs and branding rules, run sample QA, and give you per-client weekly reporting you can present as your own, with a US-based point of contact for escalations. We are BAA-ready for subcontractor agreements, and Salt Technologies is ISO certified with SOC 2 in progress. We do not contact your clients, and we do not promise specific collection outcomes.
White-Label RCM Services
How Salt delivers production capacity behind your brand.
Learn moreHow to Evaluate a White-Label Partner
The diligence checklist before you sign anyone.
Learn moreSecurity & Compliance
Access control, BAA readiness, and certification status.
Learn moreRelated reading
Frequently asked questions
Is white-label medical billing legal?
Yes. Subcontracting billing work is common and permitted under HIPAA, provided each client has a BAA with you, you have a subcontractor BAA with your production partner, and you respect any client or payer contract terms that restrict subcontracting or offshore access to PHI. Have counsel review your agreements before launch.
Do I have to tell clients I use a white-label partner?
It depends on your client contracts. Some require disclosure of subcontractors or offshore PHI access; many do not. Either way, decide your policy before your first sale and answer accurately if a client asks directly. White-label means the partner stays behind your brand, not that you mislead clients.
What is the best pricing model for white-label RCM?
The one that matches your cost structure. If your partner charges per seat, dedicated-seat or per-claim pricing keeps your margin stable. Percentage-of-collections pricing is easier to sell but leaves you carrying collection risk against a fixed cost. Model margin per client under slow-pay conditions before you commit.
Can I start a white-label billing business with no clients?
You can, but white-label solves delivery, not demand. Without accounts you are paying for, or negotiating, capacity you cannot use. The model works best when you already have client relationships, such as an existing billing book, a software customer base, or consulting clients who need back-office support.
How long does it take to launch a white-label RCM offering?
It depends mostly on system access, how well your SOPs are documented, and how quickly both BAAs are signed. The production work can start with a bounded pilot on one client. Packaging a repeatable offer should wait until that pilot has shown quality and reporting hold up.