Blog
→
AI Spend Management
October 16, 2026

SaaS gross margin

Written by:
Christophe Sion
CEO
Share on XShare on LinkedInShare on FacebookShare by email
In this article
Ready to get started?
Get full visibility into your spend in minutes.
Get started for free

SaaS gross margin

SaaS gross margin tells you how much revenue is left after the direct cost of delivering your product, which makes it a core metric for managing startup finances. The core formula is simple: (revenue - cost of revenue) / revenue × 100. If your company makes €100,000 and it costs €25,000 to deliver the paid service, your gross margin is 75%.

The catch is classification. This number is only useful if cost of revenue is defined correctly and you do not lump subscriptions, services, and other revenue streams into one blurry percentage.

As a practical benchmark, many SaaS businesses land somewhere around 70% to 85%. That range is a guide, not a law. Stage, infrastructure intensity, product complexity, and services mix all change what “good” really looks like.

Get cost of revenue right before you benchmark anything

Before you compare yourself to any SaaS benchmark, decide what belongs in cost of revenue. A useful rule is this: if the cost disappeared and customers could no longer receive the paid service, it usually belongs closer to cost of revenue.

  • Hosting, cloud, data, AI usage, delivery tooling (usually included): These are direct delivery costs. Without them, the product does not run for paying customers.
  • Direct support, onboarding, implementation, professional services delivery (usually included): Include the labor and tools needed to fulfill the paid service. Track services separately when possible.
  • Engineers who keep the live product running (DevOps, SRE) and operations staff (often included): If the role exists to keep the live product working for customers, it is usually closer to cost of revenue.
  • Sales and marketing (usually excluded): Customer acquisition spend is an operating expense.
  • G&A and broad product R&D (usually excluded): Company overhead and general product development should not distort gross margin.
  • Customer success or mixed roles (gray area): Split retention and adoption work from upsell activity, then apply fully loaded allocations consistently.

Calculate it cleanly in four steps

First separate gross profit dollars from gross margin percentage. Gross profit is revenue minus cost of revenue. Gross margin is that result expressed as a percentage of revenue.

  1. Define revenue for one period. Use the same month, quarter, or year throughout the calculation.
  2. Subtract only direct delivery costs. Include the costs tied to serving paying customers in that same period.
  3. Run the math. If revenue is €120,000 and direct delivery costs are €30,000, gross profit is €90,000 and gross margin is 75%.
  4. Track it monthly and on a rolling basis. That helps you spot shifts in vendor, support, or delivery costs before they become a pattern.

Split subscription, services, and other revenue before you judge the number

A single blended margin hides too much when your business sells more than software subscriptions. If you also charge for onboarding, implementation, professional services, payments, hardware, or usage-based add-ons, one company-wide percentage can make a healthy subscription engine look weak, or make a weak service line disappear inside a strong software model.

Calculate subscription gross margin and services gross margin separately. Use only the revenue and direct costs tied to that stream. That gives you a cleaner read on what scales well and what needs attention.

Lower-margin services are not automatically bad. They may help adoption, speed up time to value, or improve retention. But founders still need to see that trade-off clearly.

Your P&L and chart of accounts should support this from the start. Separate revenue lines. Separate direct cost accounts. Tag spend consistently. Tools like Husk can help by tying AI vendor costs to the features and customers they serve, which cuts down manual rework at month-end.

Why founders and finance teams care so much about this metric

Gross margin shows how much revenue is left after delivery costs to fund everything else. That includes sales, marketing, product development, finance, and company overhead. If you generate €1 of revenue at an 80% gross margin, you keep €0.80 before operating expenses. That is the money available to grow the business, extend startup runway, and move toward profitability.

It is also one of the clearest signals of scalability. In a strong SaaS model, revenue should grow faster than direct delivery cost. If direct costs rise almost one-for-one with revenue, margin stays pressured and scale becomes less attractive. That usually points to issues in infrastructure design, support intensity, onboarding effort, or too much service-heavy revenue.

