The diagnostic, not the deck.

The most expensive thing a health plan or IPA can do at the start of a network build is spend six weeks producing a strategy deck. Not because strategy is wrong — it isn't — but because a deck produced before anyone has looked hard at the actual contracting backlog, the actual credentialing capacity, and the actual state of the provider data is strategy built on assumptions. And assumptions, in network builds, cost time.

We've run builds that started with a strategy engagement from another firm. The decks are usually good. The timelines in the decks are almost never realistic, because they were built without knowing what was in the contracting queue, who owned credentialing, or how clean the provider data actually was. By the time the build team inherits the plan, three things have usually happened: the go-live date has already slipped, the budget has been partially spent on the strategy work, and the people who will actually run the build weren't in the room when the plan was made.

What a diagnostic actually is

A diagnostic is not a strategy engagement. It's a two-week structured inventory of where you actually are — not where you planned to be, not where a previous vendor said you were. It produces a build plan: a document with named owners, named dates, and a clear-eyed accounting of the gap between current state and go-live requirements.

The diagnostic covers six areas:

• Footprint and adequacy baseline. What does CMS or your state DOI require, by county and by specialty? Where are you today? What is the actual gap — not the gap from the last RFP, but from a fresh pull of your provider file against current adequacy standards.
• Contracting backlog. How many contracts are in flight, who owns each one, where are they stuck, and what is the realistic velocity? A contracting pipeline that looks like 80 signed agreements can have 60 of them sitting unsigned for reasons nobody has tracked in 90 days.
• Credentialing inventory. What is the current credentialing queue, what is the committee cadence, and is there any risk that credentialing will bottleneck go-live? This is the item that most plans underestimate — credentialing lead times are fixed by regulation and committee schedules, not by how much you want to accelerate.
• Provider data quality. CAQH hygiene, NPI validation, taxonomy codes, directory accuracy. Bad provider data is the silent killer of builds — it surfaces at go-live, not before, unless you inventory it early.
• Staffing and ownership. Who is actually running this work? Are they dedicated to this build or splitting time across three other priorities? The plan needs to reflect reality.
• Regulatory clock. What are the submission dates — CMS application, state filing, accreditation review — and are they immovable? Build the go-live date backward from the regulatory deadline, not forward from the kickoff.

What comes out of it

At the end of two weeks, you have a build plan. Not a strategy framework, not a set of recommendations — a plan. It has a go-live date that the team has agreed to. It has named owners on each workstream. It has a weekly operating cadence from day one of the build. And it has a clear accounting of what needs to be true at the end of each two-week sprint for the overall date to hold.

The build plan is also where you find out if the go-live date was realistic. We have run diagnostics where the honest answer, at the end of week two, is: the date you have in writing is not achievable given current contracting velocity and credentialing lead times. The right thing to do is surface that in week two — not in week ten, when you are three weeks from a submission deadline and the pipeline is forty providers short of adequacy.

Why the fixed fee matters

We price the diagnostic as a fixed fee, no commitment past it. This is intentional. A client should be able to commission a diagnostic, get a build plan, and then decide whether to execute with us, execute with their own team, or go find someone else. The plan belongs to the client.

The practical consequence of this structure is that the diagnostic has to be worth the fee on its own — which means it has to produce something immediately useful, not a set of findings that only make sense if you hire the firm to act on them. We have had clients take the build plan and run the build themselves. That is a good outcome. The plan was right.

The alternative

The alternative to a diagnostic is starting the build without one. This works exactly as well as you'd expect. The contracting team prioritizes providers based on whoever asked most recently. The credentialing committee discovers in month two that it does not have capacity for the volume. The provider data gets loaded to the directory before anyone ran a validation pass. The go-live date slips, and then slips again, and by the third slip the executive sponsor is asking why nobody flagged this earlier.

Nobody flagged it because there was no plan for anyone to be accountable to. The diagnostic is what creates the plan.

Most builds don't fail on strategy. They fail on the connective tissue — the handoffs, the data quality, the credentialing bottleneck that nobody owned. The diagnostic is where you find the connective tissue before it finds you.

If you are about to start a network build — or if you are three months into one and wondering why it has slowed down — the right first move is always the same: stop, do the inventory, produce the plan, then run from the plan.