Partners

For private equity operating teams

Portfolio reporting fails for a structural reason: eleven companies on nine systems, each closing on its own timetable, consolidated by an associate in Excel. Standardising the systems is a multi-year programme. Standardising the reporting layer over them is a quarter.

How many platform companies?

Tell us your portfolio shape and what reporting you cannot get. We will scope it.

1 / 3
Report across mixed systemsNo portfolio-wide migrationDiligence-grade data rooms

Partners

Six things that break portfolio reporting.

None of these are solved by mandating a single ERP across the portfolio, which is why that mandate so rarely survives contact with the first platform company.

Nine systems, one template

Each company maps its own chart to the portfolio template by hand, monthly, differently. The mapping lives in an associate’s workbook and nowhere else.

Reporting arrives at different speeds

A company closing in six days and one closing in eighteen cannot be consolidated on the same cadence, so the portfolio view moves at the pace of the slowest.

Definitions drift

Adjusted EBITDA means something slightly different at each company because each CFO interpreted the template. The differences are legitimate and nobody has written them down.

Diligence starts from scratch

At exit, three years of history has to be reassembled and reconciled, usually under time pressure, usually by the people least able to spare it.

Add-ons multiply it

Every bolt-on acquisition adds a system, a chart, and a close calendar. The consolidation problem grows superlinearly rather than by one.

It depends on one person

The portfolio model is maintained by one associate. When they move on, several quarters of institutional knowledge leaves with them.

Why the standard answer usually fails

The instinct is to mandate one ERP across the portfolio. It is coherent on a slide and it runs into three things: each platform company has its own operational requirements, each has a CFO who did not choose you as their systems consultant, and each migration is a six to twelve month project competing with the actual value creation plan.

By the time two companies have migrated, two more have been acquired on different systems. The programme never converges, and the reporting problem it was meant to solve persists throughout.

Mandating one ERP across a portfolio is a multi-year programme that gets overtaken by the next two add-ons. The reporting layer is a quarter.

The layer approach

Each company keeps its ledger. We read from it — QuickBooks, Xero, NetSuite, Intacct, Dynamics, Acumatica, or a mix — and normalise into a portfolio-level graph with a shared chart, shared dimensions, and definitions recorded rather than remembered.

The consolidation becomes continuous rather than monthly, and the portfolio view is current in week two rather than three weeks after period end. Adding a bolt-on means adding a connector, not running a migration.

Where a platform company genuinely does need a new system, that decision is then made on its own merits and at its own pace, against a dataset that has already been proven to reconcile.

Diligence and exit

The most valuable output is not the monthly pack. It is that at exit, three years of reconciled, dimensioned, drill-through-capable history already exists rather than being reassembled under time pressure.

Every figure in a data room traces to the transactions behind it. Quality of earnings work gets faster because the adjustments are computed and documented rather than reconstructed, and the definitional differences between companies are recorded rather than argued about with a buyer’s advisers.

We have seen enough diligence processes stall on a portfolio company’s inability to produce dimensioned history to think this is where the return actually sits.

What we would tell you not to do

  • Do not migrate a platform company within six months of a transaction. Acquirers prefer clean, boring history in a system they recognise. Mid-migration books are neither.
  • Do not standardise the chart before you standardise the definitions. A shared chart with nine interpretations of adjusted EBITDA produces consistent-looking numbers that mean different things.
  • Do not mandate our software portfolio-wide. Some of your companies will be manufacturers, and we tell manufacturers to buy Acumatica or NetSuite. A mandate that has to be broken immediately is worse than no mandate.

Commercial arrangement

Portfolio engagements are scoped at the fund level rather than company by company, which usually makes them cheaper per company and considerably faster to start. Referral terms are the same 10% as everywhere else, with the same disclosure condition.

Where an operating partner is compensated for the introduction, the platform company must be told. We will confirm it and will tell them directly if asked.

Start with one company

We would rather prove this on a single platform company than sell a portfolio programme. Pick the one with the worst reporting, connect it read-only, and see whether the consolidated view arrives in two to three weeks as we claim. If it does not, you have spent a fixed fee finding out. If it does, the second company is a considerably easier conversation.

Questions

Common follow-ups.

Do all portfolio companies have to move to erp.io?
No, and we would advise against mandating it. Each keeps its ledger; we read from it and normalise into a portfolio layer.
What if a company runs a system you do not support?
We scope it through a short paid discovery and tell you whether it is reachable before quoting. Some legacy on-premise systems are genuinely difficult and we say so.
How long until a portfolio view?
Two to three weeks for the first company. Additional companies are faster because the portfolio chart and definitions already exist.
Does this help at exit?
It is where most of the return sits. Three years of reconciled, dimensioned, drill-through history already exists rather than being reassembled under time pressure.
What about manufacturers in the portfolio?
We tell manufacturers to buy Acumatica or NetSuite. We can still read from those systems into the portfolio layer, which is the point of the layer approach.

Prove it on one company first.

Pick the platform company with the worst reporting. A fixed fee and three weeks tells you whether the approach holds.