Acquiring another company sounds like a finance and strategy project.
Before the deal closes, most conversations naturally revolve around valuation, customers, contracts, leadership, and whether the combination makes business sense.
Then Monday morning arrives.
Now there are two groups of people working under one organization — and they may have completely different ideas about how that organization works.
That’s when I realized that closing the transaction was only one milestone.
Integrating the workplace was an entirely different project.
My First Question Wasn’t “What Should We Change?”
It was:
“What does the acquired company currently do?”
I didn’t want to immediately replace every existing process.
First, I needed an inventory.
How were new hires handled?
Which workplace policies were employees following?
Who maintained personnel records?
How were time-off questions handled?
What benefits arrangements existed?
Who handled workplace incidents?
Which processes depended on one specific person?
Until I understood the current environment, I couldn’t distinguish something that needed to change from something that simply worked differently.
The Two Companies Used the Same Words Differently
This created more confusion than I expected.
Both organizations had managers.
Both had policies.
Both had onboarding.
Both had time-off procedures.
That made them look similar from a distance.
But once I looked closer, the actual processes could be very different.
“Manager approval” might mean one thing in our original company and something completely different in the acquired business.
The vocabulary matched.
The workflows didn’t.
I Built a Side-by-Side Process Map
Instead of debating which company had the “better” system, I documented both.
| Area | Company A | Company B |
|---|---|---|
| New hire process | Centralized | Manager-led |
| Policy documents | Company-wide | Location-specific |
| Personnel records | Standard structure | Mixed structure |
| Workplace questions | Defined contact | Usually direct manager |
| Incident process | Formal workflow | Case-by-case |
Immediately, the integration project became easier to see.
The problem wasn’t simply that the businesses were different.
I could finally see where they were different.
I Looked for Immediate Risk Before Cosmetic Consistency
It was tempting to standardize everything quickly.
Same templates.
Same terminology.
Same document format.
Same internal naming.
But visual consistency wasn’t my first priority.
I wanted to find issues that could create real operational problems.
For example:
- Missing required documentation
- Conflicting policies
- Unclear responsibility for workplace incidents
- Different practices across locations
- Important records controlled by one person
- Processes that nobody could clearly explain
Those mattered more than whether two forms looked identical.
Benefits Needed Their Own Workstream
Benefits were another area where assumptions could create confusion.
The acquired workforce might have different plans, eligibility rules, enrollment timing, or established expectations.
I didn’t want managers improvising answers simply because employees naturally started asking questions.
Instead, I treated benefits transition as its own project.
What remains unchanged?
What changes?
When?
Who is affected?
What information needs to be communicated?
Who handles questions?
That structure prevented every question from turning into a new internal debate.
I Didn’t Underestimate the Emotional Side
From management’s perspective, an acquisition can represent growth.
For the acquired workforce, it can represent uncertainty.
People may wonder:
Will my role change?
Will my manager change?
Are our policies disappearing?
What happens to the way we’ve always done things?
Even when leadership doesn’t have every answer yet, pretending those questions don’t exist makes the transition harder.
Communication needs to distinguish between:
what has been decided,
what remains unchanged,
and
what is still being evaluated.
Managers Became the Critical Link
Employees naturally asked their managers first.
That meant managers needed consistent information.
Otherwise, five managers could produce five different explanations of the same transition.
I started giving managers short, practical guidance.
Not a giant presentation.
Just:
What we know
Confirmed decisions.
What we don’t know yet
Items still under review.
What managers should not guess about
Questions that need to go to the appropriate resource.
That last category was surprisingly important.
Old Policies Didn’t Disappear on Closing Day
Another mistake would have been assuming:
“We’re one company now, so everyone automatically follows everything we already have.”
Real integration isn’t that instant.
Existing documents need to be reviewed.
Differences need to be understood.
New expectations need to be communicated.
Applicable requirements may vary depending on where people work.
I wanted a deliberate transition rather than an accidental one.
Geography Made the Integration More Complicated
If the acquired company operates in another state, the project can immediately become more complex.
Workplace requirements aren’t identical everywhere.
That means I can’t simply copy an existing process and assume it’s appropriate in every location.
This is one of the situations where working with an outside HR partner such as Trion Solutions can become particularly relevant.
The business isn’t only adding people.
It’s adding another operating environment.
I Looked for “Only Sarah Knows This” Processes
Every company seems to have some version of this.
Someone says:
“Talk to Sarah. She handles that.”
Then I ask:
“Where is the process documented?”
Silence.
An acquisition can expose a surprising amount of institutional knowledge that exists only in someone’s head or inbox.
I made those processes a priority.
Not because Sarah was doing anything wrong.
Because the combined company shouldn’t depend on Sarah being available forever.
I Created a 30-Day Integration List
I didn’t try to solve the entire organization in one week.
I separated the work.
Immediate
Issues that could disrupt operations or create unnecessary risk.
First 30 Days
Processes that needed to be documented, compared, or assigned.
Later Integration
Items that could reasonably remain different temporarily while the combined company evaluated the best long-term approach.
That prevented urgency from swallowing the entire project.
I Also Protected What the Acquired Company Did Well
Integration shouldn’t automatically mean:
“Our company bought yours, therefore our process wins.”
The acquired organization may have practices worth keeping.
Sometimes its managers have solved a problem better than we have.
I want standardization where consistency matters.
I don’t want standardization simply because one process existed first.
Where Trion Solutions Fits Into the Picture
For a growing organization, an acquisition can multiply HR administration quickly.
It’s not merely additional headcount.
It’s additional records, policies, managers, locations, workforce questions, benefits considerations, compliance responsibilities, and historical practices.
A PEO relationship with Trion Solutions can provide HR support and administrative infrastructure while leadership works through that complexity.
The value isn’t making every integration decision for the company.
The company still needs to decide how it wants to operate.
The value is having more structure around the people-related side of the transition instead of rebuilding every process from scratch while the business is simultaneously absorbing another organization.
My Post-Acquisition Checklist
During the early integration period, I want answers to questions like:
✅ Who handles what today?
✅ Which policies currently exist?
✅ Where do the two organizations differ?
✅ Are personnel records complete and organized?
✅ Which processes depend on one person?
✅ What needs immediate attention?
✅ What can remain unchanged temporarily?
✅ Are managers communicating consistent information?
✅ Do different locations create additional requirements?
✅ Which practices from the acquired company are worth preserving?
The Deal Closed on Friday. The Company Didn’t Finish Integrating on Friday.
That’s the distinction I wish more acquisition plans made obvious.
Signing documents can combine ownership.
It doesn’t instantly combine workplace processes.
Monday morning brings the real questions.
Two organizations now need to figure out how they will operate as one business without creating unnecessary confusion for the people already doing the work.
That’s why I no longer treat the people side of an acquisition as something to address after the “important” transaction work is finished.
It is important transaction work.
Because after the lawyers, executives, and financial teams finish closing the deal, someone still has to answer the most practical question of all:
“How does this company actually work starting today?”