Building a Company in Stealth | Travis Kalanick with a16z

Overview

The video is a conversation (framed as an a16z podcast) with Travis Kalanick discussing:

• (1) What happened inside Uber around 2017, and how board dynamics and culture contributed to consequences after his departure.
• (2) How Kalanick’s “stealth” approach later enabled him to build CloudKitchens, plus a broader future vision he calls “atoms” (digitizing the physical world).

---

1) Uber’s 2017 turmoil and “board absence” analysis

The discussion argues that Uber’s 2017 crisis and resulting legal/regulatory troubles were, in part, enabled by a lack of key oversight. Kalanick claims Uber “felt consequences” because Mark and Ben were not on the board, implying the outcome could have been different with their presence.

Key themes include:

• 2017 as an inflection point: Uber’s aggressive competitive behavior triggered investigations and lawsuits.
• Cultural shift with scale: conduct framed as “startup toughness” evolved into a “pirate becomes fleet” mindset—behavior tolerated (or even effective) at smaller scale became unacceptable once Uber scaled.
• Post-departure scrutiny: after Kalanick’s departure, the environment is described as being under intense monitoring (“trying to restrain him”), with multiple legal and oversight processes.

---

2) The emotional, strategic side of capital raising (Uber’s fundraising story)

Kalanick describes leading fundraising for Uber’s Series B.

Notable elements:

• “Auction” dynamics: an interplay with A16z and other investors.
• “Open anchor” negotiation: signaling a flexible starting valuation and allowing the final price to emerge as bids build.

A specific anecdote contrasts:

• a headline valuation reportedly around $375M, with
• a later reduction (down to roughly $210M) after investor pushback,

which is described as creating awkwardness, moments of broken trust, and a costly “deal reversal” feeling.

Takeaway: deal momentum can be won through negotiation dynamics, but outcomes can still shift dramatically depending on alignment and final approval.

---

3) “Stealth mode” as a way to build without external pressure

After Uber, Kalanick emphasizes building privately (“stealth”) to:

• avoid constant negative media attention,
• protect internal focus and execution.

He contrasts:

• reputational risk vs.
• building fundamentals,

arguing that public scrutiny can push decisions toward what external stakeholders approve rather than what internal teams know is correct.

Operational challenges of stealth include:

• cold recruiting and customer outreach under hidden project labeling,
• recruiting artifacts such as recruiters/LinkedIn signatures referencing “stealth project,”
• the ongoing uncertainty of whether secrecy can be maintained.

---

4) CloudKitchens: extending Uber’s playbook to food via real estate + production tech

CloudKitchens is framed as a “return to building” story.

Core claims:

• CloudKitchens connects to the emergence of “dark kitchens” after Uber Eats launched (around 2015).
• Early observations highlighted that commercial kitchens were being used for delivery rather than dine-in.

Kalanick credits a friend/real-estate expert with proposing a multi-tenant model:

• multiple kitchens in one location,
• rented as delivery-only production points.

Growth is described as a mix of:

• real estate expertise,
• acquiring restaurant tenants,
• deploying technology.

---

5) The “food computer” and “atoms” thesis (future of digitizing the physical world)

Kalanick presents a systems view: to make delivery food cheap at “grocery-like” pricing while maintaining quality, you need an “internet food court” combining:

• e-commerce ordering + orchestration,
• warehouses/logistics modeled like Amazon-style infrastructure,
• production capacity (restaurants as manufacturers),
• automation/robotics for production,
• a delivery/courier layer (including autonomous delivery concepts),
• centralized real estate integration.

He frames this with an “atoms computer” analogy:

• software manipulates bits,
• a physical-world system must manipulate atoms through production, storage/real estate, and transport/logistics.

He links the idea to autonomy and robotics, arguing that when automation reaches physical operations, regulation and industrial-scale constraints become the next major frontier.

---

6) “Industrial AI”: a broader platform for automation across physical industries

Beyond food, Kalanick describes a mission called “Industrial AI”, involving:

• building industry-specific “computers” (software + sensors + robotics + mechanisms),
• transforming entire physical transformation industries,
• starting with a “bridgehead” and iterating into more categories (e.g., transport, mining).

He emphasizes that the goal is not humanoid robots “for their own sake,” but practical automation of industrial processes.

Partnership and autonomy references include:

• pursuing autonomy capabilities with teams from Uber’s autonomy-era network,
• acquiring and working with autonomy specialists,
• references to ATG leadership and Anthony Levandowski/Pronto.

In mining (via a Pronto thread), he argues autonomy can improve safety and productivity, and mentions expectations that pilots could lead to “superexponential” growth as they mature into deployments.

---

7) Partnership and capital structure: investing founders who can build scaled companies

A meta-argument: large companies are rare and usually require:

• rare managerial opportunities and
• rare founders.

Kalanick contrasts “myth” narratives of easy origin (e.g., treating Tesla as inevitable) with the reality that scaling often requires unusually capable people.

He also discusses building a unified structure/holdco-like approach for multiple subsidiaries, aiming to:

• reduce managerial burden
• avoid coordination overhead from separately funded companies.

---

8) Cultural doctrine: why secrecy and humility matter; “let creators create”

Key cultural claims include:

• Building from the bottom (“stealth”) supports cultural stability and internal alignment.
• Delegation requires coherent culture plus consistency and responsibility for outcomes (“delegate + consistency”).
• He cites avoiding acquisitions when culture would differ (example given: inability to integrate Lyft due to culture mismatch).

---

9) Future direction criteria (“bridgehead” logic)

Kalanick says expansion is determined by finding a bridgehead—an area that becomes easier to scale.

He uses a “marathon” analogy:

• once things feel easy, push into harder territory again,
• keep generating new challenges and solutions rather than letting the organization plateau.

---

Presenters / contributors (as named in the subtitles)

• Travis Kalanick
• Mark (referenced; not clearly identified beyond “Mark” on the board)
• Ben (referenced; not clearly identified beyond “Ben” on the board)
• David Drummond (Google)
• Yuri (last name not provided)
• Scott Weiss
• Emil Michael
• Eric Mhoffer
• Anthony Lewandowski
• Rob Roy
• “Tony” (full identity not provided)
• “Diego” (last name not provided)
• “Sherwin”
• John O’Farrell