A bolt-on programme is a repeatable process, not a series of one-off deals. Here is how to structure it so each add-on closes cleanly and the whole programme stays inside the law.
Key takeaways
STEP 01 OF 10
A platform without a written screen ends up evaluating every deal on its own terms, which is slow and inconsistent. Fix the criteria that matter to the platform's thesis — geography, service mix, owner-dependence tolerance, minimum earnings size — before the first target conversation, and hold every candidate against the same bar. This is what turns a bolt-on strategy into a programme rather than a sequence of opportunistic deals.
STEP 02 OF 10
Merger notification under Part IX turns on two size tests together: the parties' combined assets or revenue in Canada exceeding a threshold set at $400 million under s.109, and the target transaction itself exceeding a separate, GDP-indexed threshold enacted at $70 million and adjusted annually under s.110. Most single SME bolt-ons will not approach either figure on their own. What a repeated acquisition programme should still track is the parties' size “together with their affiliates” under s.109(1) — a platform's own scale, aggregated across everything it already owns, is what actually gets measured, not the add-on in isolation.
STEP 03 OF 10
This is the provision most buy-and-build programmes overlook entirely, and it carries no size threshold at all. Under Competition Act s.45(1.1), it is a criminal offence for an employer to agree with another, unaffiliated employer to fix wages or terms of employment, or “to not solicit or hire each other's employees” — punishable, on indictment, by up to 14 years' imprisonment. Any informal understanding between a platform and a seller's other business interests not to poach each other's technicians sits directly against this section. The statutory ancillary-restraints defence under s.45(4) protects a restraint genuinely tied to the acquisition itself — a non-solicit written into the definitive agreement, directly related and reasonably necessary to that transaction. A standing handshake understanding across a rollup, outside any one deal's own agreement, does not have that shelter.
STEP 04 OF 10
Most bolt-ons will run as asset purchases, both because a platform generally does not want to inherit an add-on's undisclosed legacy liabilities and because it keeps CSBFP financing available where the add-on is small enough to use it. See choosing between a share deal and an asset deal for the trade-offs, and treat the asset-purchase default as a starting position you can depart from for a specific seller, not the other way around.
STEP 05 OF 10
A founder who wants to keep skin in the business after selling to the platform can roll part of their consideration into equity in the platform rather than taking a full cash-out, deferring the related tax consequence under ITA s.85, which applies where a taxpayer disposes of eligible property to a taxable Canadian corporation for consideration including shares, on a joint election. Governance for that continuing minority stake is then typically set by a unanimous shareholder agreement under CBCA s.146, which can validly restrict the directors' powers and is binding on any future purchaser of those shares. See the rollover equity glossary entry for the mechanics in full.
STEP 06 OF 10
Each bolt-on is typically its own borrowing decision — a lender underwriting the add-on's own eligible assets and cash flow, not simply extending the platform's existing facility. Where an add-on is small enough, the Canada Small Business Financing Program's asset-based test can apply to it independently of the platform's other financing; see applying for CSBFP funding on a business purchase. A share-structured add-on with a rollover seller cannot use CSBFP dollars at all, which is one more reason the deal-structure decision in step four needs to happen before financing is arranged, not after.
STEP 07 OF 10
A programme that reinvents its closing process for each deal loses the main advantage of running a programme at all. See working through the closing checklist for the items that recur on every acquisition — corporate approvals, security discharge and registration, tax elections, employment continuity — and build a template version the deal team runs against every time, adjusting only what a specific target's structure requires.
STEP 08 OF 10
A non-competition or non-solicitation covenant from a departing seller is standard, but it only protects the platform if it is actually enforceable — Ontario's ban on employee non-competes carries a narrow exception for a seller who becomes an employee of the purchaser as part of a sale of a sole proprietorship or partnership, and the exception as written does not, on its face, extend to a corporation's share sale where the seller stays on. Confirm the covenant's enforceability against the actual structure of each add-on rather than assuming the same clause language works across every deal — see the non-competition covenant glossary entry.
STEP 09 OF 10
A platform that closes three add-ons before integrating the first one is usually building operational risk faster than it is building value. Decide, before the programme starts, how much time each add-on gets before the next search begins, and hold the platform's own management to that cadence rather than letting deal flow dictate the pace on its own.
STEP 10 OF 10
A programme that succeeds eventually changes the platform's own size, and with it the Competition Act calculus in step two — an aggregated group that has grown well past its first few add-ons may approach the notification thresholds even where any single further bolt-on would not on its own. Re-check the platform's own combined size periodically as the programme compounds, rather than assuming the “too small to matter” conclusion from the first deal still holds by the tenth.
Assuming small deals mean the Competition Act does not apply at all. The merger-notification thresholds are genuinely a non-issue for most SME bolt-ons — but the criminal no-poach rule under s.45(1.1) carries no size threshold and applies to every deal in the programme.
Treating a handshake no-poach understanding as covered by the deal's non-solicit clause. The ancillary-restraints defence protects a restraint tied to a specific transaction's own agreement — a standing understanding across the rollup, outside any one deal, does not have that shelter.
Reusing a share-deal non-compete clause on an add-on where the seller stays on as an employee. Ontario's non-compete exception for a business sale is written narrowly around a sole proprietorship or partnership sale — check it applies to the actual structure before relying on it.
Closing add-ons faster than the platform can absorb them. Deal volume without an integration cadence is usually what actually breaks a bolt-on programme, not any single acquisition's own diligence gap.
Letting the same team run sourcing and integration at the same time. A deal team stretched across finding the next add-on and absorbing the last one tends to shortchange whichever task is less urgent that week — usually integration, because it has no closing date forcing it to happen.
To illustrate the mechanics only — the figures are a drafting choice for this example, not a benchmark.
Scenario A. A platform is acquiring a $600,000 add-on as an asset purchase, cash only, no rollover. The add-on falls well under both Competition Act thresholds, is financed through a CSBFP-guaranteed term loan against its equipment and leaseholds, and closes on the platform's standard checklist in roughly the same time as the previous three add-ons.
Scenario B. The same $600,000 add-on instead involves a founder who wants to roll 30% of the consideration into platform equity and stay on as general manager. The deal now needs an ITA s.85 election, a CBCA s.146 unanimous shareholder agreement governing the founder's minority stake, and — because a share component is now involved — the CSBFP financing from Scenario A is no longer available for that portion of the price, requiring a larger vendor-financed or platform-equity-funded gap instead.
Same target, same price. The rollover request changed the tax mechanics, the governance document set, and the available financing all at once — which is why the structure decision belongs early in the process, not after terms are agreed.
The considerations at add-on one are not the same as at add-on ten.
Re-run the size and integration checks periodically rather than assuming the first deal's conclusions still hold — a programme's own risk profile is not static, even where no individual deal has changed shape.
Usually not — the party-size and transaction-size thresholds are set high enough that most single small-business add-ons fall well under both. The size test still applies to the platform's aggregated affiliated group, so it is worth re-checking as the programme grows.
Only inside the transaction's own agreement, directly related and reasonably necessary to it — that is the statutory ancillary-restraints defence. An informal understanding outside any specific deal's documentation is not protected and carries criminal exposure under s.45(1.1).
A consistent default — usually an asset purchase — makes the programme faster to run, but a founder wanting rollover equity is a real reason to depart from it on a specific deal, provided the tax, governance and financing consequences are worked through each time.
A short call is enough to map your programme's screening and closing template.
Canadian small-business transaction data is not published anywhere, so most valuations in this country quote an American benchmark. The Deavo–Treadstone Acquisition Index is a daily record of Canadian listings built to replace that: asking-price distributions by province and city are published now, and days on market, departure rates and asking-to-sale spreads follow as the series lengthens. Leave an email and we will tell you as each measure lands.
No pitch, no listings. One email as each measure is published.
