Contribution Margin 1 (CM1)

What is Contribution Margin 1?

Contribution Margin 1 (also called CM1, first-level contribution margin, or product margin) is the profit remaining after subtracting only the direct cost of goods sold from revenue. It is the first and simplest of the layered contribution margin calculations that operators use to understand profitability at increasing levels of detail.

CM1 matters because it exposes whether the product itself is viable. A SaaS product with 80% CM1 has $0.80 per dollar to cover sales, marketing, R&D, and overhead. A physical product with 35% CM1 has $0.35. Every cost that sits below CM1 — fulfillment, advertising, sales commissions — must fit within that margin or the unit economics turn negative.

For B2B SaaS companies, healthy CM1 ranges from 70-85%. Below 65% signals high infrastructure costs, excessive third-party API usage, or pricing that doesn't reflect delivery cost. For e-commerce businesses, CM1 of 40-65% is standard, with the range depending on whether the company manufactures or resells.

CM1 differs from CM3 in what it subtracts. CM1 only removes COGS. CM3 removes COGS plus fulfillment costs plus marketing costs — giving a much deeper view of true unit profitability. Think of CM1 as the product margin and CM3 as the fully-loaded customer margin.

Why CM1 matters for operators

Operators who skip CM1 and jump straight to blended gross margin miss critical product-level signals. A company selling 3 product lines at 60% blended gross margin might have one line at 82% and another at 31%. The blended number hides the fact that one product barely covers its own production cost.

Without CM1 by product or SKU, pricing decisions happen in the dark. A 10% price increase on a product with 80% CM1 drops almost entirely to the bottom line. The same increase on a product with 35% CM1 has far less impact because COGS consumes most of the revenue.

A typical mid-market SaaS company calculating CM1 by product for the first time finds a 20-40 point spread between its highest-margin and lowest-margin offerings. The most common discovery: the flagship product has strong CM1 (78-85%), while add-on products or services components run 30-45% because they require manual delivery or expensive third-party infrastructure.

CM1 formula

CM1 ($) = Revenue - COGS
CM1 (%) = (Revenue - COGS) / Revenue x 100

Example (by product line):
Product A — Core SaaS platform:
- Revenue: $425,000
- COGS (hosting, infrastructure, third-party APIs): $72,250

CM1 ($) = $425,000 - $72,250 = $352,750
CM1 (%) = $352,750 / $425,000 x 100 = 83.0%

Product B — Managed services add-on:
- Revenue: $118,000
- COGS (analyst time, tooling, delivery): $74,340

CM1 ($) = $118,000 - $74,340 = $43,660
CM1 (%) = $43,660 / $118,000 x 100 = 37.0%

What each component means:

• Revenue: Net revenue after discounts, refunds, and credits. Use recognized revenue, not bookings or invoiced amounts. Revenue recognition timing matters — a $120,000 annual contract recognized monthly contributes $10,000/month to the CM1 calculation.
• COGS: Direct costs of producing or delivering the product. For SaaS: hosting, infrastructure, third-party APIs, customer support staff directly tied to product delivery. For physical products: raw materials, manufacturing, packaging. Do not include marketing, sales, or overhead costs — those appear in CM3.

CM1 benchmarks by business type

How CM1 varies across company types and stages. Ranges based on industry-observed data.

Sources: Industry-observed ranges from SaaS operator surveys, KeyBanc SaaS Survey 2025, and Fairview customer data.

Common mistakes when calculating CM1

1. Including marketing and sales costs in COGS

CM1 only subtracts COGS — the cost of producing and delivering the product. Ad spend, sales commissions, and SDR salaries are not COGS. Including them in CM1 makes the metric useless because it conflates product economics with go-to-market efficiency. Those costs belong in CM3.

2. Calculating CM1 at the company level only

A single company-wide CM1 number hides product-level problems. A SaaS product at 82% CM1 bundled with a managed service at 37% CM1 produces a blended 68% — which looks acceptable. But scaling the services component without improving its CM1 erodes the blend over time. Calculate CM1 by product line, by SKU, and by customer segment.

3. Using bookings instead of recognized revenue

A $240,000 annual contract booked in January should not show $240,000 of January revenue in the CM1 calculation. Use recognized revenue — $20,000/month — to match timing with the COGS incurred each month. Bookings-based CM1 creates false spikes and troughs.

