Bolt-on acquisition

Also called Tuck-in acquisition

Bolt-on acquisition at Hanil Widget Works

Fictional teaching case. Hanil Widget Works is an invented company used for this example.

Hanil Widget Works itself was the platform in this deal, the foundational buy chosen for its management and specialty alloy supply relationships.

Separately, in a hypothetical, an existing platform buys a competitor’s product line for US$4m and integrates its customers and capabilities. That purchase is a bolt-on; the amount is illustrative, not a Hanil transaction fact.

Test what the platform can actually absorb

Hypothetical operating review, separate from Hanil. A maintenance platform is considering a smaller competitor with customers in a neighboring territory.

The proposed benefit is serving both customer groups from the platform’s existing dispatch office.

Check whether dispatch has spare capacity, whether technicians can reach the added customers on time, and whether both businesses use compatible service records. If the combined routes need another dispatcher and extra travel time, the assumed saving may shrink or disappear.

The acquired customer list alone does not establish the benefit.

Write the operating plan alongside the price: who transfers the records, who retains the customer relationships, what transition work costs and when duplicate spending can stop. A smaller company can fit the definition of a bolt-on while failing this particular integration plan.