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 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.
Multi-Hop Causal Traversal Engine
Explore how concepts dynamically feed into each other across 1-hop, 2-hop, and 3-hop transitive relationships. Click any node to navigate the causal highway.
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.
Direct Relationships (5)
Transitive Neighbors (Connected via Hop 1)
Extended Causal Ripple Effects
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
Replace self-referential engineering story points with Annualized Productivity to Engineering Ratio to ensure technical headcount directly drives commercial revenue.
Track ARR per engineer across departments to identify bloated divisions where payroll growth has decoupled from top-line performance.
Anchor your team priorities around shipping measurable commercial value rather than celebrating the sheer volume of code merged into staging.
Help developers understand the commercial impact of their projects so sprint goals align with business revenue goals.
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
Shifts product management focus from feature output to margin contribution and P&L ownership.
The 3 Financial Metrics Every PM Needs on Their Scorecard
Deep dive into product P&L ownership, margin contribution, and capital efficiency metrics for PMs.
I Put AI Agents in Charge of My To-Do List. Here's What They Actually Took Off My Plate.
Testing autonomous AI agents across administrative, research, and software engineering chores proves that delegation does not eliminate workloads, but shifts human labor into an air traffic control supervisory review queue. While agents excel at bounded, easily verifiable technical tasks like CI pipeline monitoring, DOM contrast audits, and build validation, they fail silently with perfect syntax during complex database refactors and struggle with physical reality collisions and interpersonal nuance. Real productivity gains require four operational laws: start with read-only triggers, enforce narrow definitions of done, require human approval on external actions, and treat all output as junior drafts.
GitHub Copilot Is Generating More Code Than Your Team Can Review: Why Senior Engineers Are Now the Bottleneck
Identifies the review capacity crunch created when AI code generation outpaces senior engineering verification velocity.
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.
Canonical Specification Origin
Engineering leadership must be judged by the commercial success of the product, not the speed of the assembly line.
Corpus Interconnections
Richard Ewing artifacts developed around this canonical framework, including publications, execution tools, and diagnostic models.
External Adoption & Peer Citations
Documented instances where independent researchers, engineering teams, and publications have cited, implemented, or referenced this concept outside Richard Ewing’s ecosystem.
External Evidence: No independently verified references recorded yet.
This concept is part of Richard Ewing’s original baseline canon. External citations and implementations are added only upon rigorous empirical verification.
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 ↗ | |
| Hey, Senior PMs: Shipping Faster Won’t Get You Promoted | CIO.com | Evergreen | ★★★★★ | Supports | 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}
}