Synthesis and Storylining

Analysis creates truth; synthesis creates decisions. The goal of commercial due diligence is not to catalog findings but to change the buyer’s and lender’s decisions: buy or pass, at what price and terms, with which 90‑day moves and protections. Storylining is the craft of turning a dense body of evidence—market, customer, competition, product, pricing, GTM, ops, tech, ESG, financials, scenarios—into a short, answer‑first narrative that a time‑pressed Investment Committee can underwrite. The standard we use throughout this chapter is simple: every page says one consequential thing; every consequential thing is sized in ΔCM2, ΔCash, and headroom within the hold period; and every dollar connects to named model drivers (Chapter 14), risks (Chapter 16), and value‑capture moves (Chapter 15).

Start by agreeing the five or six “big answers” your story must deliver: (1) the market reality you are buying into; (2) the target’s true unit economics and price power; (3) competitive position and disruptor exposure; (4) GTM and operational capacity to scale without breaking CM2 or SLOs; (5) a scenario‑anchored valuation range and covenant headroom; and (6) a gated path to value with residual risks translated into terms. Everything else in the deck either earns its place by moving one of those answers, or it falls to the appendix.

17.1 Insight Prioritization Framework

An insight is not a data point or a chart. It is a decision‑relevant claim that, if true, changes valuation, terms, or execution. Prioritization is how you separate those few claims from the many observations that surround them. Use the framework below to move from a long list of findings to the eight to ten insights that carry your story.

Before scoring: hard gates that filter “non‑insights”

No materiality, no airtime. If the claim cannot move ≥2% revenue, ≥100 bps CM2, ≥50 bps covenant headroom, or ≥50 bps WACC within the hold period, it belongs in backup.
No actionability, no airtime. If there is no lever, owner, or feasible timing, it is a context note, not an insight.
No evidence, no airtime. If it cannot be tied to sources (VoC, telemetry, invoices, settlement files, GL, third‑party data) and to named cells in the driver model, it is not ready.
No legality, no airtime. Anything that would require pre‑close coordination beyond clean‑team rules is out until cleared (Chapters 11 and 15.3).

The MOVE score (Materiality, Operability, Velocity, Evidence)

Score each candidate on a 1–5 scale (5 is best). Weightings reflect what Investment Committees value under time pressure.

Materiality (40%) — “How big is it, economically?”
- Measure in ΔCM2 and ΔCash over 12–24 months.
- Anchor to the model: change the specific driver(s) by the claimed delta and read the cash/CM2 effect (Ch. 14.1–14.3).
- Heuristics: 5 = portfolio‑level step‑change; 3 = segment‑level; 1 = local.
Operability (15%) — “Can we influence it?”
- High scores require a named lever, owner, and credible path (capacity rung, policy, contract clause, FinOps toggle, etc.).
- Penalize items that depend on competitor behavior or regulator grace.
Velocity (20%) — “How fast does it show up in cash?”
- Time to 80% of impact from decision date.
- 5 = ≤90 days; 3 = one to two quarters; 1 = ≥year.
Evidence (25%) — “How strong is the proof?”
- Triangulation count (e.g., VoC + invoice audit + cohort math), data quality, and falsification attempts survived.
- Label confidence H/M/L; demote if L without a plan to lift.

MOVE score = 0.40·M + 0.15·O + 0.20·V + 0.25·E. Sort descending. Break ties with downside asymmetry (protecting headroom beats symmetrical upside) and irreversibility (closing windows first).

Tiering: P0, P1, P2

P0 – Deal‑critical (must be in the top deck): MOVE ≥ 4.0, or any item that creates/avoids a valuation step or headroom breach within 12 months.
P1 – Decision‑shaping (main body or fast backup): MOVE 3.0–3.9 with clear owner and timing.
P2 – Context (appendix): MOVE < 3.0 or high uncertainty; keep as monitoring items or options.

The Insight Card (copy‑ready template)

For every P0/P1, complete a one‑pager. If you cannot fill a field, the insight is not yet underwritable.

Headline (answer‑first): a full‑sentence claim that could sit on an IC agenda.
Why it matters: quantified ΔCM2, ΔCash, headroom, and where it hits the P&L/cash bridge.
Proof: sources, tests run (A/B, audits), and model hook (cells moved, with units).
So what: decision or action it implies (price/terms, 90‑day move, capacity rung).
Risks & sensitivity: what would disprove it; range from 14.3.
Owner & timing: named executive, start date, milestones.
Confidence: H/M/L with a plan to raise.

Building the candidate list (fast and fair)

Harvest across lenses: market, customer/VoC, competition, product/pricing, GTM funnel, ops/CTS, tech/digital, regulatory/ESG, financials, scenarios.
Phrase as “what changed” or “what must be true” statements, not as topics (“Pricing power is limited” → “Realized price can rise 80–120 bps without churn in segments A/B due to fence tightening proven in VoC + invoice audit”).
Red‑team each claim: actively try to falsify it; run the opposite (e.g., “what if elasticity is 2× worse?”); if it survives, raise Evidence.

