SaaS COGS: A Startup’s Guide to Cost of Goods Sold

Cost of Goods Sold (COGS) is the total cost of delivering your product or service to customers who have already bought it. Understanding it is critical because it directly determines gross margin, a key signal of your company's economics as you scale revenue. Yet, many companies misclassify expenses like support, hosting, payment processing, or embedded vendor costs, which can meaningfully swing gross margin and lead to worse decisions about pricing, hiring, and growth.

This guide is for founders, finance leaders, and ops teams at B2B SaaS startups. It covers what belongs in SaaS COGS, what doesn't, why it matters for decisions, how your cost profile shifts as you grow, and what healthy margins look like at each stage.

What COGS Actually Means

COGS in a recurring revenue company is about what it costs to run and support the products and services you already sold, not what it costs to build new product. SaaS company income statements often refer to COGS as “cost of revenue,” and many companies use “COGS” and “cost of revenue” interchangeably for the cost of running and supporting the products and services they have already sold.

The reason COGS exists as a separate line from operating expenses is that these costs scale roughly in line with revenue, regardless of business type. A manufacturer sells more units, and raw materials and production labor go up. A SaaS company adds more customers, and hosting and support costs go up. In SaaS, while there are no raw materials or assembly labor, your COGS is hosting infrastructure, third-party APIs, and the support team keeping the product running for customers.

Where SaaS separates itself is in its structural cost efficiency. Because software delivery is digital, the cost of delivering each additional unit is usually limited to incremental infrastructure and support rather than physically manufacturing and shipping another unit. That is why software businesses often have higher gross margins than physical goods businesses: the cost of delivering what you already sold is relatively low, while most spend sits in operating expenses like Sales & Marketing.

Where SaaS COGS Shows Up

The common misconception is that recurring revenue companies don't really have a “cost of goods sold.” They do. Your hosting infrastructure, the third-party APIs embedded in your product, your support team helping customers use what they've already purchased: these are all costs of delivering the service. They look different from a manufacturer's COGS, but they have the same meaning on your income statement: the direct cost of delivering what you already sold.

According to SaaS Capital, which has reviewed thousands of SaaS financial statements, Generally Accepted Accounting Principles (GAAP) doesn't clearly define what should be included in COGS. Each company must use its own judgment, which is also why so many founders get it wrong.

What Belongs in COGS vs. Operating Expenses

Your gross margin is only as credible as what is classified as COGS (or cost of revenue). A common error in early-stage recurring revenue companies is underloading it by pushing delivery costs into operating expenses. Misclassifying costs between COGS and operating expenses directly inflates or deflates your gross margin. Companies often unintentionally inflate gross margin by under-burdening COGS, as Vista Point Advisors notes, which makes gross margin look better than it actually is. At the extreme, as SaaStr puts it, “Whatever you do, don’t present 95%+ gross margins. That just means you’re leaving things out.”

A Practical Classification Cheat Sheet

The general rule: if a cost supports delivering your service to existing customers, it belongs in COGS. If a cost supports growth, new features, selling to new customers, or general operations, it belongs in OpEx.

Costs that belong in COGS (cost of revenue):

• Hosting and cloud infrastructure (AWS, Azure, GCP) for production environments serving customers
  
  • Note: development and staging environments are R&D (the work your engineers do to build and improve the product), not COGS
• Third-party software and APIs embedded in your core product
• Customer support focused on helping existing customers use what they've already purchased
• DevOps and platform maintenance keeping production systems running
• Payment processing fees (Stripe, ACH processing) directly tied to collecting revenue
• Implementation and onboarding when it's a standard part of service delivery

Costs that belong in operating expenses (OpEx):

• Sales: Sales commissions and marketing (always OpEx, regardless of deal size)
• R&D:
  
  • R&D and engineering building new product features
  • Development and staging infrastructure (this is R&D, not service delivery)
• General and administrative (G&A): rent, HR, legal, and executive compensation

One classification that trips up many founders is customer success (CS). The distinction hinges on function. If your CS team focuses on retention, onboarding, and helping customers use what they've already purchased, those costs belong in COGS. If your CS team has sales quotas or focuses on upselling and expansion revenue, those costs belong in Sales & Marketing (OpEx). At an early-stage company where one person does both, estimate the time split and allocate costs proportionally.

A related note on professional services: if you offer paid implementation or consulting alongside your core subscription, track that revenue and those costs separately. Professional services typically carry significantly lower margins than SaaS subscriptions, where top-quartile companies reach 80%+ gross margin, and combining them into a single figure obscures the economics of both. Your SaaS margins are usually the stronger number, and a blended figure only dilutes that.

Why Gross Margin and COGS Get Investor Attention

Founders should care about COGS because gross margin is one of the fastest ways to understand the economics of delivering the product, and it’s a practical input to decisions on pricing, support and success staffing, and whether you can afford to invest more in Sales & Marketing for growth.

