Five conversations we kept having at Unbound.
Most of the M&A and portfolio operators we met in Boston were carrying the same problem: every company they bought arrived with its own CRM. These are the questions that came up again and again, and how we answer them after doing the work.
Do we consolidate now, or phase it?
What we heard
Most people asking had closed a deal in the last year and already had the next one in view. Waiting for a quiet moment was the default plan.Phase the migration, but decide the structure now. If you buy on a cadence, the quiet moment never comes, and every delay means absorbing two or three companies at once instead of one.
Three things get settled on day one: one customer record, one agreed set of definitions, one reporting model. Everything else can move in stages.
Ask Foyer about your version of thisFrom the fieldAt one client, a group of four safety brands built through acquisition, phase one was the sales CRM only. Contacts, companies and pipeline across every brand, while the existing email platform kept running until the record underneath it was trusted.
What gets standardized first?
What we heard
Most rooms assumed the answer was a tool. The follow-up question was usually about reporting that nobody trusted.The customer record, before anyone's workflow. And the first argument is about words, not software. One company says lead, another says account. One counts a deal at proposal, another at signature.
Until those definitions are written down and agreed, every group report built on them is wrong, and nobody notices for a quarter.
Ask Foyer about your version of thisFrom the fieldOn that engagement, discovery ran brand by brand: process, roles and ownership, then data and lifecycle. Definitions came before any configuration, and that sequence kept the group away from a CRM choice that would not have fit.
How do we run several brands without chaos?
What we heard
Two camps: one portal per brand to keep the peace, or one merged list to keep it simple. Neither was working for the people who had tried it.Keep the brands inside one system. Separate portals rebuild the silos you just paid to remove. One merged list erases the distinctions each brand runs on.
The middle path: brand becomes a field on a shared record, with brand-specific lifecycle stages, pipelines and permissions on top. A customer can be existing for one brand and new for another.
Ask Foyer about your version of thisFrom the fieldFor that group, one contact record is shared across the brands, deduplicated on email, so the group avoids double-counting customers and paying for duplicate marketing contacts. Each brand keeps its own lifecycle stages and lead statuses.
Where does the lead actually belong?
What we heard
The sharpest version: a prospect fills a form on brand A's site asking for brand B's service. Who owns it?Two different questions, so two different fields. Attribution stays with the site that earned the enquiry. Ownership routes to the company that will deliver the work.
Collapse them into one field and cross-sell becomes invisible: the enquiry either lands with the wrong team or gets credited to the wrong brand.
Ask Foyer about your version of thisFrom the fieldThe group's main contact form offers a dozen services across brands, and prospects often tick several. Enquiries were defaulting to the brand whose site they came from. Moving about 77 external forms onto native HubSpot forms, with service interest captured as data, is what makes routing by service possible.
Cross-brand routing and attribution?
What we heard
Asked most often by marketing leaders who had to show a sponsor that cross-sell was real, using a spreadsheet assembled by hand.Route on service interest, not on the originating website. Keep the source brand, the delivering brand and the campaign as separate properties, so group reporting can show which brand created demand for another.
Connect the ERP rather than replacing it. It keeps products, pricing, quotes and orders. The CRM owns engagement. Custom middleware between them means the system underneath can change without rebuilding the CRM.
Ask Foyer about your version of thisFrom the fieldAt the same client, cross-sell used to be tracked in spreadsheets because every brand's email data sat in its own silo. The target state is a single pipeline view across brands, with an integration layer to the ERP so quotes and orders stay where they already live.
The overall picture from Boston
Consolidation has moved from a back-office clean-up to something sponsors ask about directly. The operators we met were less worried about picking a platform and more worried about the three things that reliably go wrong once they do.
Duplicate records
They destroy trust in the numbers faster than anything else. Resolve them before go-live, not after.
Processes nobody owns
Handoffs that cross company lines drift unless one named person owns each one.
Teams who survived a failed rollout
They are not being difficult. They are protecting themselves, and they usually have reason to. Show them their own work first.
Carrying one of these into your next board meeting?
Read the full approach, or tell Foyer, our AI concierge, what your group looks like.