Software Licences That Would Not Have Survived the Sale

The situation

What worried Giulia was not the sale price. It was the picture of Jelena and Milica showing up on their first Monday as owners, a customer calling to book an emergency drain job, and nobody being able to pull up the schedule, the customer history, or the parts inventory that made the business run. Giulia had built that system over eleven years, piece by piece, and she knew, in a way that is hard to explain to someone who has not run a service business, exactly how much of the company's value lived inside software that nobody thinks about until the moment it stops working entirely.

Giulia was selling because a health diagnosis earlier that year had made it clear she could no longer manage the physical demands of the trade or the administrative load of running a plumbing supply and service company that employed six technicians and served a wide radius around Napanee, from small residential repairs up to larger commercial contracts. She had found a buyer relatively quickly once the business went on the market. Jelena, who had worked for years as a librarian and wanted a business she could run day to day with her partner Milica, was ready to move forward, and the two of them had lined up financing based largely on the company's existing service contracts and its steady base of repeat customers. The deal was priced at $1.15 million, reflecting the service trucks, the shop inventory, and eleven years of customer relationships, a figure both sides had agreed to well before the file ever reached our office.

The file had started with another lawyer, who had handled the early agreement of purchase and sale and most of the standard corporate due diligence before a scheduling conflict forced a handoff partway through the transaction. By the time it reached our office, the deal structure, the purchase price, and the closing date were all already locked in and agreed between the parties. What had not been finished was a full review of the operational systems the business actually depended on day to day to function, and that gap, sitting between the corporate paperwork and the shop floor, was exactly where the real risk was sitting unnoticed.

Giulia herself raised the concern almost in passing during an early call with us, mentioning that she had once tried to add a part-time dispatcher to the scheduling software account and been told by the vendor's support line that licences were tied to her personally rather than to the company as a whole. She had not thought much of it at the time, since it had never actually stopped her from working. It became the first thing we checked once the file landed on our desk.

The risk we had to size

The plumbing business ran on three pieces of software that genuinely mattered to daily operations: a scheduling and dispatch platform that every technician used from a phone in the truck to get their next job, an inventory system tracking parts across the shop and two service vehicles, and a bookkeeping platform tied to the company's accounts and payroll. All three had been purchased years apart, under different account structures set up at different times, and none of them had ever been reviewed with an eye to what actually happens to the account on a change of ownership.

The scheduling platform turned out to be the serious problem. Its licence agreement, which Giulia had accepted electronically years earlier without reading it closely, the way almost everyone does with software terms, was written as a personal subscription that was non-transferable to a new account holder without the vendor's separate approval, and neither the licence itself nor any general industry practice said how long that approval would take. There was no standard timetable to rely on; the only way to know was to ask this particular vendor directly and get the answer, and the approval, in writing before closing. If ownership changed hands and the account simply carried over informally without anyone telling the vendor, the vendor would have been within its rights to suspend access entirely without warning, and there was no reliable way to know whether it would notice the change and do exactly that within days rather than months. A plumbing service business with no working schedule is not a business that keeps its customers, its technicians, or its revenue for very long.

The inventory system was less fragile but still tied to Giulia's original login in a way that made a clean handoff unclear without direct intervention, and the bookkeeping platform, while technically transferable, held years of financial history that needed to move across with proper account permissions rather than a shared password left behind on a sticky note in a desk drawer. None of these were problems the earlier due diligence process had been built to catch, because they lived outside the corporate documents, the commercial lease, and the financial statements that a standard review typically covers in a business sale of this size.

Sizing the risk meant asking, plainly, what would actually happen on closing day if nothing about the current arrangement changed. The honest answer was that Jelena and Milica could have taken ownership of a company, a loyal customer list, and a set of service trucks, while losing access within days to the one system that let anyone actually schedule and run a job. That is the kind of failure that never shows up on a balance sheet and can still sink a new owner within the first month of ownership.

What we did

