Bolt-On Acquisition Integration: A Playbook for PE Platforms in Manufacturing

Bolt-On Acquisition Integration: A Playbook for PE Platforms in Manufacturing

A bolt-on acquisition, also called an add-on, is a company a private equity (PE) platform buys to add products, plants, customers or capabilities. Integrating it well means deciding, function by function, whether to absorb it into the platform, standardize it to the platform's way of working or keep it separate.

Then do it the same way every time. The goal is a repeatable playbook, so the third add-on is easier to integrate than the first.

This guide is for PE operating partners and platform leaders running a buy-and-build strategy in manufacturing.

Key takeaways

  • Decide the integration level for each function before close: absorb, standardize or keep separate.
  • Standardize financial close, safety, quality basics and shared purchasing first.
  • Leave alone what customers buy the add-on for.
  • Run every add-on through the same 100-day plan and improve the playbook after each one.
  • Watch the platform team's capacity; it runs the business and the integration at the same time.

How is integrating a bolt-on different from a platform deal?

A platform deal builds the base: the leadership team, systems and standards the strategy will grow on. A bolt-on plugs into that base, so its integration depends on how ready the platform is to absorb it.

If you are not sure which kind of deal you have, see tuck-in vs bolt-on acquisitions.

The integration work usually falls on the platform team, which is also running the business. That is why capacity, not complexity, is often the limiting factor in a buy-and-build strategy.

The buy-and-build model only works if the platform can absorb each add-on without losing its footing. If the platform is still settling the last deal, the next one adds risk to both.

Decide the integration level for each add-on

For each function, choose one of three levels before close and write the choice down. Most add-ons need a mix of all three.

Absorb: run it on the platform from the start or soon after

  • Financial close, reporting and cash management
  • Banking, insurance and legal entity administration
  • Safety standards and incident reporting
  • Approval limits and decision rights

Standardize: keep it local, but run it the platform's way

  • KPI definitions and the weekly performance review
  • Purchasing for shared categories, such as freight, packaging and MRO supplies
  • Quality system basics: corrective actions, document control and customer complaint handling
  • Maintenance planning and critical spares

Keep separate, at least for now: protect what customers buy

  • Customer relationships and the sales team that owns them
  • Specialized processes and the people who run them
  • The brand, if customers know and value it
  • ERP, until a tested cutover plan exists

The choice can change later. What matters is that everyone knows the choice for each function on Day One.

What to standardize first

Standardize the things that protect control and visibility first. They carry low risk for customers and make every later decision easier.

  • Financial close and reporting. One calendar, one chart of accounts mapping and one monthly pack let the owner see the combined business.
  • Safety. One standard for incident reporting and the basic safety programs, because safety cannot wait for a later phase.
  • KPI definitions. On-time delivery, scrap, first-pass yield and schedule attainment measured the same way at every site.
  • Shared purchasing. Categories where the platform already buys well, as long as supply continuity is protected.
  • Approval limits. Who can approve spending, hiring, pricing and capital, written down before close.

What to leave alone

Leave alone the strengths customers pay for. Many add-ons are bought for a capability, a customer relationship or a niche process that the platform does not have.

Forcing those into the platform's standard can destroy the value the deal was meant to capture. Change them only when there is evidence that the change helps the customer as well as the platform.

What to check in a bolt-on target before close

Diligence on an add-on should answer one extra question: how hard will this business be to plug into the platform? These checks show it early.

This check is one of several reviews; see the types of due diligence in an acquisition.

  • Systems fit: which ERP, quality and maintenance systems it runs, and how its reports map to the platform's monthly pack.
  • Quality and certifications: whether its certifications and customer approvals match what the platform's customers expect.
  • Customer overlap: shared customers, conflicting pricing and any account that could object to the new owner.
  • Supplier overlap: shared suppliers and contract terms that change on a change of control.
  • Key people: who holds the critical process knowledge, and whether they plan to stay.
  • Plant capacity and condition: whether the add-on can take on volume from the platform, or will need investment first.
  • Labor agreements and shift patterns: what differs from the platform, reviewed with employment counsel.

Each answer should change the integration plan. If it does not, it was not worth asking.

A repeatable 100-day plan for each add-on

Use the same plan for every add-on, adjusted to its size and risk. Repetition is what makes the third integration faster than the first.