Investors care for the same reason. Growth is more valuable when it carries healthy gross profit behind it. Gross margin helps them assess business quality, pricing power, and operational discipline. A company growing quickly at weak gross margins may still have a hard time converting growth into a durable business.

Internally, the metric sharpens decisions. It tells you whether pricing needs work, whether services should be repriced or narrowed, whether support needs more automation, and which customer segments deserve more focus. For finance teams, it turns a vague question, “Are we scaling well?” into a measurable one.

What good looks like: SaaS gross margin benchmarks

A common benchmark range for SaaS gross margin is 70% to 85%, but that only helps if you compare like with like. ARR stage, target market, implementation burden, infrastructure intensity, product complexity, and revenue mix all change the picture.

  • Below 70% (often worth a deeper review): May be acceptable in infrastructure-heavy, AI-heavy, or service-heavy models, but pricing and delivery efficiency need scrutiny.
  • Around 70% (respectable midpoint): Common in earlier-stage businesses or companies with more implementation and support work.
  • 75% to 80% (strong for many SaaS companies): Often seen in software-led models with improving onboarding and support efficiency.
  • 80%+ (excellent if it is durable): More typical for mature, pure-software businesses with low-touch delivery and disciplined infrastructure costs.

One more rule matters: compare blended company gross margin to blended peers, and subscription gross margin to subscription peers. A services mix can make the company-level number look lower without meaning the core software business is weak.

How AI features change SaaS gross margin

AI features change the math because their cost sits in cost of revenue and grows with every request. A traditional software feature costs little to serve once it is built. An AI feature charges you each time a customer uses it, so usage growth that would lift margin in a classic SaaS product can hold it flat or push it down. Products with heavy AI usage often run below the 70% to 85% range for that reason.

The fix starts with visibility: AI cost per customer, per feature, and per plan, set against the revenue each one brings in. That shows which customers or features dilute margin and whether pricing needs a usage-based element. AI unit economics for SaaS covers the method, and Husk’s AI spend management tracks those costs live, so margin changes show up before the month closes.

Gross margin vs contribution margin: know when each matters

Contribution margin is the next layer after gross margin. It looks at what revenue is left after direct delivery costs and other variable costs tied to growth. Gross margin is the better operating metric for judging delivery economics and benchmarking SaaS quality. Contribution margin is the better unit-economics lens when onboarding intensity, support burden, or variable sales costs differ. In AI-heavy or infrastructure-heavy products, use both. Similar gross margins can hide very different contribution profiles.

Improve gross margin from the cost side first

Start with direct costs you can actually change when improving spend management. This is usually where the fastest margin gains show up.

  • Audit the biggest cost buckets. Look first at infrastructure, cloud or AI vendors, support delivery, onboarding effort, and service labor. Small improvements in large categories beat heroic savings in tiny ones.
  • Reduce one-to-one delivery work. Better documentation, self-serve setup, product education, workflow automation, and standardized implementations stop support and onboarding from scaling linearly with revenue.
  • Fix low-margin service work deliberately. Decide whether to automate it, reprice it, scope it down, or keep it only where it clearly improves adoption or retention.
  • Make cost leakage visible during the month. Better spend tagging, real-time visibility, and advanced spend forecasting techniques help you catch delivery costs early. That matters even more when cloud and AI costs move faster than the accounting close.

Then improve it from pricing, mix, and retention

Once the cost base is under control, the next gains usually come from revenue quality.

  • Revisit pricing and packaging. If your price no longer matches customer value, margin suffers. Tiering, premium add-ons, usage-based elements, or well-timed price increases can lift gross profit without adding much delivery cost.
  • Grow through existing accounts where possible. Upsell and cross-sell revenue often carries better margin than new, service-heavy business because onboarding is lighter and customer context already exists.
  • Reduce churn and tighten onboarding. Lost recurring revenue makes fixed delivery costs harder to absorb. Stronger onboarding protects retention and improves the blended margin profile over time.
  • Scale the best revenue lines, not every line equally. Prioritize customer segments, markets, and offers with better long-term margin instead of chasing volume everywhere.

