Most SaaS founders bury sales and R&D costs inside COGS by accident. That inflates margin on paper. It deflates fast once a lender rebuilds your P&L.
What Counts as SaaS COGS
SaaS COGS is narrower than most founders assume. It only covers costs tied directly to delivering the product a customer already pays for.
Three buckets make up the bulk of it. Cloud hosting for the live product comes first. Third-party API and data costs baked into the service come second.
Support and success staff who keep existing accounts running come third. Payment processing fees belong here too. So does software licensed just to run the product.
What doesn't belong: sales commissions, marketing spend, and engineering salaries for new feature work. Those are operating expenses. They grow the business, not deliver what's already sold.
The MRR a customer pays each month is the revenue side of this equation. COGS is what it actually costs you to keep that customer served, every single month.
DevOps contractors hired specifically to run production infrastructure fit inside COGS too. A contractor building a brand-new feature does not. It doesn't matter if they bill through the same vendor.
Data storage costs split the same way. Storing customer data that powers the live product is COGS. Storing internal analytics or BI dashboards for your own team is overhead.
Some finance teams also allocate a slice of security and compliance spend to COGS. That's defensible when the spend protects customer data in production. It's not defensible for general corporate risk work.
Common Misclassification Mistakes
The most frequent error is dumping all engineering payroll into operating expenses, full stop. That undercounts COGS and overstates margin.
Engineers on uptime, incident response, or infrastructure maintenance are delivering the product. Their time belongs in COGS, at least proportionally.
That's the reverse mistake. Founders lump success staff entirely into COGS, reps included. Even the ones running upsell calls all week.
Split by function. A support engineer fixing a live bug is COGS. The same person building next quarter's onboarding flow is not.
Free-tier hosting costs get missed constantly too. Those users burn real infrastructure dollars and generate zero revenue.
Exclude them, or your per-account delivery cost looks lower than it really is. Annual software licenses cause a similar problem. Expensing one lump instead of spreading it skews a quarter's margin.
Shared infrastructure creates a subtler trap. A single database cluster might serve both production traffic and an internal reporting tool.
Founders often skip the split and call the whole bill COGS. That overstates cost of service and understates margin. It's the opposite mistake, and it's just as misleading to a lender.
One-time migration costs cause confusion too, like moving from one cloud provider to another. Treat that as a project cost, not recurring COGS. It won't repeat every month.
Founders also mix up capitalized software costs with COGS, treating them as the same bucket. Some internal tools get capitalized on the balance sheet instead. They aren't expensed as COGS in the period they're built.
That's fine, but keep the policy consistent. Switching methods between funding rounds looks like margin manipulation. Nobody has to mean it that way for a lender to notice.
Cost Classification
SaaS COGS vs. Operating Expense
Where common line items actually belong on the income statement.
Illustrative classification guide based on standard SaaS finance practice. Actual treatment depends on your accountant and specific cost structure.
Hosting Costs in COGS
Hosting is usually the biggest SaaS COGS line. It's also the most commonly miscounted one.
Here's the rule. Infrastructure that serves paying customers is COGS. Infrastructure that serves your own team is not.
Staging environments, internal dashboards, and engineering sandboxes still run on cloud infrastructure. That spend belongs in R&D or overhead, even though it hits the same bill.
Most teams fix this by tagging cloud resources by environment. Production gets one tag. Staging and internal tools get another, and the monthly bill splits itself automatically.
Skip the tagging, and founders usually just guess a rough percentage. That guess gets wildly wrong once a company scales past a handful of side environments.
Autoscaling makes this messier. One enterprise customer's traffic spike can double your hosting bill for a week.
That spike is still 100% COGS. It just looks like an anomaly on the P&L.
Reserved-instance discounts complicate this too. A large upfront commitment can lower the per-unit hosting cost for years.
Spread that commitment across its full term. Don't expense the whole thing in the month you signed. One bad month of COGS will spook a lender.
One more wrinkle: multi-cloud. Some teams run redundant infrastructure across two providers for reliability.
That roughly doubles the hosting line for the same customer base. It's a real cost of delivery, not a red flag. Just be ready to explain it.
Quick Check
See what you qualify for in under 3 minutes.
No hard credit pull. Revenue history and gross margin are what qualify you.
Check Capital Eligibility →Gross Margin and COGS
Gross margin SaaS calculations only mean something if the COGS underneath is honest. Revenue minus accurate COGS is what tells you how the business really performs.
According to Esade Business School's working-capital framework, cost classification is not a formality. It shapes whether reported liquidity and profitability reflect reality, or just an accounting choice.
That framework applies directly here. Two SaaS companies with identical revenue can report very different gross margin figures. The only difference is where they draw the COGS line.
For the full walkthrough of how these two figures diverge, see our guide to gross margin vs. contribution margin.
RSM US tracks this shift. It's one of the largest global accounting and consulting firms.
Its SaaS financial metrics coverage points to finance teams moving past headline MRR. They're shifting toward committed MRR, which accounts for expected churn and plan changes.
The same shift is happening with margin. Lenders now want gross margin broken down by cohort, not blended across the whole base. A single company-wide number can hide a segment losing money on every account.
SaaS COGS composition varies by company, so no single benchmark fits everyone. Still, the direction holds. Reporting gets more granular, with less patience for averages that flatter the top line.
The "Rule of 40" gets thrown around a lot in SaaS finance circles. It says growth rate plus profit margin should add up to roughly 40% or more.
That framework only works if the margin half is real. A company hitting 40% through misclassified COGS is fooling itself, not investors or lenders.
Expansion revenue from existing customers complicates margin too. Upselling a current account costs far less to deliver than acquiring a brand-new one.
Some finance teams blend that cheaper delivery cost into overall COGS without separating it. That flatters blended margin. It also hides how dependent a company still is on new acquisition.
The pricing structure behind that revenue matters too. Usage-based and per-seat plans tend to load costs differently than flat pricing does. See our breakdown of SaaS pricing models for how each one lands on COGS.
How Accurate Gross Margin Affects Underwriting
Revenue-based lenders don't just look at how much money comes in. They look at how much survives the cost of serving each customer.
A business burying support costs elsewhere can report 80% gross margin. That looks stronger than it is. Once a lender rebuilds the P&L, that number drops fast.
Lenders reviewing SaaS deals typically want gross margin above 60%. That's the threshold for favorable terms on a revenue-based loan. Below it, expect a smaller advance or a higher factor rate.
ARR alone misleads here. A company with strong ARR and thin margin can get a worse offer. A smaller company with clean books does better.
CAC matters too, but it's a separate line. A business can post great margin and still burn cash. That happens when acquisition costs never pay back.
A concrete example helps. Take a SaaS business at $80,000 MRR with a clean 70% margin.
It might see 2 to 3x MRR offered. Restate that margin to 45% once costs get counted right, and the multiple usually shrinks.
The factor rate rises too. The lender is now pricing more real risk.
The practical move here is simple: rebuild your COGS classification before you apply. Clean numbers in mean better terms out.
See our guide on calculating your true cost of capital multiple. It shows how factor rate stacks against a distorted margin picture. For SaaS founders weighing options, our 2026 SaaS revenue financing comparison helps.
Restate Your Own Numbers
COGS Reclassification Margin Impact Calculator
Enter your MRR and reported COGS, then add any costs you suspect are currently misclassified as overhead (support staff on live product, free-tier hosting, shared infrastructure) to see your restated margin and where it lands against the 60% lender threshold.
Formula used: Gross Margin = (MRR − COGS) ÷ MRR. Restated COGS = Reported COGS + Misclassified Costs Added Back.
Illustrative estimate only, using the standard gross margin formula. Actual underwriting terms depend on the lender, industry, and full financial picture — not this calculator alone.
- SaaS COGS covers hosting, support tied to delivery, third-party API costs, and payment processing.
- Sales, marketing, and new-feature engineering belong in operating expense, not COGS.
- Production hosting is COGS. Staging and internal tool hosting is not.
- Free-tier infrastructure costs should be excluded when calculating per-account margin.
- Lenders typically want gross margin above 60% before offering favorable RBF terms.
- Cohort-level margin reporting is replacing blended, company-wide averages.
- Clean COGS classification before applying usually leads to better financing terms.
Frequently Asked Questions
SaaS COGS covers the direct cost of delivering your product. That means hosting, third-party API fees, and support staff who keep paying accounts running. Payment processing counts too.
It excludes sales, marketing, and product-development salaries.
It depends on the role. Support staff who troubleshoot the live product and keep existing accounts functioning belong in COGS.
Account managers focused on upsell or renewal belong in sales and marketing instead. Their work drives new bookings, not service delivery.
Gross margin shows how much of every revenue dollar survives serving a customer. Lenders use it to judge whether a business can absorb a revenue-share payment without strain.
A business misclassifying overhead as COGS can look artificially strong. It fades fast. A rebuilt number tells the truth.
Production hosting for your live product belongs in COGS. Hosting for internal tools, staging, or sandboxes does not. That infrastructure never touches paying customers.
Splitting cloud bills by environment is the only reliable way to separate the two.
Lenders reviewing revenue-based financing typically want gross margin above 60%. That's the bar for favorable terms.
If restated COGS drops your margin below that line, expect a smaller advance. A higher factor rate is likely too. Some lenders will ask for a full P&L rebuild first.
RSM US — Key Financial Metrics for SaaS Companies — RSM Technology Blog
Ready to check your options?
Rev Boost Funding connects operators with independent financing partners. We are not a lender.
Affiliate partnerships present.
Check Capital Eligibility → You Finished This — Add as Preferred Source