Case · 2024
ZoomInfo
GitHub Copilot enterprise deployment for developer productivity
Maturity stage
Production
Use-case type
Augmentation
Function
Software Engineering/Development
Company size
Large
Evidence
33% suggestion acceptance rate; 20% line acceptance rate; 90% of developers report time savings (median 20%); 72% developer satisfaction
ROI / outcome figure
Median 20% time reduction on tasks; 63% of devs report more tasks per sprint
Deep dive
The setup
ZoomInfo deployed GitHub Copilot to its enterprise developer fleet and tracked acceptance rates, time-saving estimates, and developer satisfaction over a year.
What happened
33% of suggestions were accepted; 20% of code lines were written by Copilot. 90% of developers reported time savings, with the median estimate at 20%. Developer satisfaction was 72%.
Root cause
These figures are now the canonical baseline for code-completion ROI. The 20% median time saving is on the conservative side of the published range and lines up with what NBER's Microsoft Copilot RCT (CASE-038) found in a controlled setting.
Takeaway for teams considering similar work
Use the 20% median as the central time-saving estimate when projecting code-completion ROI. The 33% suggestion-acceptance rate is the more durable engagement metric; if a Copilot-style tool is below 20% acceptance after rollout, the deployment is in trouble.
Why this case is cited as evidence
IMeasurement Maturity
Are there established KPIs, baselines, and evaluation cadences?
More from Technology/Software
Industry deep-diveApply this to your team
Take the RAPID assessment to see whether your organisation is exposed to the same failure modes as this case - or already has the discipline that made it work.