Arcvue
Portfolio management—for private equity firms holding GovCon companies
The holding that costs you is not the bad one. It is the one nobody saw coming.
And it is usually invisible for a reason that has nothing to do with the business. Arcvue makes four independently-run holdings report on one set of definitions, out of their own ERPs, without asking any of them to change how they keep their books—refreshed nightly, so the portfolio position is current every morning rather than forty-five days old.
Specimen Systems LLC · an example 120-person contractor · all figures synthetic
Four numbers that look like the same measurement, and are not.
This is the part that does not announce itself.
A portfolio report showing gross margin for four holdings invites exactly one action: comparison. That comparison only means something if the four numbers were computed the same way. They were not: four companies, four ERPs, and four finance teams who each drew the direct-cost line where their own system made it easy.
The failure is silent because the output looks correct. Four percentages in a column, all plausible, none of them wrong in their own books. What is wrong is the column, and nothing about it says so. Ranking holdings on a metric that means four different things is how a firm concludes the wrong portco needs attention.
The fix is not a template you send them. It is normalization at ingest—each holding connects to Arcvue through its own adapter, and account 5100 in one system is mapped, once, by a human, to what account 6200 means in another. After that the comparison is a comparison. Standardizing the report format achieves nothing if the numbers underneath were built differently.
| What arrives | Why it is not comparable | What Arcvue does instead |
|---|---|---|
| Four reporting packages | Different ERPs, so different account structures underneath | Each holding connects through its own adapter. No package is produced, sent or chased. |
| Four definitions of gross margin | Each CFO drew the direct-cost line where their ERP made it easy | One definition. Each holding's accounts are mapped to it once, by a person, at ingest. |
| Two of them in a new format | Recent CFO transitions; the format left with the person | Generated from the close event, so the format does not leave when the CFO does. |
| All of them 45 to 60 days old | Quarterly cadence, on a business that moves weekly | Refreshed nightly. All four carry the same as-of date, every morning. |
Synthetic. An invented portfolio. Nothing in the middle column is anybody's fault—four competent finance teams, four systems, four reasonable choices. The right-hand column is the only part that requires a different system.
Your visibility into a holding should not depend on who is currently in the CFO seat.
In practice it does. The reporting a portfolio company produces is shaped by the person producing it—their spreadsheet, their definitions, their sense of what the sponsor cares about. When they leave, the reporting degrades for a quarter or two while somebody rebuilds an understanding that was never written down.
That is a governance exposure disguised as a staffing event. The period immediately after a CFO transition is when a sponsor can see least, and it is not a coincidence that it is also when a holding is most likely to drift—a new CFO inherits assumptions they cannot yet test.
Reporting generated from the ledger survives the transition. Arcvue produces it from the close event rather than from a person, so it does not degrade while a seat is empty, and the incoming CFO arrives to a documented set of definitions instead of a spreadsheet they have to reverse-engineer. That continuity is what you are buying; the reports are a side effect.
The add-on you close next quarter should not take a quarter to see.
Every acquisition repeats the same reporting problem from zero: a new company, a new ERP, a new finance team, and a sponsor who cannot compare it to the rest of the portfolio until somebody rebuilds its numbers in the portfolio's terms. That work usually waits behind integration items that shout louder, so the newest holding—the one carrying the most thesis risk—is the one you can see least.
Connecting a holding does not change how it operates. Arcvue reads the ERP the company already runs—read-only, through the same adapters as every other holding—and its accounts are mapped once, by a person, into the portfolio's definitions: the same mapping Section I rests on. Its books live in their own database, physically separate from every other holding's.
The new holding lands in the frame the others already report in. Same definitions, same close cadence, same lender view when you choose to grant it. Day-one visibility is not a migration project—the company keeps its ERP, and the sponsor gets the same window into it that the rest of the portfolio already has.
Three more things a sponsor needs, and each has its own page rather than a paragraph here.
Add-on evaluation, exit preparation, and covenant position across the portfolio all matter to a sponsor, and Arcvue does all three—each followed properly on its own page rather than compressed into a paragraph here.
| What you need | Where it is followed properly | The finding there |
|---|---|---|
| Evaluate an add-on the afternoon the CIM arrives | Transactions & capital | The covenant is never the exposure; the cash is, and it bites when the target does well |
| Exit preparation that starts on day one | Sell-side preparation | One unexplained figure costs 1.28× more in doubt than in the number itself |
| Covenant position before the lender has it | Lender access | 101 to 116 days between the ledger knowing and the lender knowing |
Source this site's own pages. Synthetic sample. Every finding quoted is derived on the page that owns it.