Gross Margin by Product
Gross Margin by Product breaks blended company gross margin into per-SKU, per-product-line, or per-cloud margins so you can see which products are subsidizing which. Formula per product: (Revenue_p − COGS_p) ÷ Revenue_p. The KnowMBA POV: blended gross margin is a financial press release; per-product gross margin is the operating decision. A 70% blended gross margin can hide a 90%-margin SaaS subscription propping up a 30%-margin services line that's burning operations time. Founders who don't decompose gross margin scale the wrong revenue.
The Trap
The trap is loading all gross margin into one company-level number and using it to justify pricing decisions. You see 65% blended margin and feel comfortable discounting. But your flagship product has 80% margin while your services attach has 25% — and your discount strategy is mostly hitting the high-margin product. Net effect: you're discounting profit and protecting margin you don't have. Worse, support and engineering time gets allocated by revenue, not by COGS — so the low-margin product silently consumes ops capacity.
What to Do
Build a per-product P&L monthly: revenue, direct COGS (hosting, payments, third-party APIs, support time, fulfillment), gross profit, gross margin %. Add 'fully-loaded margin' that includes allocated CS and support headcount. Kill or re-price any product line below 50% gross margin unless it's a strategic loss-leader with documented downstream value (and a sunset date). Investors discount blended margin if you can't break it out by product line.
Formula
In Practice
Salesforce reports gross margin separately by cloud: Sales Cloud (~85% margin), Service Cloud (~80%), Marketing Cloud (~70%, more services-heavy), MuleSoft and Tableau (lower due to integration services). Their blended gross margin (~75%) is meaningful, but operationally they manage each cloud's margin separately — investing in self-serve and automation specifically for the lower-margin lines. This per-cloud margin discipline is why Salesforce has steadily improved blended margin even while integrating lower-margin acquisitions.
Pro Tips
- 01
Allocate support and CS headcount as COGS, not OpEx, when calculating product margin. A support-heavy product looks great at 85% 'standard' margin but may be 55% once you load 8 CSMs serving it. The fully-loaded number drives the right pricing decisions.
- 02
Track gross margin trend by product over 12 months. A product with declining margin (–2 points/year) is being eaten by hosting, support load, or pricing pressure — diagnose before it crosses your sustainability threshold.
- 03
Bundle pricing distorts per-product margin. If you sell A + B as a bundle for $100 with $30 COGS, allocate revenue to A and B by their standalone-list-price ratio — not 50/50. Lazy allocation makes one product look great and the other look terrible.
Myth vs Reality
Myth
“Software products all have similar margins”
Reality
Pure SaaS can be 85%+. AI-feature-heavy products are 50-70% because of inference costs. Marketplace fees are 15-30%. Services are 25-40%. The 'software is high margin' generalization breaks the moment AI inference, payment processing, or fulfillment enter the equation.
Myth
“Low-margin products should always be killed”
Reality
Sometimes a low-margin product is the wedge that gets you in the door. Twilio's SMS API is single-digit margin but pulls customers into higher-margin Voice and Programmable Voice. Low-margin can be strategic IF it has documented downstream value — otherwise it's just charity.
Try it
Run the numbers.
Pressure-test the concept against your own knowledge — answer the challenge or try the live scenario.
Knowledge Check
You have three products: A (60% of revenue, 80% margin), B (30% of revenue, 60% margin), C (10% of revenue, 20% margin). Blended margin is 68%. Should you kill product C?
Industry benchmarks
Is your number good?
Calibrate against real-world tiers. Use these ranges as targets — not absolutes.
Gross Margin by Business Type
2024 averages by product typePure SaaS Subscription
75-90%
AI/ML-Heavy Software
50-70%
Marketplace Take-Rate
65-85%
Hardware + Software
30-50%
Professional Services
25-45%
Source: OpenView / Bessemer State of the Cloud 2024
Real-world cases
Companies that lived this.
Verified narratives with the numbers that prove (or break) the concept.
Salesforce
2020-2024
Salesforce reports gross margin separately by cloud in their 10-K. Sales Cloud and Service Cloud (the original products) maintain 80%+ gross margin. Marketing Cloud and MuleSoft, which involve more services and integration work, run materially lower (60-70%). By managing each cloud's margin individually — investing in self-serve where possible — Salesforce has expanded blended gross margin from 73% (FY20) to 76% (FY24) even while integrating lower-margin acquisitions like Slack and Tableau.
Sales Cloud Margin
~85%
MuleSoft Margin
~65%
Blended Margin Trend
73% → 76% (4 yrs)
Strategic Action
Self-serve investment in low-margin clouds
Per-product gross margin is a tactical lever, not a reporting metric. Salesforce uses it to decide where to invest in automation vs accept services overhead.
Zoom
2020-2023
Zoom's blended gross margin was famously 80%+ during COVID — but management was transparent that Zoom Phone (lower margin due to telecom interconnect costs) and Zoom Contact Center (services-heavy) carried 50-65% margins. As these new products grew, blended margin compressed. Zoom proactively disclosed the dynamic to investors, framing it as 'investing in long-term TAM expansion at the cost of short-term blended margin.' Investors generally accepted this with the per-product breakdown.
Zoom Meetings Margin
~85%
Zoom Phone Margin
~55-60%
Blended Compression
82% (2021) → 76% (2023)
When blended margin compresses, having the per-product story prevents investor panic. Without it, margin compression looks like a death spiral instead of a deliberate mix shift.
Related concepts
Keep connecting.
The concepts that orbit this one — each one sharpens the others.
Beyond the concept
Turn Gross Margin by Product into a live operating decision.
Use this concept as the framing layer, then move into a diagnostic if it maps directly to a current bottleneck.
Typical response time: 24h · No retainer required
Turn Gross Margin by Product into a live operating decision.
Use Gross Margin by Product as the framing layer, then move into diagnostics or advisory if this maps directly to a current business bottleneck.