Code output per employee

Output is Weave's standard unit for engineering work. For every pull request, Weave asks: how long would this PR take an expert engineer to complete?

The result is a consistent unit of output that can be compared across individuals, teams, languages, and organizations. It is not a count of pull requests or lines of code; Weave analyzes the source code changes themselves to understand the meaning, complexity, and impact of the work.

This series divides each month's attributed output by the number of attributed employees with either AI spend or code output in that same month. It is average data across all team sizes, from small startups to some of the largest enterprises.

Sample and interpretation

The public aggregate snapshot does not include monthly employee or organization counts for this series.

These are aggregate observations from Weave customer telemetry, not a controlled experiment or a representative sample of every engineering team. Changes in the observed cohort and connected telemetry can affect the series. The data alone does not establish that AI caused a change in output.

Estimated expert hours are a modeled measure of engineering output, not recorded working hours, hours saved, or a direct measure of business revenue.

For the wider measurement framework, read how to calculate AI coding ROI, including cost attribution, quality, and baseline comparisons.