The Toronto office ran payroll on the first of every month, without fail. The Lagos team never quite knew when they'd actually get paid.
This is a composite, illustrative scenario reflecting challenges founders commonly face when operating teams across Canada and Nigeria. It does not describe a specific Lemide client or engagement.
It wasn't a budget problem. The company, a small logistics and technology outfit with a founder based in Toronto and an operating team based in Lagos, had the money. What it didn't have was one clean process that treated both teams as equally real.
Contractor and employee classification had never been formally resolved on either side. Someone was manually recalculating PAYE, CRA withholding, and pension lines every month, by hand, and getting something slightly wrong often enough that it stopped feeling like an accident.
The cost showed up quietly at first. A missed payment date here, a confused message about deductions there. Then it showed up less quietly, as good people on the Lagos side started treating late pay as a signal about how seriously the company took them, which is a reasonable read of the situation even if it wasn't the founder's intent.
Late pay became a signal about how seriously the company took its Lagos team, which is a reasonable read of the situation even when it wasn't the founder's intent.
Fixing this wasn't a matter of finding a payroll app that supported two currencies. It required someone who genuinely understood both regulatory logics well enough to design one coherent process instead of two half-solutions duct-taped together.
A unified payroll process covering CRA and Canadian employment standards on one side, and Nigerian PAYE and pension structuring on the other
Formal contractor and employee classification decisions on both sides that would survive a real audit
One coherent payment schedule that treated both the Toronto and Lagos teams equally
Documentation behind every classification decision that holds up under scrutiny from either jurisdiction
Once that was built, payroll stopped being a monthly fire drill. Both teams got paid on the same reliable schedule, with documentation behind every classification decision that would hold up under scrutiny from either jurisdiction.
The lesson wasn't that cross-border teams are inherently harder to manage. It's that "just figure out payroll" usually means someone has to own two entirely different regulatory systems at once, correctly, every month, indefinitely.
Underestimating that doesn't show up as a compliance letter right away. It shows up first as attrition on a team the founder never meant to build with two classes of paycheck.