A two-lever playbook for PE operating partners. Turn portco backoffices into compounding assets that lift exit multiples, not just EBITDA.
Most PE portfolios are paying vendor margins on operations they should own. Same backoffice cost line in every portco, same vendor invoice structure, same compounding leak. The playbook below is the dual-lever recipe for fixing it. AI-native org chart on top. Offshore team inside the portco entity underneath. Together they turn each portco’s backoffice into an asset that lifts the exit multiple, not just the EBITDA line.
The pattern across the portfolio
Walk through ten portcos in a healthcare services or specialty distribution fund. Look at the income statement. The backoffice line is roughly the same percentage of revenue in every portco. The vendor names are different. The structures are identical: third-party processing, per-transaction or per-FTE pricing, multi-year contract, modest annual margin compression that the portco celebrates as cost savings.
Now look at where the AI conversation is happening in each portco. It is happening with the same vendor. The vendor is offering an "AI roadmap." The roadmap runs on the vendor’s infrastructure, trained on the combined data of all of their clients. The portco is funding the education of a system the portco does not own. Three years in, the operational intelligence the portco’s team produces every day (claims patterns, exception logic, customer-specific workflows) accrues to the vendor’s platform.
This is the leak. It is the same leak in every portco. And it is invisible on the income statement until exit, when the buyer’s diligence team asks who owns the AI layer and the answer is "the vendor." That answer compresses the multiple. Sometimes it kills the deal. The playbook is about closing the leak, portco by portco, on a timeline that lines up with the hold period.
Lever 1: the AI-native org chart redesign
Lever 1 is the work of redesigning each portco’s operating org chart AI-first. Not retrofitting AI into an existing structure. Redesigning the structure so that Virtual Employees handle the routine work and a smaller, more senior human team handles the calls that require judgment, context, and accountability.
A typical 30-person back-office function becomes 6 humans + 14 Virtual Employees doing the same throughput. The humans are not survivors of a layoff. They are a deliberate selection: one director, one manager, four senior individual contributors. The Virtual Employees handle first-pass classification, reconciliation, exception triage, and the routine documentation work. Each Virtual Employee has persistent memory across the workflow, defined governance with human approval at the decision points, and audit logs that survive the engagement.
This is the lever that drives revenue-multiple expansion at exit. The story the buyer’s banker tells changes from "this portco saves money on labor" to "this portco runs a tech-enabled operating model with proprietary intelligence that compounds." That is the difference between an EBITDA multiple and a revenue multiple. In a services rollup, that is the difference between 7x and 10x.
Lever 2: the COPO entity inside each portco
Lever 1 alone is not enough. If the AI runs inside a vendor-managed operation, the residue still leaks. The Virtual Employees produce intelligence that lands in the vendor’s data pipeline. The exit-multiple story does not survive diligence.
Lever 2 is the offshore team inside the portco’s own entity. COPO means Company-Owned, Partner-Operated. The portco owns the legal entity, the employees, the data, and the governance. Reliable Group operates the day-to-day: hiring, training, facilities, payroll, compliance, retention, the India labor law paperwork, the technical infrastructure that runs the Virtual Employees.
The team inside the COPO entity is smaller than what the legacy vendor structure required, because the Virtual Employees are doing the routine work. The team is also more senior. The senior India hires are exception-handlers and judgment-layer operators who know the portco’s domain better than anyone outside the original US team did. Eighteen months in, those operators are an institutional asset.
Sequencing across the portfolio
Do not start with the largest portco. Start with the one that has the fewest active failure modes: stable management, clean data, clear scope on the function being moved. The first portco is the proof point that funds the conversation in the next nine.
The Prove-Expand-Compound sequence runs the first portco through three phases. Prove (30 to 60 days, Flexi engagement model, one workflow scoped tight). Expand (months three through twelve, COPO entity stood up, Virtual Employees scaled in alongside the team). Compound (year two and beyond, the institutional residue starts to show up as a quality ratchet the buyer’s banker can defend).
Once the first portco is in the Compound phase, the playbook scales. The second and third portcos run six to nine months behind the first. By portco five, the operating partner has a portfolio template that can be applied to a new acquisition during the integration sprint. The right pace is one new portco entering the Prove phase per quarter.
Exit economics
The exit is where the playbook earns its keep. Two portcos in the same sector, comparable EBITDA, sell for very different multiples. The difference is what the buyer believes about year three, year four, year five. The buyer is not paying for the operation today. The buyer is paying for the operation the buyer believes the portco can run forward.
A Lever 2-only portco (offshore team, no AI-native redesign) sells on EBITDA. The story is cost arbitrage. The multiple is the sector comp. A Lever 1 + Lever 2 portco (AI-native org chart, Virtual Employees in production, owned COPO entity) sells on revenue with a tech-enabled-services narrative. The buyer’s banker can defend a higher multiple because the operating model is the asset. The institutional residue is on the portco’s books, not a vendor’s. The Virtual Employees are line items the buyer can take operational ownership of on day one. The exit price reflects that.
The math is sector-specific, but the direction is consistent. We have seen revenue-multiple lift in the range of 30 to 60 percent over an EBITDA-multiple-only comp in services rollups where the Lever 1 + Lever 2 story was credible at diligence.
The Blueprint as the entry product
The playbook starts with a Blueprint. Three to five weeks. Paid engagement. We come into the first portco, scope the current operation, redesign it AI-first, model the unit economics of the redesigned org, and deliver a phased rollout plan. The deliverables: the AI-native org chart with the Virtual Employee roster and unit-of-work pricing, the offshore team plan with role-by-role hiring scope, the entity structure recommendation, the joint unit economics, and the 12-month implementation plan.
The Blueprint is the artifact the operating partner takes to the portco CEO. It is also the artifact the operating partner takes back to the firm: a documented playbook that can be applied to the next portco without rebuilding it from scratch.
Start with one portco. The deliverables apply to the next nine.