4. Ignoring variable infrastructure costs

SaaS companies often treat hosting as a fixed cost because the monthly bill is predictable. But compute and storage costs scale with usage. A customer on a $500/month plan consuming $180/month in infrastructure has a very different CM1 than one consuming $40/month. Track infrastructure cost per customer where possible.

5. Not adjusting for returns and refunds

Revenue should be net of refunds, chargebacks, and credits. A product with 15% return rate has materially lower CM1 than the same product with 3% return rate — even if gross revenue per unit is identical.

How Fairview tracks CM1 automatically

Fairview's Margin Intelligence pulls revenue data from your payment processor (Stripe, Shopify) and cost data from your accounting system (QuickBooks, Xero) to calculate CM1 by product, by customer segment, and by time period — without manual spreadsheet assembly.

The Operating Dashboard displays CM1 alongside CM3, so operators see both the product margin and the fully-loaded margin in one view. When CM1 drops below a configured threshold for any product line, the Next-Best Action Engine recommends specific actions: "CM1 on Managed Services dropped to 33% this month. Delivery hours per client increased 22%. Review scope agreements."

The Data Connection Layer normalizes revenue recognition timing across systems so the calculation reflects actual delivery economics.

→ See how Margin Intelligence works

CM1 vs CM3

Operators use CM1 and CM3 at different decision points. They answer different questions about profitability.

CM1 proves the product model works. CM3 proves the go-to-market model works. A product with 80% CM1 and -5% CM3 has a viable product sold through an unprofitable channel. Fix the channel, not the product.

FAQ

What is CM1 in simple terms?

Contribution Margin 1 is the money left after subtracting only the direct cost of making or delivering your product from its revenue. If you sell a SaaS subscription for $500/month and it costs $85/month in hosting and infrastructure to deliver, your CM1 is $415 or 83%. It tells you whether the product itself is profitable before any marketing or sales costs.

What is a good CM1 for SaaS?

For pure B2B SaaS (no services component), healthy CM1 is 78-88%. SaaS with bundled services typically runs 55-70%. Below 65% for pure software signals high infrastructure costs, expensive third-party APIs, or underpricing. The key is tracking CM1 by product line — blended figures hide underperforming products.

How do you calculate CM1?

Subtract COGS from revenue. CM1 ($) = Revenue - COGS. CM1 (%) = (Revenue - COGS) / Revenue x 100. For a SaaS product: $425,000 revenue minus $72,250 in hosting, infrastructure, and API costs equals $352,750 CM1, or 83%. Use recognized revenue, not bookings, and include only direct delivery costs in COGS.

What is the difference between CM1 and CM3?

CM1 subtracts only COGS from revenue. CM3 subtracts COGS plus fulfillment costs plus marketing and sales costs. CM1 tells you if the product is viable. CM3 tells you if the business model around that product is viable. A product with strong CM1 and weak CM3 has a go-to-market problem, not a product problem.

How often should you track CM1?

Monthly for company and product-level CM1. Quarterly for SKU-level or customer-segment breakdowns. Monthly cadence catches COGS increases (cloud cost spikes, supplier price changes) before they compound. Product teams should review CM1 whenever pricing changes, new infrastructure is added, or vendor contracts are renegotiated.

What is included in COGS for CM1?

For SaaS: hosting and compute costs, third-party API fees, customer support salaries directly tied to delivery, and data storage costs. For physical products: raw materials, manufacturing, packaging, and inbound shipping. Do not include marketing spend, sales commissions, rent, or R&D — those are below CM1 and factor into CM3 or operating margin.

Related terms

• Contribution Margin — Revenue minus all variable costs, a broader view than CM1
• Contribution Margin 3 (CM3) — Revenue minus COGS, fulfillment, and marketing costs — the fully-loaded margin
• COGS (Cost of Goods Sold) — Direct costs of producing or delivering the product or service
• Gross Margin — Often used interchangeably with CM1, though gross margin may include allocated overhead
• AOV (Average Order Value) — Average revenue per transaction, used alongside CM1 to assess unit economics

Fairview is an operating intelligence platform that tracks CM1 by product line alongside CM3 and contribution margin by channel. Start your free trial →

Siddharth Gangal is the founder of Fairview. He built Margin Intelligence after watching operators make pricing decisions on blended margin numbers that hid 40-point spreads between product lines.