Whenever a business needs a capability it doesn't yet have — a technology, a function, a route to a market — it faces the same three-way choice: buy it, build it, or partner for it. The decision looks simple. Getting it wrong is one of the more common and costly mistakes a growing organisation makes.
The reason this choice is so easy to get wrong is that each option is attractive for reasons that have little to do with whether it's the right one. Building appeals to the desire for control. Buying appeals to the desire for speed. Partnering appeals to the desire to avoid commitment. And so the decision often gets made on temperament — what the leadership team is comfortable with — rather than on the merits of the specific situation.
A better approach starts by being clear about what each option really trades away.
What each choice actually costs
Build
Building gives you control and, if the capability is genuinely core to your advantage, the chance to make it a differentiator. What it costs is time and focus. Building well is slow, and every ounce of attention spent building something is attention not spent elsewhere. The trap is building things that feel important but aren't actually where you compete — pouring scarce effort into a capability a supplier could have provided better and faster.
Buy
Buying — whether a product, a service, or a company — gives you speed and access to expertise you don't have. What it costs is fit and, often, dependence. Bought capabilities rarely match your situation perfectly, and integrating them is almost always harder than expected. The trap is assuming the transaction is the hard part, when the integration is.
Partner
Partnering gives you access without full commitment — useful when the future is uncertain or the capability sits outside your core. What it costs is control and, sometimes, clarity. Partnerships depend on continued alignment between two organisations with their own priorities, and they can quietly decay when those priorities drift. The trap is treating a partnership as a permanent solution to a problem that actually needed an owner.
The question that cuts through
The single most useful lens is this: how central is this capability to the advantage we're trying to build?
If a capability is genuinely core — if it's part of why customers would choose you over anyone else — the bias should be toward building or owning it, even at the cost of speed. Control matters most where differentiation lives. But if a capability is necessary yet undifferentiating — something you need but that no customer will ever choose you for — then speed and focus usually win, and buying or partnering is the wiser path.
Most businesses get into trouble by inverting this: they build the things they should have bought (because building feels like progress) and buy the things they should have built (because the core felt too hard to own). The result is a business that is slow where it should be fast and generic where it should be distinctive.
Deciding well, repeatedly
This is not a decision a business makes once. It recurs constantly, as new needs emerge and old choices are revisited. The organisations that handle it well aren't the ones with a fixed preference for building or buying — they're the ones that ask the core-versus-necessary question honestly each time, and resist the pull of whichever option simply feels most comfortable.
Done consistently, this discipline compounds. You end up owning the few capabilities that genuinely make you distinctive, accessing the many that don't, and spending your scarcest resource — focus — where it actually creates advantage.