Home Features Use Cases Pricing Docs Try the Demo
Use Case — PE Portfolio Management

See every holding clearly.
On your schedule, not theirs.

Portfolio monitoring that doesn't depend on whoever is currently in the CFO seat. Standardized financial intelligence across every GovCon holding—regardless of ERP. Covenant visibility before the lender asks. Add-on evaluation the same afternoon the CIM arrives.

The Problem

The nightmare isn't the bad portco. It's the one you didn't see coming.

Every private equity firm managing GovCon companies knows the experience. The quarterly package arrives in a format that's slightly different than last quarter because the controller turned over. The team spends two days reconciling it before the numbers are usable. By the time the analysis is done, the quarter is six weeks old. The covenant ratio that was drifting was visible in the data—but nobody saw it until the lender raised it on the next reporting call.

Nearly 50% of PE CFOs at portfolio companies cite data fragmentation as their top challenge. In GovCon, the problem compounds. The portcos run different ERPs. The revenue recognition rules differ by contract type. The indirect rate structures vary by company. EBITDA means something slightly different at each portco until someone forces standardization—which usually means a consultant, a new template, and six months of retraining that drifts again when someone leaves.

The add-on that came across the desk on a Tuesday required two weeks of model-building before you could react. By then the seller had another conversation. The exit prep that should have started eighteen months ago started six months ago because the data room didn't exist in any usable form. The firms that compound value across GovCon holdings do it with better information, faster. Not because they have better judgment—because they can see what's happening before everyone else can.

Outcome 1

Consistent data across every holding—regardless of ERP or who is in the CFO seat.

"We have four portfolio companies. Three different ERPs. Two recent CFO transitions. Every quarter we receive four different reporting packages, spend a week standardizing them, and by the time we can compare companies side by side the data is two months old."

Arcvue connects directly to each portfolio company's ERP—whatever platform they run—and pulls financial data nightly through its own adapter. The standardization happens inside the platform, not in a template someone fills out. Each company's chart of accounts normalizes to a common schema on onboarding. From that point forward, every company produces the same output: same P&L structure, same indirect rate presentation, same covenant metrics, same waterfall format.

When a CFO leaves and a new one joins, nothing changes on your end. The ERP still syncs. The format is still consistent. The data still arrives nightly. You stop teaching portcos how to report and start receiving structured data automatically. The hours your team spent every quarter reconciling inconsistencies shift to analyzing what the numbers mean—which is the work that actually drives value.

Side-by-side comparison across the portfolio becomes possible in real time. Revenue trajectory, gross margin by division, indirect rate movement, covenant headroom, and pipeline coverage across all holdings on the same dashboard—updated from ERP actuals every morning. The company that's outperforming and the one that's drifting are both visible before the quarterly reporting cycle forces the conversation.

Arcvue — Portfolio Dashboard · Today
CompanyERPTTM RevEBITDA%vs Budget
Platform Co.UNANET$35.4M16.1%+1.2%
Add-On ACostpoint$18.2M14.8%−0.4%
Add-On BQBO$8.4M11.2%−3.1%
Add-On B EBITDA% tracking 3.1 pts below budget. G&A pool expanded in Q1 without corresponding revenue growth. Review flagged.
Outcome 2

Know your covenant position across the portfolio before the lender does.

"Our lender called to discuss covenant compliance before we'd seen the Q3 numbers in any usable form. We spent the next four days in emergency mode pulling together data we should have been watching all quarter."

Covenant compliance in Arcvue is computed nightly from actual ERP data across every portfolio company. DSCR and leverage are always current—not estimated from last quarter's model, not built from a management report that takes two weeks to arrive. The EBITDA figure includes your bank-approved add-backs: owner compensation adjustments, one-time transaction costs, D&A, and any other items the credit agreement specifies. When a ratio is drifting, you see it in the morning before the trend becomes a problem.

Three scenarios run simultaneously for each company—base, upside, and downside—tested against actual covenant thresholds. The downside scenario models specific contract losses or revenue haircuts against the actual debt structure so you know covenant headroom under the credit case before anyone asks. When the lender calls, the answer is ready. When the LP asks about portfolio risk, the covenant dashboard tells the story with numbers, not with reassurances.

