Your Primary Care Access Problem Is the Start of a Payer Partnership
A primary care access bottleneck is often the best opening a physician network gets to build a partnership with a payer. Here is the five-step playbook I would hand a leadership team starting today.
Most physician network leaders I talk with describe the same bottleneck: Patients wait weeks or months for a primary care appointment, attributed patients find care elsewhere, value-based contracts slip, and the referrals that fund the rest of the system become easy for a competitor to pick off. The familiar fixes are new clinics and new physicians. But, for many organizations today, cash is low, capital is expensive, and clinicians are hard to find.
What I wish more physician network leaders knew is that a primary care access problem is often the best opening a network gets to build what payers value most, a primary care experience their members want. The payers I have worked with now treat the patient experience as their own problem, which makes a network that solves access a partner worth building with. Recently, I've worked alongside a clinically integrated network as it turned this exact bottleneck into a virtual-first care model and a commercial HMO experience, co-developed with a regional payer and launching in January 2027. Here is the playbook as I would hand it to a leadership team starting today.
1. Find the capacity you already have
Access feels like a supply problem, so leaders tend to start with supply. A more useful first question comes from a method I've used nationwide, the Capacity Creation Assessment: what is the lowest-cost setting where each service can be safely delivered? It is the practical side of the Sufficiency Razor, and it screens a practice's office visits against the conditions that can be safely treated in a lower-cost setting, then sizes the physician hours that moving those visits would free. New clinics and recruiting remain necessary in many growing markets, and this analysis tells you how much of that investment you actually need.
That network ran this screen at one of its employed practices after its first virtual-first launch, to make the case for expanding; if I were starting today, I would run it before anything else. The screen compared the primary diagnosis on every office visit with a physician-sourced list of virtually addressable conditions. The study had real limits: one practice and nine months of encounter data. Within those limits, about one-third of office visits could have been handled virtually, an opportunity worth roughly sixty hours per physician per month. The study also modeled what that time could do, such as opening panels to new patients, which is how freed capacity becomes access and revenue. These figures are an identified opportunity, and their value was in giving leadership a clinical and numerical definition of the problem that they could defend.
Gate. Leadership accepts a number for how many visits at one practice could move to a lower-cost setting.
2. Write one value proposition every function can support
A virtual-first product touches clinical leadership, IT, revenue cycle management, payer contracting, marketing, and legal. Each of those teams holds a practical veto, and each will judge the product through its own risks. The network aligned them around one value proposition designed from the start to negotiate payer and employer partnerships. The same story went into its executive memos, internal reviews, and eventually the conversation with payers.
Consider writing that story before you write requirements, and name one leader who owns the product across all six functions so the trade-offs between them get settled in one place. A value proposition that survives your own organization's scrutiny is usually ready for a payer's.
Gate. Your contracting team can explain how the product changes a negotiation, and your clinical leaders can explain how it changes a physician's week.
3. Build one front door
The next design question is where patients enter. The network defined a virtual-first model: a single point of entry to medical, behavioral, and pharmaceutical services that always begins virtually and moves patients to privileged navigation of in-person care when they need it. The first version went live with a triage chatbot and an on-demand virtual clinic.
The hardest discipline was saying no to well-meaning requests. As service lines grew curious about digital front doors of their own, the network held to a principle I recommend to anyone in this position: if every service line has its own digital front door, you have only virtualized your legacy fragmentation problem. Virtualized fragmentation leaves the patient piecing the journey together, now across a set of apps and portals. One entry point puts the work of routing patients on the network, and it gives a payer one product to evaluate. It also does the critical work of supporting patient behavior change. Most health systems already run a patient portal, a vendor chatbot, and an app or two from individual service lines, so for them this step is a consolidation.
Gate. A patient with a symptom has one place to start, and every other digital entry point routes there.
4. Sequence milestones toward benefit design
Many health system leaders I talk with say their organizations have been piloted to death, and the critique is fair. A pilot built to pass or fail on its own usually ends with a report, and the next idea starts from zero. The network organized its work as a deliberate journey toward one vision, that everyone in its region with a medical or behavioral symptom would start their care journey there. It launched the first version as a baseline to collect feedback and iterate, and its roadmap grew into six milestones across three eras:
- Virtual urgent care. Launch, then widen access with a web version and guest flows for people who were not yet patients.
- Hybrid primary care. Add the ability to bill insurance, expand clinical scope to close gaps in care, and stand up a virtual primary care practice integrated with the network's in-person care.
- Population health. Co-develop a benefit design with a payer, so the plan steers members to the virtual-first model and the network can capture the value it creates.
Each milestone made the next one possible: billing competency gave the product a business model, and the virtual primary care practice gave a payer something to attribute members to. That auto-attribution model became critical to a commercial HMO experience launching next year. Payer readiness varies by market, so some organizations will spend longer in the hybrid era before a payer is ready to co-develop a plan, and the same sequence applies. Write your own eras before launch, with the payer conversation as the last one, and fund one milestone at a time. By the population health era, the product passes the test I apply to any payer product, the Attribute-Steer-Pay test: a payer can attribute members to it, steer members toward it through benefit design, and pay for it.
Gate. Each milestone has a written question about what your organization must learn or build before the next stage is funded, so a disappointing answer adjusts the route toward the same vision.
5. Measure value in the payer's terms
A payer will ask what the product is worth, so build the answer at launch and keep it current. The network models potential cost avoidance by comparing where each user intended to seek care before triage with where they intended to go afterward, then discounting for the factors that limit follow-through. Through August 2026, that model put potential cost avoidance at $0.6 to $1.7 million on conservative assumptions, and up to $4.4 million at the high end. These are modeled figures, and actual capture depends on patient behavior and the payment model behind each patient's care. Present the method alongside the range. In my experience, payers give real weight to a conservative number they can audit.
Gate. Your model passes the Analyst Rerun Test: a payer's analyst could rerun it from your documentation and land in your range.
Nexcurve's role
In this work, our clients' leaders make every decision. Nexcurve serves as their advisor and consultant product lead, and brings three capabilities most physician networks and health systems do not have in-house.
- Judgment from having done it before. Nexcurve's advisors have built virtual-first products and made these investment decisions on the payer side. We bring the Capacity Creation Assessment in step 1, size the opportunity clinically and numerically, and make the case for one front door when the pressure to add more is strongest. That gives leadership a choice it can defend under its own organization's scrutiny.
- One story across six functions. In most networks and health systems, no single team owns clinical, IT, revenue cycle, contracting, marketing, and legal at once. Nexcurve develops the value proposition in step 2 with our clients' leaders, drafts the executive memos built on it, and keeps the same story intact from internal review to the payer's table.
- Payer fluency and product leadership. Nexcurve frames the product and its value model in terms a payer recognizes, and can lead the work end to end: the vision and roadmap, partner selection, and the product build.
Discretion is part of the work, so this article names no organizations.
Questions for your leadership team
- How many of your primary care office visits could be safely delivered in a lower-cost setting, and at which practices?
- Which of your physician groups or partner functions would be the last to support a virtual-first model, and what story would bring them along?
- How many digital front doors does your organization run today, and which one would a payer evaluate?