Gross Margin Analysis for SaaS: Benchmarks and Best Practices

What Is Gross Margin and Why It Matters

Gross margin is the percentage of revenue remaining after subtracting cost of goods sold (COGS). For SaaS, COGS typically includes cloud infrastructure (AWS, GCP), payment processing fees (Stripe), and any direct costs of serving customers. If you have $100K revenue and $15K in COGS, your gross margin is 85%. This metric is critical because it shows how much revenue is available to cover operating expenses (sales, marketing, engineering) and eventually profit.

Investors obsess over gross margin for good reason. A company with 60% gross margin needs much more revenue to be profitable than a company with 85% gross margin. Gross margin also indicates pricing power and competitive advantage. If your gross margin is declining while competitors stay flat, you might be losing pricing power. If your gross margin increases, you've found operational efficiencies or better unit economics.

SaaS Gross Margin Benchmarks by Stage

Seed-stage SaaS startups typically operate at 50-70% gross margin. Why so low? Because they're inefficient at scale. Your infrastructure spend might be fixed cost spread across few customers, or you have intensive support requirements. As you scale, gross margins typically increase. Series A SaaS companies average 70-75% gross margin. Series B+ companies often achieve 80-90% gross margin. This improvement comes from leverage: infrastructure costs become negligible at scale, payment processing fees decrease with volume discounts, support becomes more efficient.

However, benchmarks vary by SaaS type. Horizontal SaaS tools (like Slack or Notion) with minimal infrastructure requirements hit 85%+ margins early. Vertical SaaS with custom implementations might stay at 60-70% for longer. Usage-heavy products (like video streaming platforms) have higher COGS. Infrastructure-as-a-service products have much lower margins because they're CPU-intensive. Know your category's benchmarks.

Calculating COGS and Gross Margin Accurately

Most founders underestimate COGS. Start by listing all direct costs: (1) Cloud infrastructure, (2) Payment processing, (3) APIs and data sources, (4) Customer support (if outsourced), (5) CDN and bandwidth, (6) Direct labor if you have a cost-of-service team. Then allocate a percentage of engineering labor to support (especially in early stage when engineers fix customer issues).

Don't include general overhead in COGS. Salaries for your CEO, CFO, and most engineers are operating expenses, not COGS. The blurry line is often customer support engineers and customer success managers. If they're directly servicing customers, consider them COGS. If they're improving the product generally, they're R&D. Most founders conservatively put 30-50% of customer support labor into COGS.

The AWS Trap: Infrastructure Costs at Scale

A common mistake: early-stage founders massively underestimate infrastructure costs because they haven't scaled. You might spend $500/month on AWS today. You assume COGS will stay at 5% of revenue. But as you scale, you might pay 10-15% of revenue to AWS if you didn't optimize. This compression kills your margins.

The solution: monitor your infrastructure spend per customer. If you have 100 customers paying $1,000/month on average ($100K MRR) and spending $8K/month on AWS, your infrastructure COGS is 8%. When you hit 200 customers ($200K MRR), you might only spend $13K on AWS due to efficiency improvements (better caching, code optimization, reserved instances). Your infrastructure COGS drops to 6.5%. Track this metric actively. If it's increasing as you scale, investigate your infrastructure team.

Payment Processing and Pricing Strategy

Stripe charges 2.9% + $0.30 per transaction (or 1.5% for ACH transfers). If you're charging monthly on credit card, that's 2.9% * 12 = ~35% annual Stripe fees as a percentage of customer lifetime. For a $1,000/month customer on a 12-month contract, Stripe costs you about $348 total, or 3.5% of revenue. But if you switch to annual billing upfront, you pay Stripe once ($348), which is 3.5% of annual revenue. This is worth thinking about in your pricing strategy.

Some SaaS companies negotiate custom Stripe rates below 2.9% as they scale. Others move to direct bank integration. Neither matter much until you're large enough that the savings outweigh implementation complexity. For now, assume 2.9% + $0.30 and factor it into COGS.

Gross Margin Improvement Strategies

Strategy 1: Optimize infrastructure. Work with your infrastructure team to identify waste. Use auto-scaling to match capacity to demand. Implement caching aggressively. Move expensive operations to batch jobs. Reserve instances for baseline load to get discounts. Many companies save 30-40% on cloud spend with optimization.

Strategy 2: Improve pricing. If you're underpricing relative to value delivered, increase prices for new customers and gradually for existing ones. A 10% price increase with 90% customer retention improves gross margin by 10% on new cohorts. Many founders are shocked by their price elasticity—customers often don't churn when you raise prices moderately.

Strategy 3: Reduce support costs. Build better documentation so customers need less support. Automate common support requests with chatbots or self-service. Shift from reactive support (fixing problems) to proactive support (preventing problems through better onboarding). Reduce support headcount as a percentage of customers.

The Relationship Between Gross Margin and Customer Economics

Gross margin directly affects your LTV and unit economics. If you have a $5,000 customer with 70% gross margin, you retain $3,500 gross profit per customer. If you improve gross margin to 80%, you retain $4,000 per customer. That extra $500/year per customer compounds—with 100 customers, that's $50K additional yearly gross profit. This money can fund 2-3 additional engineers. This is why gross margin improvements are so valuable.

Conversely, if your gross margin is declining (from 75% to 70% as you scale), that's a red flag. You're losing leverage. Investigate why. Is infrastructure spend scaling faster than revenue? Are support costs increasing? Are payment processing fees eating larger percentage? Declining margins require action.

Communicating Gross Margin to Investors

In your monthly reports and investor updates, include a graph of gross margin over time. Show your gross margin trend clearly. "Our gross margin has improved from 65% at launch to 78% this month due to infrastructure optimization and scale. We expect to reach 82% by Series A close." This tells investors your unit economics are improving and you have a path to higher profitability.

If your gross margin is lower than benchmarks for your category, explain why. "Our gross margin is 68% due to high support costs while we onboard enterprise customers. We expect this to decline to 60% as we add enterprise support, then return to 75% as support becomes routine." This narrative prevents investors from assuming something is wrong when it's actually intentional.