Acquisition Evaluation Scorecard
Evaluate an acquisition from its history through its strategic outcome
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 98%
The Acquisition Evaluation Scorecard moves from evidence to judgment through a consistent sequence. First, reconstruct what happened, including the target’s condition, deal timing, price, and subsequent milestones. Next, classify the deal according to what the buyer principally obtained, such as people, technology, product, business line, or assets. Build a counterfactual describing the target and buyer without the transaction, then identify broader strategic or technological themes. Finally, assign a grade that weighs purchase price, execution, strategic value, and opportunity cost. Keeping these stages separate reduces hindsight bias: an unfinished technology can become an extraordinary asset through later execution, while an attractive product can still become a poor acquisition if integration destroys its value.
Origin
Ben Gilbert outlines Acquired's recurring review format while introducing the show's episode on Google's acquisition of Android.
Core principles
- 01Establish the facts before judging the deal
- 02Classify what the buyer actually acquired
- 03Test the outcome against a credible counterfactual
- 04Separate purchase quality from subsequent execution
- 05Translate qualitative evidence into an explicit grade
How to run it
- 1
Reconstruct the History
Build a dated account of the target, transaction, market context, and important post-acquisition developments. Distinguish documented facts from estimates or retrospective claims.
Pro tip Use contemporary reporting and litigation disclosures to recover facts that were not public when the deal closed.
Watch out Do not let the eventual outcome distort what was knowable at the time.
- 2
Classify the Acquisition
Decide whether the buyer primarily acquired people, technology, a product, a business line, or an asset. Classify the deal at the time of purchase rather than by what it eventually became.
Pro tip Ask what could actually have been transferred or deployed on closing day.
Watch out A successful evolution after closing does not retroactively make an unfinished technology a finished product.
- 3
Build the Counterfactual
Assess what probably would have happened to both companies without the deal. Consider whether the buyer could and would have built the capability internally and whether another buyer could have acquired the target.
Pro tip Separate technical feasibility from the organizational willingness to pursue the project.
Watch out Avoid assuming that the acquired startup could have achieved the same scale independently.
- 4
Extract Strategic Themes
Identify reusable lessons about distribution, competition, platform control, integration, or market timing. Tie each theme to concrete evidence from the case.
Pro tip Look for mechanisms that apply beyond the companies being studied.
Watch out Do not treat a colorful anecdote as a general strategic law.
- 5
Assign and Defend a Grade
Grade the deal by comparing its cost with financial, strategic, and defensive outcomes. Explain whether value came from the original asset, the buyer's execution, or both.
Pro tip Name the strongest comparable deal before deciding whether the acquisition deserves the highest grade.
Watch out Do not count avoided costs and generated revenue as if they were the same kind of value.
In the wild
Google bought a small team developing an unfinished Linux-based mobile operating system before it had shipped a phone. The hosts reject the product category because Android lacked a complete market-ready product and independent strategy at closing, classifying it instead as a technology acquisition that later evolved into a product, business line, and defensive asset.
→ The time-specific classification produces a more precise account of what Google bought and what Google subsequently built.
A software company buys a five-person analytics startup with a working prototype but no customers. An analyst reconstructs the timeline, classifies the deal as technology plus talent, tests whether the buyer could have built it internally, identifies its role in customer retention, and grades it only after comparing integration costs with retained revenue.
→ The analyst distinguishes the quality of the original purchase from the quality of later execution.
Common mistakes
Classifying with hindsight
Judging the target by what it became obscures the capability and risk transferred when the deal actually closed.
Skipping the counterfactual
A large outcome does not prove the acquisition was necessary if the buyer could and would have created the same result internally.
Grading only financial returns
Defensive control, avoided platform taxes, and preserved customer access may be strategically valuable even when the acquired product is not a standalone profit center.
Is it for you?
Best for
It is best for investors, operators, and analysts reviewing technology acquisitions after meaningful evidence has accumulated.
Not ideal for
It is not ideal when deal terms, strategic intent, and post-acquisition outcomes remain almost entirely unknown.
From the transcript
“then we go into acquisition history and facts where David takes us through What actually happened.”
“then we get into the acquisition category where we decide if it's a people acquisition, technology, product, business line.”
“then we talk about what would have happened otherwise, uh, what tech themes this illustrates for us, we then formally give the grade of our…”
From the episode
Android