---
title: "Private equity: one data and reporting layer across the portfolio | Rig"
description: "Rig gives PE-backed companies one data and reporting layer across the portfolio: map each estate, integrate add-ons and report comparable KPIs."
canonical: "https://rig.so/for/private-equity"
format: markdown
---

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.

[Request a case study](https://rig.so/book-demo)

Your systems, in viewShared data and definitions

**Salesforce**Customers & revenue

N

**NetSuite**Finance & orders

S

**Shopify**Commerce

❄

**Snowflake**Your warehouse

Systems Map

Context & definitions

ReportsWorkflowsAgents

Dependencies for one field

The reports, flows and teams that use it.

Impact mapped

Illustrative platform viewIngest → Rig Map → Migrate → Run

## Every 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.

## How two education software companies changed their systems with Rig

[Customer stories](https://rig.so/case-studies)

[An education software companyHow mapping Salesforce first made a cleanup safe to run40,000+custom Salesforce fields mapped22 daysto a full field mapRead the story](https://rig.so/case-studies/education-software-group)[A merged education software groupHow two companies’ data moved onto one reporting layer108 of 322Tableau workbooks still in use, found overnight12,411real customers, where the old count said 43,245Read the story](https://rig.so/case-studies/education-software-merger)

## Where to start

[M&A systems integration](https://rig.so/use-cases/ma-systems-integration)[Buy-and-build integration](https://rig.so/use-cases/buy-and-build)[Portfolio reporting](https://rig.so/use-cases/portfolio-reporting)[Story: one reporting layer for a merged group](https://rig.so/case-studies/education-software-merger)[Story: mapping Salesforce before a cleanup](https://rig.so/case-studies/education-software-group)[Rig Map](https://rig.so/products/rig-map)[Gateway](https://rig.so/products/gateway)[Post-merger IT integration checklist](https://rig.so/blog/post-merger-it-integration-checklist)

## 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.

SOC 2 Type 2EU and US hostingRole-based accessYour warehouse or ours

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.

[Request a case study](https://rig.so/book-demo)Use the platform with your team, or add our engineers.

---

- [This page as HTML](https://rig.so/for/private-equity)
- [Site map for language models](https://rig.so/llms.txt)
- [API and agent documentation](https://rig.so/developers)
