Normalizing revenue across an IT services roll-up
A managed IT services platform planned to acquire independent providers and bring their offers onto one commercial system for small and midsized businesses. It had initial target financials, size-based deal scenarios and a pricing study that mixed user, device, server, hourly and spend-based fees.
Servers, hours and service-specific measures add further bases that must reconcile into one revenue view.
Recurring support can be bundled while security, cloud work and consulting follow their own commercial logic.
Existing customer agreements remain visible until renewal or a deliberate move to the platform price book.
Each target enters with its own closing date, operating profile and integration cash requirement.
WHY THIS WASN’T A TEMPLATE EXERCISE
The model had to respect
how the business actually moved.
The reconstructed architecture converts users, devices, servers and service activity into a common revenue bridge, then separates acquired operations, contract migration, cross-sell, integration cost and financing on a deal-cohort timeline.
One revenue dollar could have several denominators
Providers charged by customer, user, device, server, hour or infrastructure spending. Comparing targets only on reported recurring revenue would hide the activity and service mix underneath it.
Pricing observations were not customer contracts
The research described market ranges and packaging conventions. A useful model needed to preserve those as reference assumptions while keeping each target's actual customers and legacy prices separate.
Closing did not standardize the revenue base
Customers would continue on existing terms until renewal or migration. Moving every acquired account to the platform price book on the closing date would create revenue synergy before the business could earn it.
Service mix determined delivery capacity
Remote support, onsite work, managed security, cloud administration and professional projects consumed different skills and hours. Cross-sell could improve revenue while also exposing a staffing constraint.
MODEL ARCHITECTURE
From operating activity
to a decision-ready view.
Each layer has one job. Together they keep the commercial story, unit economics and cash consequences on the same timeline.
Target intake
A common template captures customers, users, devices, servers, services, contract terms, staffing and standalone financials for each acquisition candidate.
Billing-driver library
Per-user, per-device, server, hourly and spend-based services feed one recurring and project-revenue bridge without forcing them into one artificial unit.
Standalone target economics
Legacy revenue, direct labor, service delivery and overhead remain visible before any platform assumption changes the target.
Deal cohorts
Closing dates trigger purchase consideration, transaction costs, financing, integration spending and the addition of each target's operating results.
Contract migration
Renewal timing, retention and conversion rates move accounts from legacy terms to a standard price book over time.
Cross-sell
Service eligibility, attach rate and adoption lag determine when an acquired customer adds security, cloud or project work.
Delivery capacity
Support volumes and project hours translate into remote-help-desk, field-service and specialist staffing requirements.
Consolidation and cash
Acquired earnings, platform overhead, integration costs, expected savings and financing roll into a consolidated profit-and-loss and cash view.
WHAT THE ANALYSIS SURFACED
Useful answers,
without exposing client data.
The takeaways are intentionally qualitative. Exact assumptions, calculations and outputs remain inside the confidential client model.
Revenue per customer was a weak target comparison
Two providers could report similar account revenue while supporting very different numbers of people, endpoints and servers. Normalizing the billing drivers showed whether the difference came from price, service depth or customer complexity.
Migration timing controlled when pricing synergy appeared
A standard price book affected new sales immediately, but acquired contracts changed on their own renewal path. Cohorting that migration kept the forecast from recognizing improvement at the closing date.
Cross-sell created workload before all of its margin arrived
Adding specialist services raised account value, but it also required qualified staff and delivery time. Attach rates therefore belonged beside utilization and hiring rather than only in the revenue schedule.
The largest target could create the deepest cash trough
Purchase consideration, transaction cost and integration work arrive before the full benefit of contract migration or overhead savings. Comparing deal sizes on consolidated cash exposed that timing difference.
MODELING APPROACH
The working system
behind the answer.
- Target-intake template and acquisition-scenario controls
- Customer, user, device, server and service-driver schedules
- Legacy and platform pricing architecture
- Target revenue, delivery-cost and margin bridge
- Acquisition calendar, purchase consideration and financing schedules
- Contract-renewal, migration and retention cohorts
- Service eligibility and cross-sell adoption model
- Support, field-service and specialist capacity plan
- Integration costs, overhead savings, consolidated cash and comparison dashboard
CASE CONFIDENTIALITY
This anonymized case explains the managed-services roll-up, pricing and integration logic without naming the company, founders, executives, advisers, acquisition targets, research participants, sources, services, regions or dates. Exact pricing ranges, service packages, customer and equipment counts, target financials, deal scenarios, purchase prices, valuation terms, integration assumptions, staffing, forecasts and financing remain private because client work can be confidential or NDA-protected. The source slides, table, logos and company materials are not reproduced. The illustration is an original fictional service network rather than a real platform, provider, customer site, interface, acquisition or operating result.