Manufacturing Solutions Group

Post Merger Integration Consulting for Owner-Run Companies and PE Add-Ons

Post merger integration consulting from Manufacturing Solutions Group is for three readers: the owner who just bought another shop, the owner who just sold to a private equity platform, and the platform closing its next add-on. The companies run 10 to 200 people, the owner is also the integration lead, and the deal is too small for the firms that write about this subject to staff.

We are an operator-led firm, not a strategy practice. Our acquisition integration consulting starts where small deals lose money: the payroll that runs late on the first Friday, two quoting systems with different margins, an ERP migration started in week two, and the people who quit before anyone told them what would change.

Day 1, Day 30, Day 100: what has to be true at each checkpoint

A hundred-day plan is only useful if it says what must be true at three points. We write these states into the proposal before close.

The three states

  • Day 1. Everyone on both sides is paid on the date and by the method they expect. Every phone number rings to a person. Every open order and scheduled job proceeds on its existing paperwork. Nothing is merged yet, on purpose.
  • Day 30. One quote format reaches customers, one way to book a job, one list of open work, and a written keep, retire or bridge decision for each of the seven systems below. The seller's key people know, in writing, what their job is this year.
  • Day 100. One set of books closes on the lender's calendar. One weekly scorecard covers both companies with the earnout numbers still measurable on their own. Retired systems are off and archived. The second-deal notes are written.

The seven systems that collide, and the keep, kill or bridge call for each

Every small acquisition brings two of everything. It is not one decision called systems integration; it is seven decisions with seven deadlines.

System
ERP or MRP
What collides
Part numbers, routers, BOMs, open work orders
Usual call
Bridge for a quarter, then migrate one product family at a time
When
Decide by Day 30, migrate after Day 60
System
Accounting
What collides
Charts of accounts, fiscal calendars, approvals
Usual call
Keep the buyer's, map the seller's chart to it, run both until one clean close
When
Map by Day 30, one close by Day 100
System
CRM and customer records
What collides
Duplicate accounts, two owners of one contact
Usual call
Keep one, import the other, seller's rep keeps the relationship
When
Day 30 to Day 60
System
Quoting and estimating
What collides
Two rate tables, two margin assumptions
Usual call
One output format first, one rate table after both histories are reconciled
When
Day 30 format, Day 100 rate table
System
Dispatch and scheduling
What collides
Two boards, two crews, one customer calling either number
Usual call
Separate until capacity is shared, then one board, crew intact
When
Not before Day 60
System
Payroll and HR
What collides
Pay dates, pay methods, PTO balances, benefits
Usual call
Keep the seller's provider for two pay cycles, then move with a letter in hand
When
Hold on Day 1, move Day 30 to Day 90
System
Phones, email and domains
What collides
Numbers on trucks and certs, saved addresses, websites
Usual call
Keep every number and address alive, forward rather than retire
When
Keep through Day 100 at least

What the seller's people are afraid of, and the order you answer it

The people on the seller's floor are asking five specific questions, in order, and asking each other because nobody has answered. The buyer who answers all five in a one-page letter on closing day keeps the crew. The buyer who holds a town hall about synergies does not.

The five questions, in the order they are asked

  • When do I get paid, and does the check look the same? Give the next three pay dates and the method.
  • What happens to my vacation balance and my insurance? Give the balance carried over in hours and the date any plan changes.
  • Do I keep my seniority, my shift and my rate? Answer per person, in writing, through the supervisor they already have.
  • Who do I report to now? Give a name they know. If the seller is staying, say for how long and doing what.
  • Is this building staying open? Answer honestly. If undecided, say when it will be decided and that they hear it first.

Buyer side and seller side: the same 100 days from each chair

From the buyer's chair, the owner now runs two companies with the same hours in the week. The deal was negotiated around a spreadsheet; the integration is negotiated around Monday's schedule. What goes wrong is not strategic: a forgotten software renewal, a vendor who will not ship to the new entity, a part number that exists twice, a top technician with a job offer in week three.

