Outsourcing Revenue Cycle Management: What They Don’t Tell You

You know that moment when your CFO walks into your office and says, “We’re thinking about outsourcing revenue cycle management”?

Your stomach drops. Because you’ve seen this movie before. The last vendor promised the moon, delivered basic data entry, and somehow made your days in AR worse. Now you’re stuck explaining to the board why you have 15,000 employees across three continents and still can’t get payment posting caught up.

But here’s the thing: outsourcing revenue cycle management can work. I’ve seen it save hospitals millions. I’ve also watched it burn through budgets faster than a Medicare audit.

The difference? Knowing what you’re actually buying.

The Real Cost of Keeping RCM In-House (Nobody Talks About This)

Let’s get specific. When Eddie Tan from Guardant Health told me they’re approaching a billion dollars in U.S. clinical revenue with mostly in-house RCM, I asked him the question nobody wants to answer: “What’s it really costing you?”

Not just salaries. I mean the hidden costs:

  • The expertise drain: Your best AR rep just left for a $3/hour raise at the hospital down the street. Now you’re training someone new for the fourth time this year.
  • The technology gap: Insurance carriers have been automating for decades. You’re still manually checking claim status on 800+ payer portals because your PM system’s “automation” only works for three of them.
  • The opportunity cost: While your team is drowning in payment posting, those credit balances from 2022 are still sitting there. Small balances aren’t getting worked. Underpayments aren’t getting appealed.

One revenue cycle director at a 250-bed hospital told me they calculated the true cost at $47 per claim when you factor in all the overhead. Their vendor quoted $12. Even at $18 (the real price after negotiations), the math made sense.

Why Most RCM Outsourcing Fails (And How Vendors Get Away With It)

I’ve spent 28 years in revenue cycle management. Started at the front desk verifying insurance, worked up through VP of operations. I’ve hired RCM vendors. I’ve been the RCM vendor. Here’s what nobody tells you during the sales pitch:

They don’t understand your workflows.

When Ensemble Health Partners was evaluating automation vendors, their CIO had a massive list of integration tasks. Things like benefits mapping at a person-by-person level. The kind of detail that only matters when you’re bringing on a full end-to-end outsource client.

Most vendors hear “eligibility verification” and think they can just run a 270 transaction. They don’t ask if you have a hard close or soft close at the end of the month. They don’t know what a UB04 is. They definitely don’t understand why Blue Cross suddenly started blanket denying knee replacements with diagnosis codes in a specific range (true story, cost one of my clients $2.3M before we caught it).

They’re not actually automating anything new.

The vendor shows you a demo of their “AI-powered” solution. It looks impressive. Then you sign the contract and realize they’re just throwing more people at the same manual processes you’re already doing. They call it “automation” because the staff is offshore and uses macros.

Real talk: if your vendor can’t tell you their bot’s success rate on claim status checks (it should be north of 95%), they don’t have bots. They have people in the Philippines doing what your team already does, just cheaper.

The pricing model is designed to hide the real cost.

“We only charge per transaction!” Sounds great until you realize they’re counting every single action as a transaction. Checked eligibility? Transaction. Posted payment? Transaction. Updated a note? Transaction. Your “$2 per claim” somehow becomes $34,000 a month.

Or my favorite: the vendor that quoted a hospital $40/hour for “automation development” but buried a clause requiring 4,000 minimum hours per year. That’s $160,000 committed before they’ve automated a single process.

The Framework That Actually Works for Outsourcing Revenue Cycle Management

After watching hospitals succeed and fail with outsourcing, here’s the framework that separates the winners from the disasters:

Start with a Process Audit (Not a Vendor Search)

Before you talk to a single vendor, answer these questions:

  1. Where is staff spending time on data entry vs. decision-making? If your senior AR reps are copying and pasting between systems, that’s not an expertise problem. That’s an automation problem.
  2. What’s your current cost per function? Not per FTE. Per function. What does it cost you to verify one eligibility? Check one claim status? Post one payment? (Hint: most hospitals have no idea. Figure it out. This is your negotiating power.)
  3. What are your actual denial reasons? Pull six months of CARC and RARC codes. If 40% of your denials are eligibility-related, you don’t need better AR follow-up. You need better front-end verification.

