Building the Direct Contracting Business Case for Your CFO

Most direct contracting pitches die in the same room: the CFO’s.

Not because the idea is bad, but because the business case sounds like a vendor webinar instead of a capital decision.

The reality is simple: if you are already self-funded, direct contracting is a finance‑native idea. You are paying the claims today. The question is whether you control the price, the steerage, and the information.

If your CFO cannot see what changes on the P&L, they will quite reasonably say "not this year."

Here is how to build a business case that sounds like capital discipline, not benefits innovation.

1. Frame it as taking control of an existing line item

CFOs do not wake up wanting a more interesting benefit strategy.

They want fewer unpleasant surprises on a very large expense.

Lead with three facts in plain language:

• We are already self‑funded. We carry the risk whether we like it or not.
• Our current model keeps us far from the actual contract mechanics. We buy a discount, not a price.
• Direct contracting is a way to get closer to unit cost, steerage, and data without changing who pays the claims.

Then tie it explicitly to the finance agenda:

• Expense control
• Forecastability and variance reduction
• Better use of working capital (for example, 30‑day payment vs 120‑day float that buys us nothing)

You are not asking to chase a trend. You are proposing a different way to buy something the company already purchases at scale.

2. Quantify the baseline with your own numbers

A CFO does not care what “the average employer” spends.

They care what you are spending and where it is leaking.

Pull a simple baseline from your claims or stop‑loss reports:

• Total allowed amounts over the last 12–24 months
• Trend line by quarter
• Top 5–10 service lines or facilities by allowed amount
• Any obvious outliers (for example, a hospital that is 40–60% above your internal benchmark)

Summarize it in one page:

"We are spending $48M per year on medical claims. Trend is +7% annually. Three service lines (joints, GI, imaging) represent 32% of spend. In those areas, our average allowed amounts are 18–25% above credible benchmarks."

The point is not to show off analytics. The point is to make it obvious that you already own the downside, and the current contract stack is not earning its keep.

3. Make the direct contract delta painfully concrete

Most "business cases" stop at "direct contracts can lower cost and improve quality."

That is not a business case. That is a hope.

Take one or two target service lines and build a blunt comparison table:

Service line	Baseline allowed / case	Direct contract allowed / case	Steerage assumption	Implied annual savings
Joint replacement	$45,000	$32,000	50% of eligible	~$650,000
Outpatient imaging	$1,200	$550	40% of eligible	~$220,000

Then show a range, not a single point:

• Conservative: 30% steerage
• Target: 50% steerage
• Upside: 70% steerage

CFOs are comfortable with ranges and sensitivity, as long as the mechanics are visible:

• What changes in price
• How much volume can reasonably move
• How that combination behaves over a year

4. Say the quiet part about risk up front

Finance is not afraid of risk. They are afraid of unpriced risk.

Address three questions explicitly:

1. What if steerage underperforms?
   Underperformance means forgone savings on the in‑scope slice, not catastrophic new exposure. Members still have access to the legacy network; the pilot fails quietly instead of loudly.

2. What if utilization spikes?
   Be honest about whether you are still fee‑for‑service or sharing risk. If you are FFS with better unit prices, say so. Do not pretend you have solved over‑utilization in a 90‑day pilot.

3. What if the partner under‑delivers?
   Point directly to contract language on service levels, payment timing, data reporting, and exit ramps. Show that you can unwind without a public divorce.

If you cannot answer these three questions in two pages, you are not ready for finance.

5. Show the operating model, not just the paper

CFOs have seen too many "great contracts" that never showed up in the numbers.

Spell out how this one avoids that fate:

• Navigation and steerage: Who owns it (internal, TPA, platform) and what tools you actually have (benefit design, incentives, outbound outreach).
• Exception handling: Who can approve going out of network and under what rules.
• Review cadence: Quarterly performance reviews with finance in the room, not just HR.

A one‑page operating model that names owners and cadences is worth more than 20 slides about "member experience."

6. Put the investment and payback in CFO language

Direct contracting has real costs. Pretending otherwise just burns credibility.

Lay them out:

• Platform or TPA fees (per member per month, per case, or both)
• Internal FTE time to stand up and run the program
• One‑time transition costs (communications, eligibility configuration, analytics lift)

Then put them next to the savings range:

• Year 1: invest ~$250k, expected net savings $400k–$800k on a $10–15M in‑scope slice
• Year 2: incremental fees roughly flat, savings scale with additional service lines and markets

You do not need a 50‑tab model.

You do need to show that, even under conservative steerage, the math looks like a real capital decision—not a rounding error.

7. Ask for a disciplined, reversible test

Do not ask your CFO to bless a multi‑year network overhaul.

Ask for permission to run a bounded 90‑day pilot with a clear decision gate. That means:

• One or two service lines
• A specific geography
• 5–15% of total medical spend
• A pre‑scheduled review with finance where you commit to bringing:
  • Steerage and unit cost results
  • Member and provider feedback
  • A simple recommendation: expand, extend as‑is, materially change, or exit

You are essentially asking to run a controlled experiment on a leaky part of the P&L.

If you present direct contracting that way, most CFOs will at least stay at the table.

If you present it as another "innovation initiative" with fuzzy numbers and no exit ramp, they shouldn’t.