APER (Annualized Productivity to Engineering Ratio)
A macro-economic metric calculated by dividing Annual Recurring Revenue (ARR) by Total Engineering Headcount. APER replaces isolated, self-referential metrics like story point velocity with a direct measurement of economic output per engineer. It serves as a high-level indicator of whether engineering investments are translating into actual commercial value. Featured extensively in executive leadership discussions, APER aligns technical execution with corporate financial realities.
“Shipping code is a cost. Only shipping value is a victory.”
Engineering teams often declare success because they shipped a high volume of code or completed many story points, even while the company’s revenue growth stalls. APER forces engineering leadership to take responsibility for commercial outcomes, not just output. It quickly identifies when an organization has hired beyond its capacity to generate revenue. This metric shifts the engineering culture from a factory mindset to a value-creation mindset.
Richard Ewing’s Research Thesis
Engineering leadership must be judged by the commercial success of the product, not the speed of the assembly line.
Why This Specification Exists
Engineering teams claim success based on velocity while the business stagnates.
Measuring engineering solely by story points, DORA metrics, or lines of code.
Lack of a macro metric tying engineering headcount directly to commercial output.
A high-level ratio dividing ARR by engineering headcount.
What Changes If You Believe This?
Teams stop working on features that have no path to revenue generation.
Can accurately gauge if engineering hiring is pacing with business growth.
Must map every feature clearly to commercial outcomes.
Security investments must be framed as revenue protection to avoid hurting APER.
Recommended Action by Role
Report APER at board meetings instead of velocity or burndown charts.
APER Calculator
Calculates your organization's APER and compares it to industry benchmarks.
Latest Publications & Research Activity
Hey, Senior PMs: Shipping Faster Won’t Get You Promoted
GitHub Copilot Is Generating More Code Than Your Team Can Review: Why Senior Engineers Are Now the Bottleneck
In the Vibe Coding Era, What Does a Software Engineer Even Do?
Frequently Asked Questions
Q:How is APER different from Revenue per Employee?
APER isolates the engineering organization to specifically measure the commercial efficiency of the product development engine.
Q:What is a healthy APER score?
It varies heavily by industry and company stage, but a declining APER year-over-year always indicates bloat or misaligned product strategy.
Inspectable Evidence Ledger
Classified evidence items supporting, extending, or refining this canonical research specification.
| Evidence Item | Publisher | Evidence Type | Strength | Role | Action |
|---|---|---|---|---|---|
| Hey, Senior PMs: Shipping Faster Won't Get You Promoted | CIO.com | Tier-1 Article | ★★★★★ | Origin | Inspect ↗ |
| The 3 Financial Metrics Every PM Needs on Their Scorecard | Mind the Product | Industry Article | ★★★★ | Extends | Inspect ↗ |
| The Product Economist: A Structural Shift | Post | ★★★ | Extends | Inspect ↗ |
Recommended Citation
Ewing, R. (2026). "APER (Annualized Productivity to Engineering Ratio)." Richard Ewing Research Canon. Available at: https://www.richardewing.io/concepts/aper-metric
@article{ewing_aper_metric,
author = {Ewing, Richard},
title = {APER (Annualized Productivity to Engineering Ratio)},
journal = {Richard Ewing Research Canon},
year = {2026},
url = {https://www.richardewing.io/concepts/aper-metric}
}