The Company-Inside-a-Company Incubation Playbook
Spin a 0-to-1 business inside a mature company by ring-fencing it completely from the core
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 92%
A repeatable structure for launching a new high-growth business inside an established company without the core org smothering it. The core idea is total separation: dedicated people with a single job, a separate operating rhythm, founder-level attention, and compensation tied to the new venture's hurdles. Garrett used it to take Handshake AI from $0 to $50M ARR in four months on top of Handshake's decade-old, $200M business.
Origin
Developed by Garrett Lord while launching Handshake AI inside Handshake in 2025; he frames it as 'running back a new company inside of a company for the second time.'
Core principles
- 01A mature business runs on cadence and checks-and-balances; a 0-to-1 needs speed and single-owner clarity — the two operating models fight unless physically and organizationally separated
- 02People incubating the new business must have exactly one job and no legacy responsibilities that let them say 'I can't prioritize that this week'
- 03The founder/CEO must be in founder mode on the new thing (80%+ of attention), not delegate it to a lieutenant
- 04Compensation and expectations should match an early-stage company (equity-like hurdles, intense pace), not the parent's norms
- 05Name the chaos out loud so recruits self-select into it
How to run it
- 1
Ring-fence a fully separate org
Stand up separate engineering, design, operations, finance, recruiting, onboarding, and all-hands for the new business. Sit them in a different part of the office. Keep only a few deliberate integration points with the core.
Pro tip Give the new unit its own separate all-hands and onboarding so its culture forms independently from day one.
Watch out Deep coupling to the core too early lets existing priorities and politics slow the new business down.
- 2
Assign single-job owners with no legacy duties
Move people into the new org so they have one job only and zero responsibilities in the existing business. Make it extremely clear who the directly-responsible individual (DRI) is for each area.
Pro tip Pick the DRI by who is most capable of driving the initiative, regardless of their function or title.
Watch out If someone keeps a foot in the core business, they will default to 'I already have a set of priorities' and starve the new venture.
- 3
Put the CEO in founder mode on it
The CEO personally leads the new business, with most direct reports reporting to them, while trusted executives run the core. Aim to be 'another smart guy in the room,' not a distant sponsor.
Pro tip Hand the mature core business to a strong executive team you trust so you can spend 80%+ of your time on the new bet.
- 4
Staff with ambiguity-comfortable operators
Hire people who have started companies or only worked at early-stage startups, plus parachute your most entrepreneurial senior/staff/principal engineers over from the core when scaling starts to topple.
Pro tip Ask your best core-business people directly to join — and accept that some will say no to the 2am pace; the honest ask still surfaces the right people.
Watch out Generalists comfortable only in mature-company processes will struggle with the chaos and slow you down.
- 5
Set startup expectations, comp, and cadence explicitly
State up front that it's a 24/7, insane-pace, weekends-included job. Tie compensation to hurdles in the new business so people feel like owners. Run a data/metrics operating cadence (weekly/monthly/quarterly) from the earliest stage.
Pro tip Own the 'this is going to be chaotic' narrative publicly at the core company's all-hands so nobody is blindsided.
Watch out Handshake's core business resisted a metrics cadence for years — the new unit adopted rigor early precisely because ambiguity is higher when moving fast.
In the wild
Garrett built a separate org with its own engineering, design, finance, and recruiting, moved single-job owners in, sat them in a separate part of the office, ran a metrics cadence, and personally led it while his executive team ran the $200M core. Headcount went from 4-5 people to 75+, with 12 starting in a single week.
→ $0 to $50M ARR in four months, on track to blow past $100M in year one — approaching the run-rate of a business that took 10 years to build.
Common mistakes
Delegating the 0-to-1 to a lieutenant
Garrett went into founder mode himself. Treating a genuine new-company bet as a side project owned by a mid-level manager denies it the speed and decision authority it needs.
Letting people keep core-business duties
Split attention means the new work loses every prioritization contest. Only fully reassigned, single-job owners move fast enough.
Importing the mature company's operating model
The cadence, checks-and-balances, and comp norms of a 10-year-old business will strangle a 0-to-1. Separation of process is as important as separation of people.
Is it for you?
Best for
Founders/CEOs of an established, resourced company who spot a fast-moving new opportunity adjacent to their existing asset and can commit personal founder-level attention
Not ideal for
Small teams without the headcount to fully staff a separate org, or leaders unwilling to step away from running the core business
From the transcript
“it's separate and everything like separate engineering team separate design team separate accounts and operations team separate finance team like early on everything was separate…”
“everyone did not have any responsibilities in the existing part of the business it was extremely clear who was like the directly responsible individual”
“we sat in a separate part of the office”
“the compensation was also different too and based on like hurdles in this new business so people felt like owners”
“We pick the best person who's most capable of driving an initiative forward, regardless of the function to be the DRRi”
“running back a new company inside of a company for the second time over again”
From the episode
Inside the expert network training every frontier AI model
Garrett Lord (Handshake CEO)