The API-Centric Distribution Model
Business development through code, not connections
Andrew Chen identifies a fundamental shift in business development from people-centric to API-centric approaches. Traditional business development relied on personal relationships, handshake deals, and partnership negotiations conducted over lunches and golf courses. In the API-centric model, distribution partnerships are built through code: integrating with platform APIs, building automated data flows, and creating seamless cross-product experiences that benefit users on both sides. This shift means that the most valuable business development professional is no longer the person with the best Rolodex but the engineer who can identify and execute the highest-leverage integration opportunity. Chen argues that this represents a structural, permanent change driven by the rise of superplatforms that mediate access to hundreds of millions of users through standardized APIs rather than individual relationships. Companies that master API-centric distribution can achieve scale that would take traditional BD teams decades to build through individual partnerships.
- Business development is now API-centric, not people-centric.
- The best partnerships are built through code, not contracts.
- Superplatforms provide access to hundreds of millions of users through standardized APIs.
- Traditional BD channels like PR are lagging indicators, not growth drivers.
- Audit available platform APIsSystematically review the API documentation of every platform relevant to your target users. Identify which user actions, data points, and content types are accessible through each API. Map the integration points where your product could create value for users on those platforms. Pay attention to rate limits, terms of service restrictions, and deprecation risks. Create a ranked list of integration opportunities based on the size of the user base, the quality of API access, and the naturalness of the integration with your product experience.Pro tipJoin developer communities and forums for each platform to learn about undocumented capabilities and upcoming API changes before they are publicly announced.WarningAPI access can be revoked at any time. Never build your entire distribution on a single platform API.
- Build the highest-leverage integration firstSelect the integration opportunity with the best ratio of engineering effort to distribution potential. Build a minimum viable integration that proves the distribution hypothesis before investing in a polished version. Measure the cost per acquired user through the integration and compare it to other channels. If the economics are favorable, invest heavily in optimizing the integration for conversion rate, user experience, and scalability. This single integration may produce more users than all traditional marketing efforts combined.Pro tipStart with the platform where your users already spend time and where the action gap between their current behavior and your product is smallest.
- Diversify across multiple platformsOnce the first integration proves successful, replicate the approach across additional platforms to reduce platform dependency risk. Each integration should be built by engineers who understand both the technical API constraints and the marketing objectives. Track the acquisition cost and user quality from each platform separately, as users from different platforms may have dramatically different retention and monetization profiles. Build a portfolio of integrations that provides resilient distribution even if any single platform restricts access.Pro tipAllocate 20% of engineering resources to exploring new platform opportunities continuously, as the API landscape changes rapidly.WarningQuality varies dramatically across platforms. Users acquired cheaply from one platform may have poor retention compared to those from another.
Zynga built FarmVille and other social games that deeply integrated with Facebook's API, allowing viral distribution through news feed posts, invitations, and social features. At its peak, Zynga acquired tens of millions of users through Facebook's platform at near-zero cost. However, when Facebook changed its API policies to restrict viral distribution, Zynga lost its primary growth channel and never fully recovered.
Chen observed this shift through his work advising Silicon Valley startups between 2009 and 2012. He watched companies like Zynga grow explosively through Facebook's API, Spotify integrate deeply with Facebook's social graph, and numerous startups build entire distribution strategies on top of Twitter's API. In contrast, he saw traditional companies spending months negotiating individual partnership deals that produced a fraction of the distribution. The Airbnb-Craigslist case was the most dramatic example: rather than approaching Craigslist for a formal partnership (which would have been declined), Airbnb's engineers simply built the integration themselves. The contrast between 1995—when the entire internet had 16 million users—and 2012, when individual platforms like Facebook had nearly a billion users accessible via API, made the structural nature of this shift undeniable.