R&D Efficiency
Ratio of net-new ARR generated in a period to R&D spend in the same period — answers "how much revenue does each R&D dollar produce?" Distinct from sales-efficiency metrics (Magic Number, CAC payback) which measure sales/marketing productivity. Common pitfall: R&D-driven ARR (new capabilities, expansion features) shows up on a 2–4 quarter lag after the spend — single-period ratios mis-state the relationship. Boards should look at trailing-twelve-month R&D efficiency, not month-over-month, and pair with `innovation_capacity_pct` to understand whether the spend is on growth bets or maintenance. — Product KPI, I'mBoard-authored (editorial tier).
I'mBoard-authored (editorial tier)
No public third-party standard anchors this KPI yet, so I'mBoard authors and maintains the definition — transparently labeled as editorial tier. See the ontology methodology for the published vs editorial tier system and the back-attribution workstream.
Rogue ID: product.rd_efficiency
Type: Number
Domain: Product
Definition
Ratio of net-new ARR generated in a period to R&D spend in the same period — answers "how much revenue does each R&D dollar produce?" Distinct from sales-efficiency metrics (Magic Number, CAC payback) which measure sales/marketing productivity. Common pitfall: R&D-driven ARR (new capabilities, expansion features) shows up on a 2–4 quarter lag after the spend — single-period ratios mis-state the relationship. Boards should look at trailing-twelve-month R&D efficiency, not month-over-month, and pair with innovation_capacity_pct to understand whether the spend is on growth bets or maintenance.
Formula
rd_efficiency = net_new_arr_in_period / rd_monthly_spend_in_period. Best computed on a trailing-twelve-month basis to absorb the spend-to-revenue lag. Note: not the same as "R&D ROI" (which would deduct R&D cost from revenue); this is a velocity ratio, not a profitability ratio.Why it matters
Highest-leverage indicator of whether R&D investment is converting into revenue. A persistent decline signals either an over-built team relative to demand, a feature-product fit gap, or accumulated tech debt slowing throughput — each prescribes different board action.
How to interpret
No single published benchmark applies across stages and business models. Industry folk-wisdom, not citation-grade: at growth-stage SaaS, $1 of R&D spend producing $1–2 of net-new ARR is healthy; below $0.5 is a flag; above $3 typically signals either underinvestment in R&D (about to hit a velocity wall) or a one-time price-increase boost. Always pair with quality_churn_pct — high efficiency with rising quality-churn means the ratio is borrowing from future periods.
Related KPIs
product.rd_monthly_spendproduct.total_engineersproduct.innovation_capacity_pctproduct.quality_churn_pctsales.arr
Source
I'mBoard editorial — authored and maintained by I'mBoard, first published 2026-04-01. No third-party standard is cited for this KPI; when one emerges, the definition is back-attributed and promoted to the published tier (a minor version bump). Read the ontology methodology for the published vs editorial tier system, attribution rules, and dispute process.
Industry benchmark
A reference distribution sourced from imboard Editorial (2026):
| Percentile | Value |
|---|---|
| 25th | 0.15ratio |
| Median | 0.27ratio |
| 75th | 0.4ratio |
Higher is better.
Stage relevance
| Company stage | Priority |
|---|---|
| Series A | Core |
| Series B | Core |
| Series C+ | Core |
| Public | Core |
Suggested for stages: Series A, Series B, Series C+, Public.
Default owning functions
- R&D
Machine-readable
- This KPI as JSON:
/api/ontology/product/rd_efficiency.json - All Product KPIs:
/api/ontology/product.json - Full catalog:
/api/ontology/index.json
Churn from Quality Issues
Percentage of customer churn (logo or ARR, define explicitly) where the primary stated reason is product or quality problems — bugs, performance, missing core functionality, reliability incidents. Distinguishes product-driven churn from pricing-driven, competitor-driven, or use-case-fit-driven churn. Common pitfall: relying on free-text exit-survey reasons. Customers commonly cite "price" when the underlying issue was reliability or missing features — boards should require both the customer-stated reason and the CSM/Account-Manager-assigned root cause, and watch the gap. The Pendo "Product-Led Growth Benchmark" and similar product-analytics publishers cover product-driven churn qualitatively, not as published numeric ranges. — Product KPI, I'mBoard-authored (editorial tier).
R&D Monthly Spend
Total monthly cash outflow on research and development — fully-loaded engineering, product, and design payroll plus tooling, infrastructure dedicated to product development, contractors, and direct R&D vendor spend. The "input" side of R&D efficiency. Common pitfall: companies report base-payroll R&D and exclude the loaded cost (benefits, stock comp at cash-cost basis, allocated rent, dev tooling), under-reporting true R&D burn by 25–40%. Boards should always ask whether the number is base-payroll, fully-loaded, or GAAP R&D expense — they tell different stories. The KBCM/Sapphire SaaS Survey reports R&D as a percentage of revenue for its company panel — use that as the benchmarking lens. — Product KPI anchored to KBCM/Sapphire SaaS Survey 2024 (15th Annual).