R&D Monthly Spend
Definition
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.
Why it matters
Largest single line of operating spend at most growth-stage SaaS companies — the input that `rd_efficiency` converts into revenue. The board reads this to gauge whether the company is over- or under-investing in product velocity relative to revenue ramp.
How it's calculated
Sum of fully-loaded R&D-team payroll + benefits + allocated stock-comp + R&D-dedicated infrastructure + R&D tooling + R&D vendor spend, expressed as a monthly figure. Different from GAAP R&D expense (which capitalizes some software development costs); footnote the convention. How to interpret it
Compare R&D spend to revenue (or ARR run-rate) to derive R&D-as-% of revenue. Per the KBCM/Sapphire SaaS Survey (latest annual edition — see capital-allocation section), median R&D-as-% of revenue runs ~25–35% at early-growth SaaS and compresses with scale. Out-of-band (e.g. 60%+ at a $20M ARR company) usually signals either heavy platform-investment cycles or under-monetization — flag for context. Always pull the current KBCM/Sapphire edition rather than relying on a memorized range.
Source
KBCM/Sapphire SaaS Survey 2024 (15th Annual) · R&D as % of Revenue (capital-allocation section)
Stage relevance
Typically owned by
Related KPIs
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.
Headcount of engineers (software, infrastructure, security, data, ML) in the R&D organization, typically including full-time employees plus contractors at a defined FTE-equivalence factor. The "capacity input" side of all R&D ratios. Common pitfall: definition drift. Some companies include only software engineers, others include product managers and designers, others include all of R&D plus QA, plus support engineers. Boards should anchor the definition once and hold it stable — otherwise quarter-over-quarter comparisons are noise. Pair with `rd_monthly_spend` to derive fully-loaded cost-per-engineer.
Percentage of R&D capacity (typically measured in engineering-weeks or story points over a quarter) allocated to net-new capabilities, as opposed to maintenance, bug fixes, internal tooling, or customer-support engineering. The "available bandwidth for offense" view. Common pitfall: confusing innovation capacity (input — how much team-time is available for new work) with `offensive_roadmap_pct` (output — what proportion of the planned roadmap is growth-oriented). A team can have 60% innovation capacity allocated entirely to defensive work if the roadmap demands it. Boards should look at both together.
Annual Recurring Revenue — the value of all recurring subscription revenue normalized to a one-year run-rate as of the period close. The headline operating metric for a subscription business; every growth and efficiency ratio (NRR, GRR, magic number, CAC payback, Rule of 40) is calibrated against it. Excludes one-time fees, professional services, and non-contractual usage. Common pitfall: confusing ARR (contracted recurring) with revenue (recognized) or with CARR (contracted incl. not-yet-live) — the SMSB standard draws sharp lines between them, and boards expect the same discipline. The KpiVarianceTable widget surfaces forecast / actual / variance / status / future-forecast columns against the same field.
Average monthly net cash outflow over the reporting period — total cash spent minus total cash collected, divided by the number of months in the period. The headline survival number for venture-backed startups: it pairs with `finance.total_cash_in_bank` to produce runway, and pairs with revenue growth to produce the Bessemer "burn multiple". Common pitfall: net burn is volatile — large quarterly bills (annual SaaS renewals, employer-tax true-ups), enterprise prepayments, and FX swings can mask the underlying trend. Smoothing over a trailing 3-month average is standard board practice. Equally important: do not silently include one-off cash events (acquisitions, settlements, large prepayments received) without flagging them — boards prefer a "core burn" and "headline burn" pair when the period is noisy.
EIN verified against IRS records Encrypted at rest and in transit Export everything, free, forever Monthly — cancel in one click Security details
Track these KPIs with your board
I'mBoard helps startup CEOs report the metrics that matter, track resolutions, and run better board meetings.