Standardising revenue policies for a buy-and-build exit

A professional services group built through a buy-and-build strategy, spanning services from tax to HR, went into its own sale process carrying the policy debris of every deal that had built it. By the time QuantSpark had finished, the number of revenue policies had fallen to an average of four per business unit, running on just two billing and revenue-recognition methods, and two years of historical revenue from disparate entities had been re-mapped into a single, comparable group-level view. That mattered because it landed at exactly the moment it counts most for a business built for eventual sale: due diligence ahead of exit.

The problem

Buy-and-build strategies create value by acquiring and combining businesses, but they rarely rationalise the back office at the same pace as the front office grows. Here, successive acquisitions had left disconnected entities running on disparate systems, each with its own conventions for recognising revenue, tracking work-in-progress and structuring client fees. Individually, none of this was a crisis; each entity could report its own numbers well enough to run its own business.

Collectively, it was a due-diligence problem. A buyer evaluating a group built from many acquisitions needs a single, comparable view of historical performance, not a set of entity-level numbers reconciled by exception. Robust group-level revenue reporting is essential to a successful sale, and disparate recognition and billing conventions across entities threatened to undermine confidence in the numbers at the one point in the deal cycle when that confidence is scrutinised hardest.

The approach

QuantSpark's response was to standardise policy across the three areas doing the most damage to comparability: revenue recognition, work-in-progress management and fee structure.

• Diagnose the fragmentation. Review revenue recognition, WIP treatment and billing practice entity by entity, to understand how far apart the group's business units actually were.
• Standardise revenue recognition. Align recognition to a "good production" basis, reflecting billable work completed each month, so revenue means the same thing wherever it is reported from.
• Build a consistent WIP framework. Give work-in-progress a shared approach to tracking, review and provisioning, replacing entity-specific judgement calls with a common method.
• Consolidate fee structures. Group each business unit's billing methods down to a small, standard set, rather than the wider range that accumulates as acquired entities keep their own habits.
• Restate the history. Map two years of historical revenue from the disparate entities into the new common framework, so the group's past performance is expressed on the same basis as its future-state design, not just its future numbers.

How it worked

The workflow ran from diagnosis through to exit-readiness: diagnose the entity-by-entity fragmentation, design the standardised policy set, restate two years of historical revenue onto that common framework, roll the policies out across business units, and arrive at a group that could show buyers one consistent set of numbers rather than several reconciled ones.

Systems and information

The engagement worked across the group's existing financial reporting systems, which had been left disconnected by the acquisition process, and layered a common revenue-recognition and WIP framework on top of them. Billing and invoicing practice, previously varied unit to unit, was consolidated onto the same standardised approach. No specific software platform is named in the public record; the work was policy and framework design applied across whatever systems each acquired entity already ran.

The value

The headline change is structural: from a fragmented, entity-by-entity patchwork down to an average of four revenue policies and two billing and revenue-recognition methods per business unit. That is a straightforward before-and-after on policy count and method count, not a derived financial figure, and it is the only quantified outcome in the public record.

The value it protects is due-diligence credibility and deal risk, not a specific pound saving. A restated, comparable two-year revenue history and a handful of consistent methods per unit removes the reconciliation questions that slow buyers down and erode confidence in a vendor's numbers. Alongside the due-diligence benefit, the unified framework also improved cash-flow management, financial transparency and operational efficiency ahead of exit.

The public record does not disclose a valuation uplift, so the honest framing is risk reduction and deal-readiness delivered through simplification, rather than a quantified return.