Jan 2, 2019 · 30m · a16z
a16z Podcast | The API Economy -- The Why, What, and How
Sonal Chokshi · 8m spoken Christina Cordova · 7m spoken Augusto Marietti · 6m spoken Laura Behrens-Wu · 5m spoken
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 episode of the a16z Podcast, host Sonal Chokshi and industry leaders from Stripe, Kong, and Shippo explore the profound impact of the API economy on modern software architecture and business strategy. The panel examines how modular APIs lower barriers to entry, enable core focus, bridge technical tools with non-developer stakeholders, and transform software infrastructure across industries.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. The host holds 30.2% of the talking time here. How this is scored →
The host as informed peer 5.0 Guest teaching 3.8 Guest disagreement 1.4 The host pushing back 2.4
speaking balance: gold is the host, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 12:18 Augusto reframes host's definition
Augusto rejects Sonal's conceptual interpretation of 'API-first', explaining that 'first' specifies the technical interaction layer rather than corporate culture.
Hardest push from the host ▶ 11:50 Host rejects 'API-first' phrasingSonal refuses Christina's use of 'API-first', arguing that 'API-only' or 'internet-native' better describes companies built without legacy hardware.
Biggest teaching moment ▶ 12:18 Clarifying API interaction entry pointsAugusto corrects Sonal's understanding by demonstrating that 'API-first' describes interacting with an endpoint prior to a GUI.
The host holds their own ▶ 4:33 Challenging abstract software analogiesSonal demonstrates domain expertise by pressing Augusto on the limits of his assembly line analogy, emphasizing the abstract nature of software outputs.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | The host as informed peer | Guest teaching | Guest disagreement | The host pushing back | Why |
|---|---|---|---|---|---|---|
| Broadening the API Economy Beyond Tech Companies | 5 | 3 | 1 | 1 | Sonal contributes directly to the thesis by highlighting that non-software native businesses are major adopters of APIs. She elaborates with a design history story, keeping the tone collaborative and conversational. | |
| The Assembly Line Analogy and Software Modularization | 5 | 4 | 1 | 4 | Sonal critically interrogates Augusto's assembly line analogy, pointing out that software APIs remain abstract compared to physical assembly components. The guests clarify by detailing real-world API stacks like Lyft's use of Twilio and Stripe. | |
| In-House Control vs. API Integration Trade-Offs | 6 | 4 | 1 | 3 | Sonal raises the central strategic tension between maintaining full-stack control versus integrating modular third-party APIs. She references microservice origins at Netflix to show deep industry context. | |
| Defining API-First and API-Only Businesses | 6 | 5 | 3 | 5 | Sonal pushes back on the phrasing 'API-first', proposing 'API-only' as a more accurate term for native companies. Augusto politely reframes her objection by clarifying that 'first' refers to the primary technical interface rather than corporate evolution. | |
| Developer Experience, Documentation, and User Interfaces | 4 | 4 | 1 | 1 | Sonal prompts the panel on developer experience and non-technical user interface needs. Guests detail key documentation innovations, such as Stripe's three-column layout and SQL-based dashboards. | |
| Data Mobility and the Connected API Ecosystem | 4 | 3 | 1 | 1 | Sonal explores data mobility between digital systems and physical supply chains. The conversation remains highly agreeable as guests share analogies for data connectivity. | |
| Go-to-Market Strategies and Selling APIs to Organizations | 6 | 4 | 2 | 3 | Sonal frames go-to-market challenges around 'Not Invented Here' syndrome and selling outcomes over features. Guests outline how GTM strategies differ between developer influencers and executive buyers. | |
| Key Takeaways and Long-Term API Strategy | 4 | 3 | 1 | 1 | Sonal synthesizes long-term API strategies as guests warn against treating APIs as secondary add-ons. The conversation concludes on an aligned note. |
Statements from this episode (14)
Cordova: APIs allow startups to focus entirely on core product competencies
“So maybe 1015 years ago, you used to need to have someone who knew how to do bookkeeping or accounting and payments and shipping and all of these different services to get up and running. And now you can purely focus on your core competency and like building y…”
Cordova: Lyft scaled via Google Maps, Twilio, and Stripe APIs
“Rather than having to build, like, mapping and logistic services, they're integrating with Google Maps. Rather than building out, like, a push notification or phone verification system, they're using Twilio. Rather than having to build their own payment servic…”
Behrens-Wu: Stripe Radar grants startups network-level fraud prevention from day one
“I really like Stripe radar, where people who are able to just plug into Stripe Radar and prevent fraud in a way because you've seen fraud across all other customers already, and you're able to use that data and make it accessible to a company just getting star…”
Cordova: Shopify chose Stripe over building end-to-end payments infrastructure
“Shopify, rather than, like, building their own payments infrastructure from end to end, said, rather than building it ourselves, we'd rather go down the path of working with Stripe and building on top all of the technology that we have to offer.”
Cordova: Shopify CEO admitted replacing Stripe would severely delay company goals
“Their CEO said it on, like, an earnings call. Fairly recently, that getting to a point where you say, like, we want to bring this in-house, like, sure, we could do that, definitely something that Shopify could do, but it would effectively require them to get a…”
Mariotti: Enterprise transition to microservices will take ten years
“At an enterprise level, you know, 99.9, they're still monolithic, so it's more a 10 years transition that we'll see, and what Netflix did, it will happen to Coca-Cola, to McDonald's, so there's a lot of value to be unlocked and to help companies doing this tra…”
Behrens-Wu: Non-Developers Are Essential Decision-Makers for API Products
“While it's API first, there are also other stakeholders in the company that are important in the decision-making process or buying process that need to be involved. And not everyone knows how to integrate an API.”
Mariotti: Stripe pioneered the now-standard three-column API documentation layout
“I think Stripe did a great job back in like five, six years ago on documentations because they were, I think, the first one to innovate in such a simple thing. But it looks simple, but actually very complex to make it easy to digest by having a three column st…”
Mariotti: Kong locks its GUI and management dashboard behind enterprise subscriptions
“For us, the GUI is more an enterprise feature. DevOps download it and use it, engineers use it. Then when you go in an enterprise relationship, usually you have higher stakeholder than ones, obviously, a management console or dashboard, and that one is part of…”
Mariotti: Only 10% of Apple product components are built in-house
“Even at Apple, 10% of all the pieces are built by Apple. Actually, 90%, it comes from outside.”
Behrens-Wu: Shipping options directly drive e-commerce checkout conversion rates
“Shipping is no longer a means to an end to get your item from A to B. The buyer at checkout looks at whether shipping is free, whether it meets their expectation around transit times, and if it doesn't, they close the window and they go to Amazon and buy it th…”
Mariotti: Open-source software marketing gains are offset by enterprise sales friction
“So 50% of our competition is ourself. So in open source, what you gain in marketing, you lose it in sales.”
Cordova: Dropbox's Most Successful APIs Focused Directly on File Syncing
“If you look at Dropbox, not an API first or API only company, but very much a lot of their really great and most successful APIs were focused on syncing, right? Which was something that they're particularly great at.”
Mariotti: Fortune 500 APIs Fail When Treated as Brand Ego Projects
“You have giant Fortune 500 that thought that way, and just because they're the ego of the brand, but they never went anywhere, nobody used their APIs. Just because they think like an afterthought or a satellite thing, rather than the future.”