Your company needs a new capability. Should you build it, buy it, or partner for it?
Years ago, I made the case to the leadership of a global consumer electronics company that it should acquire a relatively young streaming-device company. The TV screen was becoming a dumb pipe, and the value was moving to the software that decided what viewers watched. Owning the startup would let the company keep making world-class TVs while extending its reach onto screens it didn’t make. The…
In recent years, a global consumer electronics company pondered the acquisition of a younger streaming-device startup. The shift of value from TV screens to software that decides viewers' content led the company to consider purchasing the startup. While the internal teams possessed strong hardware expertise, the startup's software was superior.
However, the final product failed to gain traction, and the project was discontinued. This story is a common tale among businesses grappling with the decision to build, buy, or partner.
Artificial intelligence has greatly accelerated the development of new products, market entry, and customer reach. However, it also reveals gaps in a company's capabilities, prompting leaders to face the build/buy/partner question more frequently. Unfortunately, a bias towards building in-house persists due to overconfidence, "not-invented-here" syndrome, and the misconception that building will be faster than running the capability.
AI is changing the cost of starting a project, but not the cost of ownership. Building a capability creates a long-term cost burden, while AI significantly reduces the initial costs of prototyping. Despite these advantages, many businesses still default to the wrong decision, which is building. To make a more informed choice, businesses should evaluate the capability against four criteria: defensibility, time to value, integration risk, and cultural fit.
A capability must be defensible, enabling durable moats and advantages that customers notice. It should also be achievable within a reasonable timeframe, have low integration risk, and align with the company's culture. While building a capability might be necessary in some cases, it is essential to consider the costs and benefits carefully. A partner or acquisition might be more suitable if the capability is not easily replicable by competitors and can be integrated into the company's operations easily.
Written by urgent.news from Fast Company's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.