Services Rollup Repositioned From EBITDA-Multiple to Revenue-Multiple Narrative Inside the Buyer’s Diligence Window

The CEO was preparing for a majority recap with an active buyer process underway. The financial picture was solid. The narrative was not. The buyer’s diligence team had been clear that a tech-enabled-services story underwrites differently than a services-margin story, often at a meaningfully different multiple range. The CEO did not have time to build a software product. The CEO did have time to redesign the operating company so that the services it delivered were demonstrably AI-native, with the institutional knowledge accruing inside the entity the buyer was about to acquire.

The Blueprint was sequenced backwards from the buyer’s diligence questions. Both levers had to be defensible at the unit-economics level, the governance level, and the architecture level by the time diligence opened.

The legacy administrative team was redesigned function by function. Routine document processing, customer service triage, compliance reporting, vendor reconciliation, and AR follow-up were moved to Virtual Employees with persistent memory across the operating cycle. The exception escalations sat with a leaner human team. The redesigned org chart became part of the buyer-facing materials.

The leaner human team was hired inside the company’s own COPO entity (no vendor intermediary, no per-seat billing relationship to disentangle at close). Recruiting, facilities, payroll, and compliance ran underneath. The entity, the employees, the data, and the AI workflows all consolidated on the company’s balance sheet.

Buyer’s preliminary multiple range moved from EBITDA-multiple to revenue-multiple framing in the second round of diligence after the AI-native org chart was presented and verified. Routine administrative cost reduced an estimated 40 to 50 percent against pre-Blueprint baseline. The cost story remained the underneath. The narrative on top was capability. Token-cost run-rate stabilized inside the unit-economics model RG had built inside its own operations. No surprise at month four. The transaction proceeded inside the buyer’s stated window. Specific multiple, transaction value, and post-close operating arrangement are confidential.

The buyer underwrote a tech-enabled services business with proprietary operating capability inside the entity. Every workflow improvement from the day after close compounds inside the new ownership structure. The company avoided the alternative path: closing on a services multiple, then trying to build the AI capability inside someone else’s portfolio thesis. The buyer repriced the asset from a services-firm multiple to a platform multiple. The shift is what the AI-native operating model produced: demonstrable operating leverage on a question the buyer used to ask without a real answer.

The CEO’s decision was about which story the buyer would defend at investment committee. A services story is a services multiple. A tech-enabled story with institutional AI capability inside the entity is a different story. From a services firm that scales through hiring to a platform that scales through systems. Both levers had to be running, both had to be defensible, and they had to have been running long enough by close to be more than a slide.