#metrics

Planning a launch, an onboarding overhaul, or deciding where the next quarter's developer-marketing budget goes.

Setting DevRel goals, building the quarterly report, or defending the function's budget.

Reporting adoption of a seat- or license-based AI product — to your own leadership, in a customer-facing admin dashboard, or ahead of an enterprise renewal.

Building an outbound or expansion motion for a self-serve developer product, or evaluating community- and intent-data vendors.

A full-cycle developer marketing agency, five practice areas from go-to-market through developer experience to ROI measurement, and it maintains a public developer events calendar.

Marcos Placona, 12+ years of DevRel at Twilio and Circle, co-author of a developer-ecosystems framework book, with Sourcegraph and DigitalOcean among the named clients.

Team of ex-operators from GitHub, MongoDB and Atlassian, with AWS, GitHub, MongoDB, Netlify and Buildkite as clients, plus their own GA4/Search Console analytics app.

30,000+ developers surveyed a year across 168 countries, 17+ years of continuous waves, and a published methodology, sold as population sizing, segmentation and developer-programme benchmarking.

Thirty-three checks across AI discoverability, structure, content quality, SEO and internal linking, returned as a 0–100 score with prioritised fixes.

A new enterprise dashboard sorts Copilot seats into adoption-phase cohorts and breaks out a "Passive" segment — GitHub productizing the adoption story its buyers are being asked to prove.

GitHub priced AI code review as a seat plus a meter on Monday, then shipped the dashboard that counts unused Copilot seats on Wednesday — the vendor selling AI seats is now arming buyers to find the shelfware, because the ROI-skeptical renewal conversation demands it.

For a developer product, the minutes between install and first success predict adoption better than almost any campaign. Here's how to find that path, measure it, and pave it.

Practitioner writing in 2026 keeps landing in the same place — DevRel should report influenced pipeline and activation, not last-touch sourced leads, because a capture-first quota corrodes the trust that makes DevRel work.