How to Run a Profitability Analysis

Profitability analysis answers a question that top-line reports cannot: where is money actually being made, and where is it being subsidised by the profitable parts of the business. In most mature businesses, the decomposition reveals a concentrated profit pool and a long tail of break-even or loss-making activity.

The framework here follows the standard cost-accounting treatment^[1], with the ABC (activity-based costing) refinements that have become standard since Kaplan and Cooper^[2].

1. Layer profitability — gross, contribution, operating

Three layers, each answers a different question:

• Gross profit = Revenue − COGS. Answers: is the product economics working at unit level? Gross margin varies by category — in 2024 SaaS benchmarks, median is 72–78%^[4]; retail runs 30–45%; services 40–60%.
• Contribution profit = Gross profit − Variable selling and marketing costs. Answers: after acquiring and serving the customer, what is left to cover fixed overhead?
• Operating profit = Contribution profit − Fixed overhead allocation. Answers: at the segment/product level, is this activity covering its share of overhead?

Most business reports stop at gross. That is where the money-losing long tail hides — products with 60% gross margin can be operating-loss if they require high-touch onboarding or heavy support.

2. By product or SKU

Compute gross margin per SKU. Rank them. The pattern is almost always Pareto: 20% of SKUs generate 60–80% of gross profit^[2].

For each SKU, also compute a variable-cost-to-serve: support tickets per customer × support cost per ticket, average onboarding time × loaded hourly cost, returns and refund rate × average transaction. Some products with high gross margin are actually contribution-negative after cost-to-serve. These are the quiet losses in most catalogs.

Action triggers from SKU-level analysis:

• SKUs with gross margin below 30% and meaningful cost-to-serve: discontinue unless they are loss leaders with proven attach rates.
• SKUs with low volume and low margin but high complexity cost (SKU count burdens operations): rationalise at next catalog review.
• Top 5 SKUs: protect. These are where operational improvement compounds fastest.

3. By customer segment

Segment by something operationally meaningful: size band (SMB / Mid-market / Enterprise), industry vertical, geography, acquisition cohort. For each segment, compute:

• Average revenue per customer.
• Gross margin per customer (carries category COGS).
• Fully loaded cost-to-serve (support tickets, CS time, custom work).
• Net contribution per customer.

The common pattern in B2B: SMB customers often have 30–50% lower gross margin after support costs than the company-wide average, while enterprise customers carry lower top-line margin but lower cost-to-serve, netting out similar. Mid-market is often the sweet spot — high ACV with moderate support burden. Reveal this in the data before you shift go-to-market strategy^[4].

A caveat on cost allocation: using revenue as the allocation base for shared overhead (CS, infrastructure, management time) systematically over-allocates to enterprise customers because they have higher revenue but often similar or lower incremental cost. Use activity drivers — ticket count, provisioned seats, time-use — where possible^[2].

4. By acquisition channel

Channels differ dramatically in customer quality, not just cost. Compute CAC, retention, LTV, and resulting LTV:CAC by channel:

• Organic (SEO, direct, content): Typically lowest CAC, highest retention, strongest LTV. Usually the best channel — except that it's capacity-constrained.
• Paid search: Medium CAC, intent-qualified leads, often strong retention. Scales but margin compresses at volume.
• Paid social: Variable CAC, lower intent, often weaker retention unless targeting is tight.
• Partnerships/referrals: Highest conversion rates, best retention, but dependent on partner capacity.
• Outbound sales: Highest loaded CAC, enterprise ACVs, long sales cycle. Economics work only at ACV above some threshold (typically $15k+ ARR).

The profitability picture changes by channel. A channel with 2.5:1 LTV:CAC might still be healthier than one at 4:1 if the first has better retention and shorter payback.

5. Turn analysis into action

Profitability analysis only matters if it changes decisions. Three typical outputs:

• Pricing changes. Segments with below-target margin often need a price increase, a feature pull-back, or a restructured offer.
• Product rationalisation. Loss-making SKUs and segments get cut. The secondary benefit — reduced operational complexity — often exceeds the direct margin improvement.
• Investment reallocation. Channels and segments generating the top-decile contribution margins get disproportionate sales, marketing, and R&D investment. Underperforming areas get frozen or cut.

