The scheduling software the whole landscaping business ran on

The situation

'Can we just keep using Menachem's account after we take over, since the login already works?' That was the question Miriam asked in her first call with us, and it took the rest of the file to answer properly. Miriam, an early childhood educator who had left the classroom two years earlier to run the day-to-day operations of a landscaping company, had agreed with Cynthia, a landscaper who had worked the crews for a decade, to buy the business together from its owner, Menachem, who was ready to retire. The deal was priced in the low hundreds of thousands, modest by most standards, and both women were financing their share carefully, treating it as the biggest purchase either had made.

Before calling us, Miriam had spent an evening searching online for how software licences work when a small business changes hands. Several forum posts and a general business guide suggested that software licensed to a company, rather than to an individual, simply transferred along with the business when it was sold, the same way a lease or a supplier contract might. Reassured, she told Cynthia the software was not something they needed to worry about, and the two of them focused their attention on the trucks, the equipment and the client list instead.

The route-scheduling and invoicing software the business ran on was not incidental. Every crew's daily route, every client's billing history and every recurring contract lived inside it, built up by Menachem over nine years. Losing access to it, even briefly, would mean crews showing up at the wrong addresses and invoices going unsent. When we reviewed the vendor's licence terms as part of standard closing diligence, several weeks into the file, it became clear the online advice Miriam had relied on was wrong for this software specifically: the licence was issued personally to Menachem as the named account holder, and its terms expressly barred any transfer or assignment without the vendor's written consent.

By the time this surfaced, Miriam and Cynthia's closing date was five weeks away, their financing was tied to that date, and neither of them had budgeted for buying a new software licence on top of everything else.

Cynthia, who had spent a decade running crews for Menachem, understood the operational side of the business better than the paperwork side, and she was the one who raised the alarm when a crew supervisor mentioned that Menachem's login was tied to his personal email rather than a company one. That detail turned out to matter more than either partner initially realized.

What the other side was relying on

The vendor's position, once we contacted them, was built entirely on the licence agreement's plain wording. Their terms of service stated that the account was personal to the named subscriber, non-transferable, and that any change in the business's ownership triggered a requirement for the new owner to sign up as a fresh customer, at current pricing, with no discount or continuity credit for the years Menachem had already paid. The vendor's representative was polite but firm: this was a standard clause across their customer base, not something negotiated case by case, and they had no process for waiving it.

Menachem, for his part, had never read the clause closely either. He had signed up for the software years earlier, treated it as a routine business expense, and had no reason to think about what would happen to the account when he eventually sold. When we raised it with him, he was sympathetic but candid that he could not simply hand Miriam and Cynthia his login and walk away, since doing so would breach his own agreement with the vendor and could get the account suspended entirely, with no data recoverable, right in the middle of a transition.

The vendor was, in effect, relying on the fact that most small businesses in this position have no leverage. A single landscaping company switching software mid-sale is not a customer the vendor is worried about losing, and the standard terms reflect that: take it or leave it, at list price, with no continuity of the historical data unless a new account is set up and the old one's records exported into it. Current pricing for the software's business tier was meaningfully higher than what Menachem had been paying under an older plan he had held since before the vendor's last price increase.

This mattered because Miriam and Cynthia's purchase price had been negotiated on the assumption that operating costs, including software, would simply continue unchanged after closing. A new licence at current rates, plus the cost and disruption of migrating years of route and client data into a new account, was a real expense that had not been priced into the deal at all, and the vendor had no incentive to make that transition any easier than its standard process already allowed.

There was also a quieter assumption embedded in the vendor's position that we had to unpack for Miriam and Cynthia: the vendor was treating the sale of the business as entirely separate from the question of who owned the data inside the software, as though the two could be cleanly divided. In practice, nine years of client billing history, service notes and route optimization settings were not something either partner could reasonably recreate from scratch, which meant the vendor's standard terms, written for an ordinary new customer signing up cold, did not fit a situation where continuity of that data mattered enormously to the business being sold.

What we did

