Almost any project — a product line, a capability, a market presence — has three roads to it: build it internally, buy it ready-made, or reach it through a partner who already has it. Companies often choose among the three by temperament: builders build, buyers buy, and everyone else signs partnerships. The choice deserves better than temperament, and it reduces cleanly to two questions that can be asked before the first meeting with any vendor, target or partner.
The first variable is strategic: is the thing the project delivers part of what makes customers choose this company, or is it infrastructure — necessary, but invisible to the customer's decision? What differentiates must be owned, because renting it means renting the company's advantage to whoever else the landlord serves. What is infrastructure should generally be rented or bought, because building it spends the scarcest resource — the organization's capacity for complex work — on something the customer never rewards. Most bad build decisions are infrastructure built out of pride; most bad buy decisions are core competence bought out of impatience.
The second variable is time in two forms. How fast the capability must arrive: a market window that closes in quarters forgives only buying or partnering; a thesis with years of runway can afford building, which is slower per project and compound per capability. And how fast the field moves: in domains where the state of the art resets quickly, a partnership rents an asset someone else keeps current, while a build commits the company to maintaining that freshness itself — a cost that never appears in the project budget and never stops appearing in the operating one.
The three roads are not symmetrical in one respect that decides many cases: building and buying are commitments, partnering is an option. A company unsure of the demand behind the project does well to partner first, not because partnership is cheaper — it is usually more expensive per unit — but because its main purchase is information, and information is what the other two roads spend so freely. The market-side half of the question — whether the project deserves any of the three — is the territory of how investment decisions are made and what the financial model must show before the roads are compared.
Own what differentiates, rent what does not, and let the clock — not the budget of the current quarter — decide which is which.
Running the two questions against a concrete project, and mapping the three roads' commitments against them, is standard work in the project and investment practice — a short exercise that saves companies from the two most expensive phrases in the genre: «we'll build it ourselves» and «we'll figure the integration out later».
We use cookies to analyse traffic and improve the site. Analytics is enabled only with your consent. Cookie Policy