Don't Compete With What You Bought
The classic acquisition killer: building a rival in-house version of the thing you just acquired.
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 92%
Twitter was, in Beykpour's telling, phenomenal at spotting consumer behaviour shifts and putting money behind them — and then botching the execution the same way twice. Both Vine and Periscope were acquired, kept as separate orgs, and then quietly competed with by a parallel in-house team building the same capability on a different stack. The result was two visions, two architectures, and years lost to headbutting.
Origin
Kayvon Beykpour's account of Twitter's Vine and Periscope acquisitions, and the resulting doctrine he applied to Spaces — where he refused to let the company repeat the pattern.
Core principles
- 01Spotting the behaviour shift and buying the company is the easy part; integration is where the value is won or lost.
- 02The moment you stand up a parallel internal team on the same capability, you have created two competing product visions inside one company.
- 03Competing internally guarantees you cannot make good on the vision that justified the acquisition.
- 04The internal duplicate usually starts for a sympathetic reason — the core org feels it can't get things done — and that reason is never worth the cost.
- 05The failure mode is a leadership vacuum: without a unified, opinionated decision-maker at the top, conflicting bets get funded simultaneously.
- 06Fixing it later is possible but expensive: persistence, impatience and table pounding, plus a long technical re-integration.
How to run it
- 1
Define one capability owner at acquisition time
Before the deal closes, name the single team and single stack that owns the capability across its whole spectrum. Twitter never did this for video, and ended up with UGC live (Periscope) and premium live (Thursday Night Football / NFL) on entirely separate teams, products and architectures.
Watch out 'We'll figure out integration later' is how you end up with two UXes for the same behaviour.
- 2
Pour gasoline instead of building a rival
Integrate the acquisition holistically into the core product and amplify it. Twitter instead built a native Twitter video stack — uploads plus a professional tool called Media Studio for publishers like ESPN — as a separate team fundamentally competing with Vine.
Pro tip Ask the direct question: is any internal team's roadmap now a substitute for the thing we just paid for?
- 3
Insist on unified, opinionated leadership over the capability
Beykpour's diagnosis of the root cause: without unified leadership you make decisions that conflict with one another. There must be a highly opinionated person at the top who prevents the mess from ever forming.
Watch out In a functional org with no tie-breaker, this failure is the default outcome, not the exception.
- 4
If it has already happened, force the re-merge
It took persistence, impatience and table pounding to eventually merge Twitter's UGC and premium live video into one stack and one experience. Do it — but count the cost honestly: it wastes time, resources and produces a subpar product experience in the meantime.
Pro tip The end state is worth naming: ESPN going live from Wimbledon and a user going live from an iPhone on the same stack and the same UX.
- 5
Carry the scar into the next bet
Having botched Vine and Periscope, Beykpour refused to repeat it with audio: Spaces was made the number one priority of the company, above every other project, with a single team and radical execution.
Pro tip Use the previous botch as internal narrative fuel — 'we are not doing this to ourselves again' is a powerful alignment device.
In the wild
Twitter had the insight on short-form video and bought Vine — then kept it as a separate org in a separate New York office while building its own native Twitter video stack (uploads, plus Media Studio for publishers like ESPN) with a different team on a different stack. Two visions for short-form video ran in parallel.
→ Vine faded away and was shut down; the short-form video category was ceded entirely, later to be won by TikTok.
Periscope owned UGC live video from the phone. Twitter then entered premium live video with the Thursday Night Football NFL rights, staffed by a separate team, on a separate stack, with a totally different UX — while pouring investment into marketing Twitter as the place to watch the NFL, in parallel to a burgeoning UGC ecosystem it barely supported.
→ The same mistake, repeated. It was eventually fixed via persistence and table pounding into a single stack — but only after a tremendous amount of time, resources and politics were wasted.
Common mistakes
Standing up an internal team because the core org 'can't get things done'
The calcification that makes leaders spin up a fresh internal team is real — but the cure creates a competing vision that guarantees the acquisition thesis fails.
Segmenting one capability into premium and UGC tracks
Twitter split live video into professional and user-generated with separate teams, stacks and UX. The user does not experience two live videos; they experience one incoherent product.
Great insight, no follow-through
Twitter spotted Vine, Periscope and even Instagram before Facebook did. Spotting the behaviour change is not the moat — execution and integration are.
Is it for you?
Best for
Corp-dev, product and engineering leaders integrating an acquired consumer product into a large platform, especially when the core org is slow and tempted to build its own version
Not ideal for
Pure financial or talent acquisitions where the acquired product is being deliberately sunset and no capability overlap exists
From the transcript
“they had the Insight around short front video they bought Vine they then competed with Vine internally”
“you're not going to be able to make good on the vision of buying the company and integrating it in all the right ways if…”
“guess what happened we competed internally um rather than um have a cohesive Technical and product vision”
From the episode
Twitter’s former Head of Product opens up: being fired, meeting Elon, changing stagnant culture, building consumer product, more
Kayvon Beykpour