From the seller's chair, the owner has an earnout that depends on numbers somebody else controls, a crew that trusted them personally, and a shop being changed by people who have not run it. Most firms write for the buyer and send the seller an invoice. We work both chairs, sometimes on the same deal when both sides agree, because the plan that protects the earnout and the plan that protects the buyer's return are usually the same plan with different reporting.

The chairs disagree on pace. The table above is the answer: consolidate what the customer and the earnout cannot see, and leave the rest until both sides accept a baseline.

Part numbers, routers, BOMs and quoting history: the data merge nobody mentions

Integration pages talk about systems. What decides whether the combined ERP ever works is the data underneath, and in a small manufacturer it has a particular shape: two part-numbering schemes, two routing conventions that treat setup differently, two bills of material naming the same purchased part two ways, customer approvals tied to the entity that submitted them, and a quality certification whose scope names one address.

None of that merges by import. It merges by a person who understands both shops sitting with the data for a few weeks, building a crosswalk, and deciding part family by part family what survives. We do that before any migration is scheduled, and we tell the owner which customer approvals must be re-submitted under the new entity.

Quoting history is the same problem in the office: two records of what was quoted, what the job took and what margin was assumed, and they rarely agree. Reconcile both against actual cost before anyone harmonizes a rate table.

What the customer must never notice, and what they should

The customer chose the company you bought, not you. Nothing the customer sees changes until they have a reason to be glad it did: the number they call still rings, the name on the truck and the certificate stays, the person who answers is the person who answered last month.

What they do not see can change on your schedule: who cuts payables, who runs payroll, who buys raw material and at what discount, how the books close. That is where the savings in a small deal live.

Past Day 60, give the customer something to notice: a quote back in a day because both estimating histories live in one system, one invoice instead of two, a second crew when the first is booked. Only then does the brand question come up at all.

When not to integrate: three tests for leaving an acquired shop alone

Not every acquisition should be integrated past the back office. Platforms that buy by the dozen know this; owners buying their first shop usually do not.

Three tests that say stop at payroll, books and purchasing

  • Approvals and certifications are tied to the legal entity or the address. Re-qualifying under your name usually costs more than consolidation saves.
  • The brand has its own customers. If the acquired name wins work where yours is unknown, folding it into yours turns an asset into a marketing expense.
  • The processes are incompatible and nothing is shared. A high-mix job shop and a repetitive line, or a service company with its own dispatch region, share a bank account and a payroll provider and little else.

Post acquisition integration as a playbook: why the second add-on should cost less than the first

For a platform doing add-ons, the first integration is tuition. The second should cost a fraction of it, and that only happens if the first was written down while it happened. At our size the playbook is five documents the platform owns and we help build during deal one.

The Day 1 letter with the five answers, as a template. The systems decision sheet: seven rows, keep, retire or bridge, with reasons. The data crosswalk method. The cutover checklist for each migrated system, with what broke. The 30, 60 and 100 day scorecard with the earnout lines kept separate. A platform holding those five pages can run its second add-on with its own controller in the lead seat and call us only for the data merge.

Earnouts, seller notes and lender rules that set your integration calendar

In a small deal the integration calendar is mostly set by the paperwork signed at closing. We are not lawyers or lenders and do not interpret those documents; we build the plan around what they say, with your attorney and banker reading over our shoulder.

The earnout formula decides which numbers must stay measurable on their own. If the seller is paid on the acquired company's gross profit for two years, that revenue and cost cannot disappear into a consolidated ledger in month three. The seller note keeps the seller at the table, which argues for a real role rather than a title. The lender's reporting dates set the deadline for one clean close. The purchase agreement often fixes what can be renamed, moved or closed, and when.

Read those documents before the plan is written, not after a step has to be unwound.

How the engagement runs, who sits in the integration lead seat, and what moves the fee

