Strategic Acquisition Decision Ladder
Choose whether to build, buy, or acquire the category leader
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 96%
The decision ladder begins by defining the capability the company needs and identifying why it matters strategically. Leaders then classify the possible acquisition as a technology, product, adjacent-business, or talent deal so that the intended value is explicit. The company compares acquisition candidates with an internal build, considering time, product quality, user pull, and execution risk. When individual adoption determines category success, buying the established leader can be more valuable than settling for a weaker candidate. Talent is evaluated during diligence and retained deliberately, but it does not replace the need for a strong product thesis. The output is a defensible build-or-buy decision tied to a specific strategic objective rather than an acquisition pursued for novelty or defensive maneuvering.
Origin
Kurt DelBene described how Microsoft evaluated its mobile productivity gap before acquiring Acompli, Sunrise, and Wunderlist.
Core principles
- 01Start with the strategic capability gap
- 02Compare internal development with acquisition
- 03Treat product, technology, adjacency, and talent as distinct motives
- 04Prefer the category leader when user pull matters
- 05Use talent quality as diligence, not a substitute for product fit
How to run it
- 1
Define the strategic gap
Specify the customer scenario or capability where the existing portfolio is inadequate. Connect that gap to the broader product strategy.
Pro tip Describe the required outcome before discussing acquisition targets.
Watch out Starting with an attractive company can produce a deal without a durable strategic rationale.
- 2
Classify the acquisition motive
Decide whether the primary objective is product, technology, adjacency, or talent. Keep secondary benefits separate from the principal rationale.
Pro tip Use one primary classification to clarify post-acquisition priorities.
Watch out Multiple vague motives make success impossible to evaluate.
- 3
Compare making with buying
Estimate what an internal build would require and what it could realistically deliver. Compare its timing, quality, and adoption prospects with available targets.
Pro tip Include the cost of entering behind a product with strong user pull.
Watch out Do not assume an incumbent organization can reproduce an external team's execution speed.
- 4
Identify the required market position
Determine whether a capable second-place product is sufficient or whether the strategy requires the category leader. Prioritize leadership when the client controls the customer relationship.
Pro tip Look at active use and engagement, not only feature lists.
Watch out Buying a weaker product can leave the original strategic gap unresolved.
- 5
Diligence the team and product
Validate product quality, user momentum, leadership capability, and the likelihood of retaining key people. Confirm that the team can operate effectively inside the acquirer.
Pro tip Assess how the founders' skills could contribute beyond the original product.
Watch out Do not turn an attractive leadership candidate into an excuse for a weak product acquisition.
In the wild
Microsoft identified email, contacts, calendaring, and to-do as core Office 365 scenarios that needed excellent mobile clients. It compared building internally with acquiring available leaders, then selected Acompli for its product quality, adoption, and strategic fit. Sunrise and Wunderlist extended the mobile productivity footprint.
→ Microsoft rapidly established strong mobile productivity applications across iOS and Android.
Common mistakes
Buying to block a competitor
A defensive chess move does not provide the positive product mission needed to overcome normal acquisition risk.
Settling for second best
When end-user pull drives adoption, acquiring a weaker client can preserve the category leader's advantage rather than close the gap.
Confusing secondary benefits with the thesis
Talent and competitive benefits may be valuable, but the principal acquisition rationale must remain explicit.
Is it for you?
Best for
It is best for established companies deciding how to close an important product or platform gap.
Not ideal for
It is not ideal for opportunistic deals that lack an identified capability gap or committed product sponsor.
From the transcript
“And so we said, do we want to make or do we want to buy?”
“there are times when you think you can buy the second best or the third best person or uh product or company, and there are…”
“The primary reason for this acquisition was they had a great product in a in a space that we thought was super complimentary to us.”
From the episode
Acompli, Sunrise, and Wunderlist (with Kurt DelBene)