The situation
The deal closed on a Friday in early June, right as the landscaping season in Guelph was hitting its stride. A private-equity-backed buyer building a small portfolio of home and commercial services companies had just completed an asset purchase of a landscaping business for roughly $5.5 million, bringing on its two founders, Kwame and Luc, as employees for a transition period. Kwame had started the company himself years earlier as a working landscaper before hiring his first crew; Luc had joined a few years later, having spent his earlier career as a line cook before deciding he wanted to build something of his own outdoors instead of in a kitchen. Together they had grown the business into one worth acquiring.
Rejean, the platform's integration lead, retained our team the week after closing. His job was to fold the newly acquired company into the platform's shared back office within a matter of weeks: a single bank account structure for cash management, a unified payroll system, and centralized invoicing software replacing the standalone tools the founders had used for over a decade. The purchase agreement included a transition services agreement, a short-term arrangement where the sellers agreed to keep operating certain systems and support the handover for a fixed number of weeks after closing. The clock on that agreement was already running.
What the transition uncovered
The trouble surfaced within the first ten days. The transition services agreement had been drafted during the deal's final rush and gave the buyer only four weeks of the sellers' cooperation to migrate banking, payroll and the client billing system. Nobody had accounted for the fact that late June and July were the company's highest-volume invoicing months, when roughly sixty active landscaping contracts needed to be billed on staggered schedules the sellers' old system had been customized to handle for years. Migrating banking and payroll was the easier half of the job. Migrating the billing logic without dropping or double-charging a client was the part that could not be rushed.
Kwame and Luc, for their part, had their own pressure. About $550,000 of the purchase price, roughly ten percent, sat in an escrow holdback — money held back from the sale proceeds and released to the sellers later, once the buyer confirmed there were no undisclosed liabilities or warranty breaches in the business it had bought. The holdback was scheduled to release in two installments over the following year. With the four-week transition window closing and both founders increasingly needed on active job sites rather than in front of a computer walking a new bookkeeper through invoicing quirks, Luc told Rejean plainly that once the four weeks ended, he considered his cooperation obligation finished, holdback or no holdback.
That put the buyer in a difficult spot. Forcing a systems cutover before billing logic was fully mapped risked missed or duplicate invoices on the company's busiest month of the year — the kind of operational stumble that erodes client trust in exactly the business a PE platform had just paid a premium to acquire. But the transition services agreement gave the buyer no contractual right to compel the founders to keep helping past the four-week mark, and going back to court to force the point would have taken far longer than the problem itself.
What we did
- Read the transition services agreement for leverage, not just obligations. The agreement was short on the buyer's rights but it also gave the sellers no independent right to accelerate the holdback release. That gave both sides something the other wanted — the buyer wanted more weeks of help, the sellers wanted their money sooner — and a trade became possible.
- Mapped the billing migration into discrete phases. Rather than ask for open-ended cooperation, we worked with Rejean's operations team to identify exactly which parts of the billing system still needed the founders' input: about three weeks of focused work covering the highest-complexity contracts, not the full client list. That let us ask for a specific, bounded extension rather than an indefinite one, which made it an easier request for Luc and Kwame to say yes to.
- Proposed an early partial release of the holdback in exchange for a two-week extension. We recommended releasing about $200,000 of the $550,000 holdback immediately, ahead of its scheduled date, conditioned on Kwame and Luc providing defined hours of support each week through the extension period. The buyer kept the remainder of the holdback in place as protection against any warranty issues that might still surface.
- Put the new terms in a short written amendment, not a handshake. The original transition services agreement was amended to specify the extended end date, the weekly hours each founder would commit, and the amount and timing of the early release. This mattered because an informal understanding about a bit more help is exactly the kind of thing that unravels under the pressure of a busy season — a signed amendment meant everyone knew precisely what was owed.
- Sequenced the banking switch around, not during, the busiest billing week. We advised moving the bank account and payroll migration to a lower-volume week in the cycle, while leaving the client billing software running in parallel with the new system for a short overlap period so nothing was cut over cold.
- Confirmed payroll continuity obligations under the Employment Standards Act, 2000. Because the founders and several long-serving crew members were continuing as employees of the buyer, we confirmed how their length of service and accrued entitlements carried forward, so payroll migration did not inadvertently create a gap in vacation pay or other statutory entitlements during the switch.
The outcome
The compromise held. Kwame and Luc agreed to the extended, defined-hours transition in exchange for the early partial holdback release, and the amendment was signed within a week of the dispute surfacing — well inside the original four-week window, so no days were lost to negotiation. The banking and payroll migration happened in a single lower-volume week with no missed pay runs. The billing system conversion took the full extended period, running about five weeks in total rather than four, with the old and new systems operating in parallel through the busiest stretch. No client invoices were dropped or duplicated.
It was not a clean win for either side. The buyer paid out roughly $200,000 of the holdback earlier than planned, giving up some of the leverage that money represented if a warranty issue turned up later. The remaining $350,000 stayed in escrow on its original schedule, so the buyer's core protection was intact, but it was a smaller cushion than before. Kwame and Luc, in turn, gave up their claimed right to walk away after four weeks and worked a fifth week each at defined hours during what should have been their transition out of the business — not what either of them had planned when they signed the original deal. Both sides left the table having conceded something real, which is usually the sign that a compromise was actually necessary rather than merely convenient.
Three months later, the acquired business was fully integrated into the platform's back office, and Rejean reported that client retention through the transition period held steady, with no client complaints tied to the systems switch. The episode became a template the platform's integration team reused on its next two acquisitions: build transition services agreements around the buyer's actual seasonal calendar from the start, rather than a generic number of weeks, so the same scramble does not repeat itself.
What you can learn from this
- A transition services agreement should be built around the target company's actual operating calendar, not a generic number of weeks — a landscaping company's busiest billing month is not the time to be short on the sellers' cooperation.
- An escrow holdback protects the buyer, but it is also leverage the sellers eventually want back. Both sides having something the other wants is often what makes a mid-integration dispute solvable without litigation.
- Sequence system cutovers around your predictable high-volume periods, and run old and new systems in parallel through the transition rather than switching cold on a single date.
- Verbal understandings about extended cooperation do not survive a busy season. Put any renegotiated terms — hours, dates, payment amounts — into a written amendment before work resumes.
- When employees carry over to a buyer after closing, confirm how service length and accrued entitlements transfer before payroll systems switch, so a systems migration does not accidentally create a statutory compliance gap.
This is a mergers & acquisitions problem we handle
Start a file online — flat, published fees, reviewed by a licensed lawyer before a dollar is owed.