For how sponsors build the plan itself, see what a 100-day plan in private equity includes.

  1. Before close: turn the diligence findings into an integration thesis, the integration level for each function and a Day One plan. Operational due diligence gives you the starting facts.
  2. Day One: protect continuity. Pay, safety, customer orders, supplier payments and quality release come first. The Day One readiness checklist covers the details.
  3. Days 1 to 30: stabilize, confirm the baseline on the floor and meet the key customers and people.
  4. Days 31 to 60: absorb and standardize the functions you chose, starting with finance, safety and KPIs.
  5. Days 61 to 100: capture the agreed synergies, confirm the results with finance and hand the plan to the add-on's leadership.

The 100-day manufacturing integration checklist lists the actions behind each stage.

Make the playbook better after every add-on

A playbook gets better only if someone updates it. After each add-on, hold a short review and change the templates before the next deal.

  • What took longer than planned, and why?
  • Which Day One checks were missing?
  • Which synergies were overstated, and what evidence would have caught it?
  • Which templates should change: the Day One checklist, the KPI dictionary, the approval matrix or the communication plan?
  • Who on the platform team carried the most load, and is that sustainable for the next deal?

Keep the playbook short. A ten-page playbook that people use beats a hundred-page one that nobody opens.

When the platform team needs outside help

Bring in outside help when the integration starts to compete with running the platform. The signs are usually visible before results slip.

Outside help works best inside a clear post-merger integration strategy.

  • Two deals are closing close together, or the last add-on is not settled yet.
  • Nobody on the platform team can lead the integration full time.
  • The add-on is regulated, so quality system changes need validation and careful control.
  • The plan includes the platform's first plant consolidation or ERP migration.
  • The owner needs one independent view of progress, risks and synergies.

Our integration support for PE platform add-ons integrates each add-on onto the platform's operating system, standard work and reporting, and flags early when the platform itself needs strengthening before the next acquisition.

KPIs operating partners track in the first 100 days

Track a short set of measures, defined the same way at the platform and the add-on. Review them weekly during the first 100 days.

To size the savings behind these measures, see how to calculate synergies.

  • On-time delivery to customers
  • Safety incidents and near misses
  • Customer complaints and quality escapes
  • Retention of key customers
  • Retention of key people, such as supervisors, maintenance leads and quality managers
  • Synergies realized against the approved plan
  • Working capital and cash conversion
  • Integration milestones met on time

Common bolt-on integration mistakes

Most add-on integrations that disappoint fail in familiar ways. Check your plan against these six.

  • Treating every add-on like the platform. A small add-on needs a lighter plan, not the full platform program.
  • Forcing the ERP move in the first month. System changes made before the operation is stable put customer orders at risk.
  • Losing the founder's or plant manager's knowledge. Retention plans often cover executives and miss the people who actually run the floor.
  • Telling customers too much too early. Promise only the changes that are decided and tested.
  • Counting the same synergy twice. Savings claimed by both the platform and the add-on need one owner and one number.
  • Nobody owns the integration full time. Part-time ownership stretches a 100-day plan far beyond 100 days.

Frequently asked questions

What is a bolt-on acquisition?

A bolt-on acquisition, or add-on, is a company that a private equity platform buys to add products, plants, customers or capabilities to an existing business. It is usually smaller than the platform and is integrated onto the platform's systems, standards and leadership.

What is the difference between a platform and an add-on acquisition?

The platform is the first, larger acquisition that becomes the base of a buy-and-build strategy, with the leadership team and systems the strategy relies on. Add-ons are later, usually smaller acquisitions that plug into that base and benefit from its scale, systems and buying power.

How long does it take to integrate an add-on?

It depends on the size of the add-on, the integration level chosen for each function and whether plants or ERP systems will be combined. The first 100 days are the most intensive period, and full system or footprint changes can take longer.

Should every add-on move to the platform's ERP?

Not always, and not on Day One. Move an add-on to the platform's ERP when the benefits are clear and a tested cutover plan exists.

Until then, map its reports into the platform's monthly pack so the owner still sees one view.

Building a platform through acquisitions?

We help PE platforms integrate manufacturing add-ons hands-on, from the Day One plan through the first 100 days. Talk with our team before your next close.

Schedule a Call or call 717-707-7826.