The reporting a portfolio company owes its sponsor, and who builds it

Every PE-backed company owes its sponsor a package. The contents vary by fund and the shape is remarkably consistent. Financials in the sponsor's format, a set of operating metrics chosen at close, a comparison against the plan the deal was underwritten on, covenant compliance on the lender's schedule, and a board deck that has to say what changed and why.

The company was staffed for the close. It was rarely staffed for the package. So the package gets built by whoever built the first one, which at a middle-market company is the CFO or the single analyst sitting next to them, and then it gets built again the following month, and the month after that, for the length of the hold.

What reporting does a private equity sponsor expect from a portfolio company?

Most sponsors expect the same five things on a monthly or quarterly cycle, delivered in the sponsor's format rather than the company's.

• Financials in the sponsor's template. Your trial balance mapped to their line items, remapped every time an account is added.
• The metric set. Operating KPIs selected during diligence, defined once, and expected to mean the same thing in month thirty as they did in month one.
• Budget versus actual, with the variance explained. The comparison is arithmetic. The explanation underneath it is where the work is.
• Covenant compliance and a cash view. On the lender's calendar rather than yours, and unforgiving about dates.
• The board package. All of the above, plus progress against the value creation plan, which is a claim on the same calendars the initiatives already run on.

None of that is difficult in the way an accounting judgment is difficult. It is exacting production against a fixed date. It is also additive. A question asked in a board meeting tends to become a standing exhibit in the next package, so what a company produces in year three is materially longer than what it agreed to at close, and nobody ever formally decided to lengthen it.

What is the difference between the monthly close and FP&A?

The close establishes what happened. FP&A compares it to the plan and asks what the rest of the year looks like now.

The close is backward-looking and transactional. It has a defined standard, a defined endpoint, and a sign-off. Which parts of that cycle an embedded seat can hold is settled in what an offshore finance team can own and what stays with your controller. This piece starts after that endpoint.

The package runs on different material. It takes closed numbers and turns them into comparisons. The month against budget, the quarter against last year, the year to date against what the sponsor underwrote. Then it asks the forward question the close never asks. Given this result, what does the rest of the year look like, and what has to change.

Two things follow from the sequencing. The package cannot start until the close finishes, so it compresses into the narrowest and most crowded stretch of the month. And the skills are different. Close work rewards accuracy and control. Package work rewards structure and repeatability, so that an owner reads the same document every cycle and spends their attention on the business rather than on the format.

Who builds the board reporting package at a mid-market company?

One person, usually, and usually someone too senior to be building it.

The pattern is easy to see once you look for it. The package was designed under deadline in the months after the deal, by the CFO, because nobody else understood both the company's numbers and what the new owner was asking for. Design work of that kind belongs to a CFO. The thirty rebuilds that follow it do not, and they land on the same calendar anyway, because the file carries the CFO's logic and nobody else has ever opened it.

What senior time spent that way costs a company has an answer of its own. The observation that matters here is structural. Companies hire for the close, because a close has an obvious owner and an obvious title. Almost nobody carries the title of the person who produces the package.

Across a portfolio the oddity gets sharper. The sponsor's format is the one stream of work that genuinely looks the same in every company the fund owns, and it is usually the least standardized thing in the portfolio.

Nobody ever decides to lengthen the sponsor package. It lengthens one board question at a time.

Can FP&A work be done by an offshore team?

The production can. The view cannot.

An embedded seat can hold the recurring build of the package, which is most of the hours in it.

• The mapping. Chart of accounts to the sponsor's template, maintained as the accounts change.
• The build. Same exhibits, same order, same definitions, every cycle, so this month's document is readable against last month's.
• The variance bridge. Movement decomposed into price, volume, mix, and timing, with the support attached underneath each piece.
• The metric set. Operating KPIs pulled from the source systems on schedule, with the definitions written down and held steady.
• Reforecast mechanics. The model updated, the drivers refreshed, and the sensitivities run against assumptions the CFO sets.
• The open-question log. Whatever the sponsor asked at the last meeting, carried forward and closed out in writing before the next one.

What does not move is anything that requires a view on the business.

• The assumptions. A reforecast is a set of judgments about demand, pricing, and timing. Someone has to hold them and be wrong in public when they turn out wrong.
• The narrative. A variance can be decomposed by anyone. What it means, and what the company intends to do about it, is the CFO's to say.
• The room. Board and sponsor conversations run on follow-up questions, and the person answering should be the person accountable for the answer.
• The framing. Which exhibit leads, what gets flagged early, and what a company chooses to put in front of its owners is a judgment about the relationship as much as about the numbers.
• The commitment. A reforecast presented to a sponsor becomes a number the CFO will be held to. Nobody can agree to that on their behalf.

The dividing line is exposure. Work that ends inside the company can be owned by a seat. Work that ends in front of the owners belongs to whoever will be standing there.

Where Kayana fits

Kayana creates Mini-GCCs for PE-backed middle-market companies, and reporting is one of the clearer places for a seat to land, because the work recurs against a date somebody has already circled. A seat placed there holds the mapping, the build, the bridge, and the open-question log, working inside your model, your systems, and your reporting calendar on your business day. The environment around that seat is ours to design and operate rather than something a company invents while the month is closing. Enough of those seats in one company and what exists is the Mini-GCC model, a GCC without the entity, the real estate, or the multi-year build.

Which stream a company hands over first is a separate decision with its own three-question test, and a package produced once a month is rarely the answer to it. The embedded team at one $75M PE-backed company has grown past 10 seats since it started. Voluntary turnover across the teams we build runs 3–5% in year one, which matters here in a specific way. A sponsor's format is learned once, and relearning it is a cost the company pays rather than the seat.

Quick answers

The book is the longer argument behind all of this. Operational Alpha →