Where TPAs Fit in Direct Contracting (and Where They Don’t)

One of the quiet questions in every direct contracting conversation is simple:

"What does this mean for our TPA?"

The short answer is that good TPAs become more important, not less.

Direct contracting does not eliminate the need for claims administration, eligibility, and member support. It changes the standard for what "good" looks like in those functions.

Here is how TPAs fit into the direct contracting stack — and where employers should look beyond them.

What TPAs are uniquely good at

A strong TPA brings capabilities most employers will never build in-house:

• Eligibility and enrollment administration across multiple plan designs
• Claims intake, adjudication, and payment on top of complex fee schedules
• Integration with stop-loss carriers
• Regulatory and compliance infrastructure for ERISA plans

In a direct contracting context, those capabilities still matter.

The difference is that the TPA is no longer just administering a broad network product from a carrier.

They are administering a custom-built layer cake:

• Direct contracts with specific providers or systems
• Narrow networks or COE programs
• Legacy PPO networks for everything else

The TPA has to be able to keep that stack straight.

Where TPAs struggle in direct contracting

Not every TPA is built for this.

Common failure points:

• Systems that cannot easily handle custom steerage rules (e.g., "if member lives here and needs this procedure, route here")
• Rigid benefit coding that makes it hard to reflect nuanced cost-sharing logic
• Limited data sharing that turns performance reporting into a quarterly PDF instead of a usable feed
• Cultural resistance to arrangements that do not match a traditional network-first model

If a TPA treats every direct contract as an edge case they grudgingly support, the friction will show up quickly for members and providers.

What "direct-contract-ready" TPAs look like

The TPAs that thrive in this market share a few traits:

• Configurable platforms that can encode direct contract logic without endless custom code
• Clear support for reference-based and Medicare-indexed pricing models
• Strong API and data feed capabilities for near-real-time reporting
• Dedicated implementation teams for alternative network designs
• Willingness to collaborate with navigation vendors and platforms instead of defending turf

You can often tell in the first meeting whether a TPA sees direct contracting as a threat or an opportunity.

Where employers need more than a TPA

Even with a strong TPA, there are parts of direct contracting they are not built to own.

Examples:

• Market scouting and deal origination — identifying which health systems, physician groups, or platforms are viable partners
• Contract negotiation strategy — determining percent-of-Medicare targets, quality metrics, and data rights
• Steerage design and navigation — building the member-facing experience that actually moves volume

Some TPAs offer adjacent services here, but many employers will need:

• A specialized advisory firm
• A direct contracting platform
• Or internal capacity within HR/finance

The TPA should be at the table. They just should not be the only one bringing expertise.

How to evaluate your TPA for a direct contracting strategy

If you already have a TPA, start with a focused conversation instead of a vague request.

Ask:

• Can your platform handle custom steerage rules tied to geography, service line, and provider?
• How do you administer contracts indexed to Medicare, not just percent-of-charge discounts?
• What does your standard data feed look like for employers running direct contracts today?
• How many clients are currently using non-traditional network designs with you?
• What goes wrong most often when those programs launch?

You are not just checking boxes. You are looking for pattern recognition and honest war stories.

The bottom line

Direct contracting changes the job of a TPA from network administrator to infrastructure partner.

You still need someone to keep the machine running — eligibility, claims, stop-loss.

But you also need someone whose systems, data, and culture can support a world where the contract stack is more complex and more intentional.

If your TPA leans into that role, they can be one of your most important allies.

If they resist it, you will feel the friction every time you try to turn a strategic idea into an operational reality.