The management layer of an acquired company is the most expensive line you can cut and the most expensive one you can keep. Cut it and you lose the people who know the customers, the crews, and the quirks of the business. Keep it unchanged and you pay for duplicated work and slow decisions.
There is no right answer without a prior decision. Until you know whether you are preserving the business, integrating pieces of it, or consolidating it into yours, you cannot say which managers you need. Make that choice first, then work the people through the principles below. It all sits inside employee retention after acquisition.
Start with the operating model
If you are preserving and strengthening an autonomous business, you keep its management layer. It is the reason the business works. Your job is to support it and remove obstacles.
If you are selectively integrating, you keep management where it runs customer facing work and combine the functions that do not need to be local, such as finance, payroll, and purchasing. If you are substantially consolidating, you will have fewer layers, and you need to be honest with yourself and the people about it from the start.
Look at what each manager actually does
Map each management role to the work it performs: who makes the schedule, who owns the customer, who approves pricing, who hires and fires, who handles complaints. Ask the team, not just the manager. In small businesses, titles are poor guides. A person called an office manager may run dispatch, collections, and payroll.
Then ask which of those duties transfer to your structure and which are better kept local. A function that depends on local knowledge, such as dispatching crews who know the town, tends to stay. A function that is transactional, such as invoicing, tends to move.
The cost of flattening too fast
Flattening removes the person the technicians go to with problems. It also removes the person the customers call when something goes wrong. If you replace them with a distant manager in your structure, response times slip and people feel unsupported. Revenue follows within months.
If you do flatten, build the replacement path first. Name who handles what, make sure they know the people, and keep a visible local contact. See integrating add-ons into a platform for how the platform approach works with add-ons.
The cost of keeping everything
Preserved layers have a price too. They keep their own methods, their own tools, and their own reporting. Your leadership team has more to oversee, and consistency suffers. Decide which management activities you will standardize regardless: reporting, safety, financial controls, and the use of shared systems.
You can keep a manager and still change what that manager reports and to whom. That is often the middle path.
Where the hard cases come from
Two kinds of hard case turn up. One is when your own company already has someone in the same role; see two people in one senior role. The other is when the seller's loyal number two expects to run the business; read the seller's loyal number two. Both deserve their own decisions, made promptly. I would not remove a layer of management until I could name who the crews and customers will call instead.
Decision table: keep, fold in, or remove a management role
Apply to each role. Write the answer and the reason, and file it with the operating model decision.
| Question | If yes, it points to | If no, it points to |
|---|---|---|
| Are you preserving this business as a stand alone unit? | Keep the layer and support it | Decide role by role, using the next questions |
| Does the role depend on local knowledge or customer relationships? | Keep it, with a clear reporting line into your structure | Look at whether the work is the same in both companies |
| Is the work transactional and the same in both companies? | Fold it into your central function with a handover plan | Keep it local until you know what it does that yours does not |
| Does your company already have someone in this role? | Decide between them on a written role description | Keep the person you have |
| Would removing the role risk a key customer or crew? | Delay and protect the relationship first | Proceed, with notice and a fair package |
Communicate the decision once and clearly
Tell each manager their position before the staff hears it. Tell the staff how decisions will be made, and who they go to for what. Vagueness here spreads faster than any announcement. If the management structure will change over time, say so, and give the period.
A manager who is told the truth early can help you plan a good transition. A manager who learns it from a rumor will start looking elsewhere, and will take what they know with them.
The managers you are deciding about are your best source of what you do not yet know about this business. Spend time with them before you decide.
Get the 100 day integration tracker
The tracker puts an owner, a date, and a status on every integration task from pre-close to day 100, so decisions like this one get made on purpose and followed up.
One email with the download, and occasional Building Results notes. Opt out any time.
Questions
Should an acquired company keep its own management team?
It depends on your operating model. If you are preserving the business, keep the layer and support it. If you are integrating selectively, keep customer facing management and combine back office functions. If you are consolidating, plan fewer layers and be honest about it early. Map what each manager actually does before deciding.
Can I keep a manager but change who they report to?
Yes. That is often the middle path: the person keeps their local role while reporting into your structure.
When should I tell managers about the new structure?
Before the staff hears it, and as early as you can answer honestly. Give each person their position privately.
What if the management layer is much more expensive than mine?
Compare the cost to the revenue and relationships they hold. Cutting a layer that holds the customers can cost far more than it saves.