> ## Documentation Index
> Fetch the complete documentation index at: https://mso.getlemma.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Decide: in-house billing vs outsourced RCM

> The cost model, the control and visibility tradeoffs, hybrid arrangements, and the contract terms to demand from an RCM vendor.

Below roughly two full-time clinicians, an outsourced RCM service usually costs less than a competent full-time biller. Above that, in-house buys visibility and control that percentage-of-collections pricing does not. This guide works the decision properly.

## The cost model

### In-house

| Component                  | Typical annual                    |
| -------------------------- | --------------------------------- |
| Biller salary              | $50,000–$85,000, market-dependent |
| Benefits and payroll taxes | \~20–30% of salary                |
| Management time            | Real, and usually uncosted        |
| Training and certification | $1,000–$3,000                     |
| Software seat              | Usually included in the EHR       |
| **Loaded total**           | **\~**$65,000–$**110,000**        |

Plus the risks that don't appear in a spreadsheet: turnover, vacation coverage, and single-person dependency.

### Outsourced

Typically a **percentage of collections**, commonly quoted somewhere in the 4–9% range depending on specialty, volume, and scope. Verify what "collections" includes.

| At net collections of | At 6%     |
| --------------------- | --------- |
| \$600,000             | \$36,000  |
| \$1,200,000           | \$72,000  |
| \$2,400,000           | \$144,000 |

**The crossover** in this illustration sits somewhere around $1.2M–$1.5M in net collections, roughly two to three full-time clinicians in many specialties. Run it with your own numbers rather than adopting these.

**Percentage pricing scales your cost with your success**, for a service whose cost to serve does not scale proportionally. It is the right structure early, when you want variable cost, and a worse one at scale. Renegotiate the rate as volume grows — vendors expect it.

## The tradeoffs

|                                | In-house                                                | Outsourced                                      |
| ------------------------------ | ------------------------------------------------------- | ----------------------------------------------- |
| **Cost at low volume**         | High fixed                                              | Low variable                                    |
| **Cost at high volume**        | Better                                                  | Worse                                           |
| **Visibility**                 | Full                                                    | Depends entirely on reporting                   |
| **Control over priorities**    | Full                                                    | Limited                                         |
| **Denial prevention feedback** | Direct, the biller can change the front desk's workflow | Weak; the vendor doesn't control your front end |
| **Coverage**                   | Single point of failure                                 | Team coverage                                   |
| **Specialty expertise**        | You must hire it                                        | Often deeper                                    |
| **Scaling**                    | Hire again                                              | Automatic                                       |
| **Switching cost**             | Rehire                                                  | Migration, data retrieval, re-enrollment        |

**The denial prevention gap is the underrated one.** Most denials originate in the front end — eligibility, authorization, registration. An in-house biller can walk to the front desk and change the workflow. An outsourced vendor reports the problem and waits for you to fix it. If your denial rate is driven by front-end failures, outsourcing the back end treats the symptom.

## The hybrid

Frequently the best answer at mid-scale:

* **In-house:** eligibility verification, prior authorization, charge entry, point-of-care collection — the prevention side
* **Outsourced:** denial management, appeals, AR follow-up, patient collections — the recovery side

You keep control of the processes that prevent problems and buy scale on the ones that resolve them.

## Contract terms to demand from an RCM vendor

<Steps>
  <Step title="Define 'collections' precisely">
    Does the percentage apply to all cash received, or only to what the vendor collected? Does it include patient payments collected at your front desk? Copays? Payments on claims submitted before the engagement started?

    **This single definition can swing the effective rate by several points.**
  </Step>

  <Step title="Demand data rights on termination">
    On termination you get: all claim data, all remittance data, all AR detail, all correspondence, in a usable format, within a stated number of days, at no additional charge.

    Without this clause, leaving means abandoning your AR.
  </Step>

  <Step title="Set performance SLAs with teeth">
    * Days from charge receipt to claim submission
    * Days from denial receipt to first action
    * Clean claim rate
    * Days in AR
    * AR over 90 days
    * Reporting cadence and content

    And a remedy if they're missed, a fee reduction or a termination right.
  </Step>

  <Step title="Set the termination terms">
    Notice period, transition assistance obligations, and no penalty for termination on a missed SLA.
  </Step>

  <Step title="Require a BAA and confirm offshore handling">
    The vendor is a business associate. Ask directly whether PHI is accessed offshore, by whom, and under what controls. See [Put a BAA in place](/guides/agreements/draft-a-baa).
  </Step>

  <Step title="Retain coding responsibility in the PC">
    An RCM vendor providing coding services must not be *deciding* codes independent of the PC. Coding is a clinical judgment and, in an MSO-PC structure, it is the PC's responsibility — California's SB 351 and Oregon's SB 951 both name coding among the functions a management entity may not control. Document that clinicians may reject a coding change. See [What an MSO can and can't do](/concepts/model/what-msos-can-and-cant-do).
  </Step>

  <Step title="Clarify who owns payer relationships">
    Enrollment, credentialing, and contract negotiation should remain yours, or you become dependent on the vendor to change vendors.
  </Step>
</Steps>

## Verify it worked

* [ ] Cost modeled both ways at current and projected volume
* [ ] "Collections" defined precisely in the contract
* [ ] Data rights on termination specified
* [ ] SLAs with remedies
* [ ] Termination terms acceptable
* [ ] BAA executed; offshore access disclosed
* [ ] Coding responsibility retained by the PC
* [ ] Payer relationships retained by you
* [ ] A reporting pack you'll actually receive and read

## Common failure modes

| Failure                                      | Consequence                                  |
| -------------------------------------------- | -------------------------------------------- |
| "Collections" undefined                      | Effective rate materially higher than quoted |
| No data rights on termination                | Cannot leave without abandoning AR           |
| No SLAs                                      | No basis to hold the vendor accountable      |
| Outsourcing to fix front-end denials         | Treats the symptom                           |
| Never renegotiating the rate as volume grows | Overpaying at scale                          |
| Vendor owns payer relationships              | Vendor lock-in                               |
| No visibility into what the vendor is doing  | Discovering problems at month-end            |


## Related topics

- [Hire your first biller](/guides/billing/hire-a-biller.md)
- [Work the denial queue](/guides/billing/work-the-denial-queue.md)
- [What billers actually do](/concepts/payments/what-billers-do.md)
- [Clearinghouse vs RCM vs EHR (vs biller)](/concepts/payments/clearinghouse-vs-rcm-vs-ehr.md)
- [RCM & billing service directory](/reference/vendors/rcm-directory.md)
