Why the Compliance Frame Always Loses
Network build leaders are, by training and experience, fluent in compliance language. CMS standards, deficiency notices, compliance actions: these terms carry enormous weight inside the network team. They carry almost no weight in a CFO budget conversation.
CFOs are not indifferent to regulatory risk. They are, however, trained to evaluate it differently than compliance professionals do. When a network leader presents an investment as necessary to avoid a CMS deficiency, the CFO hears: "We need to spend money to prevent a bad thing that may or may not happen." That is a weak argument against competing budget priorities, and it almost always loses.
The reframe is not complicated, but it requires discipline: stop leading with compliance risk and start leading with revenue opportunity. Here is how to structure the conversation.
Lead With the Revenue That Adequate Coverage Unlocks
Every county you cover adequately is a county where your plan can enroll members. A county that fails in an application can be denied. That is not a compliance statement: it is a revenue access statement.
Build the number before you walk into the room:
- Identify the counties in your service area where you are at or near adequacy thresholds in at least one required specialty.
- Calculate the addressable enrollee population in those counties: the Medicare-eligible population multiplied by your market share goal.
- Multiply by your expected revenue per member per month. That is the revenue that adequate coverage protects.
That is the number your CFO needs to hear first: before anything about compliance. Use your own finance team's inputs, so nobody can wave it away as a vendor's estimate.
Lead with what adequate coverage enables. A dollar figure from your own model gets attention in a way that "CMS deficiency risk" never will.
Quantify the Downside With Specificity
Once you've established the revenue opportunity, the downside becomes a meaningful second argument, because now it's framed against a specific number, not as an abstract regulatory threat.
Be accurate about it. MedPAC's June 2024 report says CMS has never imposed intermediate sanctions or civil money penalties for network adequacy noncompliance, but that new applications have been denied on this basis. So for an expansion, the realistic downside is a county you can't enter:
- Projected enrollments in that county, times revenue per member per month, times the months lost.
- Plus the cost of the work already spent on the expansion.
- Plus the staff and legal cost of remediation if an operating contract fails a review.
The CFO now has two connected numbers: the revenue that investment protects, and the cost of not making the investment. Neither of those numbers is a compliance argument. Both are financial arguments.
Show the Payback Period
The final piece of the conversation is the investment itself, presented as a payback calculation. This is where network build leaders undercut themselves, by presenting a budget request without a return timeline.
Put the real quote or staffing cost next to the revenue at risk and say what share of that revenue has to be protected for the investment to pay for itself. Don't claim the spend eliminates the risk. It reduces it, and a CFO will trust you more for saying so.
The Conversation Template
Structure the CFO conversation in exactly this order: do not deviate:
- Open with the revenue opportunity: "Here are the counties where we have adequacy exposure, and here is the premium revenue we're protecting by closing those gaps."
- Quantify the downside: "If a county fails, here is what that costs us in revenue and remediation work."
- Present the investment: "Here is what the solution costs, and here is the payback period against both the opportunity and the risk."
- Close with the strategic context: "This is not a one-time fix. Adequacy is an ongoing compliance function. The investment we're asking for builds the infrastructure to manage it continuously, not reactively."
The fourth point matters. One-time investments that solve an immediate problem are easy to cut the following year, when the problem appears resolved. Frame adequacy management as an ongoing operational function, because CMS publishes a new Reference File every year and the network keeps changing.
You know the compliance stakes. Your CFO needs to know the revenue stakes. Give them your own number, and then let the math do the work.
The Blueprint team
Provider network build practice
Written by the people behind Blueprint, who between them have spent 30 years building provider networks for health plans: recruiting and contracting providers, chasing credentialing, and filing adequacy. Blueprint is new. The experience behind it isn't.