Sizing materiality quickly (what math to run)

Price and promo: apply the pricing waterfall delta to realized price bps; propagate to CM2 and retention using elasticity bounds (Ch. 8.2, 14.3).
Cross‑sell & re‑rating: attach/adoption × realized price × CM2 − incremental CTS; cap by implementation throughput and SLOs (Ch. 15.1, 10.3).
CTS levers: returns %, parcel $/shipment, cloud on‑demand share, support minutes/contact; multiply by volumes; reconcile to the CM2 bridge (Ch. 10.4, 13.2).
Working capital: DSO/DIO/DPO deltas on current volumes; reflect processor reserves/holdbacks (Ch. 13.3).
Risk items: change the driver and read headroom and 13‑week cash (Ch. 14.1, 16.1).

The Prioritization Workshop (90 minutes, step‑by‑step)

10 min – Frame: restate decision, thresholds, and MOVE weights; agree the materiality floor.
30 min – Pitch: each workstream presents its top three candidates in Insight Card form.
20 min – Score: silent voting on MOVE, then discuss gaps ≥1 point; adjust only with new evidence.
15 min – Stack: sort by score; mark P0/P1/P2; ensure portfolio balance (do not let one route or segment dominate without cause).
15 min – Assign: owners for missing proof or model hooks; due dates; pre‑draft page titles.

Turning prioritized insights into a story spine

Open with the “Big Answers” page: five bullet headlines (P0s), each with a number and a decision.
Sequence by causality: market → unit economics → differentiation → GTM/ops capacity → scenarios & risks → value capture & terms.
One‑page‑one‑message rule: title = answer; left side = proof; right side = “so what” (decision, dollars, owner, timing).
Bridge pages, not dashboards: every section ends with a bridge from last actuals to Year‑1/Year‑2 showing the few drivers that move the outcome.

Quality checks that keep the short list honest

Ratio‑of‑sums for rollups: compute portfolio effects from atomic segments, not averages.
Weather vs. response: separate passive vs. managed outcomes (Ch. 14.2) and show the cost of action.
Capacity & SLO caps enforced: no insight claims growth beyond booked rungs or error‑budget limits (Ch. 10.2, 12.1).
Headroom view present: every P0 that affects cash shows quarterly covenant headroom and breach month.
Consistency: the same driver names appear on Insight Cards, in the model, and on the bridges.

Common failure modes—and the fix

Laundry list deck. Fix: enforce materiality floor and the one‑page‑one‑message rule; cap P0/P1 count.
Topic headers (“Market,” “Competition”). Fix: convert to answer‑first headlines with numbers and actions.
Upside theater without risk math. Fix: pair each upside with its residual risk and term‑sheet translation (indexation, CPs, indemnities, earnouts).
Averages hide pain. Fix: present by segment/channel; include worst‑quartile cohorts and sensitive routes.
No owners. Fix: every P0/P1 must name an executive and a date.

What the IC wants to see (use this as your acceptance test)

Eight to ten answer‑first headlines that change the buy/price/terms decision, each with ΔCM2, ΔCash, headroom, and named owners.
A clean link from each headline to driver‑level math and scenario ranges, not trend lines.
A short list of term‑sheet protections tied to residual risks and what must be true.
A 90‑day action page that lands the first dollars and de‑risks the plan.
An appendix that is findable by model driver, not by department.

72‑hour synthesis sprint (from findings to an IC‑ready spine)

Day 0: Apply hard gates; harvest candidates; draft Insight Cards; wire model hooks.
Day 1: Run MOVE scoring; tier P0/P1/P2; draft the “Big Answers” page and page titles; assign owners for missing proof.
Day 2: Build bridges and residual‑risk call‑outs; draft term‑sheet translations; stitch the story spine; rehearse Q&A.
Day 3: Red‑team; tighten to ten pages + appendix; lock numbers to model version; circulate the executive summary.

Prioritize insights this way and your deck stops being a tour of the analysis. It becomes a decision instrument: a small set of underwritable claims, each sized in dollars and days, wired to the model, backed by evidence, and translated into moves and terms management can execute on Day 1.

17.2 Pyramid Principle Storyboarding Guide

The Pyramid Principle is the fastest way to turn sprawling analysis into a deck that drives a decision. At its core: lead with the answer, support it with three to five mutually exclusive, collectively exhaustive (MECE) arguments, and back each argument with crisp evidence. In commercial due diligence, “answer‑first” does not mean “opinion‑first.” It means cash‑first: every headline carries a number (ΔCM2, ΔCash, headroom) and a move (price/terms or execution) tied to named model drivers. Use this guide to storyboard your diligence in hours, not weeks, and to keep the spine intact as numbers update.

Start with SCQA to find the governing thought

