A helpdesk clause turned an amicable manufacturing buyout into a billing standoff

The situation

Saskia had worked for Despina for eleven years, first on the shop floor of Despina's manufacturing business and later as its general manager, before Despina decided to retire and sell. The two of them had a good relationship by any measure. Despina trusted Saskia enough to sell to her directly rather than run an open sale process, and Saskia trusted Despina enough to agree to a purchase price of just under six million dollars without hiring her own valuation expert, something we would later tell her not to repeat.

Saskia could not fund the purchase alone, so she brought in Anneke, her partner and the owner of a chain of clinics, to co-invest and guarantee part of the financing. Anneke had no background in manufacturing and no interest in running the business day to day, but she understood contracts and cash flow, and it was Anneke who first flagged that the deal's transition services agreement was thin. That agreement was meant to cover the period after closing when Despina's company would keep providing IT support, payroll processing and supplier account management to the newly independent business while Saskia built her own systems.

The agreement Saskia and Despina had shaken hands on, and which our office had not drafted, described the support in general terms and set a monthly fee without specifying what fell inside it. For the first two months after closing, that vagueness did not matter, because Despina's staff handled routine requests without comment. In the third month, Saskia's factory had a significant IT failure that took two of Despina's technicians most of a week to resolve, and the invoice that followed was nearly four times the usual monthly fee, itemized as emergency support outside the agreement's normal scope.

Saskia disputed the bill. Despina's response was polite but unmovable: her company had absorbed the cost of keeping technicians on call, the agreement did not promise a fixed scope, and if Saskia wanted a different arrangement she was welcome to build her own IT department instead of relying on Despina's. It was a fair point in principle. It also came from someone who did not need the money and could afford to let the dispute run, while Saskia's business, months into a new loan, could not.

Anneke pushed back hard on Saskia's instinct to simply pay the invoice and avoid conflict with a woman Saskia had reported to for over a decade. Anneke's own clinics had been through their own supplier disputes, and she recognized the shape of this one: a well-funded party letting an ambiguous contract do the talking, confident the other side would fold rather than fight over what looked, on paper, like a modest sum. To Despina it likely was modest. To Saskia's newly leveraged business, it was not.

The legal question

The transition services agreement Saskia had signed was a real contract, and Despina's company had performed real work, so the dispute was never about whether Saskia owed anything. The question was what the agreement actually promised, and whether Despina's company could unilaterally define emergency support as outside its scope after the fact, when the agreement itself never used that phrase.

We read the agreement closely and found it described the services as ongoing IT support, payroll processing and supplier account management, without a defined service level, without a list of exclusions, and without a mechanism for either side to flag work as chargeable above the base fee before it was performed. That absence cut both ways. It meant Despina had some room to argue that anything beyond routine, business-hours support fell outside the deal. It also meant Despina had never secured Saskia's agreement, in writing, to pay a premium for exactly the kind of emergency response her technicians had just provided.

Contracts like this are read as a whole, and courts and negotiating parties alike generally look for what the parties objectively intended at the time of signing, not what either side later wishes they had written. On that standard, a general commitment to IT support that had, in practice, covered two months of routine requests without incident supported Saskia's expectation that the fixed fee covered ordinary operations. But a single sentence in the agreement, easy to miss on a first read, gave Despina's company the right to charge separately for services requiring more than eight hours of technician time in a single incident. The failure had taken roughly thirty-two hours across two technicians. Despina was not making the surcharge up. She was, however, applying it retroactively to a bill Saskia had never been warned was coming, and pricing it well above what the same work would have cost from an outside IT contractor.

That gap between what the contract technically allowed and what a reasonable business relationship would expect was where the dispute actually lived, and it was not going to be resolved by either side insisting they were completely right.

There was a further wrinkle worth naming plainly. Despina's company was substantially larger and better resourced than Saskia's newly independent business, and Despina was not shy about pointing that out during their one direct conversation about the bill, noting she could simply let the invoice sit unpaid and pursue it through her own lawyers on her own timeline if Saskia wanted to make an issue of it. That was not itself improper. A party is entitled to rely on its resources in a negotiation. But it meant the legal question and the practical question were not the same thing, and any strategy that only answered the first while ignoring the second was going to leave Saskia worse off regardless of who was technically correct.

What we did