Investors care for a related reason: gross margin is a quick test of whether a recurring revenue company can scale, and COGS classification is what makes that number comparable across time and across companies. Revenue growth shows demand. Gross margin shows what you keep after delivering the product.

The formula is straightforward. Subtract Cost of Revenue from Revenue to get Gross Profit. Divide Gross Profit by Revenue to get your Gross Margin percentage. If you're at $1.5M in annual revenue with $300K in COGS, your gross profit is $1.2M, and your gross margin is 80%.

The most common classification error is understating COGS, which inflates your margins. For example, if you leave payment processing fees out of COGS, you're meaningfully overstating your gross margin. Some founders also exclude customer support or hosting to make margins look better, which, as Eagle Rock CFO notes, is misleading and will be caught in due diligence.

When that happens, the story you're telling investors doesn't match reality, and inconsistent classification between reporting periods is a red flag that can derail due diligence entirely. Investors look for a consistent, documented methodology that you can explain clearly, because both operators and investors care about trajectory and benchmarking, not just a snapshot.

How SaaS COGS Evolves as You Scale

COGS feels small at seed, then becomes a real management problem by $1M-$2M ARR. Hosting runs a few thousand dollars per month, you handle support yourself or with a part-time hire, and third-party API costs sit comfortably within free tiers. Your total COGS might represent 10-20% of revenue, and most of those line items barely register.

However, that cost changes faster than most founders expect.

By $500K-$1M ARR, infrastructure costs start scaling non-linearly. Database costs, compute resources, and storage demands require active management rather than passive monitoring. Third-party APIs cross free-tier thresholds, and per-call charges start adding up. You're likely making your first dedicated support hire.

By $2M ARR, the picture looks materially different:

• Hosting and infrastructure costs grow with usage and customer count, and require active cost management at this stage.
• You've likely made your first dedicated support or customer success hire, with headcount growing as customer count does.
• Third-party API fees now require vendor management.

Cost categories that were immaterial at seed can become meaningful at this stage, particularly support team headcount, production reliability and security work and third-party vendor costs that scale with customer usage. The founder who understood their cost profile early can make confident hiring, pricing, and infrastructure decisions, and the one who didn't will need to recategorize expenses before a board meeting or fundraise.

What Healthy SaaS Gross Margins Look Like

For most early-stage companies, gross margin benchmarks give you a quick read on whether you have a real cost-structure problem or a reporting problem. According to Benchmarkit's 2025 SaaS Performance Metrics report, the median total gross margin for SaaS companies is 77%. On pure software subscription revenue, the median rises to 79%, with top-quartile companies reaching 85% or above.

Investors typically expect 80%+ gross margins on pure SaaS subscription revenue, and where you fall within that range signals the scalability of your business. A few benchmarks to keep in mind:

• Below 70%: Requires a clear explanation. Investors will question whether the business model is fundamentally scalable.
• 70-75%: Acceptable, but leaves room for improvement.
• 75-80%: Competitive range.
• 80%+: Often described as strong for many "pure" SaaS products, with the caveat that product category and infrastructure intensity matter.

Some investors, like Jessica Bartos at Salesforce Ventures, cite 70%+ as a good baseline, with 85% being great.

Knowing where you fall relative to these benchmarks can inform how you evaluate the business. Higher gross margins generally give you more flexibility to invest in Sales & Marketing. If you're running below the median, it's worth understanding whether that reflects your delivery model or your reporting before drawing conclusions about your cost structure.

How to Make COGS Classification Repeatable

Accurate COGS categorization breaks down when the underlying inputs aren't tagged consistently: cloud and vendor invoices in one place, payroll in another, support time allocations not tracked at all. It also breaks down when roles that span functions like Customer Success aren't allocated with a repeatable approach. You can't separate what it costs to deliver the service from what it costs to sell it if you can't see the expense data clearly.

From Ad Hoc to Repeatable

A documented policy is the difference between a monthly close task and a forensic investigation. At minimum, write down three things: what you include in COGS, how you allocate mixed roles like Customer Success (including the time-split percentage), and how you handle edge cases like onboarding and professional services.

Tag expenses consistently in your accounting system from the moment they're incurred. When you add a new vendor, classify it immediately. When you make a CS hire, document the allocation. When your CS team's charter changes, update the split.

Classify COGS Right From Your First Invoice

COGS determines your gross margin, and gross margin is one of the clearest signals of whether a company’s delivery costs scale efficiently with revenue. Keep the core rule simple: cost of revenue captures the cost of delivering your service to existing customers. Everything else belongs in operating expenses. Classify based on function, document your methodology, and audit for the under-burdening mistakes that can make margins look better than they actually are.

As your cost profile evolves from seed to Series A, the founders who tracked SaaS COGS accurately from the start will have the clarity to make confident calls on hiring, pricing, and infrastructure. Getting investor-facing revenue metrics right follows the same logic.