Copilot Impact Dashboard Adds a 'Potential Return on Investment' Section
GitHub has added a “Potential return on investment” section to the Copilot impact dashboard, giving organizations a way to correlate what they spend on Copilot with how much pull request output developers produce.
Details
- What it shows: Two comparison cards, one per developer adoption phase, each displaying cost per developer per month (based on actual AI credit usage), that cost as a percentage of payroll, and average monthly pull request volume per developer
- Adjustable salary selector: Administrators can plug in their own payroll assumptions to model ROI scenarios rather than relying on a fixed default figure
- Where to find it: Available at both the enterprise and organization level in the Copilot impact dashboard
- Who can see it: Enterprise owners, billing managers, organization owners, and anyone with a custom role granting “View Copilot Metrics” permission; requires the Copilot usage metrics policy to be enabled
- More accurate cohorts: The dashboard now counts adoption cohorts based on all users active at any point during the full 28-day reporting window, rather than only those active on the final day
- Caveat: Cost figures are estimates derived from AI credit consumption, and the salary selector is a modeling tool, not real payroll data
How to try it
- Open the Copilot impact dashboard at the enterprise or organization level and look for the new “Potential return on investment” section
- Adjust the salary selector to model ROI against your own team’s compensation assumptions
- Make sure the Copilot usage metrics policy is enabled if the section isn’t visible