Use the SCQA scaffold—Situation, Complication, Question, Answer—to distill the governing thought for the entire deck and for each section. Situation frames the market and the target’s role; Complication states what makes this deal non‑obvious; Question names the IC decision at risk; Answer is your governing thought (e.g., “Buy at X with Y terms because Z dollars are underwritable within the hold period, with headroom ≥ W bps across scenarios”). Write SCQA in prose, then compress the Answer into a single sentence that can sit atop the pyramid.

Build the pyramid: answer → reasons → proof

Your storyboard should ladder from the governing thought down to evidence, one page per rung.

Top (governing thought): a single page with the buy/price/terms call and the total dollars that move valuation and headroom within the hold period.
Middle (reasons): three to five arguments that, together, prove the top line (e.g., “Market demand is resilient in buyer segments,” “Unit economics support price power,” “GTM and capacity scale without CM2 leakage,” “Residual risk is quantified and covered”).
Base (proof): exhibits, bridges, and model views that evidence each reason—VoC cuts, pricing waterfalls, funnel diagnostics, CTS benchmarks, scenario fans, risk heat‑maps, and value‑capture plans.

Order the reasons logically—time (now → close → 90 days → Year‑2), structure (market → firm → execution → risk), or priority (largest $ first). Never mix logics on the same rung.

Title grammar that forces decisions

Every page title must be a complete, testable sentence containing a number and a verb. Avoid topic labels. Prefer “Realized price can rise 80–120 bps in Enterprise (fence tightening; no churn delta in VoC)” to “Pricing.” If you cannot write a decisive sentence, the page may not belong in the main spine.

Patterns that work:
- “We recommend X at $Y with Z terms because ΔCash = $A and headroom ≥ B bps across scenarios.”
- “Year‑1 CM2 grows $A–$B driven by price +P bps and CTS −Q/unit; volume constrained by capacity rung #1.”
- “Downside is funded: p10 headroom ≥ H bps with reserve of $R and triggers tied to KRI set M.”

The ten‑page spine (copy for PE IC or Credit Committee)

Build a minimal, decision‑grade narrative before adding detail. This default spine fits most CDDs; tune titles and exhibits to your case.

Investment recommendation (answer‑first): buy/price/terms; ΔCM2, ΔCash; headroom by quarter; three reasons; two gating risks and protections.
What we’re buying (market reality): TAM/SAM/SOM and growth drivers; exposure by segment/route; scenario fan for demand.
True unit economics: pricing waterfall to realized price; CM1→CM2 bridge; sensitivity to price, returns, freight/cloud/API.
Competitive position: share and momentum; moats/differentiation scorecard; disruptor threat scenarios.
GTM and capacity to scale: funnel diagnostics; channel mix economics; capacity ladder and SLO guardrails; CAC payback.
Scenario‑anchored valuation: driver‑based base/downside; tornado of value drivers; covenant headroom path.
Risk & mitigation: top‑10 Cash‑VaR heat‑map; triggers/plays; residual risk and reserves; term‑sheet translations.
Revenue synergies we will underwrite: attach/re‑rating math; proof tests; gates; ΔCM2 and cash timing.
Cost & CTS improvements we can bank: procurement/logistics/FinOps levers; run‑rate vs. in‑period cash; one‑time costs.
90‑day value capture & Day‑1 controls: dated actions, owners, KPIs; TSA exits; what flips the model toggles.

Everything else moves to the appendix, organized by model driver (price, mix, conversion, returns, freight, cloud, minutes/contact, take‑rates, DSO/DIO/DPO, reserves) so Q&A finds proof quickly.

Page archetypes and the right exhibit for each

Use the smallest artifact that proves the point. When in doubt, show bridges and deltas, not levels.

Bridge pages prove change: last actual → Year‑1 → Year‑2 with bars labeled price, volume, mix, CTS, opex, working capital.
Waterfalls prove composition: realized price from list to cash receipt (on‑invoice, off‑invoice, fees, penalties, returns).
Fans and bands prove uncertainty: base vs. scenario bands with p10/p90 shading and triggers.
Tornado charts prove sensitivity rank by absolute dollar effect on CM2 or cash.
Heat‑maps prove concentration and risk (by segment/route).
Ladders prove capacity and gating (rung cost, lead time, throughput, SLO impact).

Each exhibit must carry units, time base, constant‑currency note, extract dates, and source codes. The number in the title must be traceable to a named model cell.

Storyboarding in six passes

Move quickly from a blank page to a coherent draft by separating creation from critique.

Pass 1 – Headlines only: draft titles for the ten pages in answer‑first grammar. No charts yet.
Pass 2 – Argument bullets: under each title, list the three proof points you will show (one line each). Kill any page with <2 proof points.
Pass 3 – Exhibit stubs: write the name of the exhibit (e.g., “CM2 bridge by segment, FY+1”) and the model pull needed. Assign owners.
Pass 4 – Numbers in: populate the exhibits from the current model version; add sources and dates; ensure title numbers match charts.
Pass 5 – Transitions: add one sentence at the bottom of each page that leads to the next page (“…which is why we test price power next”).
Pass 6 – Ruthless prune: remove any page that does not change the decision, compress two if they say the same thing, push context to the appendix.

