A Day in the Life of an FDD Analyst: What Really Happens on a Deal?

A Day in the Life of an FDD Analyst: What Really Happens on a Deal?

The Version You Read in Job Descriptions vs What Actually Happens

Job descriptions for transaction services roles are masterpieces of vague language. "Work on complex financial analyses." "Support deal teams in multi-jurisdictional transactions." "Develop relationships with senior stakeholders."

All technically true. All completely useless for understanding what you will actually be doing on a Tuesday at 11pm when the data room just updated and your manager needs a revised EBITDA bridge by 6am.

What follows is a genuine account of a typical deal week—based on my experience across dozens of transactions. I have changed identifying details but nothing about the texture of the work.

Day 1 (Monday): The Data Room Opens

The deal team has been briefed. The engagement letter is signed. The virtual data room (VDR) credentials arrive Monday morning.

Your first job is a data room index review—understanding what financial information has been provided and what is conspicuously missing. You build a working document: what you have, what you need, and what the gaps tell you about the quality of the seller's financial operations.

By mid-morning, you are in a kickoff call with the client's deal team. Scope confirmation. Timeline discussion. Red flags from the initial information memorandum (IM) that the client flagged as areas of concern.

By end of day, you and the team lead have designed the databook structure—the multi-tab Excel workbook that will house every piece of analysis for the next four weeks. Tab structure. Formula conventions. Version control protocol. This sounds tedious. It is also critical: a poorly structured databook will cost you hours of rework at the worst possible moment.

Day 2 (Tuesday): Building the Financial Model

The management accounts are in the VDR. Monthly P&L for the past three years. Quarterly by segment. Some notes. Some gaps.

You spend Tuesday inputting the historical financials into the databook—carefully, because every number is a foundation for the analysis that follows. Any input error that surfaces in week three will require a cascade of corrections across interdependent tabs.

By afternoon, you have a preliminary view of revenue trends: is growth accelerating or decelerating? Is the margin profile stable or volatile? Are there periods that look like anomalies and need investigation?

You flag three questions for management: a revenue spike in Q3 of year two that does not correspond to any disclosed event, a sudden jump in professional fees in the final quarter of the most recent year, and a customer that appeared in year one's top-ten list and has since disappeared entirely. These become the seeds of your initial Information Request List (IRL).

Day 3 (Wednesday): Management Call

Management calls are where the real intelligence is gathered. The documents tell you the numbers. The management call tells you the story—and, more importantly, whether the story is credible.

Your team lead runs the call. You are on mute, taking detailed notes, tracking which questions get answered directly and which ones get redirected. Credibility is assessed in real time: does the CFO know the numbers cold, or are they referring to a prepared document for every question? Does the commercial explanation for the revenue spike hold up, or does it feel rehearsed and imprecise?

The three items you flagged yesterday come up. The revenue spike was a large one-off government contract that is not expected to recur. The professional fees include legal costs related to a pending employee dispute that was not disclosed in the IM. The missing customer churned following a product quality issue eighteen months ago.

Each of these answers creates a new action: the government contract becomes a normalisation adjustment. The legal dispute becomes a potential debt-like item. The customer churn becomes a revenue quality question that needs deeper investigation.

Day 4 (Thursday): The Grind

Thursday is the day you rarely see in LinkedIn posts about glamorous M&A careers.

You are reconciling management accounts to the statutory financial statements—a necessary but painstaking exercise that often surfaces timing differences, reclassifications, and occasionally genuine inconsistencies. You are building a working capital schedule, calculating trailing twelve-month averages, and constructing the normalised working capital peg.

By afternoon, your inbox has 23 new responses from management to the IRL. You work through each one, updating the databook, closing items that are resolved, and flagging the four responses that have raised more questions than they answered.

At 9pm, your manager sends an email: the client has asked for a preliminary EBITDA view by Friday morning to support a board discussion. You rebuild the EBITDA bridge with the data you have, document the assumptions clearly, and note what would change as additional data arrives. You send it at 11:30pm with a one-page cover note.

Day 5 (Friday): Deliverable Pressure

The preliminary EBITDA note was received well. But the client now has follow-up questions. Three of them require analysis you have not yet completed. You reprioritise.

By midday, you have a clearer picture of the business. The adjusted EBITDA is approximately 18% below what the seller's model implies—a combination of three normalisation adjustments the seller made that do not survive scrutiny, and two items the seller missed entirely.

You begin drafting the relevant sections of the report. Good FDD writing is precise, concise, and does not hedge unnecessarily. Every finding needs a number, a source, and a commercial implication. "Revenue quality appears reasonable" is not a finding. "Revenue is concentrated in three customers representing 67% of EBITDA; the largest has been in annual price renegotiation for the past two years" is a finding.

By 6pm, you are on a catch-up call with the team. By 8pm, you are back in the databook. This is a four-week engagement. This was week one.

What This Actually Teaches You

An FDD engagement compresses more financial learning into four weeks than most finance roles deliver in a year. You are reading three years of management accounts, understanding a business model from first principles, interrogating management representations, and forming an independent view of financial quality—all under time pressure and directly in service of a commercial outcome.

The analysts who thrive in this environment share a few characteristics: they are detail-oriented without losing sight of the big picture, they communicate clearly and without ego, and they can sustain quality under pressure.

The analysts who struggle are usually those who expected a more structured, predictable environment—or who underestimated how much writing and communication the role requires alongside the numbers work.

If reading this account makes you think "that sounds genuinely interesting"—you are probably the right person for this career.

📌 Train like you are already on a deal. The Investyn FDD Masterclass uses live deal case studies to prepare you for exactly this environment. Enroll now.