Fixing a Founder's Signature Habits Before They Caused a Problem

The situation

Arben and Bikash had known each other for almost a decade before they ever did business together, first as neighbours and then as friends who occasionally traded favours: Bikash, who worked as a security guard and picked up shifts flexibly, would help move equipment for Arben's growing company on his days off, and Arben would return the favour in kind. Arben had spent years as a letter carrier before starting the company evenings and weekends, and it had grown, slowly and mostly through word of mouth, into a modest operation doing under a million dollars a year connecting local businesses with short-term staffing and logistics support, run largely out of his kitchen table before he could finally step away from the letter carrier job entirely. When the company needed a reliable subcontractor for a larger client engagement, bringing Bikash in felt less like hiring a vendor and more like formalizing something that had already been working informally for years.

That informality carried straight through into how the arrangement got documented, which is to say it barely did. Arben had emailed Bikash a summary of the terms, the scope of work, the rate, and a rough timeline, and Bikash had replied with a thumbs-up emoji and started the work the following week. No one signed anything. It was, in Arben's mind, the same kind of arrangement they had always had, just with more money attached this time.

The relationship soured about four months in, after a disagreement over whether a set of additional tasks Bikash had performed fell inside the original scope or represented extra work owed additional payment. What had been a friendly disagreement between neighbours became, within a few weeks, an actual dispute over several thousand dollars, with Bikash pointing to the email as proof of the agreed rate for everything he had done, and Arben pointing to the same email as proof the additional tasks were never part of it.

Arben came to us not because the dollar amount was large in absolute terms, but because he realized, mid-argument, that he had no idea whether the email exchange even counted as a binding agreement, and no better answer for any of the roughly dozen other arrangements the company had running the same way with other vendors and clients. He had tried, for about two weeks before calling us, to sort it out directly with Bikash over increasingly terse text messages, and had only made the disagreement more personal in the process.

The risk we had to size

The first question was narrow: was the email exchange between Arben and Bikash a binding agreement at all, and if so, on whose terms? Under general Ontario contract principles, a contract does not need a wet-ink signature or a corporate seal to be enforceable; an exchange of emails setting out clear terms, followed by one party's performance and the other's acceptance of that performance, can form a binding agreement even without any formal signing step. That cut against Arben's instinct that nothing was truly agreed until someone signed a document, and it meant the dispute could not be resolved simply by pointing out that nothing had been formally executed.

The harder question, and the one that actually mattered for pricing the risk, was what the email's terms covered. Arben's original message described the scope in general language that could plausibly be read either way; specific enough to define the core engagement, vague enough to leave real room for a genuine disagreement about the additional tasks, rather than one side simply being wrong. That ambiguity made the dispute a real coin flip rather than a case with an obvious winner, which changed the entire calculation about whether to fight it out or settle it.

Underneath that one dispute sat a much larger exposure. Once we asked Arben how many other arrangements the company had running the same way, informal email exchanges, verbal understandings, the occasional agreement scratched out over a coffee meeting, he counted roughly a dozen active relationships with no consistent documentation standard at all. Some had more detail than others; none had a signature, a defined acceptance process, or a record of who at the company had actually agreed to the terms on the company's behalf. For a company his size, that was less a single legal problem than a structural one: every one of those dozen relationships carried the same ambiguity that had just cost him weeks of stress over one disagreement with a friend.

The risk we ultimately had to size for Arben was not just the current dispute's dollar value, which sat in the low thousands either way it resolved. It was the cost of doing nothing about the underlying practice: a company that would keep generating disputes shaped exactly like this one, with a client or vendor list eventually large enough that the next disagreement would not be with a friend willing to have a reasonable conversation about it.

What we did

