When an MSP employee finds out the company they work for has been acquired, it can be shocking and leads them to wonder:
This employee uncertainty is not a minor detail during an acquisition. It is central to whether the deal delivers value. Customer loyalty, recurring revenue, and the strategic goals behind the transaction all hinge on how the team feels when they walk in on Monday, trying to make sense of what has changed.
Most of their concerns fall into four categories: 1) day-to-day changes, 2) financial impact, 3) cultural shifts, and ) technology adjustments. When MSP buyers proactively address these areas, the transition becomes far smoother, and the long term success of the acquisition becomes much more likely.
The first three questions employees ask are usually practical:
Underneath all of that sits the real one: “Will I or any of my coworkers lose our jobs?”
When you are addressing the team for the first time post-closing, start by welcoming everyone to the team and being direct about job security. Never promise “no one will be let go” if you know there will be cuts. That destroys trust instantly. If any roles are already known to be redundant, address that clearly so rumors do not spread. Once people understand they still have a place in the organization, the anxiety level drops, and they become more open to conversations about systems, training, and future goals.
Once people know whether they still have a seat, the employee concerns often shift to money:
The most successful integrations tend to follow a few proven principles. Base salaries are matched or slightly improved for the retained team members. The upside for employees is communicated, be it performance-based bonuses or opportunities for career advancement. Expectations are documented clearly from the start, including each person’s role, goals, reporting structure, and how success will be measured. This level of clarity gives employees confidence and reduces the uncertainty that can sometimes cause turnover during an acquisition.
Then there is the less glamorous side: accrued vacation and legal liability. These details may not be the most exciting part of a transaction, but mishandling them can create major problems. In many deals, sellers are responsible for paying out vacation and similar liabilities up to the closing date. In an asset purchase, employees are typically terminated by the seller and rehired by the buyer under new contracts, while in a share purchase, those liabilities remain with the company and are managed through working capital adjustments. But these rules can vary by jurisdiction.
The priority should be to clearly separate old obligations from new ones, recognize past employee service appropriately, and communicate how vacation time, benefits, and tenure will carry forward. When those details are vague, frustration and distrust grow fast.
Owners often focus on customer contracts, geography, and service mix. While employees will concern themselves over things like:
Take branding, for example. For a founder, the logo and name represent years of effort. For long-time staff, it represents identity and pride. Some acquirers keep the brand for a period, tagging on “a division of X,” then gradually transition to a single name. Others fold everything into their own brand almost immediately. There is no single right approach, but buyers would be well advised not to rock the boat too soon until they’ve been able to gauge the temperature of the team.
Culture goes beyond branding. Small IT firms often have rituals that matter more than leaders realize: Friday afternoon flexibility, monthly social events, an N64 in the break room, etc. When you plug them into a larger, faster-paced environment with more process, some staff will thrive, but others may decide it is not for them.
During due diligence, buyers should take stock of cultural norms on both sides. How do people work, meet, and celebrate wins today? Then decide intentionally which elements you will keep, which you will adapt, and which will change. Involve leaders from both companies in shaping a shared vision, values, and long-term goals, then present that clearly to the whole team.
After an acquisition, technical staff may wonder:
From the buyer’s side, technology decisions often involve balancing two competing priorities. On one hand, standardizing tools and platforms can prevent unnecessary complexity and cost from spiraling out of control. On the other hand, acquisitions can introduce better tools or unique capabilities that the parent organization may want to adopt.
Navigating that balance requires careful due diligence to fully understand the acquired toolset and how it aligns or conflicts with current systems. Buyers should look closely for situations where the acquired company actually uses a stronger or more efficient solution that deserves consideration as the new standard. Successful integrations build two-way learning into the transition plan, where the new team receives clear training on the parent company’s systems, while existing employees gain exposure to tools and approaches that are joining the environment through the acquisition.
If you want your next MSP acquisition to go smoothly, employee concerns should be at the forefront of the process:
If you would like to hear the full conversation these insights came from, carve out some time to watch the complete discussion on YouTube and dig into the nuances that could make or break your next deal.