1. Reviewed the full transition services agreement line by line rather than relying on the disputed invoice alone, because we needed to know whether Despina's eight-hour surcharge clause was an isolated provision or connected to other pricing terms elsewhere in the document. It turned out to be the only pricing mechanism beyond the flat monthly fee, which meant every argument about the invoice's fairness would have to run through that single sentence rather than a broader pattern of undisclosed pricing terms.
2. Documented the first two months of routine support Despina's staff had provided without additional charge, using Saskia's own service logs and email records, to establish a clear baseline for what both sides had, in practice, treated as covered by the flat fee before the disputed invoice arrived. This mattered because it showed the parties' actual course of dealing, not just the words on the page.
3. Obtained comparable quotes from two independent IT support providers in the region for equivalent emergency response work, specifying the same failure scope and after-hours timing so the comparison would hold up if challenged. This gave Saskia a concrete benchmark for what the disputed charge should have cost if priced at a market rate rather than set unilaterally by the party billing it, and it turned a subjective sense that the invoice felt high into a number we could put in front of Despina's company directly.
4. Sent a written response to Despina's company disputing the amount, not the principle, conceding that the surcharge clause was valid and that some premium was fair, while laying out the market comparison to show the invoiced amount was roughly double a reasonable rate. This avoided a fight Saskia could not win about whether any surcharge applied at all, and it forced Despina's side to respond to a specific number rather than to a general complaint that a court or a negotiator could easily wave off as sour grapes.
5. Proposed a formal amendment to the transition services agreement that replaced the vague eight-hour trigger with a defined schedule of rates for after-hours and emergency work, capped at a stated multiple of the base monthly fee, so neither side would face another unpriced surprise before the transition period ended. This gave both sides a document to point to instead of a memory of a conversation, which mattered given how differently Saskia and Despina had each understood the original handshake arrangement.
6. Negotiated directly with Despina's lawyer once she retained one, which slowed things down initially but ultimately helped, since it moved the conversation from a personal disagreement between two people who had worked together for over a decade into a structured commercial negotiation both sides could exit from without damaging the relationship further. Routing the discussion through counsel also meant every concession was recorded in writing rather than left as an informal understanding that could later be remembered differently by either side.
7. Advised Saskia and Anneke to begin transitioning IT support in-house on a fixed timeline regardless of how the dispute resolved, since the underlying problem was dependency on a seller with no ongoing incentive to keep prices reasonable, not just the specific invoice in front of them. Setting a concrete date for the switchover, rather than leaving it open-ended, gave Saskia's own hiring plan a deadline to work backward from and removed Despina's company as a single point of failure for the business's daily operations.
8. Kept Saskia out of direct back-and-forth with Despina once the dispute moved to lawyers, routing all further communication through counsel on both sides. Given the length and closeness of their working relationship, direct exchanges risked becoming personal in a way that made compromise harder, and a structured negotiation between lawyers gave both women room to reach a commercial outcome without either having to concede the argument face to face.

The outcome

Despina agreed to reduce the disputed invoice by close to forty percent, reflecting the market rate comparison rather than her original figure, and both sides signed the amended transition services agreement with the capped rate schedule going forward. Saskia paid the reduced invoice within two weeks of the amendment being signed, and the remaining transition period, roughly four months, ran without another disputed bill.

This was a negotiated compromise, not a clean win. Saskia still paid meaningfully more than she believed the original emergency support should have cost, and Despina's company never conceded that its initial invoice had been improper, only that a lower figure was commercially sensible given the ongoing relationship and the cost of a drawn-out dispute. Anneke, whose financing was tied to the business's early cash flow, absorbed the payment as a cost of an imperfectly drafted agreement rather than a legal defeat, which is a more accurate way to describe it.

Saskia's IT department was operating independently within five months of closing, well ahead of the original transition timeline, largely because the dispute made clear that relying on Despina's goodwill was not a stable long-term plan. The manufacturing business itself was not disrupted at any point; the failure that triggered the dispute was resolved, production continued, and the disagreement stayed contained to a billing question rather than spilling into the operating relationship both women needed to preserve for the following months.

Despina and Saskia continued speaking after the dispute closed, though the tone between them was noticeably more formal than before, with most substantive matters now handled through the amended agreement's written terms rather than the informal calls that had characterized the first two months of the transition period. Saskia later said the dispute had cost her more in stress than in dollars, though the dollars were real too, and it left her far more careful about what a handshake actually covers once money and a decade-long relationship are on the same table.

What you can learn from this