MECE without dogma

MECE is a means, not an end. In practice: ensure your middle‑rung arguments are non‑overlapping (e.g., demand, unit economics, execution capacity, risk) and cover the conclusion. Avoid pseudo‑MECE splits that confuse the reader (“customers, competitors, and internal” on the same rung is usually topic‑based, not argument‑based).

Visual and language hygiene that speeds comprehension

One page, one message. If you need two verbs in the title, you likely need two pages.
Show change, not just levels. Bridges beat bar charts; fans beat two scenarios side‑by‑side.
Numbers first, adjectives last. Replace “strong,” “attractive,” “limited” with bps, days, $/unit, %.
Consistent units and time base. Monthly for 8–12 quarters, then annual; constant currency with a clear FX overlay.
Label the uncertainty. Low/base/high bands; confidence labels; scenario names and weights.
Color with purpose. Use consistent colors across the deck for “base,” “downside,” “managed response”; avoid decoration.

Audience tuning: IC vs. lenders vs. strategic buyers

PE Investment Committee: bias to cash and headroom; emphasize ΔCM2 drivers, scenario bands, residual risk and term‑sheet translations; keep synergy to what lands in the hold period.
Credit Committee/lenders: lead with downside path (p10), covenant headroom by quarter, 13‑week cash; show passive vs. managed outcomes and reserve policy; list collateral/ABL details.
Corporate/strategic: add “fit” and option value; still price the first 24 months in cash; call out integration posture and customer/brand risks.

Appendix architecture that makes Q&A easy

Organize backup by driver and exhibit type, not by department. In each section, the first page is a map: list the named model cells it supports, the source files, and the date last refreshed. Include audit trails: invoice and settlement samples for realized price; parcel and cloud bills for unit costs; AR/AP agings for working capital; VoC call list (anonymized) and discussion guides.

The five‑minute executive summary (spoken and written)

You need one oral version and one written page. Both mirror the pyramid.

Spoken: 30–60 seconds on the governing thought; one sentence per reason with the key number; one sentence on residual risks and protections; one sentence on the 90‑day plan.
Written: a single page repeating the same structure, with each reason linked to its page number and the model version stamp.

Quality control for the story (run these checks before you send)

Model lock: every title number reproduces from the current model version in ≤3 clicks; FX and perimeter treatments are explicit.
Weather vs. response: you show both passive and managed outcomes and the cost of action.
Capacity & SLO constraints enforced: no growth beyond booked rungs or error‑budget limits.
Headroom visible: any page that changes cash shows quarterly headroom; breach month and cure if relevant.
Consistency: driver names and units are identical across pages; scenario names and weights match Chapter 14.
Legality: clean‑team and antitrust guardrails respected; no customer‑identifying data or competitor‑sensitive pricing in the main deck.

Red‑team questions that sharpen the spine

If the top page vanished, would the next three pages imply the same conclusion?
Where could a skeptical CFO reasonably say “you showed me levels, not deltas”?
Which page would a lender care most about, and is it in the main spine?
What must be true for each headline? Is that condition evidenced, gated, or translated into the term sheet?

A one‑page storyboard template you can copy

Title (answer‑first with number and verb).
Why it matters (ΔCM2, ΔCash, headroom; where it hits the bridge).
Proof bullets (3): exhibit name + one‑line takeaway + source/date.
So what: decision, action, owner, timing; toggles that flip in the model.
Transition: one sentence that sets up the next page.

The 24‑hour polish

In the last day before IC, lock the model version; re‑generate bridges; scan for mixed units; footnote sources with extract dates; compress titles by one clause each; cut one page that no longer changes the decision; rehearse the five‑minute summary; align the appendix index to model drivers; and export a one‑page “terms asks” list tied to residual risks.

Use the Pyramid Principle this way and your CDD deck becomes a decision engine: a short, answer‑first spine supported by MECE arguments and driver‑level proof, with clear lines from insight to dollars, from dollars to scenarios, and from scenarios to terms and Day‑1 actions.

17.3 Executive Summary Checklist

The executive summary is the only page many decision‑makers will read before they form a view. It must be answer‑first, cash‑first, and model‑anchored—stating the buy/price/terms recommendation, the dollars that move valuation within the hold period, and the protections that keep headroom intact in downside scenarios. Treat it as a binding contract with the rest of your deck: every number in the summary must reproduce from named drivers in the model (Chapter 14), trace to the analysis sections, and translate into Day‑1 actions and term‑sheet asks.

Core principles (design rules you should not violate)

