PE-Backed Provider Group·Multi-State Contract Ops·3-Week Engagement·$2-5M annualized upside · 10-20% lift of total annual revenue
How a 3-week diagnostic became the foundation for a multi-state provider’s payer contracting function.
Diagnose, build, operate. Inside the contract lifecycle the client’s commercial team already runs or is trying to improve.
How the engagement runs
01Week 1
Diagnostic
Team interviews, document discovery, 6-agent design, 1,000-doc practice execution run.
02Weeks 2-3
Build
Six agent workflows tuned, cross-entity reconciliation, Future State Operations scoped.
03Weeks 4-7+ (projected)
Operate
4-week stand-up of the running engine. Steady-state cadence after.
Composite outcome from anonymized engagements
$2-5M
Annualized upside
Surfaced in diagnostic
10-20%
Of annual revenue
Same upside, expressed as lift
1,000+
Documents ingested
in Week 1
6
Agent workflows validated
design ready for stand-up
3 → 1
Entities reconciled
one contracting view
120 / 365
Renewal visibility (days)
priority / forward
How the 3Pillars team learned every contract on the book.
Week 1 was about getting honest about what the organization actually had. Legacy entities meant multiple filing conventions, multiple sets of payer relationships, and no point person who held the full mental model of the contract book.
Days 1-2
Interviews and discovery
Sessions with revenue cycle, finance, and the leaders of each legacy entity. Document sweep across shared drives and email archives.
Days 3-4
Map and design
Current-state workflow visualized. 6-agent design specified, modeled on how a regional health plan runs its contracting shop but sized for a $50M provider group.
Days 5-7
Practice execution
Agent design run end to end against ~1,000 documents. Contracts sorted from non-contracts. Payers identified, carrier families normalized for M&A. Gap list produced.
What the client walks out of the Diagnostic with
A structured repository of every contract the organization can find
A current-state map honest about what exists and what doesn’t
A validated 6-agent design, pressure-tested against the real corpus
A payer outreach list for documentation gaps, sequenced by revenue exposure
How the diagnostic becomes an executable system.
Across Weeks 2 and 3, the validated design from Week 1 becomes a working contracting capability, deployed inside the client’s environment and running on the client’s data. The team scopes Future State Operations in parallel so the stand-up plan is ready when Week 3 closes.
Four levers, instrumented
Rate optimization. Underpaying contracts flagged automatically against internal and market benchmarks.
Gap closure. Missing fee schedules, missing addenda, stale terms surfaced for resolution.
Footprint expansion. Favorable contract structures mapped to candidate states and lines of business.
Renewal discipline. Every termination, notice, and auto-renewal clause tracked, alerted, and queued for negotiation prep.
Six workflows go live
01Rate Analysis
02Rate Structure Analysis
03CPT Code Analysis
04Contract Cycle Tracking
05VBC Arrangement Analysis
06Contract History + Negotiation Case
What else gets stood up
Cross-entity reconciliation. Three NPIs, three Tax IDs, three ways of describing the same clinical service reconciled into one view so agents can compare like with like.
Human-in-the-loop validation. Issues identified by the contracting and finance leads feed back into the workflows so errors are corrected on future runs.
Future State Operations scoped. Roles, refresh cadence, escalation paths, and the projected 4-week stand-up timeline specified before the team walks out of Week 3.
What gets built and how it runs.
Six workflows. One canonical contract layer. For each: the inputs, what the agent does, what humans see, and where the human-in-the-loop checkpoint lives.
Rate Analysis
01
Inputs
Every contract in the repository, segmented by line of business (Medicaid, MA, commercial), entity, state, and payer.
Does
Extracts headline rates, normalizes across fee schedule references, benchmarks within and across payers. Flags outliers where one entity is paid materially less than another for the same service in a comparable state.
Output
Rate table by payer, state, entity, and LOB. Outliers tagged with underlying contract language linked.
Human
The contracting lead signs off on the outlier list before it feeds the negotiation pipeline.
Rate Structure Analysis
02
Inputs
Contract language describing how rates are derived: percent of a referenced fee schedule (Medicare, Medicaid, custom) versus direct fee schedules with codes priced explicitly.
Does
Classifies each rate provision by structure. Flags structures that carry hidden volatility (a percent-of-Medicare rate drifts if the reference changes).
Output
Structure map showing rate-derivation mechanism by payer and entity, with volatility flags.
Human
Finance reviews volatility flags before they shape forecast assumptions.
CPT Code Analysis
03
Inputs
Full code set referenced in each contract, including codes priced explicitly and as part of a group or category.
Does
Reads explicit versus grouped code structures across payers, entities, and states. Identifies codes priced in one contract but missing from another, inconsistent pricing across entities for the same payer, and groupings that obscure the true rate for high-volume services.
Output
Code coverage map by payer, entity, and state, with gap and inconsistency flags.
Human
Revenue cycle reviews the gap list before it feeds payer outreach.
Contract Cycle Tracking
04
Inputs
Effective dates, renewal terms, auto-refresh mechanisms, notice-period requirements, and amendment history for every contract.
Does
Maintains a 12-month forward calendar. Prioritizes negotiations by revenue exposure and rate competitiveness. Surfaces auto-renewal clauses before they bind.
Output
Negotiation calendar refreshed weekly. Priority alerts at 120 days, next-tranche at 180 days, full 365-day visibility available.
Human
The contracting lead confirms priority tiers each quarter.
VBC Arrangement Analysis
05
Inputs
Contract language covering attribution methodology, payment mechanics (shared savings, capitation, bundled, quality bonus), quality measures referenced, and any risk corridors.
Does
Reads VBC provisions across payers, entities, and states. Normalizes how attribution and payment differ. Identifies where the organization is taking on risk implicitly and where VBC opportunity exists with peer-comparable payers.
Output
VBC inventory by payer. No active VBC arrangements in this book. Opportunity list of payers whose current contract language could evolve to VBC, or who are most inclined to engage based on current quality metrics.
Human
Clinical leadership signs off on the opportunity list before it informs reporting investments.
Contract History + Negotiation Case
06
Inputs
All prior versions, amendments, and correspondence for each payer relationship, plus outputs from Workflows 1-5.
Does
Builds full payer relationship history. Assembles a negotiation business case 120 days before each priority window with current rate position, peer comparison across entities, ROI of proposed changes, and a recommended ask.
Output
Per-payer dossier and negotiation business case drafted 120 days before priority negotiation windows.
Human
The contracting lead and entity leader review and adjust the business case before it goes into negotiation.
How the work flows across the people who run it.
Pick a persona in the left nav to see how the engine changes that seat.
Director of Payer Contracting
Owns the relationships. Runs the negotiations.
Sits in every negotiation. Was hired into a function that did not yet exist. This work was not their day-to-day responsibility, so no time was allocated toward it.
Before
No central view of the book. No negotiations prepped or actively participated in because there was neither time nor visibility into when they should happen, or how. Limited negotiations that did occur were prepped on partial information assembled by hand. No reliable way to know what one entity was being paid versus another for the same service.
After
Proactive outreach, or the option to walk into every negotiation with a dossier already drafted, peer comparisons run, and an ROI on the proposed ask. The agent can also begin prep for a renewal cycle the team would rather not engage in this round.
What the agent does for this role
Flags upcoming negotiations the agent will begin prep for, in case the internal team prefers not to engage this cycle
Drafts the negotiation business case 120 days out for priority renewals
Flags rate outliers across entities for the same payer
Surfaces auto-renewal clauses before they bind
What the team will build next.
The 3-week engagement delivered the diagnostic, the validated 6-agent design, and the scoped Future State Operations plan. The next 4 weeks (projected) stand up the running contracting engine. The agents do the reading. The team does the deciding.
4-week stand-up (projected)
Week 4
Repository deployment in the client's preferred system. Agent workflows ported. Initial team enablement.
Week 5
Renewal calendar instrumented. First 120-day priority alerts fire on real contracts.
Week 6
First negotiation business cases drafted for upcoming priority renewals. Quarterly cadence stood up.
Week 7
Full handoff. The engine runs at steady-state cadence.
Cadence (steady-state)
Daily
New documents land in the repository inbox, are classified, and routed. Any contract or amendment ingested today is fully indexed by tomorrow.
Per renewal
Negotiation business case generated 120 days before the priority window, refined with the contracting team, deployed.
Quarterly
Full re-read across the corpus. Priority tiers reset. VBC opportunity list refreshes. Rate structure map updates against reference fee schedule changes.
What expansion looks like
New entity onboarded. Repository extends to the new NPI and Tax ID. Agents re-run cross-entity comparisons against the expanded book.
New state entry. Agents extend the state-level rate and code maps to cover the new market.
New line of business. Workflows extend to the new LOB without restructuring the underlying agents.
What’s Nextfuture
Claims-to-contract reconciliation. Tie paid claims back to the contracted rate to identify systematic underpayment by payer, code, and entity.
Growth-state targeting. Use the rate, code, and utilization map to identify which states and payer relationships represent the strongest expansion economics for the next entity acquisition.
Upcoding accuracy by provider mastery level. Layer provider license and credential data against billed CPTs to identify cases where a provider is billing a lower-acuity code than their license could support.
A multi-state provider group built the foundation for this in three weeks. Every new payer, state, and contract after that feeds the same engine.
Run this on a contract book.
30-minute working session. We’ll walk through what an engagement could look like.