Separate the Team, Bundle the Customer Experience
Preserve the acquired team while combining distribution and customer value.
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 97%
Keep the acquired development team and its working culture sufficiently independent to preserve the product insight that justified the purchase. Instead of immediately centralizing decisions, supply the resources the team previously lacked: capital, industry credibility, platform guidance, distribution, and access to customers. Integration should first occur at the customer layer, where products can be packaged, discovered, purchased, or used together. Deeper technical integration can follow once the combined customer proposition is proven. The mechanism separates two questions that acquirers often confuse: how the product should be built and how the portfolio should be sold. PowerPoint benefited because Microsoft initially lacked the machinery to control its distant Silicon Valley unit, yet could still finance it and eventually bundle it with Word and Excel.
Origin
Extracted from Acquired's analysis of Microsoft's purchase of Forethought and its decision to preserve the Silicon Valley PowerPoint team while eventually incorporating the product into Microsoft Office.
Core principles
- 01Protect the capabilities that made the acquisition valuable.
- 02Provide resources without imposing unnecessary control.
- 03Keep development autonomy separate from customer-facing integration.
- 04Bundle products only where the combination improves customer value.
- 05Integrate gradually rather than shipping the acquiring company's org chart.
How to run it
- 1
Protect the Product Engine
Identify the people, practices, and decision rights responsible for the acquired product's success. Preserve those elements rather than automatically replacing them with the buyer's standard processes.
Pro tip Ask which constraints or unusual practices enabled the team to outperform larger competitors.
Watch out Nominal autonomy is ineffective if every meaningful decision still requires headquarters approval.
- 2
Supply Missing Leverage
Give the team the capital, platform knowledge, credibility, and distribution it could not obtain alone. Focus support on removing constraints rather than directing routine product work.
Pro tip Assign experienced executives as advisers without placing them inside every operating decision.
Watch out Resources can become control mechanisms if they arrive with excessive reporting and coordination costs.
- 3
Integrate the Customer Surface
Connect the acquired product to the buyer's sales channels, identity systems, discovery mechanisms, or complementary products. Make the combined offering easier and more valuable for customers.
Pro tip Begin with reversible packaging and distribution experiments before forcing deep technical convergence.
Watch out Do not bundle merely to hide a weak product or restrict customer choice.
- 4
Converge Selectively
Standardize shared components and product conventions only where doing so improves usability, reliability, or portfolio economics. Allow differences that remain strategically useful.
Pro tip Use customer friction, not organizational neatness, to prioritize integration work.
Watch out Premature convergence can erase the acquired team's speed and distinctive expertise.
- 5
Reassess Autonomy Over Time
Review whether continued separation or additional integration now produces more value. Change the boundary as the market, team, and product portfolio mature.
Pro tip Evaluate product velocity, retention, cross-product usage, and employee attrition together.
Watch out Temporary autonomy should not become permanent neglect.
In the wild
After buying Forethought, Microsoft allowed the PowerPoint operation to remain in Silicon Valley as its own graphics business unit. The team retained substantial development independence while receiving Microsoft's money, industry influence, Windows guidance, and eventually the distribution power of the Office bundle.
→ PowerPoint developed into a dominant presentation product and an essential component of Microsoft Office.
A large software company acquires a specialist analytics product. It leaves the product and engineering organization intact, adds single sign-on and marketplace discovery, and offers the product alongside its existing suite before attempting a shared technical architecture.
→ The acquired team maintains release velocity while the buyer increases adoption among existing customers.
Common mistakes
Standardizing Everything Immediately
Forcing the acquired team onto every process and platform at once can remove the autonomy and speed that made it valuable.
Confusing Separation With Neglect
An autonomous team still needs capital, executive access, platform guidance, and measurable strategic goals.
Shipping the Org Chart
Customer workflows should determine product integration; internal reporting lines should not dictate awkward product boundaries.
Is it for you?
Best for
It is best for acquisitions where a strong standalone product can benefit from the buyer's resources, platform, or customer base.
Not ideal for
It is not ideal when immediate technical consolidation is required to address security, compliance, or product failure.
From the transcript
“Avoid smothering. So provide the resources that are helpful, don't trample and then figure out when bundling makes sense.”
“keep the development team separate, pour resources on, allow sort of uh separate cultures at least for a time, but figure out how to bundle…”
“PowerPoint has been so very successful after its acquisition, and mostly as far as I can see, because Microsoft in 1987 lacked any technology or…”
From the episode
PowerPoint