Historical performance is not a backward-looking ritual; it is the most efficient way to falsify (or fortify) the forward thesis. A clean, decision‑grade read of the last 12–16 quarters tells you what the engine actually produces—by segment and route‑to‑market—when price changes, mix shifts, promotions ebb and flow, competitors react, or operations strain. This chapter focuses on turning the income statement into bridges that quantify drivers you can underwrite: price realization, volume, mix, channel, geography, product family, FX, inorganic moves, and one‑offs. The output should plug directly into your demand, pricing, unit‑economics, and scenario work so the “plan” is a continuation (or an intentional break) from what’s been demonstrated.
13.1 Revenue Bridge Analysis – Step-by-Step Guide
A revenue bridge explains how the business moved from Revenue A (period 0) to Revenue B (period 1) by isolating the drivers that matter for underwriting. The goal is not just the picture; it is the math and governance behind it—definitions, allocation rules, reconciliations, and confidence labels—so Finance, Sales, and the deal team agree on what is “price,” what is “volume,” and what is simply noise.
What the bridge must answer (and for whom)
- For investors: What portion of growth is repeatable (price power, mix, expansion) versus episodic (one‑offs, promotions, timing)? What is organic, constant‑currency growth after stripping FX and M&A?
- For operators: Which segments and channels created or destroyed realized price? Where did promotions or paid placement buy volume at poor economics?
- For risk: How much of the change came from customers or SKUs with delist, churn, or compliance exposure?
Freeze the rules before you compute
- Revenue definition: Use vendor‑realized revenue (list − on‑invoice discounts − off‑invoice/promos − returns/chargebacks − marketplace take‑rates) to align with the pricing waterfall (Chapter 8.2). Document exceptions (e.g., gross vs. net for marketplaces; pass‑through freight or fuel surcharges).
- Scope and granularity: Build bridges at total company and at least two cuts that drive economics (e.g., Product Family × Route‑to‑Market; Region × Segment).
- Comparison windows: LTM vs. prior LTM, YoY by quarter, and YTD—pick one primary view and reproduce the others from the same base.
- Currency: Present constant‑currency results (period‑1 revenues restated at period‑0 average rates or rolling monthly rates) and show the FX step explicitly.
- Organic vs. inorganic: Separate M&A/divestiture effects. Pro forma if transparency exists, but never bury inorganic growth in “volume.”
Assemble the minimum viable data pack
Request once; reuse everywhere:
- GL revenue by month with adjustment details (discounts, rebates, returns, chargebacks, take‑rates).
- Order/invoice line‑items: SKU, quantity, list price, net price, discounts, promo codes, customer, channel, ship date, region, currency.
- Customer master: segment/tier, route‑to‑market, region, “new vs. existing” flag, parent/child hierarchy.
- Product master: family, KVI status, lifecycle (new/active/EOL), regulated or approval‑bound flag.
- Promotions and price changes: effective dates, fences, and guardrails; paid placement spend where relevant.
- M&A/divestiture log: close dates, included SKUs/customers/geos, pro forma notes.
- FX rates: monthly averages used by Finance.
- Calendar/timing notes: 53rd week, shutdowns, stockouts, backlog burn‑down.
- SaaS/recurring: ARR/NRR roll‑forward (New, Expansion, Contraction, Churn) with cohorts and price/seat logs.
- Marketplace/platform: GMV, take‑rates by tier/category, refunds, penalties.
The decomposition methods (pick once; document)
To avoid “residual” fights, use explicit formulas and apply them consistently.
- Price–Volume–Mix (transactional):
Work at the line‑item or SKU‑family level. A robust and simple approach is the mid‑point (Fisher) method which splits cross‑terms fairly:- Volume effect = Σ(Q1−Q0)×(P0+P1)/2(Q₁ − Q₀) × (P₀ + P₁)/2(Q1−Q0)×(P0+P1)/2
- Price effect = Σ(P1−P0)×(Q0+Q1)/2(P₁ − P₀) × (Q₀ + Q₁)/2(P1−P0)×(Q0+Q1)/2
- Mix effect = the remainder after isolating price and volume at the family or segment level (i.e., change in composition across SKUs/segments holding total volume and weighted average price constant).
Where list/discounts are available, break Price into List change, On‑invoice discounts, Off‑invoice/promo, Take‑rate change, and Compliance/chargebacks to align with realized price analytics (8.2).
- Order math (e‑commerce & retail):
Revenue = Sessions × Conversion × Orders per buyer × AOV (units × net unit price). Bridge each driver; tie AOV to realized price factors. - ARR roll‑forward (SaaS/recurring):
ΔARR = New + Expansion − Contraction − Churn ± Price − FX ± M&A.
Keep Price separate from Expansion/Contraction (true re‑rating vs. seat/module adds). Use cohorts to reconcile to NRR (6.3). - Marketplace net revenue:
Net Rev = GMV × Take‑rate − Incentives − Refunds/Penalties. Bridge GMV drivers (buyers × orders/buyer × AOV), then isolate take‑rate and penalty shifts.
Step‑by‑step build (from blank sheet to decision‑grade)
1) Reconcile the perimeter
Start with booked revenue Period 0 → Period 1. Add a first bridge that isolates FX and M&A/divestitures. Now you have organic, constant‑currency change to decompose.
2) Choose the unit of analysis per cut
- Transactional: SKU family × Region × Channel.
- SaaS: Cohort × Segment × Product family.
- Marketplace: Category × Tier × Region.
Document any roll‑ups.
3) Normalize for timing and policy artifacts
- Calendarization: correct 53rd week, holiday shifts, or one‑time backlog release.
- Policy & accounting: flag any revenue‑recognition changes (sell‑in vs. sell‑through, bill‑and‑hold, multi‑element allocation). Do not treat these as “price” or “volume”; show a separate step.
4) Compute the “price tree” before anything else
Walk realized price from list to net:
List → − On‑invoice discounts → − Off‑invoice promotions → − Take‑rates/fees → − Chargebacks/compliance → = Vendor‑realized net price.
Quantify the change in each branch vs. prior period. This isolates true price power from promotion mix or channel fees.
5) Run the price–volume–mix math
Apply the mid‑point formulas at your chosen granularity. Present in this sequence: Price → Volume → Mix. For SaaS, pair with ARR roll‑forward so the field sees both lenses.
6) Attribute mix visibly
Break Mix into the drivers that matter for underwriting: Product mix, Geography mix, Channel/route‑to‑market mix, Customer/segment mix. Avoid dumping all cross‑terms into a single “mix” bar.
7) Compile the bridge narrative
Create a Revenue Bridge Canvas for every top cut that states, in plain English, why each bar moved (e.g., “Retail channel −$3.2M: higher take‑rates and OTIF penalties; realized price −210 bps despite +90 bps list increase”).
8) Tie to economics
- Map Price changes to CM2 via the pricing waterfall (8.2) and cost‑to‑serve (10.4).
- Map Volume to capacity (10.2) and service (10.3) to explain sustainability.
- Map Mix to NRR/CAC (6.3, 9.4) where channel and segment economics differ.
9) Produce three standard bridges
- Company LTM YoY (constant currency, organic).
- Top Segment (e.g., Product A × Direct NA).
- Recurring/ARR roll‑forward (SaaS only).
Use the same definitions and allocation rules across all three.
10) Quality‑assure and lock
Reconcile to GL by period; ratio‑of‑sums for roll‑ups; footnote exclusions; label low‑confidence cuts. A second person should reproduce each bar from source files.
Practical allocation rules (write them on the page)
- Promos vs. price: Promotions that are discounts belong under Price; funded paid placement lives outside Price (treat as CAC/marketing cost) unless it permanently changes take‑rate.
- Returns and chargebacks: Include their net revenue effect under Price (realized price) and their cost‑to‑serve effect in CM2 (10.4).
- Channel fees/take‑rates: Treat as part of realized price, not as opex.
- Intro SKUs and EOL: When new SKUs launch or old ones sunset, attribute to Mix; if pricing ladders changed, show a Price bar as well.
- Large deals/projects: Call out as a separate One‑off step if the revenue pattern will not recur at similar margins or conversion cost.
Templates you can copy as you work
Revenue Bridge Canvas (one page per cut)
- Scope & period: [e.g., LTM through Jun‑2025, constant currency, organic].
- Starting revenue → Ending revenue: values and % change.
- Bars and $ impact: FX, M&A, Policy/Timing, Price (List, On‑invoice, Off‑invoice, Take‑rate, Chargebacks), Volume (units/orders/ARR adds), Mix (product, channel, region, segment), One‑offs.
- Plain‑English attribution: top 3 reasons with evidence (price file, promo calendar, take‑rate letter, S&OP notes).
- Economics link: CM2 impact from price moves; CTS impact from penalties/returns; CAC/payback impact from channel shift.
- Confidence & QA: reconciliation note; low‑confidence cuts flagged.
Data request (issue once)
- GL revenue with discount/return/chargeback/take‑rate detail by month.
- Order/invoice line‑items with SKU, quantity, list, discount, net, currency, customer, channel, ship date.
- Price lists and promo calendars, with effective dates and fences.
- Customer and product masters; route‑to‑market mapping.
- M&A/divestiture log; FX monthly averages; accounting policy notes.
- SaaS cohort/ARR roll‑forward (if recurring); marketplace GMV and take‑rate files (if applicable).
Driver dictionary (put in the appendix)
- Price: list changes, on‑invoice discounts, off‑invoice promotions, take‑rates/fees, chargebacks/compliance fines.
- Volume: units shipped, orders, active buyers, new ARR, seats/modules added.
- Mix: product family, channel/route, region, segment/tier, SKU lifecycle.
- Policy/Timing: accounting changes, calendar effects, backlog release.
- FX: translation only; transaction FX shows up inside price realization if priced in multiple currencies.
- M&A/Divestitures: inorganic additions/subtractions.
QA checklist (use verbatim)
- Revenue definition matches vendor‑realized basis; price waterfall reconciles to GL discounts, rebates, and fees.
- FX and M&A isolated before decomposing; constant‑currency policy documented.
- Price/volume/mix math uses mid‑point (Fisher) or another documented method; no unexplained residuals.
- ARR roll‑forward reconciles to bookings/billings and recognized revenue; price re‑ratings separated from expansion/contraction.
- Promotions treated consistently; platform take‑rates inside realized price; paid placement treated as CAC (unless it structurally changes fees).
- Ratio‑of‑sums for roll‑ups; currency consistency; all exhibits footnoted; second‑person reproduction completed.
- Low‑confidence cuts labeled; known data gaps and their expected direction of bias disclosed.
Interpretation guide (what the bars usually mean)
- Price ↑ with stable or improved mix: Evidence of differentiation (8.4); likely supports higher realized price corridors and lower promo dependence.
- Price ↑ but CM2 ↓: Take‑rates, penalties, or returns/chargebacks may be rising—check 10.3 and 10.4.
- Volume ↑ with Mix ↓: Growth via channels/segments with weaker economics; revisit channel spend and price fences (9.2, 9.3).
- Mix ↑ driven by route‑to‑market shift: If mix improves because of direct channels, CAC/payback may also improve (9.4); validate with funnel and cost‑to‑serve.
- FX dominates: Underwrite constant‑currency; consider natural hedges or indexation (11.3, 11.4).
- One‑offs large: Move those dollars to upside‑only; reflect in terms (earnouts, covenants).
Red flags—and how to respond
- Growth mainly from promotions (off‑invoice) with flat or falling list: Lower realized price corridors; enforce discount guardrails; test elasticity (6.4).
- Take‑rates and compliance fines rising in marketplaces/retail: Treat as structurally realized price pressure; diversify channels or raise price fences (9.2, 11.4).
- Revenue recognition policy shifts driving growth: Move to a separate Policy bar; don’t underwrite as price or volume; consider a quality‑of‑earnings deep dive.
- High return/chargeback rates contributing to “volume”: Shift attention to 10.4; pull back on low‑quality demand.
- Mix skew to a few customers/SKUs: Concentration risk; scenario a delist or churn (7.4, 10.1).
72‑hour sprint plan (from blank page to a defendable bridge)
- Day 0: Freeze revenue definition, scope, periods, and constant‑currency policy; issue the single data request.
- Day 1: Land GL tie‑out; build the FX/M&A/policy first bridge; compute realized price tree (list → net).
- Day 2: Run price–volume–mix math at chosen granularity; build ARR roll‑forward (if recurring) and marketplace net‑revenue bridge (if applicable); attribute mix (product/channel/region/segment).
- Day 3: Produce three standard bridges; write plain‑English attributions; push price and mix deltas into CM2, NRR, CAC/payback; label confidence; log verifier sign‑off.
Acceptance criteria (your “done” checklist)
- Organic, constant‑currency growth computed and reconciled to GL; FX/M&A/policy bars isolated.
- Price–volume–mix bridges produced at company and at least one economic cut; price tree reconciles to the pricing waterfall.
- ARR roll‑forward (if recurring) and/or marketplace net‑revenue bridge (if relevant) completed and reconciled.
- Mix properly attributed (product, channel, region, segment); no unexplained residuals.
- Economics links explicit (CM2, NRR/CAC/payback); model updated within 24 hours; confidence labels present.
- QA complete with second‑person reproduction; all exhibits footnoted; clean‑team rules observed.
Run this guide and your revenue story stops being a line on a chart. It becomes a set of auditable drivers you can price, staff, and defend—so the plan you underwrite is a continuation of demonstrated price power and repeatable mix, not a hope that promotions or one‑offs will keep saving the quarter.
13.2 Margin Decomposition Template
Margin work in diligence is not an accounting exercise; it is a translation between how value is created (price power, mix, efficiency, service quality) and how cash lands (CM2 and beyond). The objective is a decision‑grade margin tree and a set of bridges that quantify what drove the last 12–16 quarters of margin up or down—by segment and route‑to‑market—and what that implies for the forward case. The output must reconcile to the GL, align with your revenue bridge (13.1), and plug directly into pricing (Chapter 8), cost‑to‑serve (10.4), capacity (10.2), service levels (10.3), and digital unit costs (12.1/12.2).
Define the margin tree up front
Use consistent definitions across every exhibit and label them on the page:
- Vendor‑realized revenue (VRR): list price minus on‑invoice discounts minus off‑invoice/promotions minus take‑rates/fees minus returns/chargebacks.
- CM1 (Gross Margin): VRR − COGS (materials/components, direct labor, manufacturing/fulfillment overhead actually in COGS, landed freight to inbound, packaging, duties; for SaaS: hosting and core third‑party compute if presented above the line).
- CM2 (Contribution after Serve): CM1 − Cost‑to‑Serve (CTS) (pick/pack/ship outbound, accessorials, returns/refurbishment, compliance penalties/credits, support/success minutes, field/service, payment processing and fraud, platform/third‑party API usage, cloud overage tied to delivering the service).
- Optional CM3 (after variable selling): CM2 − variable S&M (paid placement, performance marketing that scales with orders, reseller commissions). Use only if the operating model benefits from it; otherwise keep S&M below the line.
Write once how the company books hosting, support labor, outbound freight, and platform fees; these classifications materially affect comparability and must be frozen before analysis.
Build a single margin narrative anchored in four bridges
Every analysis references one or more of these bridges:
- Price–Cost Gap Bridge: from VRR to CM1 by isolating realized price drivers versus input costs (commodities, components, labor, freight, duties).
- COGS Variance Bridge: from standard to actual cost per unit (or from prior period cost to current), decomposed into rate and efficiency variances.
- Cost‑to‑Serve Bridge: from CM1 to CM2 by bucket (shipping, accessorials, returns, support, payment fees, API/cloud, penalties).
- Mix & Channel Economics Bridge: how product/channel/region/segment mix changed CM1% and CM2%, even if price and unit costs were flat.
Step‑by‑step guide (from blank sheet to decision‑grade)
1) Freeze scope, segmentation, and period
Adopt the same segments used elsewhere (customer/job, size band, route‑to‑market, region, product family). Choose one primary time view (LTM vs. prior LTM or YoY by quarter) and reproduce others from the same base. Work in constant currency for comparability.
2) Land the minimum viable data pack
Ask once; reuse across all bridges.
- Revenue and discounts files at invoice/line level (list, net, promo codes, take‑rates, returns/chargebacks).
- COGS detail by SKU or family: BOMs, standard costs and revisions, purchase prices, PPV logs, labor rates, routings, overhead rates and absorption, scrap/yield, inbound freight/duty, broker/surcharges, inventory adjustments (E&O, revaluation).
- CTS detail: WMS/TMS pick and pack minutes, materials, parcel/LTL invoices with accessorials, returns/refurb costs, payment processor fees and chargebacks, support/success minutes and rates, field/service logs, cloud invoices (compute/storage/egress) and third‑party API bills, SLA credits/retail penalties.
- Operational context: service metrics (OTIF, latency), capacity headroom, expedite spend, changeover time (10.2/10.3), promotions calendar, KVI list.
- Accounting context: capitalization policies (software, tooling), overhead allocations, freight capitalization, classification of hosting/support, revenue recognition notes.
3) Draw the margin tree first
On one page, walk List → VRR → CM1 → CM2 with dollars and percentages for the period and prior comparable period. This becomes the anchor everyone references.
4) Compute the Price–Cost Gap Bridge
Start with VRR. Build bars for:
- Price tree: List, on‑invoice discounts, off‑invoice/promos, take‑rates/fees, returns/chargebacks.
- Input costs: materials/components (and commodity indexation), direct labor, manufacturing overhead, inbound freight/duty.
- Result: CM1 movement from prior to current period.
Use mid‑point (Fisher) math to split price and volume fairly, then attribute the remainder to mix. Keep FX and M&A outside this bridge.
5) Run a COGS variance analysis (rate vs. efficiency)
For manufactured or assembled goods, use the standard variance taxonomy; for each SKU family, compute:
- Material price variance (MPV) = (Actual unit price − Standard unit price) × Actual quantity purchased.
- Material usage variance (MUV) = (Actual quantity used − Standard quantity allowed for actual output) × Standard unit price.
- Labor rate variance (LRV) = (Actual hourly rate − Standard rate) × Actual hours.
- Labor efficiency variance (LEV) = (Actual hours − Standard hours for actual output) × Standard rate.
- Manufacturing overhead variances (spend, efficiency, and volume/absorption).
- Yield/scrap variance (if tracked outside of usage).
Reconcile these to the GL’s variance accounts; keep an audit trail by SKU family or value stream.
For SaaS and usage businesses, translate to unit‑cost variances: $ per API call/account/order, split into rate (provider price or on‑demand mix) and quantity/efficiency (inefficient queries, low cache hit, data retention bloat).
6) Build the Cost‑to‑Serve (CTS) Bridge
From CM1 to CM2, quantify each bucket as $ and as % of VRR, by segment and channel:
- Outbound shipping and accessorials (fuel, oversized, residential).
- 3PL fees and storage (for fast turns); brokerage and duties on outbound if any.
- Returns/reverse logistics (probability × cost − recovered value), refurbishment, markdowns.
- Payment processing fees and chargebacks; fraud losses.
- Support/success minutes and field/service costs; warranty reserve movement.
- Platform/marketplace credits/penalties; OTIF/compliance fines.
- Cloud and third‑party API unit costs tied to serving transactions/tenants (for digital products).
Use time‑driven ABC for people steps and invoice‑anchored numbers for bought services. Reconcile totals to the GL (10.4).
7) Attribute mix explicitly
Do not hide composition effects. Decompose mix into:
- Product mix (shift to premium/complex SKUs or regulated lines).
- Channel/route‑to‑market mix (direct, marketplace, distributor, OEM).
- Geography mix (landed cost and duty changes by region).
- Customer/segment mix (enterprise vs. SMB; tiered support entitlements).
Show how mix alone lifted or diluted CM1% and CM2%.
8) Normalize and isolate non‑recurring items
Call out the dollars and logic for E&O write‑downs, warranty campaigns, recall costs, one‑time logistics disruptions, unusual hedging gains/losses, and accounting policy shifts. Move these to “one‑offs” and keep them out of recurring drivers.
9) Tie to the operating model and the forward case
- Translate price–cost gap into realized price corridors (8.2) and indexation policy.
- Convert COGS variances into capacity and supplier actions (10.1, 10.2) and procurement terms.
- Convert CTS drift into route/network fixes, policy and packaging changes, and support deflection (9.2, 10.4, 10.3).
- Reflect mix in channel spend and coverage (9.1–9.4).
10) Push toggles into the model within 24 hours
Add scenario levers for commodity/fuel/wage moves, FX, returns rate, take‑rates, cloud on‑demand share, and support minutes. Update CM2 by segment/channel accordingly.
Practical formulas and allocation rules (state on the slide)
- CM1% = CM1 ÷ VRR; CM2% = CM2 ÷ VRR.
- Price–cost gap (ΔCM1%) ≈ ΔRealizedPrice% − (wmaterial×ΔMaterialCost(w_material × ΔMaterialCost%) + (w_labor × ΔLaborCost%) + (w_freight × ΔInboundFreight%) + (w_overhead × ΔOverhead%)(wmaterial×ΔMaterialCost, where weights are prior‑period cost shares.
- Return drag on CM2 (per order) ≈ Return probability × (reverse logistics cost − recovered value) + incremental support minutes × rate.
- Payment fee drag ≈ Card‑processed VRR × Δbps.
- Cloud unit‑cost = Cloud spend attributable to serving ÷ (API calls or active accounts); split rate (provider price, on‑demand vs. reserved) and efficiency (engineering fixes).
- Use ratio‑of‑sums for roll‑ups; never sum of ratios.
- Promotions and take‑rates live under Price; paid placement is variable S&M (optional CM3), not Price, unless it permanently changes fees.
- Outbound shipping belongs in CTS; inbound freight/duty belongs in COGS.
- Hosting/support classification: respect the company’s policy but disclose it prominently; for cross‑company comparisons, provide an “analytical restatement”.
Templates you can copy directly
A) Margin Tree Canvas (company or segment)
- Scope & period; VRR, CM1, CM2 (dollars and %).
- Price tree to VRR with bars and dollars.
- COGS buckets with dollars and % of VRR.
- CTS buckets with dollars and % of VRR.
- One‑offs and policy notes; confidence label; GL tie‑out statement.
B) Price–Cost Gap Card (per product family × region or segment)
- Realized price movement (list, discounts, promos, take‑rates, returns) with evidence.
- Input‑cost movement (materials, labor, freight, duties, overhead).
- Net CM1 change; sensitivity to commodity/fuel ± bands; indexation coverage; owner and next action.
C) COGS Variance Card (manufactured goods)
- MPV, MUV, LRV, LEV, overhead variances; scrap/yield; absorption.
- Root causes (supplier, yield, mix, learning curve); mitigation and timing; GL reconciliation note.
D) CTS Variance Card (by segment/channel)
- Shipping & accessorials, returns/refurb, support minutes, payment fees/fraud, API/cloud, penalties/credits.
- Drivers (distance/speed, DIM/oversize, policy thresholds, contact rate, SLA adherence); levers and owners.
E) Mix & Channel Economics Card
- Mix deltas across product/channel/region/segment; CM1%/CM2% impact; CAC/payback and NRR implications; planned re‑weighting.
QA and data‑hygiene checklist (use verbatim)
- Margin definitions (VRR, CM1, CM2) written on page; hosting/support/outbound shipping classification disclosed.
- GL tie‑out complete for COGS and CTS totals; timing differences explained.
- Constant‑currency policy applied; FX separated before decomposition.
- Price–volume–mix uses mid‑point method; no unexplained residuals.
- Variances reconciled to standard‑cost accounts (where used); absorption and E&O isolated.
- Invoice‑anchored rates used for freight, duties, processors, cloud, APIs; TDABC rates documented for people time.
- Ratio‑of‑sums applied to roll‑ups; confidence labels set (H/M/L).
- One‑offs flagged; promotions/paid placement and take‑rates treated consistently with revenue work.
- Verifier re‑computation passed; clean‑team protocols observed.
Interpretation guide (what the deltas usually mean)
- CM1 ↑ while realized price flat: real cost wins (e.g., mix to low‑duty geos, supplier price breaks, yield fixes). Test sustainability and indexation.
CM1 ↓ despite list increases: promotions or take‑rates are offsetting; discount governance or channel shift likely required. - CM2 ↓ with CM1 flat: serving the business is getting more expensive—returns, shipping, support, or platform/API costs rising. Move quickly on policy, packaging, routing, and deflection.
- Mix dilutes CM2% but lifts revenue: growth is coming through weaker‑economics channels or segments; revisit coverage and price fences.
- Cloud unit‑cost spikes with growth: reserve coverage low or engineering hotspots; add FinOps fixes to Day‑1 plan.
Early‑warning indicators (monitor monthly post‑close)
- CM1% and CM2% by segment/channel with variance to plan; price–cost gap trend.
- Freight/accessorials as % of VRR; return rate and “no fault found” share; support minutes per order/account.
- Payment fee bps; chargeback rate; fraud losses.
- Cloud $ per API call/account; on‑demand share; third‑party API cost per active.
- Commodity index proxies; supplier lead‑time and PPV; absorption variance.
- Penalties/credits (OTIF/SLA) and delist warnings.
- Mix drift: share of revenue in low‑CM2 channels/segments.
Red flags—and immediate responses
- CM2 erosion concentrated in marketplaces/retail: rising take‑rates or penalties; diversify channels, tighten OTIF, raise free‑shipping thresholds, and enforce return policies.
- Manufacturing absorption swings driving CM1 volatility: capacity utilization or standard setting is off; adjust rates, level‑load, or rebase standards post‑close.
- High E&O or warranty spikes: quality or demand‑planning issues; reprice or exit SKUs; launch root‑cause program with 90‑day targets.
- Support minutes and SLA credits trending up: reliability gap; launch error‑budget governance (12.1) and raise deflection/self‑serve.
- Cloud/API overage bills without growth in actives: runaway queries or leakage; pause feature rollouts until hotspots fixed; add reserved commitments.
90‑day margin plan (only moves that change cash fast)
- Indexation: add CPI/commodity/fuel clauses in new and renewal contracts (where legal); harden discount guardrails and price fences (8.2).
- Freight & packaging: rebid priority lanes; add a secondary gateway; reduce DIM weight; set late cutoff capacity (10.1, 10.4).
- Returns: tighten policy and triage; improve fit/quality; stand up refurb channels where margin‑positive.
- Support & success: deploy deflection and knowledge base fixes; re‑tier entitlements; staff to severity SLAs; automate low‑value contacts.
- FinOps: convert eligible cloud services to reserved/savings; fix top two hotspots (cache/query); renegotiate or replace low‑ROI APIs.
- Supplier terms: dual‑source critical components; lock allocation priority; negotiate MOQs and lead times; secure cost‑down roadmaps.
- Standards reset: if standard cost is stale, re‑set standards to reduce false variances; align absorption to realistic volumes.
72‑hour sprint plan (from blank page to a defendable margin view)
- Day 0: Freeze definitions and classifications; issue a single data request; align constant‑currency policy.
- Day 1: Publish the margin tree (List → VRR → CM1 → CM2); compute the Price–Cost Gap Bridge and identify top three drivers.
- Day 2: Run COGS and CTS variance bridges for two largest segments/channels; attribute mix; isolate one‑offs; reconcile to GL.
- Day 3: Push toggles into the model (price, commodities, freight, returns, payment bps, cloud, support minutes); issue a 90‑day margin plan with owners; set early‑warning indicators; document confidence and verifier sign‑off.
Acceptance criteria for a decision‑grade margin decomposition
- Margin tree published with clear definitions; GL tie‑out complete; FX/M&A isolated.
- Four bridges produced (Price–Cost Gap, COGS Variance, CTS Bridge, Mix & Channel) for company and top segments/channels.
- Equations, allocation rules, and confidence labels on the page; no unexplained residuals; ratio‑of‑sums respected.
- Model updated within 24 hours; red flags and 90‑day actions assigned with owners and timelines; clean‑team rules observed.
Use this template and margin talk becomes a precise, auditable story: where value is created, where it leaks, and which few levers move CM2 quickly and sustainably in your hold period.
13.3 Working Capital Diagnostic Checklist
Working capital is the cash reality of your business model. It converts bookings into bank balances (or not), determines how fast you can fund growth without external capital, and telegraphs operational health long before the P&L does. A robust diligence looks past the headline DSO/DIO/DPO to the machinery underneath—terms discipline, deductions, returns, reserves, processor holdbacks, inventory accuracy, supply‑base power, project billing hygiene, and seasonal bulges. Your aim is to produce a segmented, decision‑grade picture of working capital, express it as levers that move cash in the next 13 weeks and 12 months, and wire those levers into valuation, covenants, and the 90‑day plan.
Scope and definitions—freeze what you will measure
Anchor every exhibit to the same definition: Operating Net Working Capital (oNWC) = (Trade Receivables + Inventory + Other Operating Current Assets) − (Trade Payables + Other Operating Current Liabilities), explicitly excluding cash, short‑term debt, current tax, and one‑off items. Compute and discuss both absolute dollars and days (DSO, DIO, DPO, CCC). Segment by product family, customer tier, route‑to‑market, and region; averages hide cash.
Data pack—request once, reuse everywhere
- Trial balance and monthly balance sheets (36 months if available).
- AR aging by customer (current/30/60/90/120+), dispute and deductions codes, credit notes, chargebacks, processor holdbacks/reserves, credit insurance, factoring/SCF usage.
- AP aging by vendor, terms by contract and actual paid‑days, early‑pay discounts, dynamic discounting/SCF files, three‑way‑match exceptions.
- Inventory by site and category (raw/WIP/finished/field stock/consigned/VMI/in‑transit), cycle‑count results, slow‑moving/obsolete reports and reserves, returns/RMA and refurbishment.
- Revenue/COGS monthly, by segment/channel; purchase journal or receipts (for DPO on purchases); promotions calendar, trade spend accruals, retailer/marketplace penalties.
- Contracts and policies: payment terms (sell‑side/buy‑side), incoterms, billing milestones, retention/withhold clauses (projects), processor/marketplace payout terms, warranty/returns policy.
- SaaS/recurring: bill timing (annual vs. quarterly vs. monthly), prepaid/contract liabilities (deferred revenue), renewal schedule, refund/cancellation terms.
- Project‑based: WIP schedules, under/over‑billing, change orders, retentions, certifications.
- FX exposure by currency for AR/AP; tax/VAT receivable/payable.
- Seasonality markers (peak months, Chinese New Year builds, holiday freezes), S&OP calendars.
Formulas you will use (write them on the page)
- DSO = (Average Trade AR ÷ Credit Sales) × Days. (Also compute cohort DSO by customer tier to expose tail pain.)
- DIO = (Average Inventory ÷ COGS) × Days. (Also compute Weeks of Supply and turns.)
- DPO (purchases‑based) = (Average Trade AP ÷ Purchases) × Days. Use purchases rather than COGS where possible to avoid absorption noise.
- Cash Conversion Cycle (CCC) = DSO + DIO − DPO. For recurring/subscription models, compute Days Contract Liability (DCL) = (Deferred Revenue ÷ Revenue) × Days and show Net CCC (CCC − DCL) to capture negative working‑capital effects.
- Early‑pay APR (to judge discount economics) ≈ Discount % ÷ (Days saved/365).
- Inventory health: % slow‑moving (no movement in 90/180/360 days), RMA rate, first‑pass refurb yield.
Step‑by‑step diagnostic (from blank sheet to decision‑grade)
1) Reconcile and normalize
Tie ending balances to the GL; strip FX and M&A first. Adjust for accounting policy shifts (e.g., freight capitalization, standard‑cost rebase). Anchor analysis in constant currency and like‑for‑like perimeter.
2) Build the working‑capital bridge
Show how oNWC moved from prior LTM to current LTM by driver: AR, Inventory, AP, Other Op Assets/Liabilities, FX, scope, one‑offs. Write one sentence per bar in business language (e.g., “$12.4M AR increase from retail deductions and processor reserves; paid‑days slipped 7.”).
3) Decompose receivables beyond DSO
- Aging & tail risk: % >60/90/120; top‑20 customer balances and delist/churn hazard; cross‑age with dispute codes.
- Terms discipline: policy vs. actual paid‑days by tier/channel; audit “net‑30 means net‑45” leakage; EOM and receipt‑of‑goods wrinkles.
- Deductions & chargebacks: root‑cause mix (OTIF, price, promo, compliance); win rate on disputes; cycle time to resolution; accrual adequacy.
- Processor/marketplace effects: payout lags, reserve rates, rolling holdbacks; fraud/chargeback programs and thresholds.
- Credit risk: insurance limits and utilization; risk tiering; first‑order default probability signals (dispute rate, days past due trend).
- Factoring/ABL: eligible base, advance rates, recourse terms, covenants; cost vs. early‑pay APR.
4) Examine inventory as a system
- Structure: mix across raw/WIP/FG/field stock/consigned/VMI/in‑transit; location accuracy vs. ERP; cycle‑count variance.
- Health: slow‑moving and obsolete ladders; weeks of supply by KVI/SKU family; RMA loop and refurb yield; shrink/scrap trend.
- Planning & capacity link: forecast error, safety‑stock policy, MOQ/lead‑time drag; changeover time and lot‑size economics (10.2); E&O reserve adequacy.
- Ownership & terms: incoterms cutoffs (FOB vs. DDP), title transfer in transit, supplier‑owned inventory on‑site, consignment accounting.
- Seasonality: pre‑build profiles; peak sell‑through vs. carryover risk.
5) Pressure‑test payables
- Term discipline: policy vs. contracted vs. actual paid‑days; early‑pay usage and realized APR; dynamic discounting or SCF penetration; share of spend on “Day‑0” rails (card, ACH on receipt).
- Leakage controls: three‑way‑match exceptions, duplicate payments, vendor‑master hygiene (duplicates, bank change controls), price/quantity variances.
- Supplier power: concentration, sole‑source status, allocation risk; penalties for late pay; relationship temperature.
- Compliance: public‑sector prompt pay rules, construction lien waivers, labor/material lien releases.
6) SaaS/usage specifics
- Billing cadence & DCL: annual vs. quarterly vs. monthly prepay; DCL by tier; renewal cliffs; refunds.
- Collections: involuntary churn (failed payments), dunning effectiveness, dispute rate; reseller/marketplace payout schedules for ARR.
- Consumption: true‑up/overage timing; credit balance liabilities; contract assets (unbilled receivables).
7) Projects & long‑cycle businesses
- WIP hygiene: under/over‑billing, retentions, certification cycles, change‑order approval lags; claim rates and win times.
- Milestone truth: % revenue recognized ahead/behind billings; cash vs. POC gap; performance bonds and guarantees.
- Customer funding: mobilization advances; escrow arrangements; joint‑check agreements.
8) FX and tax timing
- Currency mismatches between AR and AP; natural hedges; collection lag vs. FX swings; VAT/GST receivable aging and refund cycle times.
9) Build a 13‑week cash view tied to working capital
Translate the diagnostic into a forward cash cadence: receipts by cohort, deductions cadence, processor payouts, inventory receipts vs. supplier payments, retentions and certifications, VAT refunds. This becomes the operating bridge between plan and liquidity.
10) Wire into model, covenants, and terms
Push DSO/DIO/DPO and oNWC turns by segment into the driver model; add scenario toggles (DSO +10, DIO +7, DPO −5; processor reserve +1–2% of GMV; return rate +300 bps). Map covenant headroom (ABL borrowing base, interest coverage) to these toggles. Convert big uncertainties into structure: receivable ineligibles, inventory appraisal haircuts, SCF adoption milestones.
The checklist (use this verbatim as you work)
Receivables (cash in)
- Aging structure and tail >60/90/120 days; top‑20 exposure; dispute backlog age.
- Terms: contracted vs. realized paid‑days by tier/channel; EDI compliance; grace‑period “gotchas.”
- Deductions: OTIF/compliance/price/promo root causes; recovery rate; cycle time; accrual sufficiency.
- Processors/marketplaces: payout lags, rolling reserves %, chargeback ratio vs. program thresholds; reserve release cadence.
- Credit risk: limits, insurance coverage, concentration; watchlist and triggers.
- Mechanisms: lockbox, auto‑cash application, dunning ladder, payment links, self‑service disputes.
- Financing: factoring/ABL/SCF use, cost, covenants; assignability in key contracts.
Inventory (cash stuck)
- Composition by type/site; cycle‑count accuracy; variance trend.
- Slow‑moving/obsolete ladders, reserve policy vs. reality; RMA and refurb yields.
- Weeks of supply by KVI/SKU family; safety‑stock method; MOQ/lead‑time constraints.
- In‑transit ownership and cutoffs; consignment/VMI accounting clarity.
- Planning discipline: forecast error, S&OP cadence; promotions link to pre‑build logic.
- Quality/returns: first‑pass yield, defect codes; warranty reserves and burn.
- Capacity coupling: changeover/lot size driving excess; supplier allocation risk.
Payables (cash out)
- Paid‑days vs. contracted terms; early‑pay discount capture and APR; SCF participation.
- Three‑way match exception rate; duplicate payments; vendor‑master hygiene; bank detail changes approval.
- Concentration: top‑20 vendors’ share and leverage; penalty clauses; prepayment requirements.
- Compliance: liens, statutory prompt pay, public sector clauses; audit rights.
Other operating current items
- Deferred revenue / contract liabilities (DCL) and renewal timing; credit balances.
- Trade spend accruals, post‑audit claims (retail); co‑op/MDF timing.
- VAT/GST receivable aging; customs deposits; payroll timing; insurance prepaids.
- Processor reserves and escrow balances; warranty and returns reserves.
- Project retention and performance bonds.
Governance and controls
- Policies exist and are enforced: credit approval, terms exceptions, returns/RMA, deductions write‑off thresholds, vendor onboarding, three‑way match.
- Dashboards track p50/p75/p90 paid‑days and dispute/return backlog, not just averages.
- S&OP integrates inventory/cash; AR/AP calendars aligned to peaks and promotions.
Triangulations that catch hidden cash issues
- Cohort DSO vs. headline DSO: rising tail while average holds flat → deductions are masking slippage.
- DSO vs. processor reserve trend: higher reserve + flat chargebacks → a policy change, not behavior; adjust cash view.
- DIO vs. service metrics: rising inventory and rising backorders → location/accuracy problem, not level.
- DPO vs. price‑cost gap: deteriorating DPO alongside worsening input costs → supplier power shift; pre‑negotiate SCF or indexation (11.4).
- Returns vs. CTS: return spikes driving cash drag and CM2 erosion → fix policy/quality (10.4) before chasing AR.
Industry nuances to handle explicitly
- Retail/CPG: deductions and post‑audit claims dominate; scan‑based trading and consignment blur title; OTIF penalties and routing guide compliance drive cash.
- Marketplaces/DTC: processor reserves and payout lags; refund/chargeback programs; paid placement timing vs. cash recognition.
- SaaS/usage: negative working capital via DCL; involuntary churn (failed payments) is cash leakage; reseller billing creates timing mismatches.
- Hardware + service: spares and field stock; RMA loops; warranty reserves; import duties timing.
- Construction/industrial projects: WIP under/over‑billing, retentions, certifications; change‑order cash timing; lien waivers.
- Healthcare: payer mix, prior‑auth denials, clawbacks; 835/837 remittance timing; credit balances handling.
Early‑warning indicators (monitor weekly/monthly)
- % AR >60/90/120 days; dispute backlog age; win rate on deductions.
- Paid‑days drift vs. policy by top customers; new “net‑45” creep on formerly net‑30 tiers.
- Processor reserve % or payout lag increases; chargebacks > program thresholds.
- Slow‑moving inventory share; E&O reserve releases or spikes; cycle‑count accuracy.
- DPO slipping; early‑pay usage falling without a rate change; duplicate payment flags.
- VAT/GST receivable growth; retention aging; warranty reserve burn variance.
- Seasonality build deviating from S&OP; CCC trending away from plan.
Red flags—and immediate responses
- Retail deductions explode without root‑cause closure → stand up a deductions war room, pause low‑ROI promos, tie customer compliance to ship‑confirm; haircut revenue in the model and add CM2 drag.
- Processor reserves jump → treat as quasi‑structural; widen cash ranges; renegotiate tiers or diversify providers.
- Inventory accuracy <97% or cycle‑count deltas rising → freeze SKU introductions in affected sites; launch inventory integrity sprint; cap bookings that depend on suspect stock.
- Paid‑days slippage with top vendors → escalate an SCF program or structured early‑pay with APR math; assign executive coverage and set a vendor calendar.
- Retentions/WIP swell → tighten billing milestones; require joint‑checks on risk accounts; add covenant and liquidity buffers.
Levers that move cash in 13 weeks and 12 months
- AR & collections: term enforcement and DOA, auto‑dunning, small‑balance auto‑writeoffs, payment links/portals, lockbox, dispute triage, credit insurance expansion, receivable financing (with explicit cost).
- Deductions control: close top root causes (OTIF, ASN, price files); weekly dispute clinics with big‑box retailers; tighten promo approval and accruals.
- Inventory: re‑tier safety stocks, SKU rationalization, VMI/consignment where supplier power allows, location accuracy fix, refurb/resale channels, MOQ renegotiation.
- AP: convert to purchases‑based DPO discipline; expand SCF; capture economically rational early‑pay discounts; clean vendor master; enforce three‑way match.
- SaaS/usage: increase prepay share; smooth renewals; reduce involuntary churn (card updater, retries); shorten refund windows; tighten reseller terms.
- Projects: milestone re‑phasing, advance billing, faster certification cycles, change‑order governance, retainage release campaigns.
- FX/tax: netting AR/AP in the same currency; accelerate VAT refunds; align incoterms to cash.
Governance and cadence
- Weekly cash stand‑up (20 minutes): AR receipts vs. plan, deductions, processor payouts, inventory receipts, critical vendor payments, variance to 13‑week forecast.
- Monthly working‑capital review: segmented DSO/DIO/DPO, CCC, bridge vs. plan, early‑warning indicators, and 90‑day actions with owners.
- Quarter‑close discipline: tie oNWC to GL; document one‑offs; refresh scenario toggles in the model.
Copy‑ready templates
- Working Capital Canvas (one per segment/channel)
- Scope & period; oNWC dollars and turns; DSO/DIO/DPO/CCC (and DCL for recurring).
- Bridge (drivers and $ deltas); plain‑English causes.
- Top exposures (customers/vendors/SKUs); seasonality profile.
- Levers & 90‑day actions (cash impact, owner, date).
- Confidence label; GL tie‑out note.
- Receivables Control Card (per top customer/processor)
- Terms (contracted vs. paid‑days); aging; dispute/deduction mix; reserve/payout rules; win rates; actions and owners.
- Inventory Health Card (per site/SKU family)
Weeks of supply; slow‑moving ladders; E&O reserves; accuracy %; RMA/refurb metrics; actions.
- Payables Term & Leakage Card (per top vendor/category)
- Contracted vs. paid‑days; discount capture APR; exceptions (3‑way match); duplicate risk; actions.
- 13‑Week Cash Flow Sheet
- Receipts by cohort; processor payouts; inventory receipts; supplier payments; tax/VAT; retentions; variance tracker.
72‑hour sprint plan (from blank page to decision‑grade)
- Day 0: Freeze definitions and perimeter; issue a single data request; set constant‑currency policy.
- Day 1: Build the oNWC bridge; compute segmented DSO/DIO/DPO/CCC (and DCL); tie to GL; flag top five cash variances.
- Day 2: Deep‑dive AR deductions and processor reserves; inventory health by site/SKU; AP terms vs. paid‑days and leakage; produce three Canvas pages (largest segment, largest channel, SaaS or project cut if relevant).
- Day 3: Publish a 13‑week cash plan; add scenario toggles to the model (DSO/DIO/DPO/reserves/returns); issue a 90‑day action plan with owners and quantified cash impact; propose covenant adjustments or structural protections where uncertainty is material.
Acceptance criteria for a decision‑grade working‑capital review
- Definitions and perimeter written on page; GL tie‑out complete; FX/M&A/one‑offs isolated.
- DSO/DIO/DPO/CCC (and DCL for recurring) computed by segment/channel/region, not just company‑wide; cohort and tail analyses included.
- Working‑capital bridge produced with plain‑English drivers and cash deltas; seasonality profile stated.
- AR deductions, processor reserves, inventory health, and AP term discipline analyzed with root causes and actions.
- 13‑week cash view published; model toggles updated within 24 hours; red flags and 90‑day owners named.
- Confidence labels and verifier sign‑off recorded; clean‑team protocols observed.
Execute this checklist and working capital stops being a set of ratios at the back of the deck. It becomes a cash playbook—segmented, auditable, and actionable—so you can fund growth from operations, protect covenant headroom, and make valuation reflect the speed at which dollars actually move.
13.4 KPI Benchmark Dashboard Template
A KPI dashboard in diligence is not a wall of numbers. It is a decision system that (i) compresses the target’s last 12–16 quarters into a few trend lines that actually move valuation, (ii) benchmarks those lines against credible corridors (internal history, nearest‑neighbor comps, policy/platform thresholds), and (iii) makes the next actions obvious. Your aim is to produce a segmented, auditable dashboard that links directly to revenue bridges (13.1), margin trees (13.2), working‑capital levers (13.3), pricing and unit economics (Chapter 8), GTM and funnel (Chapter 9), operations (Chapter 10), regulatory/policy (Chapter 11), and tech maturity (Chapter 12).
What “good” looks like
- Segmented: views by product family, customer tier, route‑to‑market, and region (the same lens as Chapter 6).
- Normalized: constant currency, organic perimeter, calendarized (working days/53rd week) with definitions written on the page.
- Benchmarked: each KPI shown against two corridors—internal 12‑quarter history and an external/threshold band (peer or platform/policy).
- Economic: every KPI maps to price power, win rate, NRR/GRR, CM2, CAC/payback, cash, or timing.
- Auditable: formulas, sources, and reconciliation notes attached; confidence labels (H/M/L) visible.
- Actionable: RAG thresholds with named owners, next review dates, and pre‑agreed playbooks when red/amber.
The dashboard structure (five panes you can ship)
Pane 1 — Executive summary (one page)
- Growth: organic constant‑currency revenue YoY, ARR/GMV growth (where relevant).
- Unit economics: CM1%, CM2%, CAC payback (months), realized price corridor vs. plan.
- Customer health: NRR/GRR, logo retention, cohort survival (12‑ and 24‑month).
- Commercial engine: conversion by stage, win rate, pipeline coverage.
- Cash & resilience: CCC (or Net CCC for recurring), liquidity headroom, SLA credits trend.
Each tile shows: last quarter, LTM, 12‑quarter sparkline, benchmark band, RAG, owner.
Pane 2 — Growth & customer outcomes
- Revenue bridge highlights (price/volume/mix) with implications for realized price (13.1).
- NRR/GRR by segment; expansion ratio; churn hazard factors (from 6.3).
- New logo growth; cohort activation and 90‑day retention.
- Average order value (AOV) and frequency (e‑commerce), or seats/modules and ARPU (SaaS).
Pane 3 — Unit economics & pricing
- Realized price waterfall (list → net) and discount distribution; price realization vs. fences (8.2).
- CM1% and CM2% by segment/channel; cost‑to‑serve buckets as % of vendor‑realized revenue (10.4).
- CAC by channel; incremental ROI for top three marketing tactics (9.3); payback months (9.4).
- Contribution per order/account; promo and paid‑placement dependence (when applicable).
Pane 4 — Go‑to‑market & funnel
- Stage‑by‑stage conversion and velocity; win rate vs. top three competitors (7.x, 9.1).
- Channel mix and attach rates; partner/marketplace tier status and penalty incidents (9.2).
- Sales productivity (new ARR per seller; bookings per head); discount guardrail exceptions.
Pane 5 — Operations, tech & cash
- Service SLOs (OTIF, p95 latency), SLA credits, contact rate per order/account (10.3).
- Capacity ladders and headroom at the constraint (10.2); expedite spend.
- Cloud/third‑party unit cost curves and on‑demand share (12.1/12.2).
- Working capital: DSO/DIO/DPO/CCC (and DCL for recurring) with bridges and seasonality (13.3).
- Policy/marketplace thresholds watchlist items that affect economics (11.4).
Benchmarks without drama (the “ladder” you’ll cite on every slide)
- Internal corridors: 12–16 quarter history (p25–p75) as the default “benchmark.”
- Nearest‑neighbor comps: two to four peers (public filings, investor decks) mapped to the same metric definitions; show only ranges—not logos—unless permitted.
- Platform/policy thresholds: marketplace OTIF/return/late‑ship limits, payment network chargeback programs, regulatory SLAs—hard gates where failing turns economics red.
- Third‑party data or analyst ranges: use only as directional bands, never as the sole benchmark.
Label the ladder at the bottom of each exhibit so readers know which band they are seeing.
Build it once: step‑by‑step (a two‑ to four‑day sprint)
1) Freeze scope and definitions
- Organic perimeter, constant‑currency policy, working‑day/calendar adjustments.
- Metric dictionary (see below), segmentation lens, data sources, and confidence labels.
2) Assemble the evidence pack
- GL and order/invoice lines; pricing files and promo calendar; ARR/NRR roll‑forward; funnel exports (CRM/MAP); channel/marketplace reports; service and SLA data; cloud and third‑party invoices; working‑capital ledgers; policy/platform bulletins.
- For each source, record extract date, owner, and reconciliation status.
3) Select the KPIs (20–25 max) and map to economics
Pick only metrics that you will act on. Use the menus below per business model; avoid vanity measures.
4) Normalize and reconcile
- Strip FX and M&A; align periodization; reconcile roll‑ups via ratio‑of‑sums.
- Footnote classification quirks (hosting/support inside COGS vs. CTS, gross vs. net revenue).
5) Apply benchmark bands and RAG
- Compute internal p25–p75 and p90 bands; overlay peer/threshold corridors where available.
- Pre‑agree RAG thresholds by segment (e.g., NRR <100% = red in SMB, <105% = red in Enterprise).
6) Publish with actions and owners
- Every red tile has a lever from Chapters 8–12, an owner, and a date.
- Push changed toggles into the operating model within 24 hours.
The metric dictionary (copy, edit, and lock)
Cross‑model core
- Organic constant‑currency revenue growth: ΔRev (ex‑FX/M&A).
- CM1%, CM2%: as defined in 13.2; classification footnote on page.
- Realized price index: Net ÷ List (weighted); show distribution by segment/channel.
- CAC (blended and by channel): fully loaded marketing + sales to first dollar of gross margin/CM2; show CAC payback (months) = CAC ÷ monthly CM2 contribution from the acquired cohort.
- NRR, GRR: cohort‑based roll‑forward; treat price re‑ratings separately from expansion.
- Churn hazard factors: share of churn with leading indicator flags (SLA credits > threshold, high contact rate, return issues).
- Contribution per order/account: CM2 dollars ÷ orders/accounts.
- CCC (and Net CCC for recurring via DCL).
- Revenue concentration: top‑10 share and HHI to show fragility.
SaaS / usage
- New/Expansion/Contraction/Churn ARR (logo and $); Sales efficiency (new ARR per fully ramped seller per quarter).
- Magic number (ΔARRq/q Sales & Marketing) used cautiously—pair with payback.
- Uptime and p95 latency vs. SLO; SLA credits % of revenue.
- Cloud unit cost per active/account/API call; on‑demand share; third‑party API $ per active.
- Entitlement/billing accuracy: credits/write‑offs ÷ billings.
E‑commerce / DTC
- Traffic → conversion → AOV (units × net price); orders per buyer; repeat rate at 30/90/180 days.
- Return rate by reason; refund/chargeback rate; paid share of traffic and promo dependence.
- Outbound freight + accessorials % of revenue; pick/pack/materials %; payment fee bps.
- CM2 per order before/after returns; free‑shipping threshold hit rate.
Marketplaces / platforms
- GMV, take‑rate, net revenue; buyers/sellers active, listing depth, fill rate, cancellation/late‑ship rate.
- Trust & safety: disputes per 1,000 orders, fraud losses, policy penalties/delistings.
- Payment rails mix; processor reserve %; payout lag.
B2B distribution / hardware + service
- Fill rate/OTIF, backorder rate, order lines per order; quote‑to‑order conversion.
- Warranty claim rate, RMA loop time, first‑pass yield, field failure rate.
- Spare parts attach, service attach, contract renewal/upsell.
- Freight as % of revenue, duty mix, project implementation hours vs. standard.
Technology maturity (commercial lens)
- DORA (deploy freq., lead time, change‑failure, MTTR) and SLO burn rate; tie to SLA credits and NRR (12.1).
- Integration coverage (share of deals using certified connectors), time‑to‑integration.
Working capital
- DSO (headline and cohort), DIO (and slow‑moving ladders), DPO (purchases‑based), CCC/Net CCC; processor reserves; deductions mix and win rate.
KPI Card template (use for every tile)
- Metric & definition (copy from dictionary; include formula).
- Scope (segment/channel/region), period (Q, LTM), currency, perimeter (organic).
- Last value, LTM, 12‑Q sparkline with internal band; external/threshold band if applicable.
- Source & QA (system, extract date, GL tie‑out note).
- Confidence (H/M/L) and owner.
- Interpretation (one sentence): why it moved and what to do.
- Action (if red/amber): lever, owner, date, expected $ impact.
Normalization & QA checklist (use verbatim)
- Constant‑currency rule applied; FX/M&A removed before comparisons.
- LTM and quarterly series reconcile to GL; ratio‑of‑sums for roll‑ups.
- Price realization aligns to the pricing waterfall; channel fees/take‑rates inside price.
- Classification footnote for hosting, support, outbound shipping (consistency across CM1/CM2).
- Cohort logic shared across NRR/GRR, payback, and churn.
- Calendarization (working days/53rd week) documented.
- Benchmark ladder labeled on each chart (internal band, peer band, policy threshold).
- Confidence labels assigned; low‑confidence metrics quarantined from investment case.
- Second‑person reproduction test complete.
RAG thresholds and playbooks (examples to adapt by segment)
- NRR: <100% red; 100–110% amber; >110% green → actions: price fence fix, expansion motion, success coverage (6.4, 8.2, 9.x).
- CM2%: below internal p25 red; p25–p50 amber; >p50 green → actions: CTS levers (10.4), promo mix, freight/routing, support deflection.
- CAC payback (months): >24 red; 12–24 amber; <12 green → actions: channel shift, guardrails, pricing uplift, billing/entitlement cleanup (9.2–9.4, 8.2).
- OTIF / p95 latency: beyond threshold red → actions: capacity rung add, reliability sprint (10.2, 12.1).
- Returns / chargebacks: above platform threshold amber/red → actions: policy reset, fit/quality fixes, fraud tooling (10.4, 11.4).
- CCC / Net CCC: deterioration >10 days vs. plan red → actions: terms enforcement, reserves renegotiation, inventory health, SCF (13.3).
Visualization guidance (keep it simple and comparable)
- Sparklines + bands beat gauges; show the last 12–16 quarters with p25–p75 and p90 bands shaded.
- Distributions for prices/discounts and payback (histograms) reveal leakage; avoid single‑point KPIs when dispersion matters.
- Stacked bridges for price and CTS make drivers visible; avoid pie charts.
- Index series (100 = baseline quarter) help align seasonal businesses.
- Annotations for policy/platform changes and big promos prevent misreads.
Common traps—and how to avoid them
- KPI drift (definitions change quietly). Lock a dictionary and version it; annotate changes.
- Vanity metrics without levers. If you cannot name the lever/owner, drop the metric.
- Averages hide tails. Show p50/p75/p90 for latency, discounts, payback, DSO; tails drive risk.
- Benchmarks from different definitions. Never overlay a peer band unless formulas match.
- Mix contamination. Segment or your benchmarks lie; especially for CM2 and CAC.
- Over‑indexing one model. SaaS metrics don’t map 1:1 to marketplaces; tailor per model.
Early‑warning indicators (embed under each pane)
- Growth: orders‑to‑inventories ratio (or PMIs for industrial exposure), pipeline coverage <3× next‑quarter target.
- Unit economics: discount depth drift; take‑rate/penalty notices; on‑demand cloud share rising.
- Customer health: SLA credits > threshold; contact rate ↑; return rate ↑; cohort survival dip.
- GTM: paid share ↑ with flat conversion; win rate ↓ vs. named competitor.
- Operations & cash: DSO tail >90 days; slow‑moving inventory ↑; DPO slipping; processor reserves ↑.
Cross‑links to action playbooks
- Red/amber on price or discount → 8.2 Pricing Architecture; 8.4 Differentiation Scorecard.
- Red/amber on CM2 or CTS → 10.4 Cost‑to‑Serve; 10.3 Service‑Level; 10.2 Capacity.
- Red/amber on CAC/payback → 9.1 Funnel Diagnostics; 9.2 Channel Mix; 9.3 ROI.
- Red/amber on NRR/GRR → 6.3 Cohorts; 12.1 Reliability; 12.3 Cyber/Privacy if credits/incidents drive churn.
- Red/amber on policy/platform → 11.4 Watchlist; 11.1 Regulatory Mapping.
Copy‑ready templates (paste directly into your workspace)
A) KPI Dashboard Backlog (one line per tile)
- Metric | Definition (formula) | Segment/Channel | Period | Source | Benchmark band (internal/peer/threshold) | RAG rule | Owner | Confidence | Next action & date
B) KPI Card (single‑tile doc)
- Metric & scope; formula; last, LTM, sparkline; bands; interpretation; action; source & QA; confidence; owner; next review.
C) Benchmark Band Sheet
- Metric | Internal p25/p50/p75/p90 | Peer corridor (min–max) | Policy/Platform threshold | Notes/assumptions | Review cadence.
D) Data & QA Log
- Source system | Extract date | Fields | Reconciliation (GL/ARR/workflows) | Issues & fixes | Sign‑off.
72‑hour sprint plan (from blank page to decision‑grade dashboard)
- Day 0: Freeze scope, segmentation, definitions, and normalization rules; issue a single, consolidated data request; list 25 provisional KPIs mapped to economics.
- Day 1: Land sources and reconciliation; build Executive Summary and Growth & Customer panes with internal bands; overlay external thresholds where hard gates exist.
- Day 2: Build Unit Economics and GTM panes; compute price waterfall, CM2 by segment, CAC/payback, and funnel diagnostics; assign RAG and owners with actions.
- Day 3: Build Operations/Tech/Cash pane; add early‑warning indicators; publish the dictionary, benchmark ladder, QA log; push updated toggles into the operating model; schedule monthly dashboard cadence.
Acceptance criteria for a decision‑grade KPI dashboard
- 20–25 KPIs max, segmented, normalized, reconciled to GL/ARR/GMV; formulas on page; confidence labeled.
- Internal bands shown for all KPIs; peer/threshold bands applied for material ones; RAG rules pre‑agreed by segment.
- Explicit links from each red/amber metric to a lever, owner, date, and expected $ impact; toggles updated in the model within 24 hours.
- Metric dictionary, benchmark ladder, and QA log published; second‑person reproduction test passed; clean‑team protocols observed.
Build the dashboard this way and it becomes more than reporting. It becomes a living operating and underwriting tool—clear on what matters, calibrated against credible ranges, and wired to the exact actions that move revenue, margin, retention, and cash in your hold period.
