Closing is the starting line, not the finish. How FDD findings drive the buyer's 100-day integration plan, and why writing actionable findings pays off.
From an FDD analyst's desk, completion feels like the credits rolling: the report is signed off, the invoice goes out, and the team rolls onto the next mandate. For the buyer, the exact opposite is true. Completion is the moment the cheque clears and the risk becomes theirs. Everything the deal thesis promised - the margin uplift, the cost synergies, the "quick wins" your report politely gestured at - now has to be delivered by real people managing a real business on a Monday morning. That delivery has a name, post-merger integration (PMI), and its opening act is the 100-day plan. What almost nobody tells you as a junior is how much of that plan is quietly authored by the diligence you just finished.
The 100-day plan is the buyer's structured roadmap for the first roughly three-and-a-half months of ownership. The number is not sacred - plenty of firms run a 90-day or a 120-day version - but the logic behind it is. The first months after a change of control are the one window where a new owner has permission to change things quickly. Employees expect disruption, systems are being touched anyway, and old habits have not yet reasserted themselves. Wait six months and the organisation's antibodies have kicked in; the window has closed.
A well-built 100-day plan typically covers four strands running in parallel:
Here is the part that matters for you: strands two and three are populated almost entirely from the diligence file. The buyer does not rediscover the collections problem or the systems gap from a blank sheet of paper in week one. They lift it from your report.
Think of every finding in an FDD deliverable as having a second life. During the deal it supports a pricing or risk decision - should the buyer pay less, retain more, walk away. After the deal the same finding becomes an operational instruction - do this, by when, owned by whom. The financial due diligence process and the integration plan are two ends of the same pipe.
The migration works like this:
| FDD finding | Deal-phase use | 100-day plan translation |
|---|---|---|
| Control weakness in revenue recognition | Discount or indemnity request | Day-one workstream: install cut-off controls, monthly close discipline |
| Overdue receivables inflating working capital | Adjust working capital target | Owner tasks finance with a collections sprint |
| Deferred maintenance flattering cash flow | Reduce quality of EBITDA | Budget and schedule the maintenance capex catch-up |
| Founder holds all key relationships | Retention condition in the SPA | Execute retention terms, cross-train a deputy |
| Two customers are 45% of revenue | Sensitivity in the model | Named workstream to diversify the book |
Notice that none of these require new analysis after close. They require execution of analysis that already exists - yours.
Remediation items lead the list. Anything you flagged as a control weakness becomes an explicit early workstream, because a new owner - especially a private equity sponsor with its own investors and lenders to report to - needs trustworthy numbers fast. A sponsor cannot report a quarterly valuation to its LPs off a management accounts pack it does not trust. So the first thing that often happens post-close is a scramble to rebuild the monthly close and reporting discipline, and the specification for that scramble is your list of control findings.
Retention plans get activated the moment the deal signs. If diligence flagged that one or two individuals carry disproportionate institutional knowledge or client relationships, the retention steps negotiated pre-close - reduced-role agreements for a departing founder, cross-training, deferred consideration tied to staying - get actioned in week one. Retention is perishable; a key person who feels ignored for two months is halfway out the door.
"Must-spend" capex gets a real budget and a real date. A re-platforming need or a deferred maintenance backlog cannot stay a caveat in a report. It needs a line in the integration budget with a start date, or it silently becomes next year's crisis. Your maintenance capex normalisation is the sizing exercise the buyer inherits.
Your quick-win candidates get harvested. A gross-margin observation that pointed at a pricing or procurement inefficiency, or an NWC analysis that showed collections drifting well beyond the industry norm, tends to reappear verbatim as an early line item on the operating agenda - because these are the cheapest, fastest value the new owner can bank.
Takeaway: The distance between "a finding in your report" and "a task on someone's Monday morning list" is much shorter than most juniors assume. Write every finding as though the person reading it has to do something about it - because someone will.
Let us make this concrete. Suppose your NWC analysis found that the target collects its receivables in 68 days against a sector norm of about 50. Revenue is €40m. On the buy-side, that gap is not just a working-capital-target negotiating point - it is a one-off cash release the new owner can chase in the first 100 days.
| Metric | At completion | 100-day target | Basis |
|---|---|---|---|
| Revenue | €40.0m | €40.0m | Unchanged |
| Debtor days (DSO) | 68 | 55 | Tighten toward sector norm |
| Receivables balance | €7.45m | €6.03m | Revenue ÷ 365 × DSO |
| Cash released | - | €1.42m | Reduction in receivables |
That €1.42m is a genuine, low-risk cash prize - no restructuring, no redundancies, just tighter credit control. It typically funds part of the very capex catch-up your report also identified. The point for you as the analyst: the same diligence workpaper that supported a working capital peg negotiation also handed the integration team a €1.4m target with the arithmetic already done. One analysis, two audiences.
Not every 100-day item is a value grab. Much of the plan is about not breaking things - retaining staff, holding customers, keeping the lights on through a systems migration. But the value-creation strands connect directly to the deal's synergies in M&A case. Cost synergies (duplicate overhead, procurement scale) and revenue synergies (cross-sell, pricing) are usually scoped in the plan but delivered over a longer horizon. The 100-day plan's job is to start the clock and lock in the easy wins, not to book the entire synergy case in fifteen weeks. A plan that promises to deliver every synergy by day 100 is a plan written by someone who has never run one.
There is a well-known leak in the deal pipeline: the handoff between diligence and integration. The team implementing the 100-day plan often never reads the FDD report closely, or reads it without the context the diligence team carried in their heads. A finding that was obvious to you - "this add-back is aggressive and the underlying cost is real" - arrives to an operator as a single dense paragraph they skim past.
So a growing number of firms build an explicit diligence-to-integration handoff: a short, structured session that translates the report's findings into a prioritised, owner-ready action list. This is a genuine service beyond the traditional FDD deliverable, and it is one of the clearer ways diligence work is climbing the value chain. If you can be the analyst who runs that translation cleanly - who turns "quality-of-earnings observations" into "here are the six things to do first, in order, with the numbers attached" - you are worth considerably more than one who simply produces a technically correct databook and disappears.
The practical craft point is this: an FDD finding can be technically defensible and operationally useless at the same time. "We note the debtor days of 68 exceed peers" is defensible. It is also inert. Compare:
The second version is a sentence an integration lead can act on without re-deriving anything. It names the size, the location, and the mechanism. Writing this way costs you two extra sentences and dramatically increases the odds your work actually changes the business. It also, not incidentally, makes you look like the sharpest analyst in the room. Anchoring your write-ups against the deal thesis and the red flags you raised keeps them pointed at consequences rather than observations.
Once you are past entry level, "what happens after the deal closes?" is a favourite because it separates candidates who understand the deal lifecycle from those who only know their own workstream. A strong answer connects your work to the buyer's actions.
"Once the deal completes, the buyer moves into post-merger integration, and the first structured phase of that is usually a 100-day plan - the window where a new owner can change things quickly before the organisation settles back into old habits. What I find interesting from an FDD perspective is how much of that plan is authored by the diligence. The control weaknesses we flag become the day-one reporting workstream, because a sponsor needs numbers it can trust to report to its own investors. The key-person risks we raise become retention actions. And the softer findings - say a working-capital analysis showing debtor days well above the sector norm - often become a literal cash target in the first hundred days. If receivables were sitting at 68 days on €40m of revenue against a 50-day norm, that's roughly €1.4m of cash the buyer can release just by tightening credit control, no restructuring required. So I try to write findings knowing they may become someone's to-do list - sized, located, and with the mechanism spelled out, not just an observation that something looks high. That's also where I think diligence is heading: teams that can bridge the report into an integration plan add a lot more value than teams that just hand over a databook."
That answer works because it moves from mechanics (what the plan is) to insight (your work feeds it) to self-awareness (how that changes the way you write), which is exactly the arc interviewers are listening for. Pair it with the framing in a good interview preparation plan and you will handle the follow-ups comfortably.
If you began learning this trade by worrying about your first 90 days as an analyst, it is worth ending with the buyer's first 100 days as an owner - because they are the same skill viewed from opposite ends of the deal. The junior who only knows how to build a report produces something technically correct that may or may not change anything. The one who understands where that report goes - onto an integration lead's desk, into a sponsor's board pack, onto a credit controller's task list - writes differently, thinks about consequences, and quietly becomes the person clients ask for by name. Your report is not the finish line. It is the opening chapter of someone else's hardest year. Write it like you know that.
The Transaction Services Interview Programme (€119.99, one-time) includes a full module on the deal lifecycle beyond completion - how FDD findings feed the 100-day plan, PMI, and value creation - with model answers to the "what happens after signing?" interview questions that trip up strong candidates. 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.