Quick answers to the SaaS margin questions that come next

Once gross margin is clear, most follow-up questions are really about three different things: delivery economics, total-company profitability, and growth efficiency. Keeping those separate makes the numbers far more useful.

Is a 70% gross margin good for a company?

For many SaaS companies, yes, 70% is respectable. But it is not an automatic gold star. It looks stronger in an early-stage business, an implementation-heavy model, or an infrastructure-heavy product than it does in a mature, pure-software company. The right comparison is not “best-in-class SaaS” in general. It is peer companies with a similar stage, pricing model, service mix, customer profile, and delivery complexity.

What is the average SaaS profit margin?

This question is about net profit margin, not gross margin, so the two should not be used interchangeably. Gross margin measures delivery economics. Net profit margin measures what is left after all operating expenses, financing costs, taxes, and the rest of the company cost base. Many early-stage SaaS businesses have healthy gross margins but low or negative net margins because they are still investing heavily in growth. Use each metric for its own job.

What is the rule of 40 in SaaS?

The Rule of 40 says a SaaS company’s revenue growth rate plus profit margin (usually EBITDA or free cash flow margin) should equal 40% or more. It is a high-level efficiency benchmark, not a replacement for gross margin. Gross margin still matters because it determines how much gross profit is available to fund growth in the first place. A company can have strong gross margin and still miss the Rule of 40 if growth is weak or operating discipline is poor.

What is the 3 3 2 2 2 rule of SaaS?

The 3 3 2 2 2 rule is a separate SaaS growth heuristic, not a gross-margin formula. It describes a growth path often called T2D3: once a company reaches meaningful recurring revenue, it triples annual recurring revenue (ARR) for two years in a row, then doubles it for three years. Few companies sustain that pace, so treat it as a venture-scale ambition. In practice, pair any growth heuristic with gross margin, retention, and burn rate before drawing conclusions about business quality.

‍

Same model, different bill: direct APIs, clouds and routers

The same model can produce a different bill depending on where you buy it, because LLM pricing is several markets stacked on top of each other: model makers selling direct, managed cloud platforms, routing services and hosts that run open models. Each route changes how pricing, access and governance work.

Common buying routes

  • Direct provider API: best for access to the newest models, simpler pricing and fast experimentation. Total cost can rise through separate billing per vendor, fewer controls across providers and no built-in backup if one vendor fails.
  • Managed cloud platform: best for enterprise procurement, control over where data is processed, security and governance. Total cost can rise through platform-specific pricing, regional price differences and possible markup.
  • Router or marketplace: best for switching models quickly, one connection to many vendors and automatic fallback. Total cost can rise through markup, different rounding and extra monitoring or routing fees.
  • Open-model hosting provider: best for low token prices on selected workloads and a wide choice of models. Total cost can rise through uneven quality, missing features and host-specific limits.
  • Self-hosted open models: best for predictable high volume and heavy customization. Total cost can rise through hardware costs, servers sitting idle, engineering time and responsibility for uptime.

Direct provider APIs

Direct APIs are usually the cleanest place to start a comparison. Pricing is easier to read, new models arrive there first, and there is no extra commercial layer between you and the model maker. For testing the newest models or moving quickly, this route gives the clearest view of raw model economics.

Managed cloud platforms

Azure, AWS Bedrock, Vertex AI and similar platforms add considerations beyond price. A company may accept a higher rate because the route fits its procurement process, regional deployment, data-handling policy, network setup or existing cloud commitments, such as an annual spend already agreed with AWS. For many finance and compliance teams that trade-off makes sense, as long as it is measured explicitly.

You deserve
financial clarity.
Get full visibility into your company’s finances in minutes.
Get started for free