What happens to finance in the first 100 days after a PE investment?
In the first hundred days the finance function acquires obligations it did not have the week before: a reporting calendar set by the credit agreement, a sponsor expecting monthly information in a specific format, and covenant tests with dates attached. Most founder-run companies can produce none of it on day one, and the deadlines have already started running.
The gap is rarely competence. It is that the company was built to answer to itself and is now answering to institutions with standardised expectations and contractual deadlines.
Days 1–15: read everything, change nothing
The instinct is to start building. Resist it for two weeks. Building against a misunderstanding of the obligations is more expensive than the delay.
Read the credit agreement properly. Not the summary, the agreement. Specifically: the definition of Consolidated EBITDA and every permitted add-back with its cap; the financial covenants, their levels, and their step-downs over time; the reporting obligations and their deadlines; the definition of a responsible officer; cure rights and their limits; and the restricted payments clause governing what can be distributed.
Write these into a one-page summary. That page becomes the reference for the next several years, and producing it takes a day.
Read the purchase agreement, particularly the working capital true-up mechanism, which frequently has a settlement date inside the first hundred days and real money attached.
Read the last four board packages and the sponsor's reporting template. The template tells you what format is expected. The packages tell you what the company has been able to produce.
Walk the close with the controller. Not a conversation about the close — sit through one. You are establishing which numbers are reliable, where the bottlenecks are, and how long each step actually takes.
Days 15–30: the obligations calendar and the first cash view
Build the calendar. Every deliverable required by the credit agreement and the sponsor, with due dates for the full year, working backwards through the close to the date each must start.
| Deliverable | Due | Work starts |
|---|---|---|
| Monthly financials to lender | Day 30 | Day 20 |
| Monthly sponsor package | Day 20 | Day 12 |
| Quarterly compliance certificate | Day 45 | Day 30 |
| Quarterly board materials | 5 days pre-meeting | 15 days pre-meeting |
| Annual budget | 30 days pre-year-end | 90 days pre-year-end |
Missing a delivery deadline is technically a default even when every ratio is comfortable. It is also the most avoidable failure in this entire period, because it is purely a scheduling problem.
Build a first 13-week cash flow. Deliberately rough. A forecast in use and being corrected weekly is worth more than a polished one delivered in week ten. The structure is here.
Recalculate the covenants yourself. Do not accept the deal model's figures. Calculate the opening leverage and fixed charge coverage from the actual trial balance and the actual definitions. This is where companies discover their EBITDA is lower than they believed, because an add-back they had been applying freely is capped.
Days 30–60: build the model, fix the close
The three-statement model. Driver-based, monthly, backtested against two or three years of history. Backtesting is the honest test — if the drivers cannot explain periods that already happened, they will not forecast the ones that have not. Structure and linkage logic.
Attack the close. Most founder-run companies close between day 15 and day 25. Sponsors expect day 10 or better, and the binding constraint is almost never effort. It is usually one or two specific steps — an intercompany reconciliation with no owner, a revenue cut-off that requires a conversation with sales each month, a bank reconciliation waiting on a statement that arrives late.
Sequence matters more than speed. Find the steps that block others and give each an owner and a deadline. A close going from day 22 to day 12 is normal in this period and rarely requires new headcount.
Settle metric definitions. If sales and finance count bookings differently, every future board discussion will be about the definition rather than the result. Agree it once, write it down, restate the history onto the agreed basis, and disclose that you have.
Days 60–100: produce a full cycle
Run one complete cycle end to end. Close, reforecast, variance analysis, sponsor package, board materials, on the calendar dates. The first cycle will be uncomfortable and will surface the disagreements. That is its function — better in month three than in month nine with a covenant test approaching.
Build the board package properly. Seven sections, main body under twenty slides, distributed five business days ahead. Section by section.
Cut the KPIs to eight or twelve, each with a target, a trend, and an agreed definition. Picking them.
Write the finance team plan. What the function needs over the next eighteen months, in what order. Frequently the first hire is an FP&A analyst rather than a more senior person, because the recurring analytical load is real, ongoing, and belongs in-house.
The three failures that recur
Discovering a reporting obligation late. A monthly certificate that was never filed, found in month seven. The lender may not have chased it; that is not the same as it not mattering. Read the agreement in week one.
Building the forecast on an unreliable close. A model fed by numbers that do not tie produces a confident projection of an error. Fix the close first, even though it is the less interesting work.
Reporting what is easy instead of what is asked for. The sponsor has a template because they aggregate across a portfolio. Submitting a different format means someone re-keys it, and it signals that the company has not understood the relationship.
What should exist at day 100
A reasonable standard to hold the period to:
- A one-page summary of the credit agreement's definitions, covenants, and obligations.
- A full-year calendar of every deliverable, with owners.
- A 13-week cash flow, updated weekly, with several weeks of variance history.
- A backtested three-statement model with a documented update routine.
- A close finishing by day 12 or better.
- Eight to twelve KPIs with written definitions and restated history.
- One complete reporting cycle delivered on time.
- A finance team plan for the next eighteen months.
None of this requires a full-time CFO in most lower-middle-market companies. It requires someone senior for a few days a month who has done it before — which is the engagement itself, and what it costs.
What the sponsor is actually assessing
Something worth naming plainly: in the first hundred days the sponsor is forming a view of the finance function, and that view is durable. It is being formed from a small number of observable things.
Does the company hit its dates? Reporting delivered on the calendar date, every time, is the single strongest signal available. It is also almost entirely within your control, which is why missing a date is read as a statement about management rather than about circumstances.
Do the numbers stay still? A figure that changes between the flash report, the board package, and the compliance certificate is the fastest way to lose confidence. One source, one definition, and a disclosed restatement when something genuinely must change.
Does management know the numbers before being asked? A CEO who opens with "margin fell 240 basis points, three-quarters of it mix from the two new contracts, and here is what we are doing" is describing a business under control. The same facts delivered in response to a question read very differently.
Is bad news early? Sponsors expect problems; portfolio companies have them. What they are testing is whether the problem surfaced when it was still a set of options. A forecast breach raised two quarters out with a plan attached builds more confidence than a good quarter does.
The mistake of trying to look finished
There is a temptation in this period to present the finance function as more capable than it currently is — to smooth over the day-22 close, to avoid mentioning the reporting obligation that was missed before anyone noticed.
It does not survive. The close date becomes evident within two cycles, and the missed obligation surfaces during the next amendment or diligence process, at which point the concealment is a larger problem than the original omission.
The stronger position in month one is an honest inventory: here is what works, here is what does not, here is the sequence for fixing it, here are the dates. Sponsors are experienced at reading portfolio finance functions and are rarely surprised by the findings. What they remember is whether they heard it from management or discovered it themselves.