Your fourth add-on will not fail because of the fourth add-on. It will fail because of the first three, which you integrated by hand, a little differently each time, and never wrote down. Then deal four arrives, the person who remembers how deal two went is busy, and you start from scratch with a bigger business and less attention.
That is the quiet danger. Each add-on looks small. Together they become a business you can no longer see clearly. Owning the branches does not mean you understand them yet.
This page makes add-on acquisition integration something your team can repeat. You get a platform integration standard by function and a readiness checklist for serial acquirers.
Get the integration playbook (PDF)
The playbook walks the operating model decision, decision rights, sequencing, the governance cadence and exit criteria, with the add-on case built in. Leave your email and it comes to you.
Why add-ons are a different problem
A first acquisition is a project. An add-on is a process. In a project you lean on your best people and late nights. In a process, those same people get pulled into the next deal before the last one is finished, and the heroics stop scaling.
The platform is what you are really building. If it has no standard way to take in a new branch, crew, route, or sales team, every deal becomes a custom job, and custom jobs leak value. A customer gets two invoices. A technician stays on the old pay plan for six months. A purchasing agreement nobody checked quietly costs margin.
A repeatable method beats heroics for a commercial reason: speed and quality of integration decide how soon an add-on earns what you underwrote.
Start before the close, and decide the operating model on purpose
Integration starts before the close, in the seller conversation and in diligence. Set expectations early: what changes, what does not, how long the seller stays, and what they have told crews and customers. Read the data room for integration risk, not only deal risk: change-of-control clauses, key-person dependency, customer concentration, handshake pricing.
Then make the operating model decision for each add-on, on purpose.
- Preserve and strengthen. The business runs well and its local identity is part of its value. Add finance, systems, and purchasing support, and leave the rest.
- Selectively integrate. Some functions move to the platform, others stay local. This is the right answer more often than people expect.
- Substantially consolidate. The add-on overlaps your footprint. Branches merge, routes are redrawn, the old brand goes away. The hardest path, and the easiest to rush.
One size does not fit all, and a platform that forces every add-on into the same box will crush some of what it bought. When the choice involves the name on the trucks, read rebranding after an acquisition before you decide.
The platform integration standard
The standard is a written statement of what every add-on gets from the platform, and what the local business keeps. Centralize where scale and control create value and customers rarely notice. Leave local what customers and employees feel directly. Adjust it to your business, then hold to it. Each row is owned by the platform head of that function, who signs off before the add-on counts as integrated in that area.
| Function | Every add-on gets (centralize) | Stays local (unless you decide otherwise) |
|---|---|---|
| Finance | Chart of accounts, month end close calendar, cash and collections reporting, banking and signing authority, a weekly cash view | Local credit judgment on established customers, inside agreed limits |
| Purchasing | Review of vendor terms, one approved vendor list, volume agreements where the platform rate is better than theirs | Existing vendor relationships that carry a better rate or better service. Find out why before you switch |
| Systems | Identity and access, security baseline, reporting feeds into the platform scorecard, a defined cutover date for core systems | Field tools the crews already use well, until the replacement is proven and trained |
| HR and pay | Payroll continuity on day one, benefits transition plan, safety and compliance standards, a retention map for the critical few | Local pay structure for top producers until you have modeled the change |
| Brand | A decision and a timeline, made once and communicated clearly | The local name and identity until the decision says otherwise |
| Customer relationships | Account ownership transfer for top accounts, a contact plan, early churn signals | Who calls on the customer, and how. The relationship holder stays put |
| Scheduling and dispatch | Visibility into capacity, response times, and backlog | Day to day scheduling, crew assignment, and route design, since local knowledge wins here |
| Sales | Targets, pipeline reporting, a cross-sell plan with named owners | Territory relationships and local selling style |
The middle column is a floor: every add-on gets it, on a schedule set in advance, so the finance lead is not inventing a close process for the fifth time. The right column is a promise. When the leaders of an acquired business hear what stays theirs, they stay. When they hear nothing, they assume everything is up for grabs.
The sequence for the first 100 days is in the first 100 days integration plan, and the wider method sits in the post-merger integration playbook.
What breaks across branches, crews, and routes
Multi-location businesses fail in predictable places. Watch these first.
Crews and technicians
In field service and installation, the crew is the product. The foreman who knows the building, the technician who takes the 7 pm call: that is what the customer pays for. Keep the people to keep the customers. Change a pay plan or schedule carelessly and the people go, and the accounts follow.
Routes and delivery in distribution
Redrawing routes saves money on paper. It also changes who the customer sees and when. Before you consolidate, check what the driver does that is on no list: the early drop, the shelf stocking, the problem solved without a ticket.
Sales teams across geographies
Your sales leaders do not know their market, and their sales leaders do not know your products. Give the local leader a seat in cross-sell planning. Pushing your catalog into their accounts in month two risks the relationship you paid for. For the customer side of this, see customer retention after an acquisition.
Whatever the branch, surface the unwritten habits early: how quotes are built, how credit is extended, which customers get a favor. One issue is never just one issue. A pricing exception usually points at a credit habit, which points at a relationship you did not know you had.
The growth case, with an owner on every line
Roll-ups are underwritten on growth as much as cost. Two kinds of synergy behave differently.
- Cost synergies come from purchasing, overhead, and routing. They are more certain, and they damage service if you chase them too hard.
- Revenue synergies come from cross-sell and footprint expansion: selling the platform's services into the add-on's customers, and using a new branch as a base to serve nearby geographies. They are larger and slower.
A growth number without an owner is a wish. For each cross-sell and expansion line, write down who owns it, what must happen first, when it starts, and how you will know it works. If you cannot name the owner, take the number out until you can.
Expect the valley of despair. While people move through ADKAR (Awareness, Desire, Knowledge, Ability, Reinforcement), performance often dips before it climbs. Plan for it so a soft quarter does not trigger the wrong response.
Integration debt across serial deals
Every shortcut on one add-on is a loan against the next. A system you did not cut over, a vendor you did not review, a pay plan left alone for lack of time: each is integration debt. Across ten deals it becomes a platform with ten ways of doing the same job.
Keep a register. For each add-on, list what was deferred, why, who owns clearing it, and by when. Review it as often as your financials. If old debt is growing while you sign new deals, the platform is telling you to slow down or add capacity. For a second set of eyes, that is what post-merger integration consulting is for.
Serial acquirer readiness checklist
Use this before you sign the next add-on. Every unticked line is attention the next deal will cost you.
Can your platform actually absorb another one?
- The platform integration standard is written down, current, and known to every function head.
- One named person owns integration across deals, with authority to say no to a deal timeline.
- Each function has a standard day one and first 100 days task list that does not live in one person's memory.
- The operating model choice (preserve and strengthen, selectively integrate, or substantially consolidate) is made for the target before the LOI is signed. Owner: the integration lead.
- Integration capacity is counted: the people who will run the next add-on are not still deep in the last one.
Do you know what you must keep?
- Seller expectations are set: role, timeline, and what they have promised crews and customers.
- The critical few people are named, with a retention plan for each. Owner: the add-on's general manager and HR.
- Top accounts are listed, with an owner and a transfer plan for each relationship. Owner: the sales leader.
- Change-of-control and assignment clauses are checked in customer, vendor, and lease contracts. Owner: the finance lead with counsel.
- An opening baseline is frozen for people, customers, profits, and cash.
Will you see a problem before the P&L shows it?
- Every cross-sell and expansion line in the model has a named owner and a start date.
- A synergy ledger separates bankable cost savings from aspirational growth.
- Each add-on is measured against its own opening baseline, not the platform average.
- An integration debt register exists, and older items are being cleared, not just listed.
- Exit criteria are defined: you know what "integrated" means for this add-on, and when it moves to normal operations.
Build the standard with your team
The playbook PDF, once it is ready, gives your finance, sales, operations, and HR leaders a shared method.
Decisions on this topic
The specific calls operators face inside this part of the integration. Each has its own page, with the tension laid out and a way to decide.
- Vendor terms better than yours. Consolidating to your master agreement can move their spend to a worse rate.
- Consolidating suppliers after acquisition. Consolidate for leverage and you drop a vendor who may retaliate, or kill a supplier whose biggest customer you just bought.
- A vendor deal that rests on a handshake. Formalizing the deal can reset the favorable terms, because the relationship was the asset.
- Vendor contracts that end on a change of control. The territory or brand rights you underwrote may not survive the sale.
- Minimum purchase commitments you inherited. You cannot just move the volume.
- Vendor rebate tiers after acquisition. Consolidate or split spend and you can drop below a tier, quietly losing rebates that propped up the margin you bought.
- Vendor payment terms that differ from yours. Normalizing to your terms moves real cash and can forfeit prompt-pay discounts, or strain a supplier who relied on being paid fast.
- The seller's personal guarantee on vendor lines. The vendor wants a new guarantee from you to keep the terms.
Questions
What is add-on acquisition integration?
Folding a smaller acquired business into an existing platform company: people, customers, systems, finances, and operations. It differs from a first deal because the platform must do it repeatedly, so the standard matters as much as any single integration.
Which functions should a roll-up centralize first?
Usually finance, purchasing review, and systems access, because they give the platform visibility and control without changing what the customer sees. Brand, customer relationships, and daily scheduling are usually safer to leave local until you have a reason to move them.
How do you avoid losing key people in an add-on?
Name the critical few before the close, talk to them early, and be clear about what stays theirs. Targeted retention beats blanket retention. Do not change pay plans for top producers until you have modeled the effect.
How many add-ons can a platform integrate at once?
There is no safe number. Count the people who will run the next one. It depends on that capacity, the operating model for each deal, and the integration debt already outstanding.