· Pillar 1
SaaS Gross Margin: Why 80% Is the Floor, Not the Goal (And What COGS You're Forgetting)
Most SaaS gross margin content quotes a 70-80% bench without telling founders what to include in COGS. The hidden COGS list, the formula, by-segment benchmarks, and why 70% margin SaaS is structurally a different business than 85% margin SaaS.
Gross margin is the metric most bootstrapped founders quote a benchmark for and have never actually calculated correctly. The “70-80% is healthy for SaaS” line gets repeated in every primer — without anyone telling you what belongs in COGS, why the difference between 70% and 85% margin is structurally a different business, or why the hidden costs are what separate the SaaS that compounds from the SaaS that quietly bleeds.
This guide walks through the full COGS list (including the line items most bootstrapped founders forget), the formula, the by-segment benchmarks that matter when “industry average” is too coarse, why 80% is the floor not the goal, and a fix-burn-before-raising-prices decision tree.
SaaS gross margin in one sentence: Gross margin equals (Revenue − COGS) ÷ Revenue × 100 — the 70-80% benchmark quoted in primers is the floor for venture-grade SaaS, not the goal, and bootstrapped founders should target above 80% with operator-grade pure software hitting 85-90%. According to Bessemer’s State of the Cloud 2024, best-in-class public SaaS reports gross margin in the 78-85% band; sub-75% companies are flagged in diligence as either pricing-weak or infrastructure-heavy. The point of this post is that the 5-point spread between “fine” and “structural advantage” is hiding in COGS items most bootstrappers forget to track.
If you want to see where your current gross margin lands you on an investor’s stage radar before you book the call, the Fundability Scorecard maps it against the other capital efficiency metrics that matter at scale.
What is SaaS gross margin?
Gross margin is the percentage of revenue remaining after the direct cost of delivering the service to customers. It answers a single question: of every dollar collected, how much survives the cost of producing it?
Gross Margin = (Revenue − COGS) ÷ Revenue × 100
For SaaS, COGS is structurally narrow: it includes only the direct costs of running the service for paying customers — not sales, not marketing, not product development, not overhead. Those sit below the gross margin line in operating expenses. The discipline is mechanical: anything that scales with paid users or paid revenue goes in COGS; anything that exists regardless of customer count goes in OpEx.
Most “SaaS gross margin” content stops at the 70-80% benchmark and never enumerates what belongs in COGS for a bootstrapped SaaS in 2024. That’s where the metric gets miscomputed.
The hidden COGS most bootstrapped founders forget
The textbook COGS list for SaaS is “hosting plus support.” That list was written in 2014 and is structurally wrong for how bootstrapped SaaS gets delivered now. The complete COGS list for a 2024 bootstrapped SaaS in the $0-50K MRR range:
Infrastructure (the obvious bucket):
- Cloud hosting — AWS, GCP, Cloudflare Workers paid plan, Vercel, Render
- Database hosting — Neon, PlanetScale, Supabase paid tier, RDS
- CDN and edge — Cloudflare paid plan, Fastly, Bunny
- Storage — S3, R2, Backblaze (scales with user-generated content)
Payment processing (the line most underestimated):
- Stripe, PayPal, Lemon Squeezy, Paddle — typically 2.9% + $0.30 per transaction, plus 1% international surcharge, plus disputed transaction fees
- Payment processor reserve holds — Stripe holds 5-25% of new account volume for 90+ days; this is not technically COGS but distorts cash flow modeling
Transactional services (scale with active users):
- Postmark, SendGrid, Resend — transactional email (welcome flows, password resets, billing notices)
- Twilio, MessageBird — SMS, voice
- Cloudflare R2 egress at scale
- AWS data transfer out
Third-party APIs (the line most forgotten):
- OpenAI, Anthropic, Replicate — if AI features are user-facing, every API call hits COGS
- Plaid, Stripe Connect, Clearbit — every customer-triggered enrichment call
- Geolocation, mapping, search — Algolia, Mapbox, Google Maps
Customer-facing support (the fractional line):
- The fraction of payroll directly answering paid-customer tickets (not pre-sales, not docs work)
- Support contractor fraction (a $4K/month contractor spending 100% on customer issues is full COGS; 50% on support and 50% on docs is half COGS, half OpEx)
- Helpdesk software directly tied to paid users (Intercom, Pylon, Plain — only the seat cost attributed to support work)
On-call and incident infrastructure (the spike line):
- On-call rotation cost (PagerDuty, BetterStack, FireHydrant)
- The AWS bill spike when a customer triggers an unexpected workload — these are real COGS and should be modeled even though they’re variable
The honest COGS audit for a $50K MRR bootstrapped SaaS in 2024 typically lands at 8-15% of revenue, putting gross margin in the 85-92% band. Founders who land at 70-75% are usually either (a) running a service-heavy SaaS where support is materially larger than 5% of revenue, (b) reselling infrastructure where their compute markup is thin, or (c) carrying hidden costs that haven’t been audited.
The Runway Calculator implicitly uses gross margin in projecting how revenue offsets burn — the projection is wrong by the same percentage your COGS is misclassified.
Why 80% is the floor, not the goal
The widely-quoted “70-80% gross margin is healthy SaaS” benchmark needs to die. It was calibrated against a basket of SaaS that includes a lot of services-adjacent businesses (implementation-heavy enterprise SaaS, payments SaaS where interchange compresses margin, infrastructure SaaS reselling AWS at thin markup). For pure software SaaS shipping a product without material services attached, the floor is 80% and the operator-grade band is 85-90%.
The reason this matters compounds with scale. On $1M ARR:
- 70% gross margin = $300K available to fund S&M, R&D, G&A, and runway
- 80% gross margin = $200K available
- 90% gross margin = $100K available
That spread is the difference between the SaaS that can fund a second sales hire and the SaaS that can only afford a contractor part-time. It’s the difference between 18 months of runway and 12 months. Over a 24-month compounding window, the 90%-margin SaaS will out-fund the 70%-margin SaaS by 3x in cumulative growth investment at the same MRR — without raising a dollar of outside capital.
The structural rule:
80% gross margin is the bootstrapped floor. Operator-grade pure software SaaS should target 85-90% gross margin, and anything below 75% is a signal of pricing weakness or infrastructure overhead that needs auditing before scale.
There is one exception: services-heavy SaaS (implementation, training, managed migration) can run sustainably at 60-70% gross margin if the services component is structural to the value prop and priced accordingly. But the metric should be reported with the services revenue broken out — and the underlying software gross margin should still hit 80%+ on its own.
Gross margin benchmarks by SaaS segment
The “industry average” benchmark obscures more than it reveals. Gross margin varies materially by SaaS segment:
| Segment | Median gross margin (2024) | Operator-grade target |
|---|---|---|
| Pure software B2B SaaS | 80-85% | 85%+ |
| B2C subscription SaaS | 75-82% | 80%+ |
| Dev tools / infra SaaS | 72-80% | 78%+ (compute pass-through compresses) |
| Vertical SaaS (industry-specific) | 70-80% | 78%+ |
| Marketplace SaaS (with payments) | 60-72% | 70%+ (interchange dominates) |
| Agency / services-led SaaS | 55-70% | 65%+ (services are structural) |
| AI-feature heavy SaaS | 55-75% | 70%+ (API cost pass-through brutal) |
Sources: Bessemer State of the Cloud 2024, OpenView 2024 SaaS Benchmarks, ChartMogul 2024 SaaS Pulse.
The pattern: pure software SaaS sets the high bar, anything with embedded infrastructure pass-through (dev tools, AI features) compresses 5-10 points, and anything with embedded payments or services compresses another 5-10 points. The bootstrapped founder building a dev-tools SaaS running at 78% gross margin is structurally healthy; the same founder building a pure B2B workflow tool at 78% has a margin problem worth auditing.
The 70% vs 85% SaaS structural difference
A founder running a 70% gross margin SaaS at $20K MRR has $6K/month of gross profit. The same founder at 85% gross margin has $7K/month — a 17% difference in available cash that compounds every month into a structurally different business.
Project this across 18 months:
| Metric | 70% gross margin | 85% gross margin |
|---|---|---|
| Monthly gross profit on $20K MRR | $14K | $17K |
| Cumulative 18-month gross profit | $252K | $306K |
| Hires fundable at $120K loaded cost | 2 | 2.5 |
| Marketing test budget (10% of GP) | $25K | $30K |
| Buffer for one bad quarter | 1 quarter | 2 quarters |
The 70%-margin SaaS isn’t broken — but it has 15-20% less operational slack than the 85%-margin SaaS at the same MRR. Every decision (hiring, channel testing, runway extension, vendor negotiation) is made with less optionality.
The compounding effect: a 70%-margin SaaS that wants to fund the same growth as an 85%-margin competitor has to either (a) grow MRR 20% faster to generate equivalent gross profit, or (b) take on outside capital. Bootstrapped founders rarely have access to option (b), which makes option (a) a forced choice — and growing 20% faster than a structurally more-efficient competitor at the same stage is roughly impossible without subsidy.
This is the operator-grade reason gross margin is more decisive for bootstrappers than for any other category of SaaS founder. It’s the metric that determines how much of your own success you get to keep.
The “fix burn before raising prices” decision tree
Bootstrapped founders facing a 75% gross margin problem usually default to “raise prices on the next renewal cycle” — and skip the lower-risk move of fixing the COGS side first. The decision tree:
Step 1: Audit COGS line-by-line. Pull the actual cost breakdown for the last 3 months. Most founders find 1-3 line items that are 20-40% larger than necessary — usually one of: (a) over-provisioned hosting tier, (b) redundant tool overlap (two analytics tools, two helpdesks, two monitoring stacks), (c) Stripe fees on payment methods that have lower-cost alternatives (ACH vs card for B2B annual), (d) unused seat costs on tools billed per-user.
Step 2: Eliminate the bottom-quartile cost item. Cancel, downgrade, or consolidate the single biggest unnecessary line. This typically recovers 1-3 points of gross margin without touching pricing or risking churn.
Step 3: Renegotiate the top-3 cost items. Cloud hosting, payment processing, transactional infrastructure — all have annual commitment discounts, volume tiers, and startup credit programs. A 15% discount on a 30%-of-COGS line item moves gross margin 0.5-1 point. Repeated across 3 vendors compounds.
Step 4: Audit pricing only after COGS is clean. If gross margin is below the segment benchmark even after COGS is optimized, then pricing is the lever. Use the MRR Health Snapshot to grade expansion vs contraction baseline before raising prices, so you know whether the 20% lift produces net positive movement or triggers contraction churn.
Step 5: Raise prices on new business first, grandfathered on existing. This separates the structural pricing experiment from the retention risk on the existing book. New-business pricing increases land in 60-90 days; existing-customer increases land in 12+ months as renewal cycles cycle through.
The order matters because COGS fixes are reversible and zero-risk, pricing changes are partially reversible and carry churn risk. Doing pricing first is the bootstrapper move that looks decisive and is structurally backwards.
How to report gross margin on an investor update
Investor updates at seed stage and beyond ask for gross margin alongside the headline efficiency metrics. The operator-grade format:
- Headline line: “Gross margin: 87% trailing 3-month, 84% trailing 12-month.”
- COGS breakdown: “Of 13% COGS, 6% infrastructure, 3.5% payment processing, 2% transactional services, 1.5% support.”
- Direction: “Trending up — Q1 was 81%; vendor consolidation and Stripe negotiation landed.”
- Pricing model note if material: “Pure software; no embedded payments or services.”
Always report both trailing-3-month and trailing-12-month numbers. Investors triangulate between them to detect one-time effects in the shorter window. If trailing-3 is materially better than trailing-12, expect to be asked what changed.
Tomasz Tunguz’s investor update writing and David Skok’s forentrepreneurs benchmarks both recommend the COGS-breakdown line specifically — investors triangulate margin direction against where the cost line is moving, not just the headline.
When gross margin lies (the 3 caveats)
The metric is useful and opinionated, but it has blind spots.
Caveat 1: Annual contracts inflate short-window margin. A SaaS that collects $24K on a January annual contract shows 100% of that as January revenue if reported on cash basis — but the COGS is spread across 12 months. The Q1 gross margin looks artificially high; Q4 gross margin will look artificially low when the cost continues without the revenue catch-up. Use accrual accounting for gross margin to avoid this, or compute on a trailing-12-month basis only.
Caveat 2: AI-feature COGS scales nonlinearly with usage. A SaaS shipping AI features powered by Claude or OpenAI APIs has COGS that spikes with power users. A heavy-usage customer can cost 3-5x the median customer in API spend while paying the same subscription fee. The blended gross margin hides this; per-customer gross margin (LTV-adjusted) is the right read. The Cohort Visualizer surfaces whether heavy-usage cohorts are dragging margin meaningfully.
Caveat 3: Free tier subsidizes paid tier COGS. Many bootstrapped SaaS run a free tier whose infrastructure cost lands in COGS even though no revenue is attributed. The strict accounting separates free-tier infrastructure as a marketing expense (it’s a CAC investment, not a service delivery cost), but most founders dump it into COGS. This understates gross margin by 2-5 points at SaaS where free-tier usage is material. The structural fix is to track free-tier infrastructure separately and classify it below the gross margin line.
Frequently Asked Questions
What is SaaS gross margin? SaaS gross margin is the percentage of revenue remaining after subtracting the direct cost of delivering the service to customers (COGS). The formula is (Revenue − COGS) ÷ Revenue × 100. For SaaS, COGS includes hosting infrastructure, payment processing fees, third-party APIs that scale with usage, customer support staffing, and any transactional cloud spend tied to delivering the product.
What is a good gross margin for SaaS? The widely-quoted 70-80% benchmark is the floor for venture-grade SaaS, not the goal. Best-in-class pure software SaaS runs at 80-90% gross margin. Bootstrapped founders should target above 80% — anything below 75% structurally caps how much can be reinvested into growth and signals either pricing weakness or infrastructure overhead that scales linearly with revenue rather than logarithmically.
What costs are included in SaaS COGS? SaaS COGS includes cloud hosting (AWS, Cloudflare, Vercel), payment processing fees (Stripe, PayPal — typically 2.9% + $0.30 per transaction), transactional email and SMS (Postmark, Twilio), third-party APIs that scale with usage, customer support staffing (the fraction of payroll directly answering tickets), and infrastructure that supports paid customers specifically. It does NOT include sales, marketing, engineering, or general overhead — those sit below the gross margin line.
What is the difference between 70% and 85% gross margin SaaS? A 70% gross margin SaaS is structurally a different business than 85% gross margin SaaS. The 15-point delta compounds: on $1M ARR, that is $150K less per year available to fund growth, hires, or runway. A 70% margin business needs to grow ~2x faster to fund the same operating engine as an 85% margin business at the same MRR. Founders running at 70% margin are usually carrying hidden infrastructure costs or pricing below value — both fixable.
How do you calculate SaaS gross margin? Gross Margin = (Revenue − COGS) ÷ Revenue × 100. Use cash revenue (collected, not invoiced) and cash COGS for the same period. The trap is forgetting Stripe fees (2.9% + $0.30 per charge eats 3-4 points of margin alone) and free-tier infrastructure costs that scale with paid usage. A SaaS at $50K MRR paying $1500/month for hosting, $1450/month in Stripe fees, $400/month in transactional email, and $1100/month for a fractional support contractor has $4450 in COGS — gross margin is 91.1%, but only if all of that is correctly attributed.
Should bootstrapped founders fix gross margin before raising prices? Yes, in most cases. Raising prices on existing customers risks churn; cutting hidden COGS is a no-risk margin improvement that compounds immediately. The operator-grade move is to audit COGS first (especially infrastructure, redundant tooling, and payment processor reserve holds), then raise prices only on the segments where the audit shows pricing is materially below market or value delivered.
Why does gross margin matter for bootstrapped founders specifically? Bootstrapped founders fund growth from gross profit, not from venture capital. A 10-point gross margin difference on $50K MRR is $5000/month of cash that funds one more hire, one more channel test, or six months of additional runway. Venture-backed SaaS can compensate for low gross margin with capital; bootstrapped SaaS cannot. The metric is more decisive for bootstrappers than for any other category of operator.
Run the numbers
Gross margin is the metric that determines how much of your own growth you get to keep. The bootstrapped move is to audit COGS first, fix the hidden infrastructure spend, and treat 80% as the floor — not the goal a primer told you was good enough.
Three tools to validate your inputs and pressure-test the math:
- Fundability Scorecard — maps gross margin alongside burn multiple, CAC payback, growth, and retention against the stage you’re aiming at. Surfaces where margin is the binding constraint vs where it’s compensating for another weakness.
- Runway Calculator — projects runway under planned hires using your actual gross margin to translate revenue into available cash. The most common reason a runway model is off by 4-6 months is gross margin misclassification.
- MRR Health Snapshot — grades expansion-vs-contraction baseline so you can predict whether a planned price increase produces net positive movement or triggers contraction churn that eats the margin gain.
Continuing the financial fundamentals set:
- The 18-month runway target gross margin implicitly funds → The SaaS Runway Playbook for Bootstrapped Founders
- Burn multiple — the efficiency metric gross margin most affects → Burn Multiple for Bootstrapped SaaS
- Churn — the metric that compounds gross margin damage → SaaS Churn Rate: Logo, Revenue, Net
- MRR vs ARR — the audience map for which one to lead with → MRR vs ARR for bootstrapped founders
For dev-tools and infra SaaS specifically, the gross margin equation is structurally different because compute pass-through compresses margin 5-10 points relative to pure software — the dev-tools SaaS runway breakdown walks through the segment-specific math for founders shipping infrastructure rather than pure workflow.
Gross margin is not a vanity metric. It is the operator-grade question every bootstrapped founder should be answering every quarter: of every dollar collected, how much survives the cost of producing it? The answer determines how much of your own success you get to compound.