How to read a management presentation as a TS analyst: why the numbers rarely match FDD, what to listen for, and how to turn a sales pitch into a scope map.
A management presentation is the most persuasive document you will see in a deal, and the least reliable. It is polished, confident, and built by people who want the transaction to close at the highest possible price. If you walk out of the room having simply absorbed the story, you have done the seller's job for them. The analyst's task is the opposite: to leave with a list of claims to test, not a set of conclusions to reproduce. Get that framing right and everything downstream — your scoping, your scepticism, your EBITDA bridge — falls into place.
Early in a process, often before detailed data room access opens, the buyer's deal team sits through a session where the target's leadership walks through the business: market opportunity, history, competitive position, strategic initiatives, and a forward-looking growth plan. The deck is usually built with heavy input from the seller's advisers, and it is engineered to present the business at its best.
That means the numbers shown are the seller's preferred framing: the highest defensible EBITDA, the smoothest growth trend, the cleanest margin story. This is not deception — it is advocacy. Every business, presented by its own management, looks better than it does after an independent quality of earnings review. Your job is to know that going in.
The session is genuinely valuable, but not because the figures are trustworthy in isolation. It is valuable because it tells you, in the sellers' own words, exactly which parts of the story carry the deal — and therefore which parts you must break.
It helps to understand the mechanics of how the deck was built. In a well-run sell-side process, the target's advisers will have already produced a vendor due diligence report and a data pack, and the presentation is the human-facing distillation of that work. The order of the slides is not neutral. Whatever leads — the market, the growth rate, the flagship contract — is what the seller believes justifies the multiple. Whatever gets a single reluctant slide near the end is what the seller hopes you will not dwell on. Read the running order as a ranking of the seller's own anxieties and you are already ahead of most of the room.
Almost every management presentation contains an adjusted EBITDA figure higher than what a rigorous QoE analysis will ultimately support. This happens for structural reasons, not bad faith. Management's own add-backs are naturally more generous than an independent analyst's: they classify more items as "one-off", they annualise favourable run-rates, and they rarely deduct the normalising adjustments that cut the other way.
Consider a worked example. Management presents an adjusted EBITDA of €12.0m. Here is how a typical FDD review might reconcile it back to a defensible figure:
| Item | €m | Rationale |
|---|---|---|
| Management adjusted EBITDA | 12.0 | Starting point from the deck |
| Reverse "one-off" marketing add-back | (0.6) | Recurring in substance, spent every year |
| Remove annualised new-contract uplift | (0.5) | Contract live only 4 months; not yet run-rate |
| Add back genuine one-off legal cost | 0.3 | Defensible, non-recurring |
| Normalise owner's above-market salary | (0.4) | Adjustment overstated vs. market rate |
| Correct cut-off on Q4 revenue | (0.3) | Revenue recognised early |
| FDD-supportable adjusted EBITDA | 10.5 | Roughly 12.5% below management |
A gap of that size — €12.0m converging to €10.5m — is completely normal and does not imply anything untoward. A much larger gap, or one resting on aggressive, hard-to-defend add-backs, is a different matter: it should sharpen your scepticism for the rest of the engagement. The magnitude of the gap is itself a data point.
Treat the management EBITDA as a ceiling, not an anchor. Your reconciliation only ever moves in one general direction, and the deck tells you where the pressure will come from.
The asymmetry is worth internalising because it shapes how you set expectations with the deal team. Adjustments that reduce EBITDA — recurring costs mislabelled as one-off, cut-off errors, above-market owner remuneration, over-optimistic annualisation — vastly outnumber the ones that raise it. That is not cynicism; it is the natural result of management having every incentive to be generous with add-backs and no incentive to volunteer the ones that cut against them. When a partner asks you early in the deal "how much do you think comes off the number?", a considered answer — grounded in which specific claims look softest — is worth far more than a shrug. The presentation is where you gather the evidence for that first, rough estimate.
Note too that the direction of travel connects the presentation to the eventual SPA mechanics. If the price is struck on a management-flattered EBITDA and your work later supports a lower figure, that gap has to be absorbed somewhere — in the multiple, in the headline price, or in the completion mechanism. The earlier you flag the likely size of the reconciliation, the more room the deal team has to manage it.
You are not in the room to be impressed. You are there to catalogue. The three things worth their weight in gold:
The table below maps common presentation claims to the workstream that should test them:
| Management claim | Where you test it | What "good" looks like |
|---|---|---|
| "Revenue is highly recurring" | Revenue quality / contract review | Contracted, multi-year, low churn |
| "That cost was a one-off" | EBITDA adjustments | Genuinely non-recurring, evidenced |
| "Working capital is stable" | NWC analysis | No trend, no year-end window-dressing |
| "We have no meaningful debt-like items" | Net debt review | No hidden lease, factoring, or earn-out |
| "Growth is broad-based" | Customer concentration | Top-10 customers a modest share |
Most junior analysts do not attend the presentation directly — it is usually a deal team and senior FDD lead session. But the themes that emerge get relayed to the working team as the initial scope: "management claims X, go verify it." Understanding why those questions were flagged — because they trace to a story that needs independent testing — lets you approach the data room with the right posture. You are not summarising neutral facts; you are adjudicating contested claims.
This is also where the presentation quietly shapes your FDD report structure. The findings that matter most are almost always the ones where management's story and the underlying data diverge. If you have listened well, you already know which sections of your report will carry the weight before you have opened a single schedule.
The relaying process is imperfect, which is another reason to understand the why behind each flagged question rather than just the question itself. A scope note that reads "verify the recurring revenue claim" is much easier to execute well if you know it came from management leaning heavily on a stickiness argument they could not evidence in the room. Knowing the provenance tells you what a satisfying answer looks like and what a red herring looks like. An analyst who treats scope items as disconnected tasks will produce technically correct schedules that miss the point; one who understands the underlying claim will produce findings that actually move the deal.
The practical output of a good management presentation, from an analyst's seat, is a structured question log. For every material claim, note: the claim as stated, the evidence management offered (often none), and the test you will run. This log becomes the backbone of your information request list and, later, the spine of your findings. It is far more useful than tidy notes on the growth strategy, which you can read off the deck anyway.
A disciplined analyst can predict two-thirds of their eventual key findings from the presentation alone, simply by noting where the story is strongest and least evidenced. The strongest claims are load-bearing for the price; load-bearing claims are exactly what a buyer pays you to stress.
There is a discipline to the log itself. For each entry, record three columns and resist the urge to editorialise: the claim exactly as management framed it, the evidence offered in the room (which, for the most important claims, is frequently "none — asserted"), and the test you will run. Keep it factual, because this log will be read by people who were not in the room and who will judge your scepticism by how precisely you captured the claim. A vague note like "growth looks strong" is useless; "management attributes 60% of FY growth to two enterprise wins signed in H2, no contract detail shown — verify tenure, pricing and churn" is a testable proposition you can hand to a colleague. The best analysts treat the log as the first draft of their findings section, not as scratch notes.
One more refinement: separate claims that are checkable now from those that need data-room access. Some assertions — market size, competitive positioning — you can partly triangulate against public sources before the room even opens. Others — cut-off, add-back composition, customer-level revenue — wait on the data pack. Sequencing your log this way lets you start work the moment the room opens rather than re-reading the deck to remember what mattered.
Interviewers love this topic because it separates candidates who understand FDD as a process from those who think it is data entry. Expect: "You attend a management presentation and their adjusted EBITDA is well above what your analysis supports. How do you think about that?"
"I'd start by expecting a gap — management's adjusted EBITDA is almost always higher than what an independent QoE will support, because their add-backs are more generous and they annualise favourable run-rates. So a figure like €12m converging to €10.5m wouldn't alarm me on its own; that's a normal 10-to-15 percent reconciliation. What I'd care about is the composition and the size of the gap. If it's built on a handful of genuinely one-off items I can evidence, fine. If it rests on recurring costs dressed up as exceptional, or on annualising a contract that's only been live a few months, that tells me management is stretching, and I'd carry that scepticism into every other workstream. Either way, I treat the presentation figure as a ceiling and a hypothesis to test against the underlying data — not as an anchor. Concretely, I'd leave the room with a question log: each material claim, the evidence offered, and the test I'll run once I'm in the data room."
That answer works because it shows you expect the gap, you can size and decompose it, and you convert the session into action rather than treating it as gospel or as fraud.
A management presentation is not a set of answers — it is a beautifully rehearsed set of claims, and the polish is precisely the point. The seller has told you, at some expense, exactly which parts of the story the price depends on. Take the gift for what it is: a map of where to point your scepticism. The analyst who walks out with a question list, not a summary, is already halfway to a report that earns its fee.
The Transaction Services Interview Programme (€119.99, one-time) includes a full module on reading management presentations — turning a seller's pitch into a testable question log, reconciling management EBITDA to a defensible figure, and answering the "their number is too high" interview question with confidence. Enrol today.
Hundreds of candidates prepared their interviews with this programme. Those who landed the role have one thing in common: they worked the cases before walking into the room.
