Insight The operator's journey

Build, buy, or partner

When you need a capability you do not have, you can build it, buy it, or partner for it. Here is how to choose the right path instead of defaulting to building everything yourself.

5 min read

Every growing business keeps hitting the same situation: it needs a capability it does not have. A function, a skill, a system, a way into a market. The default founder response is to build it, because building feels serious and committed and cheap. Often it is the worst of the three options available. You can build, buy, or partner, and choosing well, rather than reflexively building, is one of the quiet leverage points of running a business. Here is how to decide.

Three ways to get a capability

When you need something you do not have, you have three paths.

Build it yourself, developing the capability in-house from scratch. Maximum control and ownership, maximum time and cost.

Buy it, paying for an existing tool, solution, or service that already does the job. Fast and often cheap for anything that is a commodity, with less control.

Partner, working with someone who already has the capability and sharing the value rather than owning it. Fast access and expertise, in exchange for shared upside and less control.

The mistake is not choosing wrong between them once. It is never really choosing at all, defaulting to build for everything and paying for it in time, money, and focus.

The default founder answer is build. It is usually the slowest, most expensive way to get a capability you did not need to own in the first place.

Build your edge, buy your commodities

The cleanest way to decide between building and buying is to ask whether owning the capability is a genuine competitive advantage, or just a cost.

When to partner instead

Partnering is the option founders forget, and it is often the best one when building would be too slow and you do not need to own the capability outright.

When speed or access matters more than control

Partner when someone already has the capability, the market access, the expertise, the infrastructure, and aligning incentives gets you there far faster than building would. Reaching a new market through someone established in it beats spending years building your own way in.

When the capability is not something you must own

If owning the capability outright is not a real advantage, sharing value to access it through a partner is a fair trade. You give up some control and some upside in exchange for speed and expertise you would otherwise spend heavily to build. A fractional expert is a version of this: partnering for capability rather than building a full team for it.

When you cannot evaluate it well enough to build it

If the capability is in an area you cannot assess, partnering or buying lowers the risk of an expensive in-house mistake, the same caution that applies to hiring for a role you cannot evaluate. Borrowing proven capability beats building something you cannot judge.

Build, buy, or partner

  • Recognize you have three options, not just build
  • Build what is core to your edge and worth owning
  • Buy commodity capabilities instead of reinventing them
  • Partner for speed and access when ownership is not the advantage
  • Resist the reflex to build everything yourself
  • Weigh time and focus, not just headline cost

The deeper point is that founders systematically overvalue ownership and undervalue speed and focus. Building everything feels like the committed choice, but it scatters your finite attention across capabilities you did not need to own, slowly, while the few things you should genuinely build get less of you. Choosing build, buy, or partner deliberately is part of the operator-journey shift from doing everything to allocating wisely.

If you are about to build a capability and are not sure it is worth owning, thinking through whether to build, buy, or partner is exactly the kind of strategic call a Growth Audit can help you weigh.