Gross Margin
Revenue minus cost of goods sold, as a percentage of revenue. Whether the business model scales.
What it measures
Revenue less the cost of delivering it, as a percentage of revenue. In software the arithmetic is easy and the classification is where the judgement lives.
What belongs in cost of revenue
| Cost | Usually in? | The argument |
|---|---|---|
| Hosting and infrastructure | Yes | Directly consumed by delivering the product |
| Third-party services in the product | Yes | Passed through to the customer |
| Support | Yes | Required to keep customers running |
| Customer success | Partly | Retention portion yes; expansion portion is a sales cost |
| Onboarding and implementation | Usually | Required before the customer gets value |
| Sales and marketing | No | Cost of acquiring, not of delivering |
Source: Conventions summarised here
Why this is a revenue operations problem, not only a finance one
Using it
Agree the classification once, write it down, and keep it stable. Comparability over time matters more than picking the theoretically perfect boundary.
Compute margin per segment. A segment needing heavy implementation can be near-zero margin while the blended figure looks healthy.
Recompute after any pricing or packaging change, since both move the denominator without touching the cost base.
Feed the result into LTV and payback rather than using revenue there.
How to compute it for a software business
Decide what sits in cost of revenue and document it: hosting, third-party licences embedded in the product, support, and the delivery portion of customer success.
Treat professional services separately. Blending low-margin services into product margin produces a figure that describes neither.
Exclude sales and marketing. Those are operating costs, not cost of revenue, and including them turns gross margin into something closer to operating margin.
Check the treatment of customer success explicitly — it is the single most contested line, and where it lands moves the figure by several points.
Recompute after any material infrastructure change. Hosting costs move with architecture, and margin assumptions made two years ago frequently no longer hold.
Where it misleads
Gross margin is highly sensitive to where the customer success boundary is drawn, and that boundary is a judgement rather than a rule.
It is a period figure and can be flattered by deferring maintenance or under-supporting customers, both of which cost more later.
Comparisons across companies are frequently invalid because the cost-of-revenue definition varies so widely.
High gross margin says nothing about whether the business can acquire customers economically — that is a different question with a different metric.
RELATED TERMS
Burn Multiple
Net cash burned divided by net new ARR added — how much cash is consumed to produce a unit of recurring revenue.
CAC Payback Period
How long it takes for a customer's gross profit to repay the cost of acquiring them. The bridge between sales efficiency and cash flow.
LTV:CAC Ratio
Lifetime value divided by acquisition cost. Whether a customer returns more than they cost to win.
COMMON QUESTIONS
- What counts as cost of revenue in SaaS?
- Hosting and infrastructure, third-party services embedded in the product, support, and the portion of customer success required to keep customers running. Sales and marketing are not cost of revenue; onboarding usually is.
- Why does gross margin matter for revenue operations?
- Because LTV, payback period and every efficiency ratio should be computed on margin, not revenue. Using revenue overstates all of them, often by a wide margin in a service-heavy business.
- Should customer success sit in cost of revenue?
- The part required to keep customers working, yes. The part driving expansion is closer to a sales cost. If the team does both and you cannot separate them, say which convention you used — the choice moves the number materially.
- What is a good SaaS gross margin?
- Software businesses typically run high because delivery cost does not scale with revenue. A materially lower figure usually means the product needs human effort per customer, which is a scaling constraint rather than an accounting quirk.
FURTHER READING
Learn how to apply this: RevOps 101: Revenue Operations Foundations
Definitions are the vocabulary. The courses are where you learn to operate it, with the interactive audit tools.
See the course