Answer‑first: open with the explicit recommendation (buy or pass), price/valuation range, and non‑negotiable terms; no “leading up to” the punchline.
Cash‑first: quantify ΔCM2, ΔCash, and quarterly covenant headroom within 12–24 months; avoid level metrics without deltas.
Driver‑anchored: cite the specific levers (price bps, conversion, attach, returns %, parcel/cloud unit cost, take‑rate bps, DSO/DIO/DPO) that create the dollars.
Scenario‑aware: show base, downside (p10), and managed‑response outcomes; separate weather from response and cost the response.
Underwritable: include only items with an owner, timing, and proof; everything else lives in upside or options.
One page by default: two pages only if lenders and equity need different cuts; anything longer is a deck, not a summary.

What must appear—one‑page default (order matters)

Recommendation line (top banner)
“Buy at $X enterprise value with Y terms (indexation, certification CPs, reserve caps, inventory/service covenants, earnout on NRR/realized price). Base case delivers ΔCM2 $A, ΔCash $B in Year‑1, with minimum headroom ≥ H bps across scenarios.” Include model version ID, perimeter, constant currency note, and date.
Three reasons that move cash
- Unit economics & price power: realized price +P–Q bps in segments α/β from fence tightening; CM2 lift $…; elasticity and VoC proof.
- Cost‑to‑serve improvements: returns −r bps, parcel/cloud $/unit −u%, support minutes/contact −m; timing and gates.
- GTM & capacity: conversion +c pp; attach +a pp; capacity rung #1 booked; CAC payback ≤ t months in channels γ/δ.
Bridge from last actuals to Year‑1 (cash and CM2)
A concise narrative of the bars you will show later: price, volume, mix, CTS, opex, working capital. Quote the two biggest bars with units (e.g., “price +110 bps,” “returns −180 bps”).
Scenario & headroom snapshot
Base vs. downside (p10) vs. managed response for cash and headroom by quarter; note first breach month in the passive downside (if any) and the actions that avoid it (with cost).
Top risks and mitigations (residual view)
List the two or three Cash‑VaR items with KRIs and flip rules, the residual Cash‑VaR after mitigations, and funded reserve/liquidity buffer. State the early‑warning indicators.
Value capture—first 90 days
The three dated moves that land dollars fastest (owner, start date, acceptance test). Example: “Re‑bid top parcel lanes (signed by Sept 30); realized −8–12% $/shipment; GL tag 6123.”
Integration feasibility gates (only those that unlock dollars)
The one or two non‑negotiable cutovers with acceptance criteria (e.g., “Billing/entitlement accuracy ≥99.5% for SKUs X/Y/Z before bundle launch”).
Term‑sheet translations
The protections are tied to residual risks (indexation, certification CPs, reserve caps, indemnities/escrows, earnouts on realized price/NRR; TSA exit milestones). State which dollar bars depend on each.
What would change our answer
The one or two facts that would reprice or turn “buy” to “pass” (e.g., “platform delist,” “processor reserve +200 bps,” “VoC shows elasticity ≥2× in Enterprise”).
Provenance
Model version stamp; FX/perimeter; sources with extract dates (VoC N interviews; parcel/cloud bills; settlement files; GL tie‑outs). Confidence labels H/M/L where appropriate.

Variant add‑ons by audience

PE Investment Committee: emphasize ΔCM2/ΔCash, scenario bands, and residual risk with term‑sheet asks; keep synergy to what lands in hold period.
Lenders/Credit Committee: add 13‑week cash low point, covenant headroom by quarter, borrowing‑base mechanics, reserve policy, and passive vs. managed comparison.
Strategic buyer: include integration posture (Fuse/Federate/Interface), customer/brand risk, and option value beyond hold period; still anchor near‑term cash.

Writing guidance (to keep it crisp and underwritable)

Use complete, testable sentences with numbers and verbs; avoid topic labels.
Quote ranges (low/base/high) when uncertainty is material; name the driver behind the range.
Replace adjectives with units (bps, pp, $/unit, days).
Define any acronym on first use; avoid internal code names.
Do not mix perimeter or currency; state constant currency and organic scope; show FX overlay only if material.

Red‑team questions to pressure‑test the page

If the top banner vanished, would the remaining lines still imply the same buy/price/terms?
Which single driver explains most of ΔCash? Is that driver in the summary with a number, owner, and proof?
Do scenario and headroom statements reflect passive vs. managed and the cost of action?
Are any dollars dependent on unproven integration, billing, or certification gates? If yes, are the gates and acceptance tests explicit?
Can a second person reproduce every number from the model in ≤3 clicks?

Quality‑control checklist (tick before sending)

Recommendation line states price and terms; numbers reconcile to the current model version.
Bridge math (price/volume/mix/CTS/working capital) sums to the Year‑1 and Year‑2 deltas quoted.
Scenario bands are consistent with Chapter 14.2 weights; first breach month (if any) is accurate.
Residual risk shows Cash‑VaR after mitigation and funded reserves; KRIs and flip rules are stated.
Term‑sheet asks correspond 1:1 to residuals and underwritten dollars.
All claims carry source dates; FX/perimeter noted; segmentation matches the rest of the deck.
Legal guardrails (clean‑team/antitrust) respected; no customer‑identifying or competitor‑sensitive data.