Most merger integration consulting is staffed as a program: an integration management office, workstream leads, weekly steering. Nothing at 10 to 200 people needs that or can afford it. We run two shapes. The one-deal engagement starts two to four weeks before close and runs to Day 100: we write the plan, sit in the integration lead seat beside the owner through Day 30, do the data merge ourselves, then step back to a weekly hour. The platform engagement does the same on the first add-on and leaves the five-document playbook behind.

The lead seat is the real staffing question. There is no corporate development team; there is an owner and usually a controller who knows where everything is. We sit beside that person for thirty days, about three owner hours and five controller hours a week, then hand the seat back.

The fee moves with six things: entities and locations, how many of the seven systems are migrated rather than kept, open-order volume that must survive cutover, whether data is mapped or rebuilt by hand, whether an earnout requires separate reporting, and days on site versus remote. One location and one system to migrate is the small end; two locations, two ERPs, an earnout and a cert transfer is the large end. You get a written number before close.

Who shows up is the person on this page. Our founder came up as a millwright and projects lead on turbine decks and refinery floors, built and ran a precision manufacturing group, and now runs several companies off one shared back office, where the payroll, phone and books problems above were learned firsthand. Roger Pemberton, our Operations Director, has run plants and the people in them. We are on site in any state and remote between visits.

Karl Gillihan

Karl Gillihan

President

Founder and President of MSG. He came up as a rotating equipment specialist in the energy industry and now runs MFGBase, LocalAISource, and ServiceStorm.

About Karl Gillihan

Frequently asked

What does post merger integration consulting from MSG actually cover?

The plan from two to four weeks before close to Day 100: the three checkpoint states, the keep, retire or bridge call for each of the seven systems, the Day 1 letter to the seller's people, the data merge, and a scorecard that keeps earnout numbers measurable.

How much does it cost for a company our size?

A one-deal engagement priced before close, or a platform engagement for the first add-on that leaves a playbook behind. The fee moves with entities, systems migrated rather than kept, open-order volume, data rebuilt by hand, earnout reporting and on-site days. Written number, not an hourly meter.

How long does merger integration consulting take for a 20 to 200 person company?

To Day 100, heaviest in the two weeks before close and the first thirty days after. Full consolidation of books and systems often runs past Day 100, and some systems are correctly never merged.

Should we move the acquired company onto our ERP right away?

No. Decide by Day 30 whether the acquired system is kept, retired or bridged, and do not migrate before Day 60. Part numbers, routers, BOMs and open work orders have to be crosswalked first. Migrating in week two is the most common expensive mistake we see.

Do payroll systems have to merge before the first payroll after close?

No. Run the seller's payroll on the seller's provider for at least two pay cycles, on the dates and by the methods the crew expects, then move it with thirty days of written notice.

We just sold to a private equity platform. What happens to our systems and our people?

It depends on the platform's plan, and a seller is allowed to ask for it in writing. We work the seller's chair too: keeping your earnout numbers separately measurable, keeping your people informed through you, and sequencing changes so your customers see nothing move.

How is acquisition integration consulting different from an ERP implementation?

An ERP implementer moves data into one product and calls it done. Acquisition integration decides first whether that migration should happen at all, what the people hear on Day 1, how the earnout stays measurable, and what the customer must never notice. Software comes last.

When should post acquisition integration stop, and the shop be left alone?

When the acquired shop's approvals or certifications are tied to its legal entity, when its brand wins work yours cannot, or when the two processes share nothing but a bank account. Then integrate payroll, books and purchasing and leave the rest.

How do earnouts change the pace of integration?

The earnout formula decides which numbers must stay measurable on their own and for how long. If the seller is paid on the acquired company's margin, that revenue and cost cannot vanish into a consolidated ledger. We build the plan around the signed documents.

Do you work only with manufacturers, and only in Texas?

Neither. Manufacturers and field-service companies are most of this work, and our clients are spread across the United States. We are based in Southeast Texas, on site in any state for the pre-close weeks and the first thirty days, and remote between visits.

Send us the closing date and the list of systems on both sides

We will tell you in writing what has to be true on Day 1, what should wait, and whether you need us at all.

How do you want to reach us?