Acquisition Target Execution Scorecard
Select the target that combines strategic coverage, leadership, and executable integration.
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 6
- Confidence
- 97%
This scorecard evaluates acquisition candidates against the acquirer's intended end state rather than using price or current product quality alone. Define the customer workflow and complete suite the combined company must deliver, then score each candidate on strategic alignment, category position, product strengths, and missing capabilities. Convert every missing capability into execution work, including additional acquisitions, integrations, teams, and sales enablement. A cheaper target can become the riskier choice if it requires several follow-on deals, while a medium-sized leader may contain enough people, expertise, and market presence to transfer its selling motion into the acquirer. The framework therefore treats organizational critical mass and integration probability as part of valuation. It also preserves a fallback candidate until closing risk has passed, preventing dependence on a single negotiation.
Origin
HP applied this logic while evaluating Opsware and BladeLogic. Opsware had broader suite coverage and market leadership, while BladeLogic had stronger usability but would have required HP to complete three additional acquisitions.
Core principles
- 01Buy against the future product strategy, not merely today's feature comparison.
- 02Market leadership can outweigh a narrower usability advantage.
- 03Count the acquisitions required to complete the strategic product.
- 04Integration complexity is part of acquisition cost.
- 05Maintain a credible fallback target until the preferred deal is secure.
How to run it
- 1
Define the Target State
Describe the end-to-end customer outcome and product suite the acquisition strategy must produce. Avoid reducing the decision to a comparison of one component product.
Pro tip Express the target state through the buyer's complete workflow.
Watch out A narrow feature comparison can favor a candidate that cannot support the broader strategy.
- 2
Score Strategic Coverage
Map each candidate's existing products, acquired technologies, and partnerships against the target state. Distinguish owned capabilities from dependencies on partners.
Pro tip Give extra weight to capabilities that are difficult to integrate later.
Watch out Partnership coverage may not provide the control or cohesion of owned technology.
- 3
Separate Position From Product Quality
Evaluate market share, sales momentum, suite breadth, scalability, and usability independently. A candidate may lead the market without having the strongest component product.
Pro tip Investigate why each candidate wins and loses deals.
Watch out Assuming that the most usable product is automatically the best acquisition can ignore channel and category dynamics.
- 4
Calculate Completion Complexity
Count the follow-on acquisitions and integrations required after buying each candidate. Estimate the probability that the full sequence can be completed successfully.
Pro tip Compare complete strategic programs, not standalone purchase prices.
Watch out Several small transactions may carry more cumulative risk than one expensive acquisition.
- 5
Assess Critical Mass
Determine whether the target contains enough people, customer knowledge, sales expertise, and product leadership to influence the acquirer. Consider how that expertise will be transferred into the larger organization.
Pro tip Favor targets capable of teaching the acquiring channel how the category is sold.
Watch out Small technology tuck-ins can disappear before their expertise spreads.
- 6
Choose a Preferred and Fallback Target
Rank the candidate with the strongest combination of alignment, leadership, and executable integration. Continue diligence on a viable alternative until the preferred transaction is sufficiently secure.
Pro tip Make the premium paid for reduced execution risk explicit.
Watch out Ending discussions with alternatives too early weakens both resilience and negotiating leverage.
In the wild
HP wanted to automate service deployment across desktops, servers, networks, storage, and related workflows. Opsware was the market leader and owned a broader data-center automation suite, although BladeLogic's server product had better usability. Buying BladeLogic would have required three additional acquisitions to complete HP's strategy. HP judged one larger integration more executable than a cheaper four-company sequence and retained BladeLogic as a fallback while pursuing Opsware.
→ HP selected Opsware and paid a premium for strategic completeness, market leadership, and lower program-level execution risk.
A platform company compares a polished component specialist with a broader suite leader. The specialist costs less but leaves gaps that require separate workflow, analytics, and security acquisitions. Applying the scorecard reveals that the apparent bargain creates four integration programs and no unified sales team. The company chooses the suite leader and funds targeted usability improvements after closing.
→ The acquirer obtains a coherent platform and avoids a fragile chain of follow-on deals.
Common mistakes
Buying the Best Demo
Superior usability in one product can distract from incomplete strategic coverage. Evaluate the whole target state and the reasons candidates win enterprise deals.
Ignoring Follow-On Deals
A low purchase price is misleading when the target requires several additional acquisitions. Completion complexity must be included in the decision.
Undervaluing Critical Mass
A small technology team may not have enough organizational weight to transfer its knowledge into a large acquirer. People and selling expertise are part of the asset.
Is it for you?
Best for
It is best for companies comparing multiple acquisition candidates within an established strategic category.
Not ideal for
It is not ideal when the company has not yet defined the customer outcome or portfolio strategy the acquisition must serve.
From the transcript
“And our theory was actually slightly bigger than that, is we felt that what customers wanted to do was deploy services end to end-to-end.”
“And we felt that the risk, even though if it would have been cheaper, we didn't, we thought that actually the likelihood of our ability…”
“We felt that we were much more likely to be able to execute that successfully than Blade Logic plus three others.”
From the episode
Opsware (with Michel Feaster)
Michel Feaster