Run the full analysis annually, update the headline numbers quarterly. The concentration of profit in a small share of activity is unchanging; the specific products, segments, and channels that occupy that share shift with market conditions. Knowing which is which, accurately, is what the work produces^[3].

6. The allocation question honestly

Profitability analysis depends on how you allocate shared costs. The two most common approaches — revenue-share allocation and activity-based costing — produce materially different answers.

Revenue-share allocation: if segment A is 60% of revenue, it gets 60% of shared overhead. Simple, but systematically wrong when segments have different cost-to-serve profiles. A segment with high ARPU but low support burden is over-charged; a segment with low ARPU and high support burden is under-charged.

Activity-based costing (ABC): allocate shared costs by their actual driver^[2]. Support time allocates by ticket volume; infrastructure allocates by actual usage; sales team allocates by hours spent per segment. More accurate, more work to maintain.

The practical recommendation for small business: start with revenue-share for the first pass, identify the 2–3 shared-cost pools where ABC would materially change the answer, and apply ABC to just those. Full ABC across every shared cost pool is rarely worth the operational overhead in businesses under $20M revenue.

7. Caveats and honest limits

Three ways profitability analysis misleads decision-makers when applied naively:

• Short-term versus long-term profitability. A segment losing money today might be the highest-LTV segment with long ramp. Pure current-quarter profitability kills new-market investments before they compound.
• Covering-overhead fallacy. "This segment is profitable once you exclude shared overhead" is usually a warning sign — shared overhead exists because the business needs it, and every segment needs to contribute to it.
• Strategic value beyond margin. Anchor customers, reference accounts, and segments that unlock distribution into other segments can be worth carrying at thin margin. The analysis should flag these but not decide for them.

The work produces numbers; judgment applies them. The analysis that routinely guides good decisions is the one that surfaces the hidden structure of where profit actually comes from, then gets debated by people who understand the strategic context beyond just the margin column.

8. Numeric worked example — segment decomposition

A $4M-ARR B2B SaaS runs a headline 78% gross margin (in line with the OpenView 2024 median of 72–78%^[4]) and an 8% operating margin. Decompose the $4M across three segments:

Segment       ARR      GM%    Support hrs/mo   Net contrib   Contrib/$ARR
─────────────────────────────────────────────────────────────────────────
Enterprise   $1.6M   82%    120             $1.08M         $0.68
Mid-market   $1.6M   78%     80             $1.05M         $0.66
SMB          $0.8M   74%    160             $0.28M         $0.35

Aggregate gross margin looks uniform; the contribution picture is not. SMB carries 2x the support burden per dollar of ARR and half the contribution efficiency. Revenue-share overhead allocation would make SMB look break-even; ABC (driver = support hours) makes it contribution-weak, with the difference absorbed by enterprise.

Decision: raise SMB floor price by 20%, accept a 10% logo-churn uplift on that cohort, and the expected effect is roughly $60k ARR attrition against $105k of margin recovery on retained accounts — a positive trade even before the operational simplification from fewer low-value seats.

9. Failure modes worth naming

• ABC over-engineering. A ticket-time-based allocation model needs weekly maintenance to stay accurate. Small operators who build a 12-driver ABC model usually abandon it within a year. Pick 2–3 drivers that actually move the answer and accept approximation on the rest^[2].
• Conflating profitability with strategic value. A flagship enterprise logo may be contribution-negative on support cost but unlock three similar logos through reference calls. Quantify the strategic dependency (how many deals cite it?) before cutting a loss-making anchor account.
• Stale fixed-overhead allocation. Overhead that was 18% of revenue two years ago may be 25% today after an ops hire wave. Rerun the full analysis when headcount or infrastructure crosses a step function; quarterly deltas are not enough.

As of 2026-Q2, the SaaS profitability picture skews toward cost-of-revenue discipline — public SaaS gross margins have held in the 72–78% band while S&M efficiency has compressed^[4], meaning incremental profitability work flows more from segment/channel rationalisation than from squeezing unit margin lower.