1. Confirmed the licence terms directly with the vendor rather than relying on the general advice Miriam had found online, since software licensing terms vary significantly between vendors and even between plan tiers from the same company, making generic guidance unreliable for a specific transaction and specific piece of software. The vendor's written confirmation that the account was non-transferable settled the question definitively, giving Miriam and Cynthia something firmer than a forum post to plan the rest of the file around.
2. Obtained a written data export process from the vendor before agreeing to anything else, confirming that Menachem's historical route and client data could be exported and imported into a new account, since without that assurance the business risked losing years of operational history in the transition regardless of how the licence issue itself was resolved. Securing that commitment in writing, rather than a verbal assurance from a sales representative, meant the migration plan rested on a documented process instead of a promise that could shift once the changeover was underway.
3. Negotiated the timing of the new account setup with the vendor so it could be created and populated with exported data before closing rather than after, meaning crews would have working routes on day one instead of a gap while the migration happened under time pressure with clients waiting on scheduled visits. That sequencing mattered more than it might on a smaller file, since a landscaping business running routes every weekday could not absorb even a short outage without missed appointments and calls asking why no one showed up.
4. Adjusted the purchase price with Menachem to reflect the new software cost, since it was a direct consequence of a limitation in the business he was selling that he had never disclosed because he had never thought to; he agreed to a modest reduction rather than treating it as entirely the buyers' problem, once we framed it as a shared consequence of how the licence had always been structured.
5. Reviewed the rest of the business's software and service contracts for the same non-assignment language, since if one vendor structured its licence this way, others might too; this turned up a similar restriction in a minor invoicing add-on, which we resolved the same way, quietly and early, before it became a second surprise close to closing. Finding it weeks ahead, rather than in the final days, meant the second fix cost a phone call and a short delay instead of another round of price renegotiation under pressure.
6. Confirmed the new account's billing history would satisfy the vendor's loyalty pricing tier eventually rather than resetting Miriam and Cynthia permanently to the highest introductory rate, negotiating a written commitment that after twelve months of continuous service the account would move to the same pricing band Menachem's original account had reached, softening the long-term cost increase. Without that commitment, the higher rate they were already absorbing at closing would simply have continued indefinitely, turning a one-time cost into a permanent drag on the margins their financing depended on.
7. Built a short transition checklist for Miriam and Cynthia covering exactly which accounts needed to move, in what order, and who at the vendor to contact if anything went wrong on closing day, so the handover itself would not depend on anyone remembering details from a months-old email chain under pressure. Neither partner had been through a business purchase before, and having the sequence written down in one place meant closing day decisions did not hinge on digging back through weeks of correspondence for a forgotten contact name.
8. Walked both partners through the finished migration line by line two days before closing, comparing routes and client records in the new account against the old one, so any gap in the transfer would surface while there was still time to fix it, not on the first morning the business belonged to them. That check found two records that had not carried over cleanly, fixed the same afternoon, confirming a careful pre-closing review catches the gap that becomes real trouble once crews rely on the data daily.

The outcome

The business closed on schedule, with a new software account set up under Miriam and Cynthia's names and populated with Menachem's historical data before the closing date arrived, so crews had working routes from their first day of ownership. The purchase price was reduced by an amount in the low thousands to reflect the new licence cost, a genuine concession from Menachem but not a full offset of what the new subscription would cost over time at current rates, since ongoing fees were higher than what he had been paying under his older plan.

Miriam and Cynthia absorbed that higher ongoing cost as part of their operating budget going forward, something neither had planned for when they first agreed on a purchase price based on the business's existing expenses. It was a real, if modest, dent in the economics of the deal, and both women were candid afterward that the online advice Miriam had initially relied on had cost them real negotiating leverage, since raising the issue earlier in the negotiation, before a price was agreed, would likely have produced a larger price adjustment than raising it during closing diligence did.

The business itself transitioned without an operational gap, which was the outcome that mattered most day to day. Clients did not notice a change in service, crews kept their usual routes, and invoices continued going out on schedule through the switch, which was the practical goal from the moment the licence problem surfaced.

The lesson both partners took from the file, and one we made a point of walking through with them afterward, was that a business's software licences deserve the same diligence as its lease or its equipment list, not an assumption borrowed from a forum post about how transfers usually work. Cynthia said afterward that the whole episode changed how she thought about the business's other contracts too, and the two of them asked us, unprompted, to build a short annual checklist for reviewing their remaining vendor agreements going forward, a small habit that cost little and closed off the chance of a similar surprise reappearing down the road.

What you can learn from this