Should You Build, Buy, Partner, or Walk Away? A Decision Framework for Healthcare Providers
Direct answer: Healthcare providers should choose build when a capability is clinically differentiating and you have the talent to run it, buy when speed and scale matter more than customization, partner when the capability is important but outside your core (and the regulatory/capital risk is shared), and walk away when the opportunity fails on margin, mission fit, or your ability to execute safely. The right answer depends on three tests: strategic centrality, execution capacity, and total risk-adjusted cost. This article walks through how to run that decision.
Disclosure: This article is published by Percision (percision.app), an AI-powered strategic intelligence platform. We reference our own tool below as one option among several — including doing this analysis manually or with a consultant.
Why the Build/Buy/Partner/Target Question Is Different in Healthcare
Most build-vs-buy frameworks were written for software companies deciding whether to write code or license it. Healthcare providers face a harder version. The decision isn't only about capability and cost — it's about patient safety, regulatory exposure, reimbursement dynamics, and community mission.
Consider the range of decisions this framework actually covers for a hospital, health system, or multi-site practice group:
- Build: Launch your own ambulatory surgery center, urgent care line, or in-house telehealth platform.
- Buy: Acquire a physician group, an imaging center, or a competing facility.
- Partner: Enter a joint venture with a payer, a management services organization, or a specialty provider.
- Target / Walk away: Decide a service line (e.g., a low-volume, high-fixed-cost specialty) isn't worth pursuing at all.
The word "Target" in the framework matters here: before you decide how to enter, you decide whether the opportunity is even the right target. In healthcare, a lot of value comes from disciplined walking away — not chasing volume you can't staff or reimbursements that don't cover cost.
The Four Tests: How to Run the Decision
Work through each option against these questions in order.
1. Strategic centrality — is this core to your clinical identity? If a capability directly shapes patient outcomes or your market position (a flagship cardiac program, a proprietary care model), lean toward build or buy so you retain control. If it's necessary but generic (revenue cycle management, food service, a niche diagnostic), partner or outsource.
What good looks like: You can name the specific outcome or margin lever the capability drives, and whether losing control of it would erode your reason for existing.
2. Execution capacity — can you actually run it? Building an in-house telehealth platform sounds cheaper than licensing one until you account for security, compliance, clinician training, and 24/7 support. Ask: do we have the talent, the IT depth, and the appetite for a multi-year ramp? If not, buy or partner where the capability arrives pre-built and staffed.
What good looks like: An honest inventory of your team's track record executing similar initiatives — not what you hope you can do.
3. Total risk-adjusted cost — including regulatory and reimbursement risk. A build looks cheaper on a spreadsheet because acquisitions carry a premium. But acquisitions come with integration risk, cultural friction, and inherited liabilities (compliance history, malpractice exposure, legacy contracts). Partnerships spread capital risk but dilute control and margin. Model each on a risk-adjusted basis, not sticker price.
What good looks like: A side-by-side comparison with explicit assumptions on Stark/Anti-Kickback exposure, payer mix, and capital cost.
4. The walk-away test. If a service line can't clear your margin threshold, you can't staff it safely, or it distracts from higher-value programs, walking away is the strategy. Framework discipline means writing down what would have to be true to make you say yes — and being willing to say no when those conditions aren't met.
How Percision Helps — and When It Doesn't
Running this analysis rigorously is where most provider organizations stall. The clinical and finance teams have the raw inputs, but assembling a board-ready comparison — DCF on an acquisition target, scenario models for a JV, risk-flags on inherited liabilities — usually takes weeks of analyst time.
This is where a tool like Percision fits. Percision runs your business context through structured reasoning steps across the Build/Buy/Partner/Target framework and produces the comparison quickly: DCF valuations and 60+ financial ratios for a buy scenario, warning signs on a target, and board-ready decks you can bring to your governance committee. It's positioned as a co-pilot, not an autopilot — your leadership team owns the decision. The value is speed and structure: getting from "we're debating this" to "here's a defensible recommendation" in minutes rather than an eight-week engagement.
When Percision is not the right call: If your decision hinges on clinical judgment that no financial model captures (e.g., whether a care model is safe), or on deep local regulatory nuance, a healthcare-specialist consultant or your compliance counsel is essential. And if you're comparing two simple options with clean numbers, a well-built spreadsheet and a good CFO are entirely sufficient. Percision earns its place on complex, multi-scenario decisions where the analytical lift is real — not on every choice.
Putting It Into an Execution Plan
A decision without an execution plan is just an opinion. Whatever the framework recommends, translate it into: (1) the specific conditions that triggered the choice, (2) owners and milestones, (3) the KPIs you'll track to know if it's working, and (4) the tripwire that tells you to reverse course. Percision's command-center dashboards can hold those KPIs, but a shared tracker maintained by your COO works too. The tool matters less than the discipline of writing it down.
What this looks like when the analysis is actually run
The same capability gap produced two different answers in two runs — one partner, one build. The comparison is the useful part.
The subject is Cedar Ridge Health Partners, a sample company profile we use for testing rather than a customer: a physician-owned multi-specialty group, $196M net patient revenue, 128 physicians, 14 clinics.
Excerpt from a real Percision run · Pricing Strategy (T2) · sample company profile
The PARTNER answer. Co-develop a shared-savings attribution and risk-adjustment engine with the existing commercial payer partner, covering 38,000 downside-risk lives. $2.5–3.0M over 18 months, returning 7.6–9.1× — $22.8M of NPV upside. Terminate if the payer refuses exclusivity by Month 6, or attribution accuracy is below 80% by Month 18.
The BUILD answer. Launch a three-year employer direct-contracting pilot targeting the 3–5 largest self-insured employers in the two metros, offering bundled care at fixed prices 8–12% below commercial payer rates. $2M over 36 months, returning 6.0–9.0×. Terminate if fewer than 2 employer contracts are signed by Month 18, or operating margin on the channel falls below 6% for two consecutive quarters.
What each depends on. The partner route depends on a payer granting exclusivity. The build route depends on the 212,000 attributed lives providing a credible pricing base and the ASC providing surgical capacity competitors cannot replicate in the same catchment.
What both are funded from. The $9M three-year distributable capital envelope already voted by physician-owners; no external financing required.
| Metric | Target | By |
|---|---|---|
| Shared-savings settlement accuracy | ≥90% vs payer file | Month 18 |
| Platform margin on shared-savings pool | 15–25% | Month 24 |
| Employer-contracted lives added via platform | +15,000 lives | Month 36 |
Partnering returns 7.6–9.1× and building returns 6.0–9.0× — close enough that the decision is not about return. It is about which dependency the group would rather carry: a payer's willingness to grant exclusivity, or its own ability to sell to employers it has never sold to.
Both routes also point in opposite strategic directions. The partnership deepens the payer relationship; the employer pilot is explicitly designed to bypass "payer intermediaries". Doing both would be incoherent, and having them priced side by side is what makes that visible before either is started.
Read a complete Percision report — every page, no email required.
FAQ
Q: When should a hospital build instead of acquire a physician group? Build when the specialty is central to your identity, you can recruit the clinicians, and you'd rather grow the culture than integrate an existing one. Acquire when speed to market or an established patient base outweighs the acquisition premium and integration risk.
Q: How do we account for regulatory risk in a build/buy decision? Model it explicitly as a cost and probability, not a footnote. Inherited compliance history, Stark/Anti-Kickback exposure, and payer contract terms should appear in your risk-adjusted comparison — an acquisition's clean spreadsheet can hide expensive liabilities.
Q: Is walking away really a valid strategic outcome? Yes. A disciplined "no" to a low-margin, hard-to-staff service line protects capital and focus. The framework's job is to make that decision defensible to your board, not to force an entry.