SaaS · Gross margin done right: capitalized costs, hosting, and support allocation
Two SaaS (Software as a Service) companies post identical $50 million in annual recurring revenueannual recurring revenueAnnual Recurring Revenue (ARR) is the normalized, predictable revenue a subscription business expects to earn from active contracts over a single year.View full definition →. Company A reports 65% gross margingross marginGross margin is the share of revenue left after subtracting the direct cost of producing goods or services, expressed as a percentage of revenue.View full definition →. Company B reports 82%. They sell in the same product category, have customer bases of the same size and run on the same cloud provider. Operations don't explain the gap. Accounting choices about what lands in COGS (cost of goods sold) versus operating expenses do. Investors who don't trace this get fooled routinely.
Why gross margin is the SaaS scoreboard
Gross margin equals revenue minus COGS, divided by revenue. For software companies, it signals how efficiently the core product delivers value, before sales, marketing, and R&D (research and development) enter the picture.
Public SaaS benchmarks (2025 estimates, based on aggregated data from sources like Bessemer's State of the Cloud reports) cluster as follows:
- Best-in-class: 78 to 85% gross margin
- Healthy median: 70 to 75%
- Below average: under 65%, often flagging a services-heavy or infrastructure-heavy business
European SaaS companies often report slightly lower gross margins than US peers, commonly cited as 3 to 7 percentage points lower on average. Smaller scale (less negotiating leverage on cloud contracts) and higher relative support staffing costs in some markets explain part of this. Treat the gap as directional, not precise.
What actually belongs in SaaS COGS
COGS for a SaaS business typically includes:
- Hosting and infrastructure: AWS, Azure, or Google Cloud bills tied directly to running the product
- Customer support: salaries for support staff resolving product issues (not sales-related contact)
- Third-party licensing fees for embedded software or data feeds required to deliver the service
- Customer success, partially: only the portion tied to onboarding and technical enablement, not upsell activity
- Platform operations engineering (site reliability, DevOps keeping the live service running), plus amortization of capitalized software
The judgment calls live in items 2, 4 and 5. That's where Company A and Company B diverge.
The capitalized software lever
Under US GAAPUS GAAPThe standard set of accounting rules companies follow to prepare consistent, comparable financial statements, dominant in US reporting.View full definition → (Generally Accepted Accounting Principles) via ASC 350-40 for internal-use software, and under IFRSIFRSThe global accounting rulebook that governs how companies report financial results, used across the EU and 140+ jurisdictions.View full definition → (International Financial Reporting Standards, used across most of Europe) via IAS 38, companies can capitalize certain software development costs rather than expensing them immediately.
Capitalizing means the cost moves onto the balance sheet as an asset, then gets amortized (spread out) over future years, instead of hitting the income statement in full today. For a SaaS platform, that amortization usually lands in cost of revenue.
Worked example. Both companies spend $8 million this year on engineers who build and improve the platform that delivers the service. Both have $9.5 million of other cost of revenue (hosting, support, licences).
- Company A expenses the $8 million straight into cost of revenue. COGS = 9.5 + 8 = $17.5 million. Gross margin = (50 minus 17.5) / 50 = 65%.
- Company B capitalizes the $8 million and amortizes it over 4 years, so only $2 million hits cost of revenue this year. It also books $2.5 million of support headcount under sales and marketing (more on that below). COGS = 9.5 + 2 minus 2.5 = $9 million. Gross margin = (50 minus 9) / 50 = 82%.
Neither company is lying. Both can be inside the rules. Note what drives B's advantage, though. If B keeps capitalizing $8 million a year, amortization climbs toward $8 million by year four and the capitalization benefit shrinks. The boost is biggest for companies whose development spend is growing fast, which is exactly when investors pay the most attention to margin.
A third path also exists: expensing that engineering as R&D, below the gross margin line entirely. That flatters gross margin even more than capitalizing, and it is common. Read the policy note to see which bucket a company uses.
The 2025 change to US rules
In September 2025, FASB issued ASU 2025-06, which rewrites ASC 350-40. The old model tied capitalization to project "stages" (preliminary, application development, post-implementation), which fit waterfall projects poorly and agile teams worse. The new rule drops the stages. Companies start capitalizing once management has authorized and committed funding and it is probable the software will be completed and used as intended.
It is effective for annual periods beginning after 15 December 2027, with early adoption permitted. So in filings from 2026 through 2028 you will see a mix: some companies on the old model, some early adopters, and transition disclosures that can shift capitalized amounts year over year. A sudden jump or drop in capitalized software may reflect the rule change, not a change in engineering activity. See the FASB standard page for the text.
Support cost allocation: the other lever
Customer support classification also swings margin meaningfully.
Some companies put support headcount, including senior technical account managers who also influence renewals, into sales and marketing instead of COGS. Company B's $2.5 million above is this move. Support costs that are part of delivering the service end up below the line, and gross margin rises.
A rough rule used by sector analysts: if support cost as a percentage of revenue looks unusually low (under 5%) while gross margin looks unusually high (above 85%), check whether support headcount got reclassified elsewhere.
Where to actually look
For public companies, the 10-KKThe average number of new users each existing user generates through referrals. Above 1.0, growth compounds on itself and becomes exponential.View full definition → (annual report filed with the US Securities and Exchange Commission, or SEC), or the 20-F or annual report for European issuers under IFRS, has a cost of revenue note, sometimes broken into subcategories. Not all companies disclose this granularly. When they do, compare:
- Hosting cost as % of revenue (typically 5 to 15% for efficient SaaS models, per industry estimates)
- Capitalized software additions each year (cash flow statement, investing activities)
- Amortization period in the accounting policy footnotes (commonly 2 to 5 years)
- Whether the company has adopted ASU 2025-06 early, and any transition effect it reports
The SEC's EDGAR database is free and lets you pull 10-Ks directly to check these footnotes yourself.
Knowledge check
1. Two SaaS companies with identical revenue report very different gross margins despite similar operations and infrastructure providers. What is the most likely explanation?
2. Why does gross margin serve as a particularly meaningful 'scoreboard' for SaaS companies specifically?
3. A customer success team spends part of its time on technical onboarding and part on upsell conversations. How should this team's costs typically be treated for gross margin purposes?
4. Select ALL correct answers about costs that typically belong in SaaS COGS.
Select all the correct answers.
5. Select ALL correct answers about why an investor should be cautious when comparing gross margins across SaaS companies.
Select all the correct answers.
A quick sanity-check ratio
When comparing two SaaS companies, a useful cross-check is:
Adjusted gross margin = (Revenue minus hosting minus all support minus cash spent this year on building and running the live product) / Revenue
This treats capitalized amounts as if they were expensed immediately and pulls reclassified support back in. It's a rough normalization, not a GAAP or IFRS metric, but serious analysts do this informally when comparing companies with different policies.
Applied to Company B: start from $9 million of COGS, replace the $2 million amortization with the full $8 million cash spend (+$6 million) and add back the $2.5 million of support. Adjusted COGS = $17.5 million, so adjusted gross margin = 65%, the same as Company A. The 17-point gap was entirely accounting.
US versus Europe, briefly
IAS 38 requires capitalization of development costs once criteria such as technical feasibility and intent to complete are met, and practice under it has often been seen as more permissive than the old US GAAP stage model. ASU 2025-06 moves US rules somewhat closer to a probability-based test, though the two frameworks still differ. Actual practice depends heavily on company judgment and auditor scrutiny. Don't assume a European SaaS company's margin gap versus a US peer reflects operations until you've checked the capitalization policy.
🎬 [VIDEO: "SaaS Metrics that Matter" - youtube.com/@saastr - SaaStr's channel regularly covers gross margin and COGS breakdowns with real operator perspectives, useful for seeing how practitioners discuss these tradeoffs]
Key Takeaways
- Gross margin gaps between SaaS companies often come from classification choices (what goes into COGS versus opex), not operational efficiency.
- Capitalizing development costs under ASC 350-40 (US) or IAS 38 (IFRS) defers cost and lifts current gross margin, most strongly when development spend is growing. Expensing engineering as R&D lifts it too.
- ASU 2025-06 (issued September 2025, effective for annual periods beginning after 15 December 2027, early adoption allowed) replaces the US stage-based capitalization model, so expect inconsistent comparisons for a few years.
- Moving support headcount into sales and marketing is a second common lever for inflating reported margin.
- Best-in-class SaaS gross margin sits around 78 to 85% (2025 estimate). Recompute an adjusted margin, with cash development spend and all support included, before trusting headline numbers.