In-application alerts notify the operating partner when a specific ratio approaches a threshold—configurable by company and by covenant. The alert doesn't arrive when the ratio breaches. It arrives when the trend is three months away from a breach, while there's still time to act. The difference between those two conversations—with management, with the lender, and with your LPs—is significant.

Arcvue — Portfolio Covenant Dashboard
CompanyDSCRMinLeverageStatus
Platform Co.1.48x1.20x3.21x● Compliant
Add-On A1.38x1.15x4.82x⚠ Monitor
Add-On B1.21x1.20x5.04x⚠ Alert
ADD-ON B — COVENANT ALERT
DSCR 1.21x approaching 1.20x minimum. At current EBITDA trajectory, breach projected in 6-8 weeks. Management call flagged.
Outcome 3

Evaluate the add-on the same afternoon the CIM arrives.

"A target came across our desk on a Monday. We knew we were interested. Two weeks later we had a model. By then the seller had received two other term sheets and we were behind in the process before we'd started."

Arcvue has the platform company's actual financials—last night's P&L, this morning's indirect rates, the current debt schedule and covenant thresholds. Enter the target's revenue, EBITDA, and purchase price. Select a structure. The combined entity's three-statement projections, sources and uses, earnout sensitivity, and covenant compliance under the combined debt load are computed the same afternoon—against your real operating baseline, not a model built from scratch.

The question of whether to do the deal and how to structure it—which used to take two weeks of analyst time—becomes a same-day conversation. The questions that drive the structure: Does the combined leverage breach a covenant in year one? What does the earnout obligation do to cash in year two? Does the deal require additional equity or can it be financed within the existing credit facility? These are answered before anyone has spent a week building a model that may not reflect your actual situation.

Post-close, both ERPs connect to Arcvue independently from day one. The combined view—intercompany eliminations applied, indirect rates computed for both entities, covenant metrics across the combined capital structure—is available the morning after close. The ERP integration project you planned can proceed on its own timeline, independent of your ability to see the combined entity clearly.

Arcvue — Add-On · Day 1 Analysis
Combined Revenue
$53.6M
Platform + add-on
Combined EBITDA
$8.9M
Pre-synergies
MetricYr 1Yr 2Yr 3
DSCR1.31x1.44x1.58x
Leverage4.82x4.21x3.64x
Free Cash$1.1M$1.8M$2.4M
Deal is financeable. Leverage normalizes below 4.0x by Yr 3. Structure earnout with Yr 2 cash impact in mind.
Outcome 4

Exit preparation that starts on day one of the hold.

"We wanted to run a process in Q3. Our banker told us we needed six months of prep before the data room was presentable. We ran the process in Q1 of the following year instead, missing the market window we'd been tracking."

The data room for a GovCon sale process asks for a specific, predictable set of documents: revenue waterfall, contract-level forecasts, pipeline coverage ratios, EBITDA bridge with documented add-backs, indirect rate history, past performance records organized by agency and work type, AR aging, debt schedule and covenant compliance, and three years of audited or reviewed financials. Every one of those documents is produced by Arcvue as a byproduct of running the business. The data room doesn't get built when the process begins. It's maintained continuously and opened when the process requires it.

When the market window you've been tracking arrives on a Tuesday, you can call the banker on Wednesday and have a preliminary process package ready by Friday. Not a sprint to catch up—a pull from a platform that's been accumulating the right information in the right format throughout the hold. That's what "exit-ready from day one" actually means in practice.

The firms that get to LOI fastest and trade with the least re-trade risk are the ones whose buyers spend diligence confirming what they were told, not discovering what they weren't. Arcvue ensures the data behind the narrative is always current, always traceable, and always organized the way buyers expect to receive it. The multiple you get reflects how well the business is understood—and how much confidence the data inspires in the people writing the check.

Arcvue — Exit Readiness · Platform Co.
READY
Revenue waterfall (auto-updated)
READY
EBITDA bridge (24 mo tracked)
READY
Pipeline coverage (unweighted)
READY
Indirect rate history (3 yrs)
READY
Past performance (28 contracts)
READY
Lender model (1-click export)
Process-ready today. Not after six months of prep.

See every holding clearly—before the problem surfaces.

Connect your portfolio companies and walk through a live demo. Standardized data across every ERP, available every morning.

Try the Demo