Hard truths about building in the AI era | Keith Rabois (Khosla Ventures)

Key points

• 'The team you build is the company you build' (Vinod Khosla). Everything else — market, product, tech — is downstream of talent density. PayPal's success and mafia came from Peter Thiel and Max Levchin marshalling an unusually dense network.
• Undiscovered-talent thesis: don't compete for known stars. Find people the monolithic hiring black-boxes (Meta, Google, Coinbase etc.) can't process correctly. Net effect usually skews younger — younger candidates have fewer data points for bureaucratic screens to index on.
• Ruthless referencing: Tony Xu runs 20 references on every senior hire at DoorDash. David Sze's Greylock rule: 'you haven't finished referencing until you hit a negative.' Right-question framing is a tactic — asking 'was Max a good employee?' killed deals that 'is Max capable of being a world-class entrepreneur?' would have won.
• Hiring feedback loop: ask yourself 30 days after any hire if you'd make the same decision. Research shows that 30-day call is as accurate as 1-2 year hindsight.
• Barrels and Ammunition: companies get frustrated post-funding because they hire a lot without expanding the number of people who can drive an initiative end-to-end ('barrels'). Stacking 'ammunition' behind the same few barrels = coordination tax, not output.
• 'The relentless application of force' (Mike Moritz on the CEO archetype). The better a company performs, the more complacency creeps in — the CEO's single highest-leverage role is offsetting it. Network effects are rare; most businesses won't run on autopilot.
• Counterintuitive signal: morale falls when talented people are coasting. Great operators get energy from creating. Brian Chesky's 'pedal to the metal no matter what' works because those people want to build.
• Coach-mode inversion: be most critical when the company is winning (errors compound quietly), most supportive when it's struggling (criticism doesn't help a founder already in pain).
• **The PM role as classically defined makes no sense going forward.** Peter Fenton's argument (which Rabois endorses): year-long roadmaps are incoherent when what was impossible in November is shippable in March. You need an organisation that rewrites the roadmap weekly.
• Every functional role — PM, designer, engineer — converges on 'chef-mode': what are we making, why, who's it for, how do we differentiate. Alfred Lin's chef analogy: the head chef at a prime restaurant isn't cooking the dish, they're setting segment, pricing, branding, differentiation. The commercial and creative instincts become the scarce skill.
• Design and code are merging. Unclear whether code becomes design or design auto-translates to code — both bets running. Design's open-role count has been flat for three years while engineering output per person explodes.
• In the best AI-native orgs, the #1 token consumer is the CMO — not an engineering team. Executives with commercial acumen who can ship work directly (landing pages, campaigns, analytics) instead of waiting on deputies are the new archetype. A Ramp engineering director ships as much code as an IC while managing 20, using AI as his second team.
• Ergonomic footnote: Keith has used only an iPad since September 2010 (Jack Dorsey's influence at Square). Tracks the 'coding from phones' trend (Boris Cherny, Simon Willison) as a leading indicator.

Notable quotes

Themes

• Talent density as the only sustainable moat
• Undiscovered talent and why younger is often better
• The end of the classical PM and the convergence of roles
• CMOs as AI-native executives