Fresh investor capital can reach a Tunisian fintech before payroll because investment and salary payments travel through different systems, with different checks, intermediaries and failure points. A funding transfer may be handled as one closely monitored transaction, while payroll requires dozens of accurate, compliant payments to individual accounts.
In 2010, Taavet Hinrikus and Kristo Käärmann faced a smaller version of the same mismatch between where money sat and where it needed to arrive. Hinrikus earned euros in Estonia but lived in London. Käärmann earned pounds in London while paying expenses in Estonia. Moving money through their banks meant delays and exchange-rate costs.
They found another route. Hinrikus sent euros from his Estonian account to Käärmann’s Estonian account. Käärmann sent the equivalent amount in pounds from his British account to Hinrikus’s British account. The money required by each person was already inside the country where it would be spent.
That arrangement became the starting point for TransferWise, now Wise. The BBC has documented how the two Estonian founders built the company around avoiding unnecessary international movement by matching money flowing in opposite directions.
The useful detail is easy to miss: their first improvement came from changing the path, rather than making the existing cross-border transfer slightly faster.
One transfer can hide a broken payment path
Consider the Tunisian founder watching investment capital appear in the company account on Thursday. Payroll is due on Friday.
The incoming transfer feels like proof that the hard part has passed. The investor completed the paperwork. The bank accepted the funds. The balance is visible.
Yet the salary file can still fail.
Investor capital arrives as one transaction between known parties, often prepared in advance with supporting documents. Payroll turns that balance into many separate obligations. Each payment depends on correct employee details, account information, approval timing, the company’s banking setup and any checks triggered along the route.
That difference matters. A large transfer can complete while a smaller salary payment waits for a correction. Money in the account proves that the company has cash. It does not prove that every employee can receive it on time.
Founders often discover this distinction late because the dashboard shows a balance, not a delivery path. Thursday’s number looks available. Friday reveals which part of it is operationally usable.
Payroll needs its own runway test
I would treat payroll readiness as a product test with a deadline, rather than an administrative task at the end of the week.
The first question is simple: what must happen between the company balance changing and an employee seeing cleared funds?
Write down that path for every country involved. Include who prepares the payment file, who approves it, what information the bank checks, where a manual review can begin and how the team confirms receipt. If one employee is paid through a different account type or country, that route deserves its own test.
Then work backwards from payday. A founder operating across Tunis, Berlin and Accra cannot assume that one successful route proves the others. Different currencies, banking relationships and compliance checks create separate points of uncertainty, even when every salary starts from the same company account.
This is the same reason I separate cash availability from cash timing when payroll competes with another urgent bill. The decision is explored more directly in what happens when payroll and the cloud bill compete for the same cash. A balance can cover both on paper while the payment sequence still leaves one obligation exposed.
The practical test should happen before the full payroll run. Send a permitted test payment through each important route, verify the recipient details, record how confirmation arrives and keep enough time to correct a rejection. Do not call the path reliable because it worked last quarter. Account changes, new hires and new countries alter the route.
The constraint sits between balance and receipt
The TransferWise story maps neatly because Hinrikus and Käärmann stopped treating international movement as the only way to solve an international money problem. They asked where the required currencies already existed, then designed around that fact.
A Tunisian fintech founder facing payroll Friday needs the same kind of distinction. The problem may sit outside fundraising and outside the payroll calculation. It may be the route between a funded company and the people owed money.
That changes the founder’s next call.
Another investor update will not fix missing employee details. A larger buffer will not correct an approval held by one unavailable administrator. Faster payroll software will not remove a banking review. Each fix belongs to a different part of the path.
I would assign one owner to prove delivery, not merely submission. That person should know which payments cleared, which remain pending and what evidence is needed to resolve each exception. “The file was uploaded” is an activity. “Every employee received cleared funds” is the outcome.
By Thursday afternoon, the founder should be looking at a short exception list, not discovering the payment system for the first time. That is the operating lesson inside the TransferWise origin story: inspect where value already sits, map where it must arrive and redesign the route around the constraint between them.
Comments
No comments yet.