Roadmap Intersection Acquisition Rule
Acquire only when a valuable target fills a defined product-roadmap gap
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 97%
This rule begins with the buyer's product roadmap rather than a list of companies for sale. The responsible product group identifies missing capabilities, future directions, and the teams or technologies needed to deliver them. Corporate development then evaluates targets against those requirements. A struggling or attractively priced company becomes interesting only when its assets intersect with a real roadmap need. The screen also distinguishes acquiring a business from acquiring a team, product, or technology. A large sales force or standalone operating structure can destroy value when it conflicts with the buyer's suite, distribution model, or existing business. By anchoring target selection in product strategy, the company avoids assembling an accidental software conglomerate and remains disciplined when market conditions produce many apparent bargains.
Origin
Schultz explained that Microsoft's smaller acquisitions are generally driven by product-roadmap holes identified by business groups rather than opportunistic central deal sourcing.
Core principles
- 01Product teams understand their markets better than a central deal team
- 02A low price does not create strategic fit
- 03Acquisition value depends on filling a defined roadmap gap
- 04Teams, products, and technologies may matter more than standalone revenue
How to run it
- 1
Start with the roadmap
Have the product team identify capability gaps and future priorities before discussing targets. Describe the customer or product outcome that the missing capability blocks.
Pro tip Frame the gap independently of any company currently being marketed.
Watch out Starting with an available target invites post hoc strategic rationalization.
- 2
Define the desired asset
Clarify whether the need is for people, technology, a product, a business line, or a combination. Determine what must survive after integration for the deal to work.
Pro tip State the minimum valuable asset in concrete terms.
Watch out Do not assume the target's entire existing business is valuable to the buyer.
- 3
Map targets to the gap
Evaluate candidates based on how directly and quickly they fill the roadmap hole. Let product-domain experts lead the market assessment while corporate development manages the transaction process.
Pro tip Compare acquisition against building internally and partnering.
Watch out A central deal team cannot remain expert in every product micro-market.
- 4
Test operating compatibility
Assess whether the target's sales force, infrastructure, pricing, and standalone business fit the buyer's operating model. Treat incompatible structures as costs rather than automatic assets.
Pro tip Model what will be retained, integrated, or discontinued after closing.
Watch out Revenue can be value destructive if preserving it conflicts with the buyer's suite or strategy.
- 5
Require the intersection
Proceed only when strategic roadmap fit intersects with acceptable price and transaction feasibility. Decline attractive companies that do not satisfy the defined product need.
Pro tip Record the roadmap milestone the acquisition is expected to accelerate.
Watch out A fallen valuation is not itself an acquisition thesis.
In the wild
A startup can no longer finance its growth, but its engineering team and product solve a capability gap already documented by a platform company. The buyer values the specific assets it needs, checks operating compatibility, and acquires the company to accelerate the roadmap.
→ The buyer gains a needed capability without allowing market availability to dictate strategy.
A mature application has revenue and a large sales organization, yet its business model conflicts with the buyer's integrated suite. Because the infrastructure would be costly to preserve and the product fills no roadmap gap, the buyer declines.
→ The buyer avoids acquiring revenue that would become strategically value destructive.
Common mistakes
Buying because the target is available
Companies seeking exits can create urgency, but availability and price do not establish product fit.
Treating all revenue as valuable
A standalone business may conflict with suite economics, sales channels, or integration plans and therefore reduce deal value.
Centralizing all market discovery
A central corporate-development team cannot match the detailed market knowledge of product groups across every micro-category.
Is it for you?
Best for
Product-led technology companies evaluating startups, distressed assets, or smaller acquisition targets.
Not ideal for
Conglomerates deliberately acquiring unrelated businesses for cash flow or overhead synergies.
From the transcript
“most of our acquisitions tend to be much smaller uh and are really driven by those product roadmaps in terms of of where there are…”
“where you have a fallen angel that's on a roadmap, that that's where things get exciting for us.”
“we're typically not looking to acquire businesses. We are typically looking to acquire teams and and products and technologies.”
From the episode
Special: A Conversation with Microsoft's Head of Strategic Investments Brian Schultz
Brian Schultz