1. Requested every software licence agreement by name. We asked Giulia to gather the account details and licence terms for every piece of software the business used operationally, not just the ones anyone had thought to mention off the top of their head, because the risk we were worried about was exactly the kind that hides in a system nobody discusses until the day it stops working without warning.
2. Read each licence for transfer restrictions. Rather than assuming any given platform would transfer smoothly along with the sale, we read the actual terms and conditions for each one in turn, which is how we confirmed the scheduling platform's licence was personal to Giulia specifically and would not automatically follow the business to a new owner without a separate approval step.
3. Contacted the scheduling vendor directly, well before closing. Instead of waiting to see what would happen after the sale closed, we reached out to the vendor's account team on Giulia's behalf to ask exactly what a proper transfer process looked like from their side, and how long it would realistically take from start to finish. We also asked plainly what would happen if ownership changed without a formal request being filed.
4. Negotiated a bridge arrangement for the transition period. The vendor's standard transfer process would not finish before the scheduled closing date, so we negotiated a temporary dual-access arrangement that let Jelena and Milica use the account under Giulia's existing subscription for a defined window while the formal transfer completed quietly behind the scenes. That arrangement was put in writing with the vendor, not left as an informal understanding.
5. Rebuilt the closing checklist around operational continuity. We added specific closing conditions requiring written confirmation of vendor transfer status for each key system, rather than leaving software access as an informal afterthought handled outside the legal documents and easy to overlook. That gave Jelena and Milica the same contractual protection the standard due diligence already gave them over the company's contracts and finances.
6. Coordinated a supervised handover with Giulia present in person. In the week before closing, we arranged for Giulia to walk Jelena and Milica through every login, every account setting, and every workaround she had developed over eleven years running the shop, so that institutional knowledge did not simply disappear along with her, including the small manual fixes she used when the scheduling software occasionally lagged on busy mornings.
7. Confirmed each transfer in writing before releasing final documents. Rather than treat software access as settled once a plan existed on paper, we held the final closing documents back until we had written confirmation from each vendor, or a documented bridge arrangement, covering every system the business genuinely depended on to operate from day one. That gave Jelena and Milica the same contractual certainty on operational continuity that the standard due diligence already gave them over price and ownership.
8. Documented the whole arrangement inside the closing file itself. Every vendor confirmation, every bridge agreement, and every account credential handed over was logged and filed as part of the closing record, so that if a dispute over access ever arose later, there would be a clear paper trail showing exactly what had been agreed, by whom, and precisely when it happened.

The outcome

Jelena and Milica took over the business on schedule, and on their first Monday as owners, the schedule loaded, the technicians' phones worked, and a customer's emergency call got booked the way it always had under Giulia's ownership. The scheduling vendor's formal transfer completed roughly six weeks after closing, comfortably within the bridge window we had negotiated in advance, and the inventory and bookkeeping systems moved over in the meantime with no interruption to daily operations at all.

Because the problem was caught before closing rather than discovered after the fact, there was no real cost to absorb beyond the time spent on the review itself. Nobody had to negotiate a price reduction for lost business days, nobody had to explain to six technicians why the tablets in their trucks had suddenly stopped working mid-shift, and nobody had to scramble to rebuild a customer schedule from memory or scattered paper notes. That is what a prevented problem looks like from the outside: quiet, almost invisible, and easy to underrate in hindsight precisely because nothing dramatic ever happened, which is exactly the point.

Giulia, who had raised the original concern almost as an aside during an early call, said afterward that she had assumed it was too small a detail to matter next to the larger questions of price and financing that everyone else seemed focused on. It turned out to be the one detail that would have determined whether the business she had spent eleven years building actually kept working on the very day she handed it over to someone else, and it cost nothing to fix once someone actually looked for it in time.

The file's mid-stream handoff between lawyers mattered too, in a quieter way. Nothing about the earlier work had been wrong; the purchase agreement and corporate due diligence were sound. But a handoff partway through a transaction is exactly where operational questions like software licensing tend to fall between two checklists, each assuming the other already covered it. Treating the file as needing a fresh look, rather than simply continuing where the paperwork left off, was what surfaced the risk in time.

What you can learn from this