GitHub has added a “Potential return on investment” section to the Copilot impact dashboard, giving enterprise and organization administrators a direct view of how AI-assisted development spend relates to pull-request output. The dashboard now groups developers into adoption cohorts based on how they engage with Copilot, then places cost and productivity metrics side by side for each group so engineering leaders can justify continued investment and target enablement programs where adoption headroom is greatest. GitHub Changelog
The new ROI section splits developers into two comparison cards. The first card covers chat and code-completion users, labeled “Passive users” and “Phase 1.” The second covers agent-first developers, labeled “Phase 2” and “Phase 3.” Each card reports three metrics: average monthly Copilot cost per developer derived from actual AI credit consumption, that cost expressed as a share of developer compensation, and average pull requests per developer per month. A salary selector lets administrators pick a compensation band, and all cost-derived metrics recalculate instantly. This turns the dashboard into a lightweight modeling tool rather than a passive reporting view. GitHub Docs
The section is available at both the enterprise and organization level. It is accessible to enterprise owners, billing managers, organization owners, and anyone with a custom role that grants the View Copilot Metrics permission. The Copilot usage metrics policy must be enabled before the data appears. GitHub notes that cost figures are estimates based on AI credit consumption and that the salary selector is a modeling input rather than actual payroll data, so the metrics should be treated as directional rather than exact. GitHub Docs
Alongside the ROI addition, GitHub updated adoption cohort user counts to reflect every user active during the full 28-day reporting window rather than only users active on the window’s final day. Previously, a report ending on a weekend or holiday could show sharply lower counts in each phase. Cohort counts are now higher and more consistent across reporting periods, though this change only affects the impact dashboard and not the Copilot usage metrics API or NDJSON exports. GitHub Changelog
For teams trying to quantify Copilot’s value, the ROI section provides the missing link between spend and throughput. Administrators can now compare early-phase and agent-first developers within the same interface, making it easier to identify which adoption stage delivers the best marginal return and where enablement resources should be focused. GitHub Changelog
Related reading: GitHub Copilot improves context handling, routing to cut token waste and GitHub Copilot agentic harness hits parity with vendor tools.
