Gross Margin
Recognized revenue minus cost of goods sold (COGS), divided by recognized revenue, expressed as a percentage. The single best read on whether the business model can ever generate operating leverage — a low gross margin caps every downstream efficiency metric (CAC payback, LTV/CAC, Rule of 40). For SaaS, COGS includes hosting, third-party software, customer support, and customer-success cost-of-service. Common pitfall: omitting customer success from COGS inflates the margin and breaks comparability with peer benchmarks. Anchored to KBCM/Sapphire SaaS Survey 2024 §Gross Margin. — Sales KPI anchored to KBCM/Sapphire SaaS Survey 2024 (15th Annual).
Rogue ID: sales.gross_margin
Type: Percentage (%)
Domain: Sales
Definition
Recognized revenue minus cost of goods sold (COGS), divided by recognized revenue, expressed as a percentage. The single best read on whether the business model can ever generate operating leverage — a low gross margin caps every downstream efficiency metric (CAC payback, LTV/CAC, Rule of 40). For SaaS, COGS includes hosting, third-party software, customer support, and customer-success cost-of-service. Common pitfall: omitting customer success from COGS inflates the margin and breaks comparability with peer benchmarks. Anchored to KBCM/Sapphire SaaS Survey 2024 §Gross Margin.
Formula
Gross Margin = ((Recognized Revenue − COGS) / Recognized Revenue) × 100. COGS for a SaaS business: cloud / hosting infrastructure, third-party data and APIs called for delivery, customer support, customer success cost-of-service, and any directly-attributable delivery personnel. Excludes R&D, S&M, and G&A.Why it matters
Caps every long-term efficiency metric — Rule of 40, LTV/CAC, CAC payback all run off contribution margin which derives from gross margin. Board uses it to verify the unit economics are real before debating S&M investment levels.
How to interpret
Per KBCM/Sapphire SaaS Survey 2024 §Gross Margin, healthy SaaS gross margin is 70–80%; > 80% is best-in-class infrastructure leverage; < 65% usually signals heavy services revenue or inefficient COGS (often customer-success scaling linearly with customer count). Sub-70% companies must show a credible path to 70%+ by next funding milestone or face valuation pressure.
Calculation policy
How an AI agent should compute this KPI from messy company data. Free-text rules consumed at reasoning time — not a deterministic DSL. The most common ways to get this wrong are listed under Common miscomputations.
Inclusion rules
- Numerator: Recognized Revenue (period) − COGS (period).
- COGS for SaaS includes: cloud/hosting/infrastructure, third-party APIs/data called for product delivery, payment-processing fees, customer support, customer-success cost-of-service, directly-attributable delivery personnel, software included with the product.
- Denominator: Recognized Revenue for the same period.
- Result is a percentage; format consistently (rounded to one decimal, or as the company's investor-letter standard).
Exclusion rules
- R&D, S&M, G&A — those are below the gross-margin line and belong in operating expenses.
- Stock-based compensation expense — exclude from COGS (separately disclose adjusted GM if non-GAAP).
- One-off implementation services revenue if reported in a separate revenue line with its own services-COGS.
Required inputs
- Period Recognized Revenue (
sales.total_revenueor income-statement total revenue). - Period COGS, broken out by component (hosting, support, CS cost-of-service, payment-processing, third-party delivery costs).
- Methodology disclosure: cash vs accrual basis; GAAP vs adjusted (SBC-excluded).
Data-source priority
- Audited or reviewed income statement.
- Internal management P&L with documented adjustments.
Edge cases
- High services-revenue mix (professional services > 15% of total revenue): break out product GM vs services GM. Blended GM hides whether the product GM is healthy.
- Customer-success cost-of-service: include in COGS for SaaS comparability. The single most common omission that inflates GM by 5–10 percentage points.
- Pure usage-based metering with variable infra cost: include the variable infra cost in COGS for each unit delivered.
- Hosting credits from cloud providers: net against hosting COGS, but disclose the credit period (it ends and COGS spikes).
Validation checks
- Gross Margin should sit in 60–85% range for healthy SaaS. Below 60% requires either a services-heavy explanation or a credible path to 70%+.
- GM × Revenue = Gross Profit — recompute and cross-check.
- Trend should be smooth at steady state; > 5-percentage-point swings quarter-over-quarter usually indicate either a one-off COGS event or a revenue-mix shift worth narrative.
Common miscomputations
- Omitting customer success from COGS — inflates GM by ~5–10 points and breaks peer comparability with KBCM/Sapphire benchmarks.
- Computing GM from ARR (not Recognized Revenue) while still using period-COGS — produces a number that is neither GM nor anything else meaningful.
- Including S&M or R&D in COGS — drops GM far below true unit economics.
- Counting SBC as a cash COGS — overstates COGS by 5–15% depending on equity comp intensity. Disclose adjusted GM if SBC-excluded is the headline.
- Mixing GAAP and non-GAAP GM across periods of the same trend chart — distorts comparability.
- Hiding cloud credits as a permanent COGS reduction — when the credit period ends, GM "drops" without any business change.
Related KPIs
sales.total_revenuesales.arrsales.cac_payback_periodoperations.rule_of_40sales.growth_rate_yoy
Source
KBCM/Sapphire SaaS Survey 2024 (15th Annual) · section: Gross Margin — published 2024-09-01.
Why does this cite KBCM/Sapphire SaaS Survey 2024 (15th Annual)? Read the ontology methodology for the published vs editorial tier system, attribution rules, and dispute process.
Industry benchmark
A reference distribution sourced from KBCM/Sapphire SaaS Survey 2024 (15th Annual) (2024):
| Percentile | Value |
|---|---|
| 25th | 65% |
| Median | 72% |
| 75th | 81% |
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
- Finance
Machine-readable
- This KPI as JSON:
/api/ontology/sales/gross_margin.json - All Sales KPIs:
/api/ontology/sales.json - Full catalog:
/api/ontology/index.json
Expansion CAC Ratio
Fully-loaded S&M plus Customer Success expense attributable to expansion divided by expansion CARR generated in the period. Per SMSB, the efficiency read on the upsell / cross-sell / land-and-expand motion. Distinct from the new-logo CAC ratio because the cost base often includes CSMs whose primary metric is retention but whose secondary metric is expansion — boards expect to see that allocation called out. Common pitfall: excluding CS comp entirely understates the true cost of expansion; including all of CS overstates it. The SMSB standard prescribes a documented allocation rule (typically tied to expansion-quota OTE share). — Sales KPI anchored to SaaS Metrics Standards Board.
Growth Rate (YoY)
Year-over-year percentage growth in ARR (or recognized revenue, if explicitly anchored) — comparing the current period to the equivalent period 12 months prior. The single most-watched investor metric and the largest single driver of SaaS valuation multiples. Common pitfall: comparing to the prior quarter (QoQ) and reporting it as "growth rate" — boards and investors mean YoY unless explicitly noted otherwise. Anchored to KBCM/Sapphire SaaS Survey 2024 §YoY ARR Growth for cross-company benchmarking. — Sales KPI anchored to KBCM/Sapphire SaaS Survey 2024 (15th Annual).