Most teams do not skip the exit readiness checklist. They run it. They just run it at the wrong time.
The pattern is consistent. The fund signals a sale window. The CFO pulls a checklist off the shelf, often a good one. The management team works through it over a few weeks, finds a list of gaps, and then realizes the gaps cannot be closed in the time left before the company goes to market. The checklist did its job. It surfaced the problems. It surfaced them six months too late to do anything but disclose them.
A checklist is a diagnostic. A diagnostic only helps if you run it while there is still time to act on the result. Run it at month 48 of a five-year hold and it becomes a list of things to apologize for in the data room.
This post does two things. It gives you a scannable checklist you can actually use. Then it explains why every item on it has to be true 18 to 24 months before exit, not 6.
The timing problem nobody names
Walk the logic backwards from the exit date.
A buyer’s diligence team will request data and watch how fast and how cleanly you answer. If your revenue does not reconcile across systems, you cannot fix that in the request window. Reconciliation is a quarter of work when there is real drift, and the drift is years old. If your KPIs are defined three different ways across three teams, you cannot agree a single definition while a buyer is waiting on the number. If the only person who understands the reporting model is one analyst, you cannot cross-train a replacement in the weeks before signing.
Every meaningful item on an exit readiness checklist has a lead time measured in months. The checklist itself takes a few weeks. The remediation takes a year. So if you first run the checklist with six months on the clock, you have built a list of problems you do not have time to solve.
This is the same dynamic playing out across the market right now. The exit backlog of roughly 32,000 companies means more sellers competing for buyer attention, and buyers using diligence friction to separate the clean assets from the messy ones. A team that ran its readiness work early shows up clean. A team that ran it late shows up explaining. In a crowded market the explaining costs you on the multiple.
The exit readiness checklist
Here is the checklist. Each item states what good looks like. If you cannot answer yes to all of these today, and you are more than two years from a planned exit, you have time. If you are inside a year, you have a disclosure list.
-
Revenue reconciles across systems. Revenue ties from your CRM to your billing system to your general ledger within a defined tolerance, with documented explanations for any variance. Not annually at audit. On demand.
-
One definition per KPI. Every metric in the board deck has a single documented definition, a named source system, and a change log. Finance, sales, and operations all produce the same number when asked the same question.
-
EBITDA adjustments have a data trail. Each adjustment can be followed from the number back to the underlying transactions by someone other than the person who built the schedule.
-
36 months of consistent history. Monthly granularity on revenue, gross margin, customer counts, and key operating metrics, with definitions that did not silently change when you switched systems.
-
Unit economics by segment. You can show contribution margin by product line, customer segment, or geography, with a documented allocation method. Not just a healthy blended number.
-
Customer concentration is mapped and stable. You know the revenue share of your top 5, 10, and 20 customers, how it has moved, and you have a plan for any single customer above 15%.
-
Churn has root causes, not just a rate. Churn is tracked by segment with tagged reasons and a trend, so a buyer can tell whether it is structural or fixable.
-
No single point of failure in reporting. More than one person can produce the key reports. The data model and integrations are documented well enough that a new hire could run them within a week.
-
Data flows are documented. A current diagram shows source systems, integration points, and the reporting layer, updated within the last six months.
-
PII and security are documented, not asserted. You have a data classification policy, a PII inventory, and access controls you can show, rather than a claim that you follow best practice.
That is the diagnostic. Now the part that matters more than the list.
Why each item needs 18 to 24 months, not 6
Take the items one layer deeper and the lead times become obvious.
Revenue reconciliation is not a report you generate. When the CRM, the billing system, and the GL disagree, the disagreement has a history. Closing it means finding where the definitions diverged, agreeing one truth, and rebuilding the tie-out so it holds every month. With real drift that is a quarter of work, and you want it running clean for several months before a buyer ever sees it. Start at month six and the buyer watches you reconcile in real time, which is the worst possible look.
KPI definitions are an organizational agreement, not a spreadsheet edit. Getting sales, finance, and operations to retire their private versions of “gross margin” or “active customer” takes negotiation and a few quarters of the new definition actually being used in the actuals. You cannot impose it under deal pressure, because the moment a number looks worse under the agreed definition, someone reaches for the old one.
Key person dependency is the slowest to fix because it is a hiring and documentation problem stacked together. If one analyst holds the reporting model in their head, removing that risk means documenting the model, cross-training a second person, and proving the second person can actually run it. That is a multi-quarter effort, and it is the item most likely to blow up between signing and close if you leave it.
The pattern repeats down the whole list. Every item that looks like a document is actually a process that needs months of running time to become trustworthy. A buyer can tell the difference between a number that has been reliable for a year and a number that was assembled last week. The first builds confidence. The second invites a second look at everything else.
The work is the same work you should already be doing
Here is the reframe that changes the timing math.
The readiness work and the year-two value creation work are the same work. You do not run an exit readiness program and, separately, a performance management program. The thing that makes a company easy to diligence is the same thing that makes it easy to run.
I wrote about this from the operating side in diagnosing a stalled value creation plan. When growth stalls at year two, the most common hidden cause is that the company cannot see its own performance clearly enough to know which lever is working. The fix is to pick the handful of metrics the plan depends on, give each one a single trusted definition, and instrument the initiatives against them.
Look at that fix next to the checklist above. One definition per KPI. Unit economics by segment. Trusted numbers more than one person can produce. It is the same list. The work that unblocks a stalled value creation plan in year two is the work that passes diligence in year four. You are not doing it twice. You are doing it once, early, and getting both returns.
That is why the timing argument is not a counsel of perfection. It is a counsel of sequence. Do the work when it also helps you run the company, and it is in place when you go to market for free. Do it only when the exit forces it, and you pay full price for it under the worst conditions, with a buyer watching.
When to actually run it
The detailed timeline for the data-specific items lives in the original exit data checklist. The short version is this.
Run the full checklist as a real assessment 18 to 24 months out. Not a glance. An honest inventory where you answer every item and rank the gaps by how much they will slow diligence or trigger an adjustment.
Spend the following year closing the critical gaps, which means reconciliation, KPI definitions, key person cross-training, and system documentation. These are the items with the longest lead times and the highest cost if a buyer finds them open.
In the final six months, stop fixing and start testing. Run a mock diligence exercise. Have someone outside the core team request data and time how fast and how accurately the team responds. By then the checklist should be a maintenance routine, not a rescue project.
If you are reading this with two years or more on the clock, you are in the right window. Run the checklist now, treat the gaps as your value creation backlog, and the version of this work that everyone else runs as a fire drill becomes something you finished long before the buyer arrived.
If you are reading this with six months on the clock, run it anyway. You will not close every gap. But knowing exactly what a buyer will find, and being the one to name it first, is a far stronger position than being surprised by it in the data room.
The checklist is not the problem. The calendar is.