TL;DR: Gross margin is the percentage of revenue left after direct costs like hosting, support, and implementation. SaaS companies should target 70-80% gross margin, but most early-stage companies sit at 50-60% because of inefficiencies they’ll eventually eliminate. Investors care about gross margin because it determines how much revenue flows to R&D, sales, and profit. Low gross margin means you need more revenue to cover operating expenses and reach profitability. Track gross margin monthly, understand what drives it, and have a concrete plan to reach 70%+ as you scale.
We talk with founders who celebrate 100% revenue growth but can’t understand why investors seem unimpressed. The answer is usually in gross margin.
Revenue growth matters, but gross margin determines how much of that revenue you can reinvest in growth or keep as profit. A company with $10M revenue at 80% gross margin has $8M to spend on sales, marketing, R&D, and overhead. A company with $10M revenue at 50% gross margin only has $5M. Same revenue, completely different economics.
Investors know this. They calculate gross margin within the first five minutes of looking at your business. Below 60%, questions start. Below 50%, many investors pass regardless of growth rate.
Public SaaS companies average 70-75% gross margin. That’s the benchmark investors use. If you’re at 55% gross margin, they want to see a clear path to 70%+. If you can’t articulate how you’ll get there, they assume you won’t and value your business accordingly.
Gross margin is revenue minus cost of goods sold (COGS), divided by revenue. For SaaS, COGS includes direct costs required to deliver your service:
Hosting and infrastructure: AWS, GCP, Azure costs for running your application. Data storage, compute, bandwidth.
Support costs: Customer support salaries, ticketing systems, phone systems. Anyone directly helping customers use the product.
Implementation and onboarding: Professional services team that configures software for new customers. Onboarding specialists who train users.
Payment processing: Stripe fees, credit card merchant fees. Usually 2.5-3% of revenue.
Third-party software directly embedded in product: APIs you call, data you license, services you resell.
What doesn’t go in COGS: Engineering salaries (that’s R&D), sales and marketing costs, general overhead, management team. These are operating expenses below the gross margin line.
The distinction matters because investors scrutinize what you include in COGS. Some companies try to inflate gross margin by excluding costs that should clearly be in COGS. This backfires in due diligence when investors reclassify expenses and your gross margin drops 10 points.
Early-stage SaaS companies typically have lower gross margins than mature companies because they haven’t optimized costs yet:
Pre-$1M ARR: 40-60% gross margin is typical. You’re over-provisioned on infrastructure, providing high-touch support, doing manual implementations. This is acceptable if you have a clear path to improvement.
$1M-5M ARR: 50-70% gross margin. You’re automating some processes, negotiating better hosting rates, shifting from high-touch to self-serve where possible.
$5M-20M ARR: 60-75% gross margin. Infrastructure is right-sized, support is mostly systematized, implementations are partially automated.
$20M+ ARR: 70-80% gross margin. Mature operational efficiency. Enterprise SaaS might be 70-75%, pure software-only SaaS might be 80-85%.
Business model also affects target margins:
Pure SaaS with self-serve: 80-85% gross margin. No services component, automated onboarding, minimal support.
SaaS with implementation services: 65-75% gross margin. Professional services to configure and deploy drag down margins.
Vertical SaaS with payment processing: 60-70% gross margin. Payment processing fees (which are COGS) reduce margins but the volume often makes up for it.
Hardware-enabled SaaS: 40-60% gross margin. If you sell hardware that connects to your software, hardware costs kill margins but can be strategic for customer lock-in.
Investors expect you to know where your model should land and show progress toward that target.
Most companies we work with enter engagements at 50-60% gross margin and need to reach 70%+ to be fundable or profitable. Here’s how that progression typically works:
Infrastructure optimization (adds 5-10 points): Right-size your servers, use reserved instances instead of on-demand, implement caching to reduce compute. Negotiate volume discounts once you hit scale. Move to more efficient architectures. We had a client spending $45K monthly on AWS for 500 customers ($90 per customer monthly). After optimization: $28K monthly ($56 per customer). That’s $204K annually—dropping infrastructure from 18% of revenue to 11%, adding 7 points to gross margin.
Support automation (adds 3-5 points): Build self-service help centers, knowledge bases, chatbots. Train customers to solve common problems themselves. Tier support so simple questions get handled by junior staff or automation, complex issues escalate to experts. The goal is reducing support cost per customer as you scale.
Implementation efficiency (adds 5-8 points): Standardize implementation processes, build configuration tools customers can use themselves, create templates for common use cases. Early-stage SaaS might spend 40 hours implementing each customer. Mature SaaS spends 2 hours. That’s the difference between implementation costs of 30% of first-year revenue versus 3%.
Payment processing optimization (adds 1-2 points): Negotiate better rates with processors once you have volume. Use ACH/bank payments for large customers instead of credit cards (much lower fees). Build incentives for customers to choose lower-cost payment methods.
Vendor negotiation (adds 2-4 points): Every third-party service you use should be renegotiated annually. Twilio, SendGrid, authentication services, monitoring tools. At scale, you have leverage. A company growing from $2M to $5M ARR should renegotiate every vendor contract. We typically save clients 20-40% on vendor costs through structured negotiation.
We see the same mistakes repeatedly when auditing SaaS gross margin calculations:
Excluding costs that belong in COGS. Support managers who spend 80% of their time managing customer issues are COGS, not overhead. Implementation specialists are COGS, not R&D. Include everything directly required to deliver service.
Not tracking hosting costs per customer. If you don’t know what it costs to serve a customer, you can’t optimize. Break down infrastructure costs by customer segment. Often you’ll find small customers cost the same to serve as large ones, but pay 10x less. This informs pricing and targeting.
Accepting vendor pricing without negotiation. Every SaaS tool charges list price until you push back. Negotiate everything. “We’re growing fast and will be a bigger customer in 12 months. What’s your volume pricing?”
Over-provisioning infrastructure “just in case.” Size infrastructure for actual usage plus reasonable buffer, not theoretical maximum load. We see companies running at 15% infrastructure utilization because they’re scared of outages. That’s burning money.
Manual processes that should be automated. If you’re manually configuring every new customer, that’s COGS that could be eliminated with investment in tooling.
Not separating one-time costs from recurring costs. Implementation might have 40% margin but SaaS revenue after implementation has 85% margin. Track both. Show investors that as customers mature past implementation, margins improve.
Sometimes low gross margin is an acceptable strategic choice, not a problem to fix immediately:
Land-and-expand model with loss-leader implementation. You might do implementations at break-even or loss to land customers, knowing the recurring revenue has 80% margins and will dominate over time.
Market penetration phase. You might subsidize hosting to acquire customers rapidly, planning to optimize later once you have scale and lock-in.
Building moat through services. Some companies deliberately provide high-touch implementation and support to create switching costs. The low margin is the price of customer stickiness.
Payment processing as strategic advantage. Payment-enabled SaaS has lower gross margin (payment fees are COGS) but the payment processing creates lock-in and lets you monetize transaction volume not just software usage.
The key is being intentional and having a plan. “We’re at 55% gross margin now because we provide white-glove onboarding. As we add self-serve onboarding tools, we’ll reach 70% by $5M ARR” is fine. “We’re at 55% gross margin and haven’t really thought about it” is not fine.
Build a simple model showing your gross margin evolution over time:
Current state: Revenue $2M, COGS $900K, gross margin 55%
– Hosting: $360K (18% of revenue)
– Support: $280K (14% of revenue)
– Implementation: $180K (9% of revenue)
– Processing fees: $60K (3% of revenue)
– Other: $20K (1% of revenue)
Future state at $5M revenue:
– Hosting: $550K (11% of revenue) – optimization + volume discounts
– Support: $400K (8% of revenue) – automation + efficiency
– Implementation: $200K (4% of revenue) – self-serve tools
– Processing fees: $125K (2.5% of revenue) – better rates
– Other: $35K (0.7% of revenue)
– Total COGS: $1.31M (26% of revenue)
– Gross margin: 74%
Show this to investors. It demonstrates you understand your cost structure and have concrete plans to improve it. This is infinitely better than saying “we think margins will improve as we scale.”
Don’t just compare yourself to public SaaS averages. Segment by business model:
Pure software SaaS (Datadog, Atlassian): 80-85%
SaaS with services component (Veeva, Guidewire): 65-75%
Marketplace/platform SaaS (Shopify, Toast): 40-60% due to payment processing
Infrastructure SaaS (Snowflake, MongoDB): 70-75%
Compare yourself to companies at similar stage and model. If you’re a $3M ARR SaaS-plus-services company at 62% gross margin, you’re probably fine. If you’re a pure software company at 62% gross margin, you need to figure out why hosting and support costs are so high.
Use public company earnings reports to see margin evolution. Many companies report gross margin by product line, showing how margins improve as products mature. This helps you model realistic improvement trajectories.
Investors will ask about gross margin in every conversation. Here’s how to handle it:
Know your current gross margin and how you calculate it. “We’re at 64% gross margin. That includes all hosting, support, implementation, and processing fees.”
Explain why you’re at current margin. “We’re doing high-touch implementations for early customers to learn. This costs us 12% of revenue but creates product insights worth way more than the margin hit.”
Show the path to target margin. “As we automate implementation and optimize infrastructure, we’ll reach 72% gross margin at $5M ARR.”
Provide proof points. “We’ve cut hosting costs per customer by 30% in the last 6 months through optimization. That improvement will continue.”
Be honest about challenges. “Support costs are higher than we’d like because our product still has rough edges. We’re investing in product quality which will reduce support load.”
The worst answer is “we haven’t really analyzed gross margin.” That signals you don’t understand your business economics.
—
Q: What gross margin is good enough to raise funding?
For seed/Series A, investors want to see 55-65% minimum with a credible path to 70%+. Below 55%, you’ll face tough questions. For Series B+, you should be at 65-70% or higher. Investors become less forgiving of low margins as you mature. The exception is if you have a strategic reason for low margins (payment processing, hardware component) that you can explain clearly. Pure software SaaS below 60% at Series B will struggle to raise.
Q: Should we sacrifice gross margin for growth?
Sometimes yes, strategically. If spending more on implementation or support helps you land customers in a competitive market, that can be worth the margin hit short-term. But have a plan to improve margins as you scale. Investors will accept “we’re at 58% margin now, we’ll be at 72% at scale” if you can show how. They won’t accept “we’re growing fast and don’t care about margins.” That’s a recipe for unprofitable growth that can’t sustain itself.
Q: How do professional services and implementation fees affect gross margin calculations?
Implementation fees are revenue. Implementation costs are COGS. If you charge $10K for implementation that costs you $8K to deliver, that’s 20% margin revenue. The key is separating one-time implementation margin from recurring SaaS margin in your reporting. Show investors that while blended gross margin is 65%, your recurring SaaS gross margin is 78% once customers are live. This proves the business model works at scale even if early implementations are lower margin. Track and report both numbers.