“We rolled up 25–30 companies and the data lives in as many systems”

Roll-up data challenges are multiplicative, not additive

Each add-on arrives with its own ERP, its own CRM, its own accounting software, and its own way of defining "customer," "job," and "revenue." Company A tracks revenue at the contract level, Company B at the invoice level, Company C in a custom database one employee understands. The platform then can't answer the exact questions the board asks every meeting — how many customers do we have, what's blended gross margin by service line, which locations underperform — and for the first 12 to 18 months the answers get stitched together by hand in spreadsheets: slow, error-prone, and impossible to audit.

This is the "N-systems" problem, and it scales nonlinearly. Overlapping customers across add-ons, inconsistent data quality from a $5M tuck-in versus a $50M company, and master-data conflicts compound with every acquisition. On a finite hold period, every week without consolidated reporting is lost value-creation visibility.

A warehouse as an abstraction layer, not a system rip-out

The fix is not to force everyone onto one ERP immediately. It's a centralized warehouse that ingests each company's existing systems and maps them to a shared schema — organized in bronze (raw), silver (cleaned and conformed), and gold (business-ready) layers. The warehouse absorbs the complexity of N source systems and emits one consistent view of the platform.

Architected correctly, it also de-risks future migrations: because history already lives in the warehouse, swapping a portfolio company from QuickBooks to NetSuite changes only a connector — the dashboards never skip a beat. Designed as a repeatable onboarding machine, the goal is to compress onboarding with every successive deal — what takes months for the first add-on should take weeks by the fifth.