The Consolidator

This is a seasoned operator with 15 to 25 years of experience. They sit inside PE-backed post-acquisition companies running between $100M and $500M in ARR, typically with 2 to 7 companies merged under one roof. They have a small internal data team — zero to three engineers — and the mandate to make everything work together.

They are technically literate but not a coder. They can read a data model, understand API limitations, and spot when a vendor is overselling. They have seen this problem before, possibly more than once. That experience makes them skeptical of big-bang approaches and wary of consultants who show up with a two-year roadmap and a seven-figure price tag.

What makes this urgent is not the tooling cost. It is the board conversation. The PE firm acquired three to seven companies expecting revenue synergies and preserved customer value from each acquisition. Without a unified customer data layer, the combined entity cannot report clean NRR to the board, cannot identify which acquired customers are at highest churn risk, and cannot tell whether retention is improving or deteriorating across the portfolio. The sponsor is not asking for a data architecture roadmap. They are asking for a retention number at the next board meeting, and nobody has one.

The Consolidator lives in a fragmented landscape that nobody planned and everybody tolerates. Multiple legacy CRMs were never rationalized after acquisition. Duplicate accounts exist across systems with no single source of truth. The product master is broken and nobody trusts it. Spreadsheets serve as the de facto reporting layer.

Microsoft Copilot is licensed but underutilized because there is no clean data to feed it. The infrastructure was never designed to support a unified revenue motion — and yet that is exactly what the PE sponsors expect them to deliver.

• Unified customer master — built outside the CRM first, then reconciled back in.
• AI-ready data layer — clean, structured data that tools like Copilot can actually use.
• Compressed timeline — turn a 2 to 3 year consolidation into weeks, not quarters.
• CRM rationalization roadmap — a clear path from many systems to one, without disrupting the business.
• One retention number for the board — a single, reliable view of GDR and NRR that spans all acquired companies, broken down by product line, customer segment, and acquisition vintage.

The Consolidator does not buy based on slide decks or references alone. They have been burned before and they need to see proof fast. They value speed over perfection — they would rather have 80% right in two weeks than 100% right in six months. Their orientation is outside-in: build the data layer alongside the CRM, not trapped inside it.

They want proof before scale — show them it works on one business unit before asking them to commit the whole portfolio. They see AI as an accelerant for matching, deduplication, and enrichment. And they prefer a hybrid build approach where their small team does the ongoing work while Balboa accelerates the hard parts.