Build, Buy, or Wait: A Framework for Timing the Bet

Why the hardest question in technology strategy isn't whether to adopt — it's when, and most executives resolve it with instinct instead of a framework. · Juan Vegarra

The hardest question in any technology strategy conversation right now isn't whether a capability matters. Almost everything under discussion in 2026 matters to some degree. The hard question is when to move on it. Move too early and you fund someone else's unfinished R&D, lock into an architecture that's obsolete within eighteen months, and train a workforce on tools that won't exist in their current form by the time anyone is fluent in them. Move too late and a competitor captures the operational advantage, the scarce talent who understand the technology, and the customer relationships that come with being the credible first mover in a category. Most executives resolve this tension with instinct, shaped mostly by whichever failure mode they personally witnessed most recently. It deserves an actual framework.

A distinction that gets collapsed too often

Build, buy, and wait are not three points on a single axis running from cautious to aggressive. They are three different bets with entirely different risk profiles, and the right one depends on where the capability in question sits relative to your actual competitive advantage, not on how ambitious your culture wants to appear this quarter.

Build makes sense only when the capability is genuinely core to how you win — when getting it right, and owning the roadmap for it, is itself a source of differentiation customers would recognize and pay for. This is a considerably smaller list than most technology leaders want to admit in a strategy offsite. Building because "we don't want to depend on a vendor" is not a strategy. It is an emotional response to a real risk, dressed up in strategic language. If the capability is not something customers pay you for, directly or indirectly, building it in-house is usually the expensive way to end up with something worse than what a mature vendor already sells.

Buy makes sense when the capability is necessary but not differentiating, and when a mature market of vendors exists solving the underlying problem at a scale no single company can match internally. The mistake here isn't buying — it's buying too early, before the vendor landscape has consolidated, when today's best-of-breed choice quietly becomes tomorrow's acquisition target with a sunset notice eighteen months later. The tell worth watching is vendor count. If there are still a dozen or more credible players and no clear category leader, you are buying into a market, not a product, and you should price that uncertainty into the decision.

Wait is the option executives are least comfortable choosing, because it can look like inaction to a board that wants to see visible momentum on every earnings call. But waiting deliberately — with a defined, specific trigger for re-evaluation — is often the highest-return decision available, and it is systematically underused because it doesn't generate a press release. The trigger has to be concrete: a cost curve crossing a named threshold, a specific competitor move, a regulatory clarification that removes a real legal risk, a reference customer at your scale succeeding publicly with the approach. Waiting without a defined trigger isn't strategy. It's procrastination with better branding, and boards should learn to tell the difference.

What the data on technology timing actually shows

There's a useful and somewhat humbling body of research behind the "first mover advantage" instinct that's worth surfacing here. An analysis of Gartner Hype Cycles going back to 2000 found that most of the technologies that went on to matter most were not identified early in their own adoption cycle by the standard hype-cycle process, and that only a small share of breakthrough technologies — something like a fifth — actually travel the full arc from innovation trigger through inflated expectations, disillusionment, and on to genuine widespread adoption in a way that was visible in advance.^[1] The practical implication is uncomfortable for anyone who wants to believe that spotting a technology early is itself the skill: identifying that something exists is not the same skill as correctly timing when it becomes investable, and conflating the two is exactly how organizations end up locked into architectures during a technology's most volatile, least mature phase, mistaking enthusiasm for readiness.

Turning the framework into a decision

The executives getting this right in 2026 aren't the fastest movers or the most cautious ones. They're the ones who can say, with real specificity, why a given capability is core rather than commodity, what the vendor landscape actually looks like today versus what it's likely to look like in eighteen months, and what concretely has to become true for a "wait" decision to convert into a "buy" decision. That specificity is what separates an actual technology strategy from a technology mood dressed up in strategy language for the board deck.

The counter-case worth holding onto

It would be too tidy to end here without acknowledging where this framework breaks down. In categories with genuine winner-take-most network effects — where the value of the platform compounds with the number of users or the volume of data flowing through it — waiting for the market to "consolidate" can mean waiting until the consolidation has already happened around a competitor, at which point buying in is no longer available on reasonable terms, if it's available at all. The framework above assumes a market with room for a considered entry later. Not every market offers that room, and part of the discipline is correctly identifying, early, which kind of market you're actually in before defaulting to the safety of "wait."

Most technology decisions aren't actually about courage or caution. They're about whether the organization can articulate, specifically, which of these three bets it's making and why. Where is your organization defaulting right now — build, buy, or wait — and is that a decision, or just momentum wearing a decision's clothing?

Juan Vegarra is the author of An Outsider's Playbook (forthcoming). The views here are his own. More essays · Write me