A roll-up buys its third company and discovers it now runs three accounting files, three CRMs, two field or practice systems and a shared drive of spreadsheets that one analyst stitches together every month. The thesis depended on running the companies as one. The software says otherwise.
This guide is for the CFO, operating partner or integration lead who has to fix that: what tends to break after each add-on, the three ways to integrate, which off-the-shelf products cover which layer, where custom software is worth it, and who to hire. Vendor facts come from each vendor's own site, checked October 28, 2026.
Our pick for the custom layer is Digital Mundo, a senior design and engineering studio that starts in one company, proves a tool there, and carries the playbook to the next add-on.
Here's the TLDR:
- Standardize finance first. One ERP with multi-entity consolidation (NetSuite OneWorld, Sage Intacct) gets you one close. It doesn't merge operations.
- Don't force every add-on onto one operating system on day one. Decide per system: migrate, connect or report on top.
- Agree KPI definitions before you build dashboards. "Revenue", "a job" and "an active customer" usually mean something different in each company.
- Build custom only for the layer the vendors leave open: the add-on onboarding playbook, cross-company reporting with your definitions, and the manual work between systems.
- Who to hire: Digital Mundo (our pick) for custom tools and AI across the portfolio; West Monroe for merger integration programs; Accordion for CFO-office systems and consolidations; your ERP's implementation partner for the ERP itself.
What breaks after an add-on acquisition
The same failure points come up in almost every roll-up, regardless of industry:
- Two of everything. The acquired company keeps its accounting, CRM and operating software because switching is risky in the first 100 days. By the fourth add-on nobody can say how many systems the platform pays for.
- The month-end close slows down. Each entity closes in its own system, then someone maps every chart of accounts into a consolidation spreadsheet. Intercompany charges get matched by hand.
- Customer and vendor records duplicate. The same customer, supplier or referral source exists under different IDs in each company, so cross-selling and purchasing power are hard to measure.
- KPIs don't compare. One company books revenue at invoice, another at job completion. One counts a callback as a new job. The board deck averages numbers that were never defined the same way.
- Reporting runs on one person. The portfolio dashboard is an Excel file an analyst rebuilds every month from exports. When that person is out, the report is late.
- Permissions are an afterthought. Shared drives and shared logins get passed around, and nobody can show diligence who saw what.
- Data gets lost at cancellation. An old system is switched off before its history, attachments and notes were exported and checked.
Three ways to integrate each system
For every system an add-on brings, you have three options. Most platforms use all three, system by system.
| Approach | What it means | Fits when | Watch out for |
|---|---|---|---|
| --- | --- | --- | --- |
| Migrate | Move the add-on onto the platform's system and switch the old one off | The platform system already fits the add-on's work, and the contract renewal is near | Data mapping, retraining, and a dip in productivity during the switch |
| Connect | Keep both systems and sync the records that matter between them | The add-on's system works well locally, or switching would disrupt customers | Sync rules, duplicate records, and who owns each field |
| Report on top | Leave systems in place and pull their data into one warehouse and dashboard | Early in the hold period, or when systems will change again after the next deal | It shows the numbers but doesn't remove any manual work |
A practical sequence: report on top in the first 90 days so the board sees comparable numbers, migrate finance onto one ERP, then decide per operating system whether to migrate or connect. Our guide to custom software for portfolio companies covers the value creation side of that plan.
The off-the-shelf layer
Buy these where they fit. Each covers one layer, and none of them merges how the companies actually work.
- Oracle NetSuite OneWorld. Oracle's OneWorld documentation describes one account managing "multiple subsidiaries" with their own currencies and tax jurisdictions, consolidated reports "in the currency of a parent subsidiary", and intercompany journal entries with eliminations. Pricing is by quote.
- Sage Intacct. Multi-entity and consolidation modules with inter-entity due-to and due-from setup and automatic eliminations, per its multi-entity page. Pricing isn't published.
- Microsoft Power BI. The usual reporting layer. Pro is $14 per user per month and Premium Per User is $24, both paid yearly, on its pricing page. It shows data; it doesn't clean or define it.
- Fivetran. Copies data from source systems into a warehouse, priced by monthly active rows, with a free tier of 500,000 rows and "700+ managed connectors" on Standard, per its pricing page. It only helps where a connector exists, and older on-premise systems often have none.
- Workato. An integration platform for syncing records between systems. Its pricing page lists editions but no prices. It moves data well; deciding which system is the record for a customer is still your job.
Where custom software earns its place
The gap sits between the ERP and each company's operating software. That's where custom software beats another subscription:
- An add-on onboarding tool. A repeatable way to map the acquired company's chart of accounts, customers, price lists and staff into the platform, with checks that counts match before anything is switched off. Built once, it gets cheaper with every deal.
- Cross-company reporting with your definitions. A KPI hub that applies one definition of revenue, jobs, utilization or same-store growth to every entity, with the formula shown so the board trusts it.
- The manual work between systems. AI that reads invoices, statements and reports arriving from many entities and puts them in front of a person to approve, instead of a shared-services team retyping them.
- Tools the vertical software doesn't have. A quoting tool, a customer portal or an approval flow that works the same way across every company, on top of whichever operating system each one runs.
Don't build what the ERP or BI tool already does well. Build where your operating model is the edge, or where people spend their day copying between systems. Our guide to software development for private equity firms covers the firm-level tools, and the app development cost guide has the price ranges.
How to scope a first project
- Pick one costly manual process in one company. The consolidation spreadsheet, invoice entry across entities, or the monthly KPI pack. Count the hours and the error rate before you start.
- Write down the definitions. Agree what each KPI means with the CFOs of each company before anyone draws a chart.
- Ship a first version in weeks, not quarters. One workflow, used by real people, measured against the before number.
- Design it for the next add-on. The real test is whether company four goes faster than company three.
- Put ownership in the right name. Code, hosting and accounts belong to the portfolio company, which keeps a later sale and its diligence simple.
Questions to ask a vendor
- Who will build this, and will we talk to them directly every week?
- What would you leave out of the first version, and why?
- How do you keep each company's data separate while sharing the building blocks?
- How do you check a migration: record counts, totals, spot checks against the old system?
- Who owns the code, the repository and the hosting accounts on day one?
- What does it cost to run and change after launch, and can part of the fee depend on measured results?
Digital Mundo publishes its own checklist for hiring a software agency with the contract terms worth insisting on.
Who to hire
1. Digital Mundo (our pick)
Digital Mundo is a US software design and development studio based in Miami and New York. For private equity and its portfolio companies it builds internal tools that replace spreadsheets, AI for invoices, reports and data entry with a person approving, KPI reporting from every company in one place, and customer portals and quoting tools. It works through an operating partner: start in one portfolio company, ship the first tool or agent "in about a month", measure it, then bring the playbook to the next company. Each company's code and data stay separate while lessons and building blocks carry over.
Pricing: not published. Terms can be ongoing, a fixed price for a defined project, or, for private equity, partly a capped share of measured savings for an agreed period. The portfolio company owns the code, accounts and documentation, so there's no lock-in at exit.
Limits: it's a senior team rather than a 50-person integration program office, so it won't staff a full post-merger integration across finance, HR and IT at once. Much of its work is under NDA, so the public proof is limited to what's on its published work page and we found no third-party reviews. It publishes no prices and no compliance certifications such as SOC 2, so ask if your diligence needs them.
Pick it if: you want the custom layer (onboarding tools, KPI hub, AI for back-office work) built by the people you talk to, and kept running across add-ons. Its internal tools page shows the kinds of tools it builds.
2. West Monroe
West Monroe calls itself "an AI-native global business and technology consulting firm", with offices including Boston, Chicago, Dallas, New York and Seattle. Its M&A practice covers diligence, carveouts and merger integration of "operations, systems, and culture", and it publishes a case study in which Rugs USA "exceeds M&A synergy targets by 60%". Its private equity page says the deal team "gets to work post-close". Pricing isn't published. Pick it if you need an integration program run across functions; expect consulting-firm pricing and team size.
3. Accordion
Accordion bills itself as "Private equity's value creation partner". Its finance and technology practice lists ERP, software selection, "Financial & Op. Consolidations" and budgeting tools, and its data practice covers data warehouses and BI reporting. Pricing isn't published. Pick it if the problem is centered on the CFO office: the close, the consolidation and the reporting stack. It's less of a fit for custom tools used by field or front-desk staff.
4. Your ERP's implementation partner
If the decision is NetSuite or Sage Intacct, the vendor's certified implementation partners set up entities, eliminations and the chart of accounts. Use them for the ERP itself, and keep the operating tools and reporting definitions with someone who knows your business.
FAQ
What is post-acquisition systems integration?
It's the work of making an acquired company's software, data and processes work with the platform's: merging or connecting accounting, CRM and operating systems, mapping records, and producing one set of reports.
Should every add-on move onto the platform's systems?
Not on day one. Finance usually should, so there's one close. Operating systems are case by case: migrate where the platform's system fits, connect where switching would hurt customers, and report on top while you decide.
How long does it take to integrate an add-on?
It depends on how many systems it brings. A reporting feed can be live in weeks; a full ERP and operating-system migration is a project of months. The goal is for each add-on to go faster than the last.
Is custom software a diligence risk at exit?
Not when the portfolio company owns the code, repository and hosting accounts, and the documentation is current. It's a risk when the agency holds them.
If you're a search fund or independent sponsor doing your first add-on, our guide to software for search funds covers the smaller version of this plan. Either way, start with the one manual process that costs the most, and make the next add-on cheaper than the last.
Disclosure: Digital Mundo LLC and Gold Penguin LLC have the same owner.