Copy‑ready one‑page structure (use these exact lines as scaffolding)

Recommendation: Buy at $X EV with Y terms; base delivers ΔCM2 $A and ΔCash $B in Year‑1; min headroom ≥ H bps across scenarios.
Why this works (#1): Realized price +P–Q bps in segments α/β; CM2 +$…; elasticity and VoC evidence; fences/DOA live by [date].
Why this works (#2): CTS down −u% ($/shipment, returns −r bps, cloud −v%); signed events and timing.
Why this works (#3): GTM conversion +c pp; attach +a pp; capacity rung #1 booked; CAC payback ≤ t months.
Bridge: Last actual → Year‑1: price +…, mix −…, CTS +…; net ΔCM2 $…; ΔCash $… (working‑capital +/− … days).
Scenarios & headroom: Base vs. p10 and managed; first breach month and cure; cost of action $…
Top risks (residual): Cash‑VaR $…; reserve $…; KRIs and flip rules.
90‑day plan: Three moves, three owners, three dates.
Gates: Billing ≥99.5% accuracy; certification X by [date].
Terms we need: Indexation; reserve caps; certification CPs; inventory/service covenants; indemnities; earnouts.
Provenance: Model v…, constant currency/perimeter; sources with extract dates; confidence labels.

72‑hour sprint to a decision‑grade summary

Day 0: Lock model version/perimeter/FX; draft the ten lines using answer‑ and cash‑first grammar; insert placeholder numbers.
Day 1: Populate from the model; reconcile bridges; add scenario and headroom statements; draft term‑sheet translations tied to residuals.
Day 2: Red‑team the page; tighten to one page; add owners/dates for 90‑day moves and gates; stamp sources and extract dates.
Day 3: Final QA with a fresh export from the model; freeze; circulate with the deck spine and appendix index.

Acceptance criteria for an executive summary worth IC’s time

A single page that states buy/price/terms and quantifies ΔCM2, ΔCash, and headroom with base/downside/managed views.
The three biggest drivers are named with units, owners, timing, and proof.
Residual risk quantified post‑mitigation with funded reserves and triggers; 90‑day moves dated and owned.
Term‑sheet asks mapped directly to residuals and underwritten dollars.
Every number reproducible from the current model in ≤3 clicks; sources dated; definitions consistent with the deck.

Use this checklist and your executive summary will earn its keep: a crisp, defensible page that tells IC exactly what to do, why, for how much, by when, and with which protections—all tied back to the model and forward to Day‑1 execution.

17.4 Recommendation Validation Template

A recommendation is only as strong as the evidence and discipline used to validate it. The purpose of this template is to stress‑test the buy/price/terms call before it reaches the Investment Committee, and to ensure that every asserted dollar—upside or downside—traces to a driver in the model, reconciles to historicals, survives scenario pressure, and is executable within the hold period. Use it as a single pass/fail framework that links insights (Chapter 17.1), story spine (17.2), executive summary (17.3), the driver‑based model (Chapter 14), value creation (Chapter 15), and risk governance (Chapter 16).

Guiding principles

Work answers‑first and cash‑first. Validate ΔCM2, ΔCash, and quarterly covenant headroom; everything else is context. Insist on reproducibility: a second person must be able to recreate each headline number from the assumption cell in three clicks or fewer. Keep segmentation consistent with the rest of the playbook (product × route‑to‑market × region × customer tier). Separate weather from response; cost the response. Stay inside legal guardrails (clean‑team, antitrust) and platform or regulatory policies.

The Recommendation Dossier (what you will produce)

One‑page executive summary (17.3) with model version stamp and scope notes.
Ten Insight Cards (17.1) with MOVE scores and confidence labels.
Model integrity sign‑off (14.4) including reconciliation to last actuals and LTM.
Scenario set and sensitivities (14.2–14.3) with passive vs. managed outcomes.
Synergy bank and 90‑day roadmap (15.1–15.4), gated and costed.
Risk heat‑map and residual risk pack with reserves and term‑sheet translations (16.1–16.4).
Integration feasibility heatmap and cutover gates (15.3).
Term‑sheet ask list mapped 1:1 to residuals and “what‑must‑be‑true.”
IC run‑of‑show: decision tree, alternatives, and conditions precedent.

Step‑by‑step validation flow

1) Restate the decision and constraints
Write the recommendation in one sentence: buy or pass, at what EV, with which non‑negotiable terms, and what cash/headroom path within 12–24 months. Note constraints: hold period, leverage and covenants, regulatory approvals, TSA windows, platform policies.

2) Trace thesis → drivers → dollars
Build a traceability link for every P0/P1 insight: which driver cells move (price bps, attach, conversion, return %, parcel/cloud $/unit, take‑rate bps, minutes/contact, DSO/DIO/DPO, processor reserves), by how much, with what lag, and what that yields for ΔCM2 and ΔCash. Reject any claim that does not resolve specific driver edits.

3) Reconcile to history and accounting
Confirm first forecast month = last actual for revenue, CM1, CM2, opex, and cash; LTM ties to GL per 13.1–13.3. Ensure pricing waterfalls and CM2 trees (8.2, 13.2) feed the model consistently. Verify working‑capital logic and AR/AP/Inventory to trial balance (13.3).

