Build vs. outsource: staffing a provider network function

What a provider network function actually does

Before you can staff the work, you have to see the whole of it. A provider network function is not one job. It is a chain of specialized functions that must run in sequence and then keep running forever after launch.

When leaders underestimate the build, it is almost always because they were picturing one or two of these steps and not the entire chain. The chain includes:

• Network strategy and adequacy modeling — deciding which specialties, counties, and access points you need to meet regulatory adequacy standards and serve your expected membership.
• Provider recruitment and outreach — identifying, contacting, and persuading physicians, groups, and facilities to join.
• Contracting — negotiating and executing participating provider agreements and their fee-schedule exhibits.
• Credentialing — primary source verification of licensure, education, malpractice history, and exclusions, typically to NCQA standards.
• Provider data management and loading — getting accurate provider records into your systems so claims pay and directories are correct.
• Ongoing network operations — recredentialing, contract amendments, terminations, adequacy monitoring, and provider relations after go-live.

The true cost of building in-house

The visible cost of an internal team is salaries, and those are real. A credentialing specialist, a contract negotiator, a provider data analyst, and someone to lead the function are the minimum for a network of any size, and specialized network staff are not inexpensive in most markets. But salary is the smallest part of the true cost.

The larger costs are the ones that do not show up on an org chart. There is the credentialing verification infrastructure — CAQH access, primary-source verification tooling, and ongoing monitoring against OIG and SAM.gov exclusion lists, which NCQA now expects on a monthly basis. There is a provider data system and the discipline to keep it clean. There is the management overhead of hiring, training, and retaining specialists in a tight labor market, where a single departure mid-build can stall an entire deadline.

There is also the ramp. A newly hired team does not produce a finished network on day one. It spends weeks learning your markets, your systems, and your standards before it is fully productive. If your deadline is inside that ramp window, the in-house build is fighting itself.

The timeline you are actually racing

Credentialing is the step that most often controls your timeline, because it has a floor you cannot compress by will alone. Industry credentialing timelines commonly run 60 to 90 days for in-state providers and 90 to 120 days for out-of-state providers, and NCQA's 2025 standards tightened the primary-source verification window to 120 days for Accreditation and 90 days for Certification. That means every provider in your network carries a multi-week clock, and those clocks have to finish before your access is real.

Contracting adds its own runway. A provider does not sign the day you call. Negotiation, legal review, and countersignature take weeks per group, and large systems take longer. When you multiply a realistic per-provider cycle by the number of providers a new network needs, the build is measured in months, not weeks.

This is why the staffing decision is really a deadline decision. If you are standing up a team from scratch and also racing a filing date, you are running two projects at once — building the machine while trying to use it.

When outsourcing is the right call

Outsourcing to a consultancy is not about avoiding cost. It is about buying speed and certainty when the deadline will not move. A firm that builds networks for a living arrives with the verification infrastructure, market relationships, and repeatable process already in place, so there is no ramp to absorb and no hiring risk to manage.

Outsourcing tends to be the right call in a few recognizable situations:

• You are a new entrant. A first MA plan, D-SNP, or IPA has no network team and no time to build one before its access must be demonstrated.
• You have a hard external deadline. A CMS filing date or a state adequacy requirement leaves no room for a hiring-and-ramp cycle.
• You are expanding into unfamiliar geography. A new service area means new markets, new provider relationships, and new fee-schedule dynamics that an internal team would have to learn from zero.
• The build is a spike, not a steady state. You need to contract and credential a large volume quickly, then settle into a much smaller ongoing maintenance load that would leave a full internal team underused.

Where the hybrid model works

The choice is rarely all-or-nothing, and the most durable arrangement is often a hybrid. In a hybrid model, a consultancy carries the heavy initial build — the surge of contracting and credentialing that gets you to an adequate, launch-ready network on deadline — while you stand up a lean internal team to own the steady-state work afterward.

This matches staffing to the actual shape of the work. Network building is front-loaded: enormous effort to reach adequacy, then a lower and more predictable ongoing load of recredentialing, amendments, and monitoring. Paying for a large permanent team sized to the peak means paying for capacity you will not use most of the year. A hybrid lets the firm absorb the peak and lets your internal team run the plateau.

A well-run hybrid also transfers knowledge. As the firm builds, your emerging internal team learns your fee-schedule logic, your credentialing standards, and your provider relationships, so ownership hands off cleanly instead of leaving you dependent.

How to decide based on stage and footprint

Reduce the decision to two questions and it becomes tractable. First, what is your stage — are you a new entrant with no function, or an established plan with a working team and a temporary surge? Second, what is your footprint and its timeline — how many providers, across how many markets, by what date?

If you are early-stage with a hard deadline and unfamiliar geography, outsource the build; you do not have time to make the classic first-timer mistakes on a clock you cannot reset. If you are established with a stable team and a modest, familiar expansion, keep it in-house; you already have the machine and the ramp is short. If you are established but facing a surge that dwarfs your team's steady-state capacity, go hybrid and let a firm absorb the peak.

The most expensive path is the one taken by default — deciding to build in-house without pricing the ramp, the infrastructure, and the deadline risk, then discovering three months in that the network will not be adequate in time.

Deadline risk is the number that matters

Every staffing model has a cost. The one that is hardest to see, and most punishing when it lands, is the cost of missing the date. A network that is not adequate by its filing deadline can delay a launch, shrink a service area, or stall enrollment entirely — and none of those setbacks appear in a salary comparison.

So weigh the decision against deadline risk, not just direct cost. The right question is not merely which model is cheaper per provider. It is which model most reliably delivers an adequate, compliant, correctly loaded network by the date that is not moving. When we help a plan make this call, that is the number we put at the center of the analysis — and it is usually the number that decides it.