← Back to list
Colossus (Invest Like the Best / Business Breakdowns)Podcast3 Mar 2020Source: investlikethebest.libsyn.comHost: Patrick O'Shaughnessy

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

In plain words

This piece features Twilio founder Jeff Lawson on building a platform company. He argues that in the digital age, companies must build their own software or die. He favors the platform model because it lets you spot new opportunities by watching how customers use your APIs. Key holdings mentioned: Twilio (his company, revenue over $1B in 2019), AWS (called the fastest-growing enterprise software company ever), and Stripe (a payment API platform). He also criticizes traditional 'agile' development for killing creativity and suggests sharing problems with developers instead of just assigning tasks.

AI SummaryAI-generated · may contain errors · verify against the original

At a Glance

Jeff Lawson, founder and CEO of Twilio, delves into the strategic value and practical methods of building platform companies. The core thesis of this episode is: In the digital economy era of "build or die," the platform model (empowering developers via APIs) holds greater advantages than traditional product companies, with success hinging on cultural shaping and customer insight. The most impactful judgment is: Jeff Lawson argues that traditional "agile development" has turned software creation into an "industrial assembly line," stifling developer creativity; the true approach should be "sharing problems, not assigning tasks," allowing developers to participate in problem definition rather than merely executing instructions.

Platform Thinking: From "Build vs. Buy" to "Build vs. Die"

Jeff Lawson points out that in the past, when faced with software needs, companies would conduct a "build vs. buy" analysis, believing non-core functions should be outsourced. But today, the digital interface has become the primary way companies interact with customers, and software capabilities directly determine customer experience and competitiveness. Therefore, companies must view software as a core competitive advantage, or they will be eliminated by digital disruptors or successfully transformed peers.

  • Historical Context: Traditional enterprises viewed IT as a cost center and tended to outsource. However, with the rise of mobile internet, customers interact with banks, retailers, and other businesses through apps, making software experience the focal point of competition.
  • Mechanism Breakdown: Lawson uses the banking industry as an example, noting that "challenger banks" like N26 and Bunk are essentially "software companies with a banking license," winning customers through superior app experiences. Traditional banks like ING Belgium responded by undergoing a company-wide "agile" transformation, where not only software development teams but even branch offices operated in two-week sprints with autonomous small teams.
  • Data Chain: Twilio crossed the $1 billion revenue threshold in 2019; AWS is described as "the fastest-growing enterprise software company in history."

The Advantage of Platforms: Discovering "Hotspots" from Customer Behavior

As a platform, Twilio can identify new market opportunities by observing how customers use its APIs, something traditional product companies find difficult. Product companies pre-assume customer problems, while platforms allow customers to build anything with modular APIs, thereby revealing unmet deep-seated needs.

  • Mechanism Breakdown: Lawson describes how Twilio discovered the structural opportunity in the "contact center" market. Many customers (like ING) did not purchase off-the-shelf contact center solutions but chose to build their own on Twilio's APIs. By asking "why," Twilio found the existing contact center market was "fragmented," with customers trapped in legacy on-premise systems for years.
  • Data Chain: Based on this insight, Twilio launched Twilio Flex—a "contact center application platform." It allows customers to launch a contact center in the cloud within minutes, while providing SDKs (Software Development Kits) for developers to perform deep customization.
  • Deduction: Platform companies should actively track customers' "non-standard" usage patterns; these "hotspots" often signal new product directions. Falsification condition: If the "non-standard" applications built by customers on the platform fail to form a scalable common need, the company should not blindly launch a new product.

Cultural Shaping: Heroes, Rituals, and Symbols

Jeff Lawson believes that company culture is a "tribal sense of belonging" that must be consciously shaped through three elements: "heroes, rituals, and symbols." Values are the "handles" of culture; they must be short, memorable, and naturally quotable by employees in daily decision-making.

  • Mechanism Breakdown:
  • Heroes: Role models the company promotes. Twilio celebrates customers who successfully build innovative applications on its platform (e.g., the CTO of Nike, the team at ING) as heroes to inspire employees.
  • Rituals: Repetitive collective activities. Twilio has traditions like "Thursday all-hands with bagels" and "Wednesday dinners." These seemingly small rituals reinforce a sense of belonging.
  • Symbols: Visual elements representing values. Twilio's values include "Draw the Owl" (figure it out, get it done, and iterate), "No Shenanigans," and "Wear the Customer's Shoes." The latter is visualized by hanging shoes gifted by customers around the office, sparking curiosity and constantly reminding employees.
  • Data Chain: Lawson mentions that he started bringing bagels when the company had only 6 people, and it has now grown to thousands of bagels.
  • Deduction: Culture is not a slogan on the wall but is continuously reinforced through daily behaviors, stories, and the physical environment. Falsification condition: If employees never reference values in their decisions (e.g., "this feels like shenanigans"), it indicates a failure in cultural shaping.

Developer First: Share Problems, Not Assign Tasks

Jeff Lawson strongly criticizes traditional "agile development" for treating developers like "factory workers." He argues that coding is creative, and the best developers are "creative problem solvers." Companies should "ask your developers," sharing business challenges with them instead of issuing specific instructions.

  • Mechanism Breakdown: Lawson points out that many companies have product managers write detailed PRDs (Product Requirement Documents) and then "throw them over the wall" for developers to execute. This stifles developer creativity. He suggests setting goals for developers (e.g., "increase website conversion by 30%") and letting them participate in designing the solution.
  • Data Chain: Lawson uses "hackathons" as an example, noting that developers can build amazing prototypes in 24-48 hours, yet companies only allow them to do so for 1 day a year, sending them "back to the coal mine" for the remaining 364 days. Many developers even spontaneously hold "hackathons" on weekends as a hobby, indicating that companies fail to unleash their immense potential.
  • Deduction: Transforming developers from "task executors" to "problem solvers" can significantly boost their engagement and output. Falsification condition: If a company observes high developer turnover or low engagement, it should first examine whether it is "assigning tasks" rather than "sharing problems."

Position Moves

Position Guest Attitude Key Data
Twilio Bullish (own platform) Revenue exceeded $1 billion in 2019; clients include Lyft, Twitch, Yelp
AWS Bullish (benchmark analogy) Described as "the fastest-growing enterprise software company in history"
Stripe Bullish (benchmark analogy) An API platform in the payments sector
ING Belgium Bullish (client case) Company-wide (including branches) adopted agile model; built its own contact center on Twilio
Nike Neutral (client case) CTO Skip Potter shared vision at a Twilio all-hands meeting
Bunk / N26 Bullish (industry case) Described as "software companies with a banking license," winning customers through superior app experiences

Investment Implications

1. "Build vs. Die" Replaces "Build vs. Buy" (Jeff Lawson): In the digital age, software experience is a core competitive moat. Companies must build software capabilities in-house or be eliminated by disruptors. Support: Using the banking industry as an example, challenger banks (N26) and transforming giants (ING) are both vying for the high ground of software experience.

2. Platform Companies Should Discover New Opportunities Through Customers' "Non-Standard" Usage (Jeff Lawson): Traditional product companies would "disqualify" customers, while platform companies should ask "why," because the "non-standard" applications customers build on APIs often reveal unmet market needs. Support: By observing customers building their own contact centers, Twilio identified structural flaws in that market and launched Twilio Flex.

3. "Agile Development" May Stifle Creativity; Replace It with "Sharing Problems" (Jeff Lawson): Placing developers on an "assembly line" to execute tasks in two-week sprints suppresses their creativity. A better approach is to share business challenges with them and let them participate in solution design. Support: Developers can work wonders in hackathons (24-48 hours), but companies only give them 1 day a year to do so.

4. Company Culture is a "Tribe" Defined by Three Elements: Heroes, Rituals, and Symbols (Jeff Lawson): Consciously shaping these three elements fosters a sense of belonging among employees and internalizes values as a basis for daily decisions. Support: Twilio's "Wear the Customer's Shoes" value is reinforced by the "symbol" of hanging customer shoes.

5. Values Must Be "Quotable," Not Just "Sound Right" (Jeff Lawson): Abstract words like "integrity" are difficult to use naturally in daily decisions. Good values should be short, memorable, and roll off the tongue in meetings, like "No Shenanigans." Support: Twilio employees say "this feels like shenanigans" when making decisions, proving the values are in effect.

6. "Draw the Owl" Culture: No Instructions, Figure It Out, Get It Done, and Iterate (Jeff Lawson): This is Twilio's core spirit, originating from an internet meme. It encourages employees to proactively "draw the rest of the owl" when faced with ambiguity and difficulty, rather than waiting for instructions. Support: Early on, investors told Twilio that "APIs aren't a product, and developers aren't customers," but the team followed the customers and vision, ultimately proving the market.

~9 min full read
Deep Analysis