4) Test scenarios and headroom
Run at least baseline, recession, and stagflation plus any exposure‑specific case (14.2). Show passive vs. managed paths; quantify the cost of action. Compute quarterly covenant headroom and first breach month (if any). Confirm the downside includes a 13‑week cash view.

5) Rank sensitivities and prove robustness
Use standardized shocks (14.3) to build a tornado for Year‑1 CM2 $ or Cash. For the top five levers, show spiders and threshold/break‑even points (cash‑zero, headroom‑zero). If the plan depends on a lever with high impact and low controllability, translate that dependency into terms (indexation, caps, CPs, earnouts).

6) Triangulate valuation
Check the price using three lenses and reconcile them to the same drivers:

Driver‑to‑DCF: cash flows from the model; WACC and terminal logic explicit.
Implied multiples: EV/Revenue, EV/CM2, EV/EBITDA against peer corridors, adjusted for growth, durability (NRR, gross churn), and capital intensity.
Reverse DCF / reverse multiple: the growth, price power (bps), CTS/unit improvements, and working‑capital turns implied by your offer; reject if these exceed evidenced ranges or capacity gates.

7) Underwrite execution and integration
Cross‑check the value capture roadmap (15.4) against integration feasibility (15.3). Every dollar after Day‑1 needs a gate (billing/entitlement ≥99.5% accuracy, certification live, capacity rung booked) and an owner with dated milestones. No gate, no dollar.

8) Quantify residual risk and funding
From the mitigation portfolio (16.3), compute residual Cash‑VaR, CVaR, and Headroom‑at‑Risk (16.4). Size operating risk reserves (fast risks) and the liquidity buffer; wire reserve draws into the 13‑week cash cadence.

9) Translate uncertainty into terms
Map residuals to structure: indexation/surcharges, reserve caps and settlement SLAs, certification CPs, inventory/service covenants, indemnities/escrows, and earnouts tied to realized price or NRR. Show how each clause reduces probability or severity in the residual math.

10) Run the red‑team
Assign a devil’s advocate to attack each P0: run worst‑plausible elasticities, delay gates by 90 days, remove unproven synergies, shock take‑rates and processor reserves by policy thresholds. Keep any haircut or range expansion that survives rebuttal.

11) Frame alternatives
Always prepare three actionable alternatives:

Reprice: lower EV or change consideration mix; show revised IRR and headroom.
Restructure: same price with stronger terms (indexation, caps, CPs, earnouts) to keep residuals within appetite.
Re‑sequence: defer value creation to cleared gates; adjust hold period or growth path.
Include “pass” criteria if minimum headroom or reserve sufficiency cannot be met.

12) Secure sign‑offs
Obtain written sign‑off from finance (model and reconciliations), commercial (insights and levers), operations (capacity and SLOs), technology/security (reliability, privacy), legal (policies and terms), and risk/treasury (reserves and liquidity). No sign‑off, no IC.

Copy‑ready tools and templates

A) Recommendation Validation Checklist (use for the final scrub)

Recommendation line states buy/price/terms, model version, scope (constant currency, organic perimeter).
All P0/P1 insights trace to named driver cells; lags and units stated.
First forecast month ties to last actuals; LTM reconciles to GL; CM2 tree consistent.
Baseline and downside scenarios show passive vs. managed; cost of action visible; headroom computed quarterly.
Tornado and break‑evens for top five drivers; capacity and policy gates enforced.
Valuation triangulated (DCF, implied multiples, reverse DCF); ranges consistent with peers and physics of the model.
Integration gates and 90‑day actions dated and owned; TSA scope priced with exits.
Residual risk quantified; reserves sized; liquidity buffer adequate; KRIs and flip rules live.
Term‑sheet translations mapped 1:1 to residuals and underwritten dollars.
Red‑team deltas incorporated; sign‑offs logged; Q&A binder indexed by model driver.

B) Thesis‑to‑Driver Traceability Card (one per P0/P1)

Headline insight and why it matters (ΔCM2, ΔCash, headroom).
Driver(s) moved with units and lags; cell references; source evidence (VoC, invoices, billing/settlement files, parcel/cloud bills, AR/AP agings).
Sensitivity band and break‑even.
Gate(s) and owner; earliest/most‑likely start and effect dates.
Residual risk/terms link; confidence label.

C) Valuation Triangulation Worksheet (fill once, reuse)

