Private equity
The operating partners would like one set of numbers
Operating partners and portfolio CFOs need the same numbers from every company, and the systems inherited with each deal rarely agree. Rig maps each company’s systems, builds one governed reporting layer, and does the integration work after each acquisition.
Systems Map
Context & definitionsThe reports, flows and teams that use it.
Impact mappedEvery deal adds another way of counting revenue
Each company in the portfolio runs its own CRM, finance system and reports, and each deal adds another set. The monthly pack is assembled by hand, revenue is counted three ways, and the value creation plan is tracked in a spreadsheet nobody can trace back to a system.
Where Rig fits across the holding period
Two companies after close
One reporting layer
Both estates sync into one warehouse and the board pack reads from there, while every system underneath is still separate.
Add-on after add-on
A map that grows
Each add-on is mapped and joins the group’s definitions, so the next one starts from the existing map.
Packs built by hand
Comparable KPIs
ARR, margin and churn are defined once and calculated from each company’s own systems.
System choices made on opinion
Migrations from the map
The map shows what each system does and what depends on it, and each migration is scoped and priced from it.
AI tools asking for data
Governed access
Gateway gives each person and each agent its own role and row limits, and logs every call.
Where to start
Common questions
How should a private equity firm get one reporting layer across the portfolio?
Sync each company’s CRM, ERP and finance systems into a governed warehouse layer, define the KPIs once, and map each company to those definitions. The portfolio reporting page covers the detail.
Do you work on post-merger integration?
Yes. The M&A systems integration page covers combined reporting after a deal and each system migration that follows.
What about add-ons in a buy-and-build?
Each add-on is mapped and synced into the group layer, so it reports to the group definitions before any of its systems change.
Can portfolio companies keep their own systems?
Yes. Rig syncs the systems each company already runs, and a system is migrated only where the group decides the move is worth it.
Do you have case studies?
Yes. Two anonymised stories from education software companies cover a merged group’s reporting layer and a Salesforce dependency map made before a cleanup.
Talk to Rig
What work do you want to improve?
Tell us where your team spends time, loses money or needs better information.
In a 30-minute call, we’ll discuss the data and systems work that could help.