Exit readiness and the back office: what diligence asks of an operating team

A sale is a planned event. The hold period has a shape from the beginning, the sponsor and the management team have been talking about the window for a while, and when a process actually starts, most of the company keeps doing what it did the month before. Customers call. Product ships. The month closes.

One part of the company picks up a second job. The finance and operations team receives a request list, then a second one, then the follow-up questions on the first two, and the base business runs on the same calendar it always did. Almost nothing on that list is new work. That is the part worth understanding before a process starts.

What a sale asks the back office for

It asks for evidence. The same numbers the company has been reporting all along, presented in a form that somebody outside the company can verify without asking a person.

Sell-side quality of earnings reviews have become close to standard in middle-market processes, and the advisers who run them describe a fairly consistent core.

• Reconciliations and account detail, with support attached, for every period in the review window.
• Revenue cut several ways. By customer, by product, by month, and tied back to the general ledger each time.
• Support for every adjustment and add-back, at the level of the invoice or the contract rather than the summary schedule.
• Working-capital detail by month, with enough history behind it to show what normal looks like.
• Contracts located and read. Customer terms, supplier terms, and the change-of-control provisions inside them.
• Reporting that is consistent across periods, so that a metric means the same thing in month nine that it meant in month one.

Every item on that list is recurring, definable work of the kind a finance department already does. What changes at exit is the volume, the simultaneity, and the reader.

How a thin finance team experiences diligence

A capable team that has been running lean answers questions quickly and produces artifacts slowly. Diligence asks for artifacts.

The mechanism is worth stating generously. When a team carries more work than its capacity, capable people close the gap themselves. The controller holds the reconciliation logic in their own practice. The FP&A lead knows which branch's numbers deserve a second look before they go out. The month closes on time because two or three people carry a large part of the method personally, and that absorption is a real part of why the numbers landed for three years.

Operational Alpha calls that absorption Coping, and the word carries no criticism. It describes the most reliable people in a company closing gaps the structure left open, and the shape it takes on a given team is the subject of how capable teams end up firefighting.

A process changes what that method has to be. A schedule that lived in one person's practice becomes a document a stranger has to follow. A number that was right every month has to be shown to be right, from source, in a form that reproduces on request. Converting practice into artifact is the actual work of exit preparation, and it is why a request list lands heavier on a lean team than its page count suggests.

What operational problems slow a sale process down

Response time, mostly, and the follow-up questions that inconsistent answers generate.

A process moves at the pace of the slowest recurring answer. Each request has a turnaround, and each turnaround competes with a close calendar that did not move to accommodate it. The same two or three people are the source for both, so a heavy week in diligence is a thin week in the base business, and the following month arrives on schedule regardless.

Version drift is the second one. When a metric has been assembled by hand every month, small definitional differences accumulate across periods. Nothing is wrong. The customer count built in March was built slightly differently from the one built in September. A reader outside the company cannot tell a definitional change from a business change, so they ask, and one question becomes four.

Continuity is the third. A process runs for months, and a person who holds a body of work in their own practice may take a new role in the middle of it. What the company still holds the next morning gets decided long in advance, which is a design question of its own.

Diligence rarely asks whether the number is right. It asks to be shown how the number was made, by someone other than the person who made it.

When a portfolio company should start preparing operationally for exit

Advisers who run these processes generally put the preparation window at twelve to twenty-four months before a sale. The capacity question sits earlier than the rest of that work, for a reason that has nothing to do with ambition.

Most of exit preparation can be commissioned. A banker is engaged, an accounting firm is engaged, and the work begins when the engagement letter is signed. Capacity behaves differently. A search, a notice period, and a ramp run in quarters, and most of what an added seat is worth shows up in the months after it has learned the company's systems and chart of accounts. Capacity is the piece of exit readiness with the longest lead time and the least ability to be bought late.

There is a better frame for it than exit preparation. Capacity built in year two of a hold works for years two, three, and four, and it happens to be standing when the request list arrives. The same arithmetic shows up at the start of a hold, where a value creation plan and the run-the-business work draw on the same calendars. At the portfolio level it shows up as a design that repeats between companies while each company keeps its own team.

Where Kayana fits

One boundary first, because it matters. Kayana does not do sell-side advisory, quality of earnings work, audit support, or valuation. Those are professional engagements, and the bankers and accounting firms that run them are good at running them. What Kayana builds is the ongoing operating capacity underneath.

That capacity is built for PE-backed middle-market companies. The operators arrive already senior, recruited out of the capability centers the Fortune 500 built, and they work inside one company's cadence, calendar, and systems. The client defines the seat and what done means. We design and run the environment around it. Grown seat by seat, that layer is the Mini-GCC model, and it takes no entity, no real estate, and no multi-year build.

At one $75M PE-backed company the team was three people, at roughly $125K a year. Six months in, two of its senior leaders had recovered enough of the week to stand up two new product lines, and the same structure has since carried that team past 10 people. Voluntary turnover across the teams we build runs 3–5% in year one, which is the part that matters at the end of a hold. The people who assembled the reporting for three years are the people who can still explain it in month two of a process.

Quick answers

The design principles behind an operating layer that compounds are the subject of the book. Operational Alpha →