Operational Profitability Analysis Framework

What this framework is for

Teams usually jump to one favorite lens:

• Sales pushes revenue.
• Operations pushes output.
• Finance pushes monthly P&L lines.

Each lens can be “green” while the business gets poorer. The framework exists to force a shared order of analysis so you do not optimize one KPI while leaking margin somewhere else.

This page is a method pillar, not a calculator and not a full replacement for the deep hosts linked below.

The five-step operational profitability map

Step 1 — Stop the leaks before you celebrate growth

Before you scale a product, customer, or department, ask where planned margin already disappears in small cross-functional decisions (discount + overtime + rush freight, rework, unbilled effort).

Deep page: Margin leakage analysis

Exit criterion: you can name the main leakage categories and owners — not only a revenue story.

Step 2 — Separate company margin stories

Clarify whether the problem is product-level gross economics or company-level operating burden. A product can look fine while operating margin collapses under overhead and inefficiency.

Deep page: Gross margin vs operating margin

Exit criterion: you know which margin layer is actually broken.

Step 3 — Product / SKU economics

Judge which SKUs fund the business after contribution and friction — not which ones merely sell the most.

Deep page: Product profitability analysis

Supporting math: Contribution margin explained

Exit criterion: protect / reprice / redesign / stop buckets exist for the top SKUs.

Step 4 — Customer economics

The same product can be healthy with one account and destructive with another. Large customers are not automatically good customers.

Deep page: Customer profitability analysis

Exit criterion: accounts are ranked by economics, not only by revenue.

Step 5 — Department / cost-center reality

When product and customer views are clear, check where department and cost-center economics explain the remaining operating result, and which owners control the actions that follow.

Deep page: Profitability by department

Exit criterion: department discussions use contribution and leakage evidence, not budget politics alone.

How to run the sequence in practice

1. Pick one consistent analysis period and use it across the views.
2. Run Step 1–2 with finance + operations in the same room.
3. Take the worst leakage themes into Step 3 and/or Step 4 — do not open every deep page at once.
4. Use Step 5 only when product/customer decisions need organizational ownership.
5. Write decisions and owners. Revisit on a fixed cadence.

If you need operating cash and liquidity pressure rather than margin structure, switch to the cash cluster (for example working capital optimization and related cash hosts) — that is a parallel control track, not a substitute for this map.

What this framework deliberately does not do

• It does not teach percentage-increase math (use the percentage-increase calculator pages for that).
• It does not retell locked Experience narratives from financial-control or manufacturing hosts.
• It does not replace the twin “operational efficiency and profitability” articles still under MERGE-REVIEW — those are separate cleanup work.
• It does not invent benchmark margins or “healthy” industry percentages.

One-page checklist

• □ Leakage categories named and owned
• □ Gross vs operating problem layer identified
• □ Top SKUs bucketed (protect / reprice / redesign / stop)
• □ Top accounts ranked by economics where relevant
• □ Department owners assigned for the decisions that remain

Related deep pages

• Margin leakage analysis
• Gross margin vs operating margin
• Contribution margin explained
• Product profitability analysis
• Customer profitability analysis
• Profitability by department
• KPI tracking — measurement discipline after the economic map is clear