Contribution per Customer
Contribution per Customer is the dollars each customer leaves on the table after their direct variable costs — the cash that flows to covering fixed costs and (eventually) profit. Formula: Contribution per Customer = ARPU − Variable Cost per Customer (hosting, support, payment fees, fulfillment per that customer). Distinct from gross margin because it's per-customer, not per-product — which lets you see which CUSTOMERS (not products) are paying for themselves. The KnowMBA POV: averaging contribution across customers hides the fact that 30% of your customer base often consumes more support cost than they pay in revenue. Find the parasites and price them out — or fire them.
The Trap
The trap is calculating one company-wide gross margin and assuming all customers contribute equally. They don't. A high-touch customer on a $99/month plan might consume $40/month of support, $15/month of hosting (heavy usage), and $3 of payment fees — leaving $41 contribution. A self-serve customer on the same plan might consume $5 support and $5 hosting — leaving $86 contribution. Same revenue, 2x contribution difference. If you don't measure per-customer contribution, you'll happily acquire more high-touch customers thinking they're identical to self-serve.
What to Do
Tag every customer with their support tickets/month, hosting consumption, payment-method fees, and any customer-specific variable costs. Compute contribution per customer monthly. Identify the bottom 10% by contribution — they're either paying too little, consuming too much, or both. Three actions: (1) Self-serve nudge (move them to lower-touch tier), (2) Price increase (charge for support overage), or (3) Offboard (politely decline renewal). Top SaaS companies like Atlassian have institutionalized this analysis.
Formula
In Practice
Atlassian famously runs a near-zero sales-touch model — their average contribution per customer is enormous because their variable cost is nearly all infrastructure. They explicitly price support as a separate paid SKU (Premium Support) so customers who need high-touch self-select into a higher contribution tier. As a result, Atlassian achieved the legendary 1,000+ FCF/employee ratio in the 2010s. Compare to enterprise SaaS that bundles unlimited support: those companies see contribution per customer drop dramatically as customer base diversifies into demanding accounts.
Pro Tips
- 01
Track contribution per customer by cohort. New customers often have lower contribution (heavier support load during onboarding) that improves over months. If contribution doesn't recover by month 6, the customer profile is structurally low-margin.
- 02
Compare contribution per customer across acquisition channels. Customers from referrals typically have 1.5-2x higher contribution because they self-onboard better. This is another reason referral channels disproportionately affect economics — not just CAC.
- 03
The 'contribution-to-CAC ratio' is more honest than LTV/CAC for short-term capital efficiency. Annual contribution ÷ CAC tells you how many years to payback on a fully-loaded basis. <0.5 means 2+ year payback (slow); >1.5 means cash-positive within a year (fast).
Myth vs Reality
Myth
“Contribution per customer is just gross margin per customer”
Reality
Gross margin uses revenue and COGS at the product level. Contribution per customer attributes specific support, hosting, and overhead to specific customers — capturing customer-mix effects that product-level margin misses. They diverge significantly when customers vary in usage intensity.
Myth
“Negative-contribution customers should always be fired”
Reality
Some negative-contribution customers are strategic: logos that close other deals, beta testers who shape the product, or temporary high-touch onboarding that pays back later. Diagnose strategic value before culling — but force the diagnosis explicitly, not by default tolerance.
Try it
Run the numbers.
Pressure-test the concept against your own knowledge — answer the challenge or try the live scenario.
Knowledge Check
Customer A pays $200/month, costs $40 in support and hosting. Customer B pays $200/month, costs $120 in support and hosting. Both have $300 CAC. What's true?
Industry benchmarks
Is your number good?
Calibrate against real-world tiers. Use these ranges as targets — not absolutes.
Contribution Margin per Customer
B2B SaaS at scaleElite (Self-Serve SaaS)
> 80%
Healthy
60-80%
Acceptable
40-60%
Marginal
20-40%
Negative
< 20%
Source: OpenView 2024 Benchmarks
Real-world cases
Companies that lived this.
Verified narratives with the numbers that prove (or break) the concept.
Atlassian
2010-2020
Atlassian built a near-zero sales-touch business by ruthlessly engineering high contribution per customer. They charged for premium support as a separate SKU, kept onboarding self-serve, and pushed enterprise customers toward Atlassian-University rather than dedicated CSMs. Result: contribution per customer at scale was 80%+ of ARPU. Combined with low CAC (organic-led), Atlassian achieved $4M+ revenue per employee — best-in-class SaaS efficiency that justified their growth-stage premium multiples.
Contribution per Customer
~80% of ARPU
Revenue per Employee
$4M+ at scale
Sales Touch
Near-zero
Premium Support
Paid add-on (self-select)
Contribution per customer is engineerable. Atlassian designed pricing and product to push variable costs onto customers who valued high-touch — keeping baseline contribution sky-high.
Hypothetical: Customer Success Reckoning
2024
Hypothetical: A $30M ARR vertical SaaS audited contribution per customer for the first time. They discovered 22% of customers had negative contribution due to enterprise CSM allocation. Rather than fire them, they restructured tiers: customers >$50K ARR got dedicated CSM (kept), customers $10-50K got pooled CSM (1 CSM per 30 accounts), customers <$10K got self-serve only. Contribution per customer jumped 45% within two quarters. Net retention barely moved — the 'high-touch' wasn't actually driving retention for small accounts.
Negative-Contribution % Before
22%
Negative-Contribution % After
4%
Contribution Lift
+45%
Net Retention Change
Negligible
High-touch CS often doesn't move retention — but always destroys contribution. Tier your touch model by contribution potential, not by customer demands.
Decision scenario
The Bottom-Decile Decision
You run $15M ARR vertical SaaS. New analysis shows the bottom 10% of customers (1,200 accounts) generate $900K ARR but consume $1.4M in support and infrastructure. Net contribution: -$500K. Top quartile customers contribute 70% margins. Board wants action before next quarter.
ARR
$15M
Bottom 10% ARR
$900K
Bottom 10% Cost
$1.4M
Net Contribution (bottom)
-$500K
Top Quartile Contribution Margin
70%
Decision 1
You can offboard the bottom 10%, raise their prices, or move them to self-serve. CFO favors offboarding for clean margin lift. CRO worries about logo count and review-site backlash.
Offboard bottom 10% — lose $900K ARR but save $1.4M cost, net +$500K contributionReveal
Restructure pricing tiers: introduce a new self-serve tier at 60% price reduction, zero CSM, eligible only for accounts <$2K ARR. Existing low-end customers grandfathered for 6 months then must convert or churn.✓ OptimalReveal
Related concepts
Keep connecting.
The concepts that orbit this one — each one sharpens the others.
Beyond the concept
Turn Contribution per Customer 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 Contribution per Customer into a live operating decision.
Use Contribution per Customer as the framing layer, then move into diagnostics or advisory if this maps directly to a current business bottleneck.