Ask a portfolio CFO how the monthly pack gets made and you will hear a description of a person. A controller who exports from the ERP, pulls a report from the CRM, merges in a spreadsheet somebody built in 2021, adjusts three things by hand for reasons they can explain but have not written down, and produces a deck.
It works. It also means the numbers arrive three weeks after month end, cannot be traced back to source, and stop entirely when that person is on leave.
Why this is a governance problem, not a convenience one
Three consequences follow, and they compound.
Decisions lag. By the time the board sees a deteriorating metric, it has been true for six weeks. Corrective action starts in month two of a problem rather than month one, which in a five-year hold is a meaningful fraction of the available time.
Numbers cannot be defended. When the sponsor asks why a figure moved, the answer requires reconstructing the spreadsheet. Under diligence at exit, that reconstruction happens under time pressure in front of a buyer, and disagreements about the definition of a metric become disagreements about the quality of the business.
Nobody experiments. When producing a number costs three weeks, you only produce the numbers you already agreed to produce. The question a director actually wants to ask goes unasked, because asking it is expensive.
What "board-grade" means concretely
It does not mean a data warehouse and a business intelligence programme. For most portfolio companies that is over-built and consumes the attention the commercial plan needs.
It means four things.
Defined metrics. Written down, agreed once, with the calculation stated. Most reporting disputes are definitional rather than factual.
A single source per metric. Each number comes from one system, not from a reconciliation of two.
Automated extraction. The manual step is judgement, not copying. If a person is retyping, that is a failure point and a delay.
A trail. Somebody can answer "where did this come from" without opening a spreadsheet.
That is achievable in weeks, not quarters, for most companies.
Sequence it before the systems consolidation
Here is the counter-intuitive part. The instinct is to fix reporting after the ERP consolidation, on the grounds that consolidating first makes reporting easy.
In practice, do reporting first. Consolidation programmes take a year or more, the board needs numbers in the meantime, and the definitional work you do for reporting is exactly the work the consolidation will need anyway. You also gain the ability to measure whether the consolidation is delivering, which is otherwise asserted rather than demonstrated.
What it is worth at exit
A buyer's diligence team will ask for the same metrics, at a granularity you do not currently produce, on a deadline. Companies that can answer in days rather than weeks close faster and give up less in negotiation, because every unanswered question is a discount somebody is entitled to ask for.
Reporting infrastructure built in year one is diligence readiness in year four, bought at a fraction of the price of doing it under pressure.