Cutting off a building's IT vendor was harder than it looked

The situation

Miriam's plan was ordinary building-management housekeeping. She owned a small commercial building in St. Catharines with a handful of office tenants, and the building's shared network, security cameras, and building-access system were all managed under a contract with a managed services vendor that had been in place since before she took over day-to-day management of the property. The contract had run for two years without much drama, but service had been slipping: slow response times, a camera system that had gone down twice without a clear explanation, and a growing sense among her tenants that something needed to change before a real security gap turned into a real problem.

Miriam worked as a security guard on rotating shifts and managed the building on the side, an arrangement that had worked well enough because the previous owner, her late husband, had set most of the systems up years earlier and she had mostly just kept them running the way he left them. Her daughter Kayla, an auto body technician, sometimes helped her deal with contractors on her days off, since Miriam's rotating schedule made it hard to be available during regular business hours when vendors typically wanted to schedule site visits and service calls.

When the vendor missed a third service response deadline in a row, this time leaving the building-access system malfunctioning for most of a weekend and leaving two tenants unable to get into their own offices on a Saturday, Miriam decided she had had enough and wanted to end the contract for good. Her brother-in-law Dov, who worked in a different technical field entirely and had strong opinions about IT contracts generally, offered to help her draft the termination letter, and Miriam, wanting to move quickly and not wanting to spend money on a lawyer for what seemed like a simple cutoff, took him up on it gratefully.

Dov's letter was assertive and detailed, listing every complaint Miriam had accumulated about two years of service and declaring the contract terminated immediately for cause, effective the date of the letter, with no further payment owed to the vendor at all. It felt satisfying to send, a clean and decisive end to a frustrating relationship. The vendor's response, arriving a week later from their own lawyer, was not what either of them expected, and it turned a simple cutoff into a genuine legal dispute almost overnight.

Why this was harder than it looked

Terminating a services contract for cause is not simply a matter of declaring that the other side failed to perform. Most contracts of this kind, including the one Miriam had signed years earlier, set out a specific process for termination: a notice period, an opportunity for the vendor to cure the identified failures, and defined categories of breach that qualify as cause in the first place. Dov's letter had skipped past all of that, treating the cutoff as effective immediately based on a list of grievances that had accumulated over two years but had never gone through the contract's own notice-and-cure steps in writing.

The vendor's lawyer seized on exactly that gap. Their position was that Miriam's letter was itself a breach of the contract, an improper attempt to terminate without following the required process, and that the vendor was entitled to continue billing under the agreement for the remaining term, plus damages for the improper termination, unless Miriam reinstated the relationship or negotiated a formal exit on terms the vendor found acceptable. It was an aggressive position, but not one built entirely out of nothing.

What made this genuinely harder than a straightforward service dispute was that Miriam's own letter had, without meaning to, undercut her strongest arguments. The service failures were real and reasonably well documented in her own emails and call logs with the vendor over the prior months, including the weekend the access system had left tenants locked out. But by terminating immediately rather than issuing a proper notice and cure period first, she had handed the vendor a technical basis to argue that her side, not theirs, had breached the agreement first, and that argument threatened to overshadow the substance of her actual complaints.

The dispute sat in the range of several tens of thousands of dollars once the vendor's claim for continued fees and alleged damages was added to the cost of urgently sourcing a replacement provider for the building's network, cameras, and access systems. Miriam needed a path that acknowledged the mistake in how the termination had been handled without simply accepting the vendor's full position, and that let her building's systems get properly and safely transitioned without an extended legal fight eating up whatever she might otherwise have saved by leaving in the first place.

What we did

1. Reviewed the termination letter Dov had sent against the contract's actual notice-and-cure provisions, confirming that the immediate termination had not followed the required process and assessing precisely how much legal exposure that gap had created for Miriam. This came first because everything else in the file, from the strength of the vendor's damages claim to how hard we could push in negotiation, depended on knowing exactly how exposed Miriam's own letter had left her.
2. Gathered the underlying service records, including Miriam's emails, call logs, and a detailed account of the weekend the access system had failed and locked tenants out, to establish that the vendor's performance problems were real and well documented, regardless of how the termination letter itself had been worded. This record became the counterweight to the vendor's process argument, showing a court or the vendor's own lawyer that Miriam's underlying complaints had substance even if her paperwork had not.
3. Sent a corrective notice to the vendor that formally invoked the contract's cure provisions based on the documented failures, effectively restarting the termination process on proper contractual footing while preserving every one of Miriam's underlying complaints for later use. This mattered because it converted an improper unilateral cutoff into a defensible contractual position, closing off the vendor's strongest argument without abandoning the substance of what Miriam had already said.
4. Opened direct negotiation with the vendor's lawyer rather than litigating the dispute over the first letter, since a prolonged fight focused narrowly on a drafting mistake would have cost far more in legal fees than it was ever likely to recover for Miriam. Negotiating early also let us frame the conversation around the vendor's real performance record rather than the technical breach argument the vendor's lawyer preferred to lead with.
5. Pushed back on the vendor's damages claim, arguing that the vendor's own repeated service failures materially reduced or eliminated any entitlement to fees for the period in question, using the documented outage record and missed response deadlines as leverage. This shifted the negotiation from a conversation about Miriam's drafting mistake to one about the vendor's own performance, which is where her actual strength in the file had always been.
6. Negotiated a defined exit date and a reduced final payment, closing out the contract on terms that reflected both sides' real positions and real leverage rather than either party's opening demand or opening threat. Settling on a fixed date also let Miriam plan the vendor transition with certainty instead of leaving the building's systems in limbo while the dispute dragged on.
7. Coordinated the transition to a new vendor so the building's network, cameras, and access system were handed over cleanly and without a gap in coverage, with Miriam retaining the full documentation history in case any system issue surfaced with the new provider down the road. A clean handover mattered because a coverage gap during the switch would have created exactly the kind of tenant complaint that started the whole dispute in the first place.
8. Set up a simple written log for Miriam and Kayla to use going forward, recording any future service issue with a date and short description, so any later dispute would start from a clear, contemporaneous record rather than reconstructed memory. This directly addressed the gap that had hurt Miriam here, where informal complaints existed but had never been organized into something a lawyer could use quickly under time pressure.

The outcome

The dispute settled with Miriam paying a reduced final amount to the outgoing vendor, roughly covering a partial notice period rather than the full ongoing fees and alleged damages the vendor had originally claimed in its lawyer's letter. In exchange, the vendor dropped its claim that Miriam's original termination had been an improper breach, and the contract closed out cleanly with both sides signing releases against any further claims arising from the relationship.

It was a compromise, not a clean win, and it is worth being honest about that. Had the termination been handled correctly from the outset, following the notice-and-cure steps the contract actually required, Miriam likely would have had a stronger argument to end the contract for cause with no further payment owed at all, given how well documented the underlying service failures genuinely were. The corrective notice process meant conceding some ground that the original letter's mistake had cost her, and the final payment, while meaningfully reduced from the vendor's opening demand, was still money she had not expected to owe when she first decided to cut ties with a vendor she felt had let her down.

Miriam's building has since moved to a new IT provider without further disruption to tenants, and she keeps a more careful written record of service issues as they arise, with Kayla helping log dates and details as problems come up. She has also told Kayla and Dov, without any hard feelings on either side, that any future contract termination goes through the office first, before any letter goes out, however satisfying it might feel to send one quickly.

What you can learn from this