---
title: "Buy-and-build systems and data integration | Rig"
description: "Buy-and-build systems and data integration for PE-backed platforms: map each add-on with Rig Map, report as one group and migrate systems in a safe order."
canonical: "https://rig.so/use-cases/buy-and-build"
format: markdown
---

[M&A systems integration](https://rig.so/use-cases/ma-systems-integration) / Buy-and-build integration

# Buy another company, inherit another reporting mess

A buy-and-build strategy grows a platform company by acquiring smaller add-ons, and each add-on arrives with its own CRM, finance system and reports. Rig maps each new estate, adds it to the group’s reporting layer, and keeps the map so the next add-on starts from what is already there.

[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 add-on arrives with its own CRM, ledger and board pack

A platform company that buys three add-ons can end up with four CRMs, four finance systems and four ways of counting revenue. If each integration is planned from scratch, group reporting waits for the systems work, and the operating partners wait with it.

## What changes with each add-on

- A new estate per deal
  
  ### One map that grows
  
  The add-on’s systems, flows and users join the group’s systems map, so the integration plan starts from what is known.
- Another set of KPIs
  
  ### Group definitions
  
  The add-on’s revenue, margin and pipeline are mapped to the group’s certified metrics, with differences marked for finance.
- Consolidation in spreadsheets
  
  ### Group reporting from the warehouse
  
  The add-on reports to the group from its first sync, before any of its systems change.
- Integration decided deal by deal
  
  ### A migration order
  
  The map shows which systems to move first and what each move would break.
- Access sorted out later
  
  ### Roles from the first sync
  
  Role and row-level access applies to people and agents from day one.

## How the work runs

1. ### Map the add-on
   
   We map what the add-on runs, what flows between its systems and who uses what, in a fixed-price discovery sprint that starts read-only.
2. ### Sync into the group warehouse
   
   The add-on’s systems sync into the group’s warehouse on a schedule, with no change to its production systems.
3. ### Apply the group definitions
   
   Revenue, margin and pipeline use the group’s certified definitions, and any difference in how the add-on counted is marked for finance to decide.
4. ### Migrate in a safe order
   
   Each system move is scoped and priced from the map, and nothing is switched off until its numbers match the original.

Customer story / An education software group

108 of 322

Tableau workbooks still in use, found overnight

12,411

real customers, where the old count said 43,245

After two education software companies merged, the group is bringing both companies’ warehouses, pipelines, BI and CRM data onto one governed data and reporting layer in Snowflake. It is rebuilding only what people use, and retiring tools as it goes.

[Read the story](https://rig.so/case-studies/education-software-merger)

## Private equity, products and proof

[M&A systems integration](https://rig.so/use-cases/ma-systems-integration)[Private equity](https://rig.so/for/private-equity)[Portfolio reporting](https://rig.so/use-cases/portfolio-reporting)[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

What is a buy-and-build strategy?

It is a private equity approach where a platform company grows by acquiring smaller add-on companies. Each add-on brings its own systems, which is where the integration work comes from.

How soon does an add-on appear in group reporting?

It appears once its systems sync into the group warehouse and its metrics are mapped to the group definitions. That usually comes well before any system migration, because nothing in the add-on has to change first.

Does each add-on need a new project?

Each add-on gets its own map and scope, and the work starts from the group map, definitions and models already on Rig.

Who can see the add-on’s data?

Role and row-level access applies from the first sync, to people and agents alike, so the add-on’s team, group finance and the operating partners each see what their role allows.

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/use-cases/buy-and-build)
- [Site map for language models](https://rig.so/llms.txt)
- [API and agent documentation](https://rig.so/developers)
