Build vs Buy vs Partner: Growth Decision Matrix
Why this matters
When you want a capability you do not have (a new service line, a crew with a skill, coverage in a new area), you have three ways to get it: build it yourself, buy it from someone who already has it, or partner with a shop that does. Each trades time, cash, and control differently. Reach for the wrong one and you either spend years building what you could have bought, overpay for a business you cannot integrate, or hand a partner the keys to a customer relationship they later walk off with. This is a sequencing and control decision, not just a cost one.
The three paths in plain terms
- Build: grow the capability in-house. Hire and train, buy the tools, ramp the line yourself. Cheapest in cash, most expensive in time, maximum control.
- Buy: acquire a shop (or a crew, a route, a customer book) that already has the capability. Fastest to capability, most cash up front, integration risk.
- Partner: team up with another shop. They supply the capability, you supply the customers or the work, you split the result. Low cash, fast, but you give up control and share the relationship.
Comparison matrix
| Factor | Build | Buy | Partner |
|---|---|---|---|
| Speed to capability | Slow | Fast | Fast |
| Cash required | Low, spread over time | High, up front | Low |
| Control | Full | Full after integration | Shared, limited |
| Key risk | Time and ramp failure | Overpaying, bad integration | Partner walks with the customer |
| Reversibility | High | Low; hard to unwind | Medium; can end the deal |
| Best when | Capability is core and you have time | You need it now and can fund it | You need it occasionally or to test demand |
When to build
Build when the capability is central to who you are and you can afford the time.
- It is a core skill you want to own permanently, not rent.
- You have the runway to ramp it without starving the rest of the business.
- Control and quality matter more than speed (you want it done exactly your way).
- The market will still be there when you finish ramping.
Building is the default for anything that defines your brand. You do not want your signature capability living in someone else's hands.
When to buy
Buy when you need the capability fast, it would take too long to build, and you can fund and integrate it.
- The capability would take years to build credibly (an established reputation, a trained crew, a customer book in a new area).
- You have the cash or financing and the appetite for the risk.
- You can actually integrate it: similar enough operations, compatible culture, systems you can merge without chaos.
The trap is buying a business you cannot run. Most acquisitions disappoint not on price but on integration: mismatched standards, a crew that leaves, customers who were loyal to the old owner. Buy only what you can absorb.
When to partner
Partner when you need the capability occasionally, want to test demand before committing, or cannot justify building or buying yet.
- The demand is real but unproven, and a partnership lets you serve it without a permanent commitment.
- The capability is adjacent, not core; you would rather refer and split than own it.
- You want a low-cash, reversible way to enter a line or area before deciding to build or buy.
The central partner risk is the relationship. If the partner serves your customer directly, they can build their own bond and eventually cut you out. Protect against it: keep the customer relationship anchored to you (you own the account, the billing, the follow-up), define the split and the boundaries in writing, and treat the partnership as a test, not a permanent outsourcing of something that should be yours.
How to choose: a quick walk
- Is the capability core to your brand? Yes and you have time -> build. Yes but you need it now -> buy.
- Do you need it permanently or occasionally? Occasionally, or just to test -> partner.
- Can you fund a purchase and integrate it? No -> build or partner instead of buy.
- Does the option keep the customer relationship with you? If a partnership would hand the customer to someone else, structure it so you stay the owner, or build instead.
Default to build for anything core, buy when speed is worth the cash and the integration is real, partner to test or to cover the occasional and the adjacent. The worst outcomes come from buying what you cannot integrate and partnering away what you should have owned.
References
- U.S. Small Business Administration: guidance on business acquisition, partnerships, and capability growth.
- Trade-standard practice on integration risk and partnership structuring.
- See related: "Add a Service Line vs Go Deeper" and "Geographic Expansion Readiness."