By role

For the person who has to make eight companies comparable

The operating partner problem is not information scarcity — every company reports something. It is that eight companies report differently, on different days, on definitions nobody agreed, so the portfolio view is assembled by an analyst and every board pack is a reconciliation exercise.

Their QuickBooksas filed
1000 · Cash412,880.14
1200 · Accounts receivable286,401.00
2010 · Accounts payable(94,220.55)
4000 · Revenue(1,842,110.00)
6000 · Operating expense1,237,049.41
Trial balance0.00
erp.io shadow ledgercomputed
1000 · Cash412,880.14
1200 · Accounts receivable286,401.00
2010 · Accounts payable(94,220.55)
4000 · Revenue(1,842,110.00)
6000 · Operating expense1,237,049.41
Trial balance0.00

184 consecutive days tied · variance $0.00

No platform mandateSame definitions, same dayFaster diligence at both ends

The situation

Six things that make portfolio oversight expensive.

Definitions nobody agreed

One company puts hosting in cost of revenue, another in opex. Both defensible, and the portfolio gross-margin comparison is meaningless until somebody normalises by hand.

Reporting on different days

Companies can close differently. They cannot report on different days without the portfolio view always waiting for the slowest.

Finance capability varies wildly

A $40M company with a strong controller and a $12M one with a bookkeeper cannot be held to one standard without doing something about the second.

The analyst is the system

Portfolio reporting maintained in a workbook by one person, which is a key-person risk sitting on top of the numbers the LPs see.

Platform mandates stall

Two years of implementations, distracted management teams, and at least one failure that becomes the reason the programme stops.

Every exit rebuilds the work

Normalisation done for diligence is thrown away rather than captured, so the next transaction starts from scratch.

Standardise above the ledgers

The instinct is a platform mandate. It is coherent, and in a mid-market portfolio it reliably takes two years, distracts management teams who have growth targets, and produces at least one failed implementation that becomes the reason the rest stalls.

The alternative is a layer above whatever each company runs. Each keeps its ledger; a shared model reads all of them into one set of definitions, with the mapping captured per company once and maintained rather than rebuilt quarterly.

You need comparable numbers, not identical systems. Conflating those is how a reporting problem becomes a two-year implementation programme.

What you get, and roughly when

  • Weeks 1–3. The portfolio chart and the metric definitions agreed with you and two or three controllers. This is the part that determines everything and it is a decision exercise.
  • Weeks 3–8. The first three companies connected, mapped, and reporting. Start with the best-run so the pattern exists before the hard ones.
  • Months 2–5. The rest, at one to two weeks per company. The weaker finance functions take longer and surface real issues, which is useful rather than inconvenient.
  • Ongoing. Add-ons mapped during their first close rather than after their first annual cycle.

Where the return actually is

Two places. Underperformance surfaces earlier — when every company reports on the same definitions on the same day, a margin drift at company four is visible in month two rather than at the annual review.

And diligence, at both ends. An add-on arrives with its own chart and normalising it is a mapping exercise. At exit, consolidated statements that trace to source transactions turn a quality-of-earnings exercise from weeks of reconstruction into a data-room link, and reviewers price uncertainty rather than arguing about it.

The companies that should move ledgers

Some will, and the reporting layer makes that visible rather than hiding it. A company on QuickBooks Desktop with four entities and a fifteen-day close is a genuine constraint. But it becomes a targeted decision about one company with a clear business case, rather than a mandate applied to seven companies that did not need it.

We do implementation and rescue work as a service, on their existing systems as well as ours, which means the recommendation is not automatically our platform.

Questions

What people ask.

Do all companies have to use your platform?
No, and we would advise against mandating it. Each keeps its ledger and the reporting layer sits above. Individual companies may move later on their own business case.
How long until we get a comparable view?
First three companies in about eight weeks including the definitional work. Each additional company is one to two weeks of mapping.
How is it priced across a portfolio?
Per company with portfolio-level agreements where a firm runs it broadly. The cross-company operating-partner view is included rather than sold separately.
What about companies we are about to exit?
Those are frequently the best place to start, because the return is concentrated in diligence. Traceable consolidated statements shorten a quality-of-earnings exercise substantially.
Can you fix the weak finance functions?
Yes, as implementation or rescue engagements on whatever they run. The reporting layer identifies which companies need it, which is usually a shorter list than expected.

Make the portfolio comparable in a quarter.

Tell us how many companies and what they run, and we will scope what standardising actually takes.