Devrel Strategy

by samber98ed86da8babMIT2 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 10 days ago

Designs a company's developer relations program from the top - the business driver that funds it, the two goals it is allowed to serve, the pillar mix (advocacy, marketing, enablement, community) for its stage, audience priority, build-vs-buy per bet, staffing sequence, and a written refused list. Use whenever someone asks whether to start doing DevRel, what a new devrel program should do first, why devrel work is busy but not landing, how to justify the program to an exec, which pillar deserves the next investment, who to hire next, or whether to outsource content, events or community - even if they never say "strategy". Not the first-90-days plan - use samber/developer-relations-skills@developer-relations-kickoff. Not metrics, org chart or budget math.

  1. 98ed86da8babCurrentcommit 98ed86dPublished Oct 8, 2026

Source and attribution

Source:samber/developer-relations-skillsinskills/devrel-strategyat commit98ed86d

License: MIT

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal