Free Network Build Assessment
Score your buildThat’s the week in a build where somebody finally runs the adequacy numbers and finds out the network doesn’t pass. There’s a scramble, a lot of calls to providers who were never going to sign in time, and a filing that goes in weaker than it should have.
Our team has spent about thirty years inside health plan network builds: on the plan side and in the shops that get hired when a plan is behind. Medicare Advantage, Medicaid, Exchange, D-SNP. Rural counties in states nobody wants to draw. The builds that go well and the ones that go to the wire.
The pattern never changed. Contracting lived in a CRM or a spreadsheet. Credentialing lived somewhere else. Adequacy lived in a tool somebody exported into every few weeks. Three systems, and the gap between them is exactly where a build goes wrong. Not because anyone was careless, because nothing connected the work to the score.
So we built the thing that connects them. The pipeline and the adequacy score run on the same data, in the same system, at the same moment.
Blueprint is new and we’re early. What isn’t new is the judgment underneath it, which specialties actually fail, which counties are quietly impossible, what a state reviewer looks at first. That part took thirty years and you can’t shortcut it.

Harney. Malheur. Wallowa. The counties that decide whether a build passes are rarely the ones anyone worries about at kickoff.
Most vendor sites in this category are impossible to fact-check. We went the other direction, because a claim you can verify is worth more than five you can’t.
Across the team, on the health plan side and in the consultancies that serve them. It's experience, not customer proof, and we don't dress it up as customer proof.
Time and distance limits, minimum counts, and county types, straight from CMS's HSD Reference File. Medicare Advantage only: state Medicaid and Exchange rules aren't built in, though you can load another standards file.
Blueprint scores on straight-line distance. A straight-line failure is real; a straight-line pass shows as unconfirmed, because drive time isn't measured.
We don't have any yet. The scenarios on this site are labeled as illustrative. When a customer says something worth quoting and lets us print it, we'll print it with their name on it.
Every vendor in this category has them. Ask where the number came from and watch what happens. We'll have ours when we've earned them.
Quest has been CMS’s own adequacy contractor since 2007. If your compliance team needs the number that CMS itself uses, that relationship isn’t ours to take, and we’ll say so on the call.
What we’re after is the twenty weeks before that measurement: the actual build, where a team is deciding who to call next and nobody can see what each signature does to the county score. That work happens in spreadsheets today. It shouldn’t.
Knowing where you sit in a market is worth more than pretending you sit everywhere.
Being early with us should be an advantage, not a risk. So the terms are built that way.
No annual lock-in. If it isn't working in month three, leave in month three. A long contract is how vendors stop having to be good.
Export your providers and pipeline to CSV any time, a format you can actually open.
We're small. That means no ticket queue, and it also means we answer for our own decisions.
It's on the pricing page. In a market where almost everything is quote-only, that's a deliberate choice.
We’ll tell you about one. That conversation will tell you more about whether we know this work than anything written on this page.