Jeff Lawson – How to Build a Platform - [Invest Like the Best, EP.158]

Episode Summary

Executive Summary: Jeff Lawson argues Twilio succeeded by treating APIs as products and listening to developers, not by forcing software into old app-centric or build-vs-buy frameworks. The conversation explores platform economics, the shift to software-defined businesses, and how Twilio’s culture—shaped by values, rituals, and customer proximity—helps it innovate and scale.

Main Topics: Draw the owl: shipping amid ambiguity (Priority: 5/5): Twilio’s ethos is to figure it out, ship it, and iterate when no playbook exists. APIs as product, not feature (Priority: 5/5): Lawson explains APIs as developer building blocks that became core infrastructure. The rise of platform businesses (Priority: 5/5): AWS, Stripe, and Twilio reflect a new software supply chain for digital companies. Build or die (Priority: 5/5): Software is now a competitive edge, so companies must build digital experiences or risk losing. Customer-led product development (Priority: 4/5): Twilio learns from how customers use the platform and turns those patterns into products like Flex. Culture as a system (Priority: 4/5): Twilio codifies identity through heroes, rituals, symbols, and values to align behavior. Ask your developer (Priority: 5/5): Businesses should give developers problems to solve, not just tasks to execute.

Key Arguments: APIs became products because developers needed reusable infrastructure, not one-off app features. Conventional wisdom said developers weren't customers; Twilio proved they were through early demand. Every company is becoming a software company, creating demand for platform supply chains. Build vs. buy is outdated in digital markets; if you don't build, you may die competitively. Platforms reveal unmet needs by observing customer behavior across many use cases. Twilio Flex emerged from repeated customer demand for a customizable cloud contact center. Great software teams should share business problems with developers, not throw specs over the wall. Culture works when values are concrete enough to guide decisions in daily language.

Data Points: Twilio valuation: $15 billion - Patrick introduces Jeff Lawson as founder and CEO of Twilio. Twilio annual revenue: a billion dollars of revenue - Lawson notes Twilio crossed this threshold the prior year. Early Twilio company size: 10 people - He recalls the 'draw the owl' meme circulating when the company was very small. First values workshop: about 15 people - Lawson describes the initial effort to articulate Twilio’s values in 2011. ING legacy contact centers: 17 legacy contact centers - ING needed to replace many on-prem systems with a Twilio-built contact center. Ing scale of dev team: 50 developers - Lawson references a customer on a multi-year roadmap to reinvent its contact center. Hackathon duration: 24 or 48 hours - He cites hackathons as proof developers can build creatively in short bursts. Hamptons retreat length: about nine months - Lawson spent this long brainstorming his next company after the dot-com crash.

Pivotal Quotes: "draw the owl" — Jeff Lawson: Describing Twilio’s core value of figuring things out without a playbook. "build versus die" — Jeff Lawson: His reframing of the old build-versus-buy debate in software-driven markets. "Ask your developer if Twilio is right for you" — Jeff Lawson: The billboard slogan that became a broader argument for involving developers in business decisions.

Implications: The unresolved challenge is organizational: companies must redesign incentives and team structures so developers stay close to customers and business outcomes.