External evangelism is the public-facing third of the evangelism job — the outreach, storytelling, and community work aimed at the developers, partners, and broader audiences outside your organization’s walls. It’s the part most people picture when they think of evangelism: the conference talks, the blog posts, the social media, the meetups, the public presence. I’ve always insisted that external is only one-third of the work — that evangelism is equal parts internal, partner, and public outreach, as I wrote in 2011 — but external is the visible third, the part that builds the public awareness and reputation an API program needs to attract a community. Done well, external evangelism is how an API goes from a thing your company built to a thing the world knows about and wants to use.
The foundational distinction is that external evangelism reaches beyond just developers. I wrote in 2011 about API evangelism versus developer evangelism, and the difference matters most on the external side: developer evangelism targets the developers who’ll integrate, while API evangelism reaches the broader external community — business people, journalists, partners, the curious public. External outreach that only speaks to developers misses the larger audience that shapes whether an API matters. The best external evangelism speaks to multiple audiences at once, meeting developers where they are technically while also making the value legible to the non-technical people who influence adoption.
The single most important principle of external outreach I took from Twilio: be part of your community, do not just sell to it. I wrote about this in 2016 because it’s the thing that separates genuine external evangelism from marketing in disguise. A vendor shows up at the external event to pitch. A community member shows up to help, to contribute, to belong. External audiences have a finely tuned detector for the difference, and the moment they sense they’re being sold to rather than genuinely served, the trust evaporates. External evangelism done right is building technical credibility and genuine relationships in the public spaces developers already inhabit — GitHub, Stack Overflow, the meetups, the conferences — not running a campaign to lure them into yours.
The practical playbook for external outreach is something I’ve mapped repeatedly. When someone has an API deployed and a base presence established and asks how to get the word out, I’ve laid out the whole external apparatus: goals, outreach, blogging, events, social media, GitHub presence, API directories, and reporting. Developer outreach specifically, which I broke down in 2014, has distinct modes — fresh engagement with new developers, active engagement with current users, historical engagement with past users, and social engagement across the community. And landscape analysis, which I also wrote about in 2014, is the external intelligence work underneath it all: monitoring the competition, the industry trends, the conversations, so your external outreach is informed rather than blind. External evangelism is a discipline with a real playbook, not just charisma and showing up.
Going outside the echo chamber is the maturity move in external evangelism, and it’s where I’ve pushed hardest in recent years. I wrote in 2019 about going outside the API echo chamber — taking your external outreach beyond the API conferences where you’re preaching to the already-converted, and into the healthcare, financial, energy, and other industry-specific conferences where the “normals” are. The easy external evangelism is talking to other API people at API events. The valuable external evangelism is reaching the audiences who don’t yet think in API terms but whose industries are being transformed by APIs. The influencer role I described in 2017 is part of this — at its best, external influence is education, awareness, and problem-solving through listening and two-way exchange, not product pitching broadcast at an audience.
The hands-on, storytelling-driven approach is what makes external outreach actually land. I wrote in 2021 about a blueprint for hands-on API storytelling — combining blog, video, images, interactive workspaces, and real executable artifacts into external content that lets the audience do something, not just read something. The grassroots external work, like the awareness campaigns I ran for Data.gov in 2011 across startup weekends and conferences, proved that external evangelism is often a ground game — showing up consistently, contributing genuinely, telling stories that resonate. The throughline across all of it is that external evangelism is the public expression of belief in the message, carried into the spaces where the audience lives, through genuine participation and compelling storytelling rather than through broadcasting and selling. It’s the visible third of the job, and it only works when it’s backed by the genuine substance that the internal and partner thirds provide.
References
- API Evangelism vs Developer Evangelism
- API Evangelism Is Equal Parts Internal, Partner And Public Outreach
- Bringing Awareness To Data.gov With Grassroots Evangelism
- API Evangelism Strategy: Developer Outreach
- API Evangelism Strategy: Landscape Analysis
- I Have An API Deployed And A Base Presence Established, What Can I Do To Help Me Get The Word Out
- Be Part Of Your Community, Do Not Just Sell To It
- What Is The Role Of An Influencer In The API Industry
- Going Outside The API Echo Chamber With Your API Services And Tooling
- The Building Blocks Of API Partner Programs
- A Blueprint For Hands-On API Storytelling
