Try-Before-You-Buy Team Acquisition
Prove a team's performance in partnership before bringing it inside the company
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 6
- Confidence
- 91%
Instead of acquiring a company or team after conventional due diligence alone, begin with a substantial operating partnership on a real product. Use that period to observe technical quality, delivery reliability, collaboration, leadership, and the assets that actually drive performance. If ownership later becomes strategically necessary, acquire only the proven people, intellectual-property rights, and operational capabilities required to close the capability gap. This makes the transaction narrower and gives the buyer evidence about how the team performs with its own employees. The approach reduces product and valuation risk, but it does not eliminate integration risk: employees may still struggle when reporting lines, incentives, identity, and organizational culture change after the deal.
Origin
The hosts describe Google's years of Pixel collaboration with HTC as a methodical, risk-mitigated way to evaluate the hardware team before acquiring approximately half of HTC's employees.
Core principles
- 01Observed collaboration is stronger evidence than presentation-based diligence
- 02Acquire only the capabilities required by the strategy
- 03A prior working relationship reduces execution uncertainty
- 04Smaller scoped transactions limit financial and integration risk
How to run it
- 1
Define the capability gap
Specify what the company cannot reliably build or operate today and why that capability is strategically important.
Pro tip Describe the gap in observable outputs rather than broad labels such as hardware expertise.
Watch out Do not acquire a team merely because its domain appears strategically fashionable.
- 2
Run a real partnership
Engage the prospective team on a consequential product with shared milestones and clear responsibilities.
Pro tip Choose work representative of the operating conditions expected after acquisition.
Watch out A low-stakes pilot may hide the coordination problems that appear under pressure.
- 3
Collect operating evidence
Evaluate quality, speed, communication, leadership, supply-chain execution, and how well the teams resolve disagreements.
Pro tip Identify which specific people, processes, relationships, and rights produced the result.
Watch out Do not attribute success to the entire organization when only a small group drove it.
- 4
Compare ownership with contracting
Determine whether acquisition materially improves coordination, incentives, speed, control, or access compared with extending the partnership.
Pro tip Model both the acquisition cost and the future payments avoided or accelerated.
Watch out Ownership adds integration costs that an arm's-length contract does not.
- 5
Acquire the minimum viable scope
Structure the transaction around the proven team and essential assets rather than automatically buying the whole company.
Pro tip Secure the intellectual-property access and operational relationships needed for continuity.
Watch out An overly narrow scope can omit hidden dependencies that enabled the team's performance.
- 6
Integrate and retain
Clarify roles, incentives, decision rights, cultural expectations, and career paths before the team enters the buyer's organization.
Pro tip Preserve effective operating routines while gradually removing duplicated boundaries.
Watch out Prior collaboration does not guarantee successful cultural integration.
In the wild
Google worked directly with HTC personnel on the Pixel smartphone line before agreeing to bring the relevant team into Google's hardware organization. The prior collaboration supplied practical evidence that the team could build a well-regarded product with Google.
→ Google acquired a focused, already-tested capability while avoiding the cost and complexity of buying all of HTC.
In a hypothetical application, a software company contracts a specialist infrastructure team to migrate one major service. It records reliability, incident response, documentation quality, and cooperation with internal engineers before considering an acquisition.
→ The buyer bases its decision on observed execution and scopes any transaction to the team and tooling that produced the results.
Common mistakes
Mistaking product success for integration proof
A team can excel as an external partner yet struggle after its incentives, authority, and culture change inside the buyer.
Buying unnecessary organizational baggage
Purchasing the entire company when only one proven capability is needed increases cost and integration complexity.
Ignoring hidden dependencies
The visible team may rely on supplier relationships, support functions, facilities, or intellectual property that must also be secured.
Is it for you?
Best for
It is best for companies that already collaborate closely with a specialist team and need deeper control over a strategically critical capability.
Not ideal for
It is not ideal when partnership work cannot realistically reveal post-acquisition cultural, retention, or operating risks.
From the transcript
“we've been burned once, and now we're going to be very methodical about this approach here.”
“it's really only exactly what they needed, and they spent, you know, years first engaging with this team, doing a try before you buy.”
“Um I mean, that this is a uh highly calculated, highly risk mitigated um transaction by by Google.”
From the episode
HTC, Google and the Future of Mobile