1. Reviewed the full email chain to establish what had actually been agreed. Rather than starting from either side's current position, we read the original scope email and every follow-up exchange in sequence to identify exactly which terms were clearly settled and which were genuinely ambiguous, since an honest read of the record, not advocacy for either interpretation, was what would let us give Arben a realistic assessment of his position.
2. Assessed the likely outcome of pushing the dispute to a formal claim. We walked Arben through what pursuing or defending the disputed amount through a small claims process would actually involve, the time it would take, the cost relative to the amount in question, and the real uncertainty given the ambiguous scope language, so he could weigh that path against a negotiated resolution with accurate expectations rather than a gut sense of who was right.
3. Proposed a split settlement reflecting the genuine ambiguity. Rather than accepting either side's full position, we suggested a compromise figure covering roughly half of the disputed additional-work amount, reasoning that a genuinely ambiguous scope description meant neither party had a strong enough position to justify holding out for the full amount, and that a fast resolution was worth more to Arben than a marginal chance at winning everything.
4. Negotiated the settlement directly with Bikash, preserving the relationship where possible. We handled the settlement conversation in a way that kept it focused on the contract ambiguity rather than on the personal disagreement that had crept in through the text messages, which let both sides agree to the compromise without either having to concede they had been wrong about the friendship itself.
5. Audited the company's other active arrangements for the same gap. With the immediate dispute resolved, we reviewed the roughly dozen other client and vendor relationships Arben had identified, sorting them by how much documentation actually existed for each and flagging the ones with the least, and therefore the most exposure to a repeat of exactly this problem. The largest, a standing arrangement with Sunita, who supplied warehouse staff for the company's biggest recurring client, had never been documented beyond a single opening email from two years earlier, and we flagged it as the first conversion once the new process was in place.
6. Amended the company's by-laws to formally adopt electronic signing. Rather than leaving the new practice as an informal office habit that could quietly lapse, we drafted a by-law amendment for Arben, as sole director, to pass, formally authorizing electronic signatures as the company's standard execution method and requiring a defined electronic signature step, not just an email exchange or a thumbs-up reply, for any engagement above a modest dollar threshold.
7. Set up a straightforward electronic signing tool and a document retention habit. We helped Arben select and configure a simple electronic signing process suited to a company his size, and set a basic habit of saving every signed agreement to a single dedicated folder, so the next dispute, if one arises, starts from a clear signed record rather than a scattered email history.

The outcome

Bikash accepted the compromise figure, roughly half of the disputed additional-work amount, within about two weeks of the settlement proposal going to him. Neither side got what they had originally claimed was owed, and the settlement did not resolve the underlying question of whether the original email had actually covered the additional tasks; it simply made that question moot by splitting the difference both men could live with.

The friendship did not fully recover the easy footing it had before the dispute. Arben and Bikash still work together occasionally, but the relationship is now handled through the same signed-agreement process Arben adopted for every other engagement, rather than the informal understanding that had defined a decade of favours between them. Arben was candid that this was a real loss, even if a modest one, and not something the settlement money offset.

The larger result was in the dozen other relationships the dispute exposed. Of those, four were converted to signed agreements under the newly amended by-laws within the following two months, starting with Sunita's staffing arrangement given the size of the client it supported, closing exactly the kind of ambiguity that had produced the Bikash dispute in the first place. The remaining arrangements are being brought into the process gradually as they come up for renewal, rather than all at once, which Arben chose deliberately so the change would not read to longstanding contacts as a sudden loss of trust. The company has not had a comparable dispute since adopting the by-laws amendment, though Arben is realistic that the real test will come with a counterparty less willing than Bikash was to settle quickly rather than dig in.

Arben has also started keeping a simple internal log noting which relationships still run informally and roughly when each is due to come up for renewal, so the remaining conversions do not quietly stall the way the original documentation gap did for years before the dispute forced the issue. He was candid, looking back, that the two weeks he had spent trying to resolve things directly with Bikash over text had mostly made the underlying dispute more personal without getting any closer to an answer, and that calling for advice earlier, before the disagreement hardened into something harder to walk back, would likely have cost him less in the end.

What you can learn from this