When Emory Healthcare brought me in, they had all their RCM leaders on the call: HIM, cash applications, customer service, vendor management. First thing I asked: “Show me your denial trending by CARC code and payer.”

They couldn’t.

That told me everything. You can’t outsource what you can’t measure.

Know What You’re Buying: People, Process, or Technology

This is where most hospitals get burned. Vendors blur the lines between these three deliberately. Here’s how to see through it:

People services: They’re providing labor. This works for specialized functions like out-of-network collections (Revco Solutions does this well) or prior authorization follow-up. You’re paying for expertise and bandwidth. Just be honest that you’re buying staffing, not transformation.

Process services: They’re taking over an entire function end-to-end. This can work for things like patient collections where you don’t have the infrastructure for early-out bad debt. But watch the KPIs like a hawk. If they can’t show you daily performance metrics, run.

Technology/Automation services: They’re replacing manual work with bots. This is where the ROI really lives, but also where the snake oil is thickest. Real automation should:

  • Work in YOUR systems (not make you adapt to theirs)
  • Have measurable success rates (99%+ on simple tasks like eligibility, 90%+ on complex tasks like payment posting)
  • Get implemented in weeks, not quarters
  • Give you the source code (so you’re not held hostage)

The best engagements blend all three. But you need to know which piece is doing the heavy lifting.

Build in the Right Safety Nets

Here’s something nobody tells you: the contract terms matter more than the sales pitch.

Performance guarantees that actually mean something. “We’ll reduce your days in AR” is meaningless. Reduce from what baseline? By when? What happens if you don’t hit it?

Better: “If we don’t achieve 95%+ eligibility verification within 30 days, you can terminate with no penalty.” Or: “If our payment posting accuracy falls below 98%, we’ll credit that month’s fee.”

Escalation paths that skip the account manager. When something breaks (and it will), you need direct access to the people who can fix it. Not a ticket system. Not an account manager who “needs to check with the team.” A phone number for the actual operations director.

Transition assistance (both ways). What happens if the relationship doesn’t work? Can you get your data out easily? Will they train your team on processes they’ve been running?

I watched a hospital spend six months transitioning back to in-house because their vendor held their denial appeal templates hostage. Don’t be that hospital.

Pilot Before You Commit

This should be obvious, but most hospitals skip it. They sign a three-year contract for “full revenue cycle” based on a demo and some references.

Here’s the better way: pick one high-volume, medium-complexity process. Not your hairiest problem (save that for once you trust them). Something like:

  • Claim status checks for commercial payers
  • Prior authorization requests for therapy services
  • Payment posting for Medicare

Give them 30 days to prove they can do it. Not “show you a demo.” Actually do it. In your production environment. On real accounts.

Track everything:

  • Accuracy rate
  • Time per task
  • Exceptions requiring human intervention
  • Impact on downstream metrics (did your denial rate actually drop?)

If they can’t knock this out of the park, they definitely can’t handle your complex stuff.

What Good Outsourcing Revenue Cycle Management Actually Looks Like

Let me paint you a picture from a real client (details changed to protect the innocent).

350-bed hospital. Net patient revenue around $400M. They had 47 FTEs in revenue cycle, plus they were using three different vendors for various pieces. Prior auth was backed up 600 requests deep. Days in AR were stuck at 52. Clean claim rate was 73%.

CFO was ready to blow it all up and hire a big-name RCM company to take over everything.

Instead, we mapped out where the bottlenecks really were:

  1. Front-end: No systematic eligibility verification. Staff was “checking” insurance, but only confirming active coverage, not benefits or auth requirements.
  2. Prior auth: Manual process. Staff spent 45 minutes per authorization between gathering documents, filling out forms, and following up. EvoCore and Availity portals alone accounted for 60% of requests, but each person did it slightly differently.
  3. Payment posting: Remits were being imported, but 30-40% of line items weren’t making the positive match. Those were going to a queue that was 14,000 accounts deep.

We didn’t outsource everything. We automated the repetitive parts and kept the expertise in-house for the complex decisions.

  • Built bots to verify eligibility and benefits for all appointments 1-7 days out. Flag auth requirements and calculate patient liability. (This is standard insurance eligibility verification software, just customized to their workflows.)
  • Automated prior auth requests to EvoCore, Availity, and the top 10 payers. Went from 45 minutes per auth to 10 minutes of human review time.
  • Built payment posting bots that could match those exception line items based on date of service, charge amount, and CPT/revenue codes. Went from 14,000-account backlog to current in six weeks.

Results after six months:

  • Days in AR: 52 → 38
  • Clean claim rate: 73% → 89%
  • Prior auth backlog: 600 → 0 (and staying current)
  • Eligibility denials: down 54%
  • Cost: $60,000/month for the automation (vs. $140,000/month they were paying their previous vendors)

Here’s the key: they still had 47 FTEs. But now those people were doing actual revenue cycle work, not data entry. Authorization specialists were handling the complex cases that required clinical judgment. AR reps were working accounts that needed negotiation and appeals. The front desk wasn’t spending three hours a day on hold with insurance carriers.

The Outsourcing Revenue Cycle Management Decision Tree

So should you outsource? Here’s how to think about it:

Keep in-house if:

  • You have stable, experienced staff (turnover under 15%)
  • Your volumes are predictable and manageable
  • You have good technology and know how to use it
  • Your margins are healthy (4%+ operating margin)

Outsource tactically if:

  • You have capability gaps (out-of-network collections, complex appeals)
  • You need to scale up/down rapidly (new hospital acquisition, closing a site)
  • You want to focus internal resources on strategic work

Outsource with automation if:

  • Your staff is drowning in data entry and manual tasks
  • You can’t hire fast enough to keep up with volume
  • Your technology gaps are costing you revenue (can’t check claim status on 600+ payers manually)
  • You need ROI fast (implementation should be 6-8 weeks, not 6-12 months)

Full outsourcing if:

  • Your RCM is fundamentally broken (days in AR over 70, clean claim rate under 70%)
  • You don’t have the leadership bandwidth to fix it
  • You’re willing to give up control for stability

Just know what you’re signing up for. Full outsourcing means you’re essentially renting someone else’s RCM department. That can be the right call. But it’s rarely the only call.

Key Takeaways

For CFOs:

  • Calculate your true cost per function before talking to vendors (it’s higher than you think)
  • Pilot one process for 30 days before committing to anything
  • Performance guarantees should have teeth (penalties and early termination rights)
  • The cheapest per-transaction price usually has the most hidden costs

For Revenue Cycle Directors:

  • Map your workflows before you outsource them (you can’t improve what you don’t understand)
  • Real automation should work in YOUR systems and give you the source code
  • If a vendor can’t tell you their success rates by process type, they’re selling labor, not technology
  • Start with high-volume, medium-complexity processes (not your hairiest problems)

For Everyone:

  • Outsourcing revenue cycle management services isn’t all-or-nothing (you can automate some, outsource some, keep some in-house)
  • Implementation timeline is a leading indicator of success (6-8 weeks is realistic, 6-12 months means they’re rebuilding everything from scratch)
  • The best vendors speak your language (they know what a CARC code is, they understand timely filing, they’ve fought with IVR systems)

What’s Next?

If you’re evaluating revenue cycle management solutions and trying to separate real value from marketing noise, the next step isn’t another vendor pitch it’s clarity.

Focus on practical outcomes: reducing manual work, improving eligibility accuracy, accelerating prior authorizations, and stabilizing cash flow. Whether through selective automation, targeted revenue cycle management services, or a broader outsourcing strategy, the goal is to free your teams from data entry so they can focus on decisions that protect revenue.

The right RCM partner understands payer behavior, denial logic, and operational reality and can prove it with results, not buzzwords.

Scroll to Top

Job Application Form

We are an Equal Opportunity Employer and committed to excellence through diversity.

cropped