Your Portfolio Company's CRM Is Already Shelfware. Here's How to Tell.
There's a moment in a lot of post-acquisition integrations where someone dares to surface the whisper as a loud statement. It could be any of these:
"Don't trust the dashboard."
"We have a spreadsheet for that."
"Only one person knows how this works."
"We'll clean the data later."
If you've sat in a portfolio company's operating review and heard any of those, you already have your answer. The CRM isn't a system of record anymore. It's shelfware — a tool everyone logs into and no one trusts. It’s surprising how fast this happens.
We made this point recently in a Hypepotamus feature on how growing companies outgrow their CRM. The framing there was aimed at founders, but the failure mode is sharper - and more expensive - inside a PE-backed rollup. So it's worth saying plainly to the operators who live this: the CRM problem you inherit at close is rarely a platform problem. It's a process problem wearing the clothes of a platform.
The diagnostic is simpler than people make it
Here's the test. If your sales, finance, customer success, or support teams can't pull every important piece of prospect or customer data out of the CRM immediately, it has become shelfware. Not "needs work." Shelfware.
The root cause is almost always the same: the system stopped reflecting how the business actually operates. Side processes appear. Reporting gets unreliable. Adoption drops. And once a team stops believing the numbers, they build their own. Inn spreadsheets, Slack threads, or - a favorite - one person's head. By the time you're spending hours a week on manual workarounds, the CRM is already costing more than it returns.
A healthy CRM creates clarity and speed. An unhealthy one creates meetings about why the CRM is wrong. You can usually tell which one a portfolio company has within the first week of diligence on its systems — long before you can tell from the data room.
Why this hits rollups harder than single companies
A standalone company with a messy CRM has one mess. A rollup has as many messes as it has acquisitions, and they don't reconcile. Different definitions of a "qualified" opportunity. Different stage names that mean different things. Different ideas of what counts as closed-won. Stack three or four of those on top of each other and "give me a consolidated pipeline view" becomes a multi-week project instead of a click.
The trap is the same one that catches a startup after a raise — it just arrives through a different door. After a raise, fresh funding triggers a wave of platform purchases, layered approvals, and automation built on top of processes that were never defined. After an acquisition, fresh ownership does the exact same thing: a mandate to "get to one system," a buying spree, integrations bolted onto undefined processes, and a new ops hire told to make it all work. More is not better. More is just more surface area for the same problem.
This is the thing we keep coming back to in this series: rollups don't fail in the deal. They fail in the systems. The CRM is where that failure shows up first and most visibly, because it's the system everyone touches and everyone judges.
The asset everyone underestimates
When operators do start fixing the CRM, the instinct is to focus on the future state - new fields, new automation, a clean instance going forward. The thing that gets left on the floor is historical activity data: the full record of emails, calls, meetings, and how opportunities actually moved through stages over time.
That's a mistake, and it's an expensive one. Two years in, historical activity data is what powers forecasting, churn analysis, channel attribution, and any AI work you eventually want to do. Lose it in a migration and you're not starting clean - you're rebuilding context from scratch, and you can't get those two years back. In a hold-period math sense, that's a chunk of your value-creation window spent re-learning what the business already knew.
So if you're consolidating CRMs across a portfolio, the migration question that matters isn't "which platform wins." It's "what history are we about to throw away, and what does it cost us in year two."
What we'd actually do first
The reflex after a close is to buy and standardize fast - to make the portfolio company look enterprise overnight. We'd push the other direction.
Slow down on the tool count. Define the processes before you automate them. Get to a shared, honest definition of the pipeline before you try to consolidate three of them. And put people onsite with the team to drive adoption, because a CRM nobody trusts doesn't get fixed by a better CRM - it gets fixed by a process the team believes in and a system that matches how they actually work.
A new platform doesn't fix shelfware. Process clarity does. The platform just makes the clarity scale.
Ground Team Solutions is a Georgia–based Salesforce partner working onsite with VC-backed and PE-owned companies on CRM systems that match how the business actually operates. If you're staring down a post-acquisition CRM consolidation and want a second set of eyes before you buy anything, let's talk.
