Article · 15 min read
Mastering Developer-Led Outbound
Martin Gontovnikas and Matteo Tittarelli · Hypergrowth Partners Playbooks Free Advanced
Three outbound plays a developer would genuinely welcome: find and report a bug in their open source repo, read their terms of service to infer the backend stack, run PageSpeed against them and show the gap. Gonto ran growth at Auth0, so this is not theory.
- Three concrete plays: flag a real bug in their open-source repo, read their backend stack out of their terms and conditions, or send a PageSpeedInsights comparison against competitors.
- Target on GitHub signals: which projects they contribute to, how much, and whether they are an IC or a manager.
- The rule is value before the pitch, because a developer's filter kills anything that opens as a sales message.