How Do I Measure Revenue Team Productivity?
Use outcome-normalized KPIs—not vanity activity—to understand Sales, Marketing, and CS productivity, then operate with a shared scorecard and cadence.
Direct Answer
Measure revenue productivity by normalizing outcomes to capacity and quality—then tracking them in a cross-functional scorecard. Use revenue (or pipeline) per FTE, conversion by stage, cycle time, and retention/expansion metrics as the core. Pair with leading indicators (coverage, meetings, qualified demand) that correlate with wins. Govern with clear definitions, clean routing, and role-level RACIs so data is trustworthy and comparable.
What “Good” Looks Like
Revenue Productivity Scorecard (Formulas & Targets)
| Metric | Formula | Target/Range | Stage | Notes |
|---|---|---|---|---|
| Revenue per AE | Closed-won ARR ÷ AE FTE | Trend ↑ QoQ | Run | Segment by tenure/region |
| Pipeline per AE | Sum of qualified pipeline ÷ AE FTE | 3–5× quota | Plan | By horizon (this/next Q) |
| Win rate | Closed-won ÷ (won + lost) | ↑ with quality | Run | Normalize by deal size |
| Sales cycle | Close date − stage entry | ↓ trend | Run | Compare by segment |
| SDR qualified pipeline per FTE | Qualified pipeline sourced ÷ SDR FTE | Trend ↑ | Plan | Pair with show rate |
| Marketing qualified demand per FTE | Qualified pipeline influenced ÷ Mktg FTE | Trend ↑ | Plan | Use consistent model |
| NRR | (Start + expansion − churn) ÷ Start | 110–125% | Run | CS/Account Mgmt |
| Expansion per CSM | Expansion ARR ÷ CSM FTE | Trend ↑ | Run | Exclude Sales-owned |
| Capacity utilization | Active opps ÷ target opps per AE | 80–100% | Run | Guard against overloading |
| Forecast accuracy | |Forecast − Actual| ÷ Actual | <10–15% | Improve | By level & stage |
Do and Don’t
| Do | Don’t | Why |
|---|---|---|
| Normalize KPIs per FTE or capacity | Judge by raw totals | Controls for staffing and mix |
| Measure quality + time, not just volume | Chase activity counts | Activity ≠ outcomes |
| Publish definitions and stage criteria | Let teams define locally | Ensures comparability |
| Segment by motion, region, tenure | Average everything | Find true outliers |
| Review in a monthly GTM council | React ad hoc | Turns data into decisions |
Expanded Explanation
Start by agreeing on stage definitions, lifecycle names, and qualification criteria so metrics are apples-to-apples. Use a compact, outcome-first core—revenue per FTE, pipeline per FTE, win rate, cycle time, forecast accuracy, and NRR—and add role-specific leading indicators that statistically correlate with outcomes (e.g., first meetings held, multi-threading, mutual close-plan adoption).
Normalize by capacity (FTE, territory potential, book of business) and control for tenure. Ensure pipeline attribution and deduplication rules are consistent across Marketing, SDR, Sales, and CS. Dashboards should show trends, distributions (not just averages), and drill-downs to manager and rep. Operate with a monthly governance cadence where GTM leaders review gaps, set experiments, and revisit enablement and territory design.
TPG POV: We stand up outcome-first scorecards, clean definitions, and operating cadences across Marketing, Sales, and CS—so leaders can coach to impact, not activity.
FAQ
Revenue (or qualified pipeline) per FTE—paired with win rate and cycle time—gives the clearest, comparable view across teams.
Use cross-checks (e.g., activity quality, stage conversion) and publish definitions; sample records monthly for audit.
Track both, but govern definitions and deduplication. For capacity planning, use qualified pipeline per FTE and cost per opportunity.
Use tenure cohorts and ramp curves; set expectations by month-in-seat with different coverage and activity targets.
Weekly team reviews for coaching; monthly GTM council for structural changes; quarterly for territory and quota resets.