Build, Buy, or Exit Decision Framework
Choose a market position by testing maturity, company fit, and the path to leadership.
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 6
- Confidence
- 98%
The framework begins with market evolution rather than a reflexive build-versus-buy comparison. First determine whether the category is emerging, where an internal challenger may still establish itself, or consolidating, where a few vendors already control most demand. Next evaluate the company honestly: its product-development strengths, sales channel, customer relationships, and ability to disrupt entrenched leaders. Because software profit tends to concentrate among category leaders, require a credible route to the first or second position rather than accepting incremental share gains. Finally, test whether an acquisition would be strategic and monetizable through the existing channel. The resulting choice is explicit: build when the market and company permit leadership, buy when ownership is strategically necessary and acquisition creates that path, or exit when neither route can win.
Origin
Michelle Feaster used this reasoning at HP after inheriting a fifth-place data-center automation business with 200 engineers, roughly $20 million in revenue, and no convincing organic path to market leadership.
Core principles
- 01Market maturity determines which strategic options remain viable.
- 02A company must evaluate opportunities against its actual capabilities.
- 03Software economics disproportionately reward the top two competitors.
- 04Buying only works when the acquirer can monetize through its channel.
- 05If neither building nor buying offers a credible path to leadership, exit.
How to run it
- 1
Classify Market Evolution
Determine whether the category is emerging or consolidating. Examine how much market share is already concentrated among the leading vendors.
Pro tip Use competitive share and buying behavior rather than the category's age alone.
Watch out Treating a consolidated market like an open greenfield can lead to years of unproductive investment.
- 2
Know the Company
Assess whether the organization is genuinely capable of building a disruptive product in this category. Include its culture, development strengths, customer trust, and channel model.
Pro tip Evaluate demonstrated capabilities rather than the capabilities executives wish the company had.
Watch out Scale and engineering headcount do not automatically produce innovation.
- 3
Demand a Leadership Path
Model whether building or buying can produce a number-one or number-two market position. Reject plans whose best plausible outcome is moving from fifth to third or fourth.
Pro tip Connect market position to the category's long-term profit distribution.
Watch out A product can grow revenue while still losing money indefinitely if it never becomes a leader.
- 4
Test Strategic Necessity
Decide whether the category is strategic land: a control point in future technology or a capability whose absence damages larger businesses. If it is not strategic, exiting may be preferable.
Pro tip Look for convergence with existing products and effects on important customer relationships.
Watch out Strategic importance should not be assumed merely because the company already operates in the category.
- 5
Validate Channel Fit
Interview salespeople and customers to establish how often the capability affects deals and whether the existing channel reaches the relevant buyer. Estimate whether the acquirer could capture revenue currently going to competitors.
Pro tip Use lost-deal evidence and buyer overlap to test monetization.
Watch out A good product without a compatible sales motion may not justify an acquisition.
- 6
Choose Build, Buy, or Exit
Build if the market remains open and the company can plausibly lead; buy if the capability is strategic and acquisition creates a leadership path; otherwise exit. Reallocate resources rather than preserving an uncompetitive business by default.
Pro tip Present the decision with a small number of concrete facts and explicit alternatives.
Watch out Do not frame buying as the only option without comparing it to a disciplined exit.
In the wild
HP had about 200 engineers, roughly $20 million in revenue, and the fifth-place product in a category where Opsware, BladeLogic, and IBM controlled about 80% of the market. Feaster concluded that HP's channel strengths could monetize a leading product, but its organizational strengths did not support building from fifth place to leadership. Because automation was strategic to HP's broader IT operations portfolio, the choice narrowed to buying a leader or exiting.
→ HP acquired Opsware and used its channel to accelerate the business rather than continuing an unlikely organic climb.
A large software company is fifth in a mature niche, lacks buyer overlap, and finds that the category does not strengthen any major portfolio product. Even if an acquisition could improve its position, the company applies the framework and declines to buy. It closes the internal product and moves engineers to a market where it has a realistic leadership path.
→ Capital and talent move away from a structurally unattractive business.
Common mistakes
Ignoring Market Maturity
A team may compare product roadmaps without recognizing that competitors have already consolidated the market. That makes an organic catch-up plan appear more plausible than it is.
Confusing Headcount With Capability
A large engineering organization may still lack the culture or strengths needed to create a disruptive product. The framework requires an honest assessment of company identity.
Accepting a Third-Place Outcome
Incremental share gains can obscure the absence of a path to durable profitability. Require a credible route to one of the category's economically advantaged positions.
Is it for you?
Best for
It is best for executives deciding whether to build, acquire, or abandon a product category.
Not ideal for
It is not ideal for very early markets where competitors, buyers, and category boundaries remain unknowable.
From the transcript
“And so to me, first principles are what do users want to do and what's happening in the market.”
“So to me, there's either emerging markets or consolidating markets.”
“So you're only left with buy or exit the market.”
From the episode
Opsware (with Michel Feaster)
Michel Feaster