Sales and API evangelism have a complicated, sometimes adversarial relationship, and navigating it honestly is one of the harder parts of the evangelism practice. Sales is the function of converting interest into revenue — the assisted, human-driven motion that takes a prospect through a funnel to a closed deal. In the API world, sales sits in tension with both self-service (which lets developers buy without a salesperson) and evangelism (which builds genuine relationships rather than driving conversions). The tension is real because developers, the audience evangelism serves, have a deep distrust of being sold to, while the business needs revenue, which means sales. Getting the relationship between sales and evangelism right — knowing where each belongs, and keeping them from undermining each other — is essential to building an API business that both makes money and keeps the trust of its developer community.
The foundational distinction is that evangelism is not sales, and conflating them corrupts both. I wrote in 2011 about API evangelism versus developer evangelism, and the deeper distinction throughout my work is between evangelism and sales as such. Evangelism builds genuine belief and genuine relationships by being authentically useful; sales drives toward a transaction. They serve different purposes and require different postures toward the audience. The Twilio principle I’ve cited constantly — be part of your community, do not just sell to it — is precisely about keeping this distinction clear. The moment evangelism becomes sales in disguise, the developer community detects it and the trust evaporates. Developers resist evangelism that’s really sales, as I wrote in 2012, because they can tell when they’re being sold to rather than genuinely helped. The integrity of evangelism depends on it not being a sales function, even though both ultimately serve the business.
The self-service-versus-sales reality is where sales finds its legitimate place, and it’s a real business decision. I wrote in 2012 about self-service versus sales-oriented web APIs — the recognition that not every consumer is best served by pure self-service. The long tail of developers wants self-service and resents a sales process; forcing them into one kills adoption. But enterprise customers, whose integrations represent significant revenue and require customization, negotiated terms, and support, often genuinely need a sales relationship. I wrote in 2014 about sales, onboarding, and support in a self-service API world — the mature recognition that the API business needs both: frictionless self-service for the broad base, and assisted sales for the high-value enterprise relationships. Sales isn’t the enemy; it’s the right motion for a specific, high-value segment. The mistake is applying sales where self-service belongs, or self-service where the customer genuinely needs sales assistance.
The funnel tension is where evangelism and sales most directly collide, and I’ve written about it from a place of genuine frustration. I wrote in 2018 about justifying my existence in someone’s API sales and marketing funnel — the discomfort of having genuine evangelism reduced to a funnel metric, evaluated by how many leads it generates. And in 2018 I asked “where am I in the sales funnel for your API?” — pointing at how API programs structure their funnels to optimize for enterprise revenue while discarding the developers, hobbyists, and small users who don’t convert but who make the ecosystem vibrant. When the sales funnel becomes the only lens, evangelism gets distorted into lead-generation, and the genuine community-building that evangelism does — which has value beyond immediate conversion — gets devalued because it doesn’t show up cleanly in the funnel. The tension is structural: sales wants to measure everything by conversion, while evangelism creates value that conversion metrics don’t capture.
The “more evangelism, less sales” position is one I’ve taken in specific contexts where the sales instinct was actively counterproductive. I argued that moving the banking API conversation forward required more evangelism and less sales — because in domains where the audience is skeptical and the trust deficit is high, leading with sales backfires, while leading with genuine evangelism and education builds the foundation that eventually makes business possible. This is the strategic ordering: evangelism first to build trust and understanding, sales later to convert the relationships that genuine evangelism creates. Leading with sales, before the evangelism has built the trust, alienates the audience and forecloses the relationship. The sequence matters: you earn the right to sell through the trust that authentic evangelism builds, and inverting that sequence — selling before you’ve earned trust — is one of the most common and most damaging mistakes in API go-to-market.
The personal-integrity dimension is one I’ve been candid about, because the tension between evangelism and commercial interest is genuine and I’ve lived it. I wrote in 2017 about my challenges taking money from startups as the API Evangelist — the real conflict of interest that arises when the evangelist’s independent voice meets commercial relationships. When evangelism is seen as being commercial, the credibility that makes it work is at risk, because the audience trusts the evangelist precisely to the degree that they believe the evangelist isn’t just selling. This is the deepest version of the sales-evangelism tension: the evangelist’s value depends on independence and authenticity, and commercial relationships always threaten to compromise that. The synthesis I’ve arrived at is that sales is a legitimate and necessary function — the business needs revenue, enterprise customers need assisted sales, and there’s nothing wrong with selling — but sales and evangelism must be kept distinct, sequenced correctly, and honest about their different relationships to the audience. Evangelism builds the trust and understanding; sales converts the high-value relationships that trust enables; self-service handles the scalable base; and the integrity of the whole thing depends on not corrupting evangelism into disguised sales, not forcing sales where self-service belongs, and not letting the funnel mentality reduce the genuine community-building that makes the entire ecosystem healthy. The developer always knows whether you’re genuinely helping them or trying to sell them, and an API business that respects that distinction — leading with authentic evangelism, selling honestly to those who warrant it, and keeping the two from undermining each other — is the one that both makes money and keeps the trust that makes the money possible.
References
- API Evangelism vs Developer Evangelism
- Self Service vs Sales Oriented Web APIs
- Developers Resist API Evangelism
- Sales, Onboarding And Support In A Self-Service API World
- My Challenges When Taking Money From Startups As The API Evangelist
- Be Part Of Your Community, Do Not Just Sell To It
- Where Am I In The Sales Funnel For Your API?
- Justifying My Existence In Your API Sales And Marketing Funnel