DCF: WACC, terminal method, key driver deltas, Year‑1/Year‑2 cash.
Implied multiples: EV/Revenue, EV/CM2, EV/EBITDA vs. peer corridors; adjustments for growth and durability (NRR, cohort decay).
Reverse DCF: implied realized‑price bps, CTS/unit change, working‑capital turns, capacity utilization; compared to evidenced ranges and gates.
Decision note: “At $X EV we underwrite Y because …; above $X+Δ, reverse DCF implies unproven Z → reprice or add terms.”

D) Risk‑to‑Terms Mapping Grid (one line per residual)

Residual risk and Cash‑VaR; KRIs and flip rules; mitigation already priced.
Proposed term(s) and how they reduce probability or severity; residual Cash‑VaR post‑terms.
Owner and negotiation status; fallback (reprice/pass) if term not secured.

E) Go/No‑Go Gate List (integration and compliance)

Billing/entitlement accuracy ≥99.5% for affected SKUs; catalog/CPQ parity; invoice credit defects = zero in pilot.
Certification/attestation live in target geos; platform listing/compliance confirmed.
Capacity rung booked; SLO headroom ≥15%; DR tested; IAM/SSO cutover ready.
Works‑council/union/legal notifications complete; TSA shadow‑runs passed with acceptance tests.

F) IC Q&A Binder Outline (organize by driver, not by department)

Price and elasticity pack; invoice and discount audits; VoC anonymized notes.
CTS pack: returns/chargebacks, parcel and cloud bills, support minutes/contact.
Funnel and channel pack; CAC/payback; marketplace policies and penalties.
Headroom and 13‑week cash; covenant math; borrowing‑base.
Residual risk cards; reserves policy; term‑sheet drafts and marked changes.

G) Decision Log and Sign‑Off Block

Decision statement; alternatives considered; reasons accepted/rejected.
Model version; sensitivity and scenario stamps; exceptions to standards.
Sign‑offs: Finance, Commercial, Ops, Tech/Sec, Legal, Risk/Treasury, Partner.
Dated conditions precedent and owners.

Mathematical and logic checks (quick formulas you should run)

Reverse DCF sanity: does the EV imply realized‑price bps or CTS/unit improvements outside proven ranges? If yes, reprice or add terms.
Payback realism: CAC payback ≤ policy guardrail in all scenarios for the channels you rely on.
Headroom cushion: minimum quarterly headroom ≥ buffer (e.g., 10–20% of covenant) in p10 downside with mitigation cost.
Capacity conservation: bookings constrained by capacity headroom and SLOs; no implied overrun of error budgets.
Ratio‑of‑sums: portfolio CM2% and NRR recomputed from segment dollars; no averaging of ratios.

Red flags—and what to do if you see them during validation

Numbers that do not reconcile. Halt; fix last‑actual and LTM ties before IC.
Upside dependent on unproven gates. Move dollars to upside‑only; add CPs/earnouts tied to NRR or realized price.
Downside unfunded. Increase reserves or change terms; if not feasible, reprice or pass.
One driver dominates a tornado with low controllability. Diversify exposure or hard‑wire terms (indexation, caps); otherwise reprice.
Clean‑team or platform policy risk. Narrow scope; delay integration; do not assume joint pricing or customer coordination pre‑close.

72‑hour sprint plan (from draft to decision‑grade recommendation)

Day 0: Freeze model version, segmentation, perimeter, FX policy. Draft the Recommendation Dossier shell and populate Insight Cards with driver cells.
Day 1: Complete reconciliations; run scenarios and sensitivities; produce headroom path and 13‑week cash; draft valuation triangulation and reverse DCF.
Day 2: Quantify residual risk and reserves; finish integration gates; map residuals to term‑sheet asks; run the red‑team; update ranges and confidence.
Day 3: Assemble executive summary; complete the Validation Checklist; secure sign‑offs; lock the IC run‑of‑show and Q&A binder indexed by driver.

Acceptance criteria for a decision‑grade recommendation

Buy/price/terms stated with ΔCM2, ΔCash, and headroom by quarter, consistent with the current model and reconciled to history.
Each P0/P1 insight traces to named driver cells with units, lags, evidence, sensitivities, and break‑evens.
Baseline and downside scenarios show passive vs. managed paths; the cost of action is explicit; headroom computed quarterly; 13‑week cash included.
Valuation triangulated and reverse‑tested; integration and value‑capture gates dated; owners assigned.
Residual risk quantified; reserves sized; KRIs wired; term‑sheet translations mapped 1:1 to residuals and underwritten dollars.
Red‑team results incorporated; alternatives framed (reprice/restructure/re‑sequence/pass); legal and platform guardrails observed.
All artifacts are reproducible in ≤3 clicks from driver cells; sign‑offs completed; IC‑ready pack delivered.

Apply this template rigorously and your “yes” will be underwritable, your “no” will be defensible, and your terms will be directly tied to residual uncertainty—turning a recommendation into a disciplined commitment the operating team can deliver against.

Commercial Due Diligence Playbook >