Jul 10, 2017 · 35m · saastr
Twilio: The Inside Story with Jeff Lawson, CEO/Co-Founder
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In this SaaStr Annual fireside chat, Twilio CEO Jeff Lawson and Jason Lemkin discuss building a multi-billion-dollar developer platform, exploring developer-led go-to-market strategies, enterprise sales scaling, organizational culture, and operational resilience.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Jason holds 25.9% of the talking time here. How this is scored →
Jason as informed peer 4.6 Guest teaching 4.3 Guest disagreement 1.9 Jason pushing back 1.7
speaking balance: gold is Jason, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 23:05 Lawson dismissing conventional focus advice
Lawson explicitly labels the standard startup mantra of 'find a niche, get rich' and strict single-product focus as bad advice, forcefully advocating for parallel experimental bets.
Hardest push from Jason ▶ 20:19 Lemkin pushing back on Lawson's no-sales beliefLemkin directly challenges Lawson's assumption that Twilio grew without early sales, calling out that Lawson traveling to meet top accounts personally was textbook enterprise sales.
Biggest teaching moment ▶ 4:05 Lawson reframing developers as an entry wedgeLawson corrects Lemkin's view of developers as the target market, explaining that developers represent an efficient bottom-up distribution vector for traditional enterprise products.
Jason holds their own ▶ 20:19 Lemkin reframing founder visits as the real sales modelLemkin leverages his SaaS expertise to highlight that Lawson's 50 in-person customer relationships served as the true foundation of Twilio's high-tier enterprise growth.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Jason as informed peer | Guest teaching | Guest disagreement | Jason pushing back | Why |
|---|---|---|---|---|---|---|
| Jason's Anecdote on Jeff Lawson and Conference Banter | 3 | 1 | 1 | 1 | Lemkin opens with lighthearted banter, recounting a story about Lawson offering to find a replacement speaker during Twilio's quiet period. The tone is entirely friendly, admiring, and collaborative with zero adversarial friction. | |
| The Developer as a Market Entry Strategy | 4 | 6 | 3 | 2 | Lemkin expresses surprise at how large the developer market is, prompting Lawson to gently correct the premise by explaining that developers are not the end market itself, but rather the strategic wedge into broader enterprise IT spend. | |
| Developer-Led Enterprise Adoption and Sales Shepherding | 5 | 4 | 1 | 2 | Lemkin probes how Twilio's sales motion evolves at scale, while Lawson details how developer prototyping generates internal executive buy-in before sales teams shepherd deals through enterprise procurement and security. | |
| Moving Upmarket with Enterprise Security and Packaging | 5 | 4 | 1 | 1 | Lemkin and Lawson discuss moving upmarket and packaging compliance checkboxes like SSO and security into paid enterprise tiers, aligning product pricing with sales rep incentives. | |
| Integrating Sales Culture into an Engineering Organization | 4 | 5 | 2 | 1 | Lawson explains that the real cultural friction in a developer-led company was not developers resisting enterprise features, but early salespeople feeling like fish out of water inside a dominant engineering culture. | |
| Measuring Sales Attribution in Usage-Based Pricing | 7 | 4 | 2 | 4 | Lawson details the difficulty of measuring sales attribution when usage grows organically, and Lemkin demonstrates sharp domain expertise by pointing out that Lawson himself was conducting founder-led sales on every major top account. | |
| Agility, Multiple Product Lines, and Small Autonomous Teams | 4 | 5 | 4 | 2 | Lawson rejects conventional startup advice to focus on a single niche, arguing instead for running multiple small autonomous teams to increase probability bets and hit unconstrained business outcomes. | |
| Portfolio Management and Backward Compatibility | 5 | 4 | 1 | 1 | Lawson explains portfolio resource management, noting that Twilio reallocates team resources without deprecating or breaking existing customer APIs in order to preserve developer trust. | |
| Agility with Resiliency and the Operational Maturity Model | 4 | 6 | 2 | 1 | Lawson rejects the false dichotomy between speed and reliability, walking Lemkin through Twilio's Operational Maturity Model (OMM/Iron Man) that enables thousands of daily production deploys with high availability. |
Statements from this episode (15)
Lawson: Developers are a market entry strategy, not the end market
“I don't think of developers as the market, per se. I think of developers as the strategy to get into the market for whatever you're doing.”
Lawson: Twilio enterprise sales exist to shepherd developer prototypes past procurement
“Developers are the ones who bring you in first, build that prototype, you know, and then it starts to snowball within the company, right? The momentum, because people see this thing and they say, oh, we want to ship that. Hey, what's preventing us from shippin…”
Lawson: Developer-led adoption replaces competitive RFP bidding with pre-built prototypes
“It's not a hero sale. You're not like, hey, let's just do an RFP with, You know, five of our competitors. It's a, Hey, the thing's already built. The executives may have even touched it and said, Oh, this is awesome. Let's get it shipped. Right. And now we're …”
Lawson: Billboards provide enterprise air cover for developer-led adoption
“You know, I think what it does is it provides air cover. So that let's say, you know, a developer builds a thing and they're in some meeting where they're saying, oh, how did you build this? Yeah. And they say Twilio, if you have name recognition, even though …”
Lemkin: Billboard advertising can work for startups at $1M revenue
“We mock a lot of this stuff, like billboards early as founders, because, like, there's no way we're going to get leads. It's not about leads, right? It's about reinforcing the brand and supporting that, and then I've heard of it. You do it just right, it can e…”
Lawson: Twilio monetizes enterprise security features as a separate recurring plan
“So for Twilio, for example, we have got our enterprise plan. It adds things like single sign-on and client certificate validation, And a bunch of other like security and compliance related things that, you know, clearly enterprises with a lot of check boxes be…”
Lawson: Usage-based SaaS needs recurring packages to justify enterprise sales reps
“If you're not willing to sign up for this monthly recurring package, then you're probably not a very qualified opportunity, right? Because with our usage-based model, the prices at Twilio start at a penny. Yeah. And you can sign up on our website and get going…”
Lawson: Early Sales Hires Face More Cultural Friction Than Engineers
“I thought that the cultural shift that happened was not so much a struggle for, like, the developers, it was actually a really interesting struggle for the salespeople, especially the early ones that we brought into the organization, because they were the ones…”
Lawson: Twilio's early top 50 accounts were personally closed by the CEO
“What I did is I looked back at, like, every major customer that, that, you know, I could look at, like, our top, like, 50 list or whatever, and I go through the list, and I, like, a substantial number of them I looked at, and I'm like, wow, when we were really…”
Lemkin: Software companies cannot easily reach $300M revenue purely self-serve
“Very, it's hard to get to three hundred million with the product selling itself.”
Lawson: 'Find a niche' and single-product focus is bad startup advice
“And I know there's this advice that entrepreneurs often get about, you know, find a niche, get rich you know, focus, focus, focus. You know, there's a lot of ways to phrase this bad advice.”
Lawson: A small five-person team is the unit of progress in software
“Right, so you don't need a hundred engineers to build a product. Like, you need five engineers who work really well together, and who know the problem domain, know the customer, can prioritize well, and can ship and operate code. Right, that's the unit of prog…”
Lawson: Twilio has never killed or deprecated an API it built
“We've killed the teams, but maintain the products. So we find another home internally for the product to live. We have never killed an API that we've ever built.”
Twilio maintains five nines API availability despite 18,000 annual production deployments
“Now we can ship 18,000 times a year, and we have a five nines available API, and a seven nines success rate of the request that we're serving.”
Jeff Lawson commits to at least three face-to-face customer meetings weekly
“And so I set the internal going and meet with at least three customers a week. And, you know, face-to-face meetings with customers, and I asked the sales team's help. Hey, I want you to bring me in. I want to meet customers. When I get on a plane, it's going t…”