The simulator company sale that ran out of runway

The situation

Diego had already been through one failed attempt to sell his company before he called our office. A university professor before he left academia to build training simulators for a niche the school system had ignored, he had spent eighteen months two years earlier with a business broker who promised a fast, low-cost process and delivered neither. That deal collapsed quietly, without much explanation, and Diego came away believing that the cost of doing a sale properly was the real obstacle to getting one done at all.

His company built simulator systems used to train air traffic controllers, a field his co-founder Katalin knew from the inside after a career at the console before she moved into building the tools that trained new controllers rather than working the boards herself. Between them they had built a business worth somewhere in the $30 million to $50 million range, and a larger operator, represented by a director named Gita, had come forward with real interest and a term sheet that looked serious.

Diego's instructions to us when he first came in were specific and, in hindsight, revealing. He did not ask primarily for the best possible price. He asked for a process he could predict, with costs he could see coming, after a first attempt that had cost him time, money, and confidence without producing a result. Predictability mattered to him nearly as much as the outcome itself, and he said so plainly in the first meeting.

We negotiated a share purchase agreement with Gita's side that included the standard mechanics of a deal this size: closing conditions around financing, regulatory clearances relevant to the simulator technology, and a fixed outside date after which either party could walk away if closing had not happened. Diego signed off on every draft. The clause that would end up mattering most was one nobody flagged as unusual at the time.

The negotiation itself moved smoothly for a deal of its size. Gita's team was professional and responsive, the price landed within the range an independent valuation had suggested, and both sides genuinely seemed to want the transaction to succeed. That smoothness is, in hindsight, part of why the outside date clause drew so little scrutiny. Nothing about the tone of the negotiation suggested the parties were heading toward a dispute over what a deadline meant.

The gap nobody had noticed

The outside date clause said closing had to occur by a fixed date or either party could terminate. What it did not say, clearly enough, was what happened to the conditions that were still in motion when that date arrived. Gita's side had a financing condition that was progressing but not finished. Our side had a regulatory clearance still working its way through review. Both were the kind of conditions that routinely take a little longer than anyone plans for, and both sides had informally treated the outside date as soft, the way earlier conversations between the parties' business people had implied it would be.

It was not soft. The agreement's language was clear that the date was a hard deadline unless both parties agreed in writing to extend it, and no such written extension had been signed. Katalin had exchanged emails with someone on Gita's team suggesting an extension was fine, but those emails did not amend the agreement, and email exchanges between operating people are rarely treated as amendments to a signed contract.

Once the outside date passed with conditions still open, the agreement was at an end on its terms. Not every agreement works that way; many instead give each side the right to terminate at that point, and which applies turns on the exact wording, but this one was drafted to expire on its own. That is a legitimate way for a deal to end, but it is a hard one, because it happens automatically rather than by anyone deciding to end it. Neither Diego nor Gita's side had made a conscious choice to walk away. The clock had simply run out under a mechanism both sides had underestimated.

The gap was not a drafting error in the sense of a typo or an omission. The clause did exactly what a standard outside date clause is supposed to do. The gap was in expectations: everyone assumed there would be room to extend informally if things ran a little long, and the agreement gave no such room. That mismatch between what the document said and what the business people believed it meant is where deals like this go wrong.

It is also a common pattern across deals of very different sizes. The people negotiating a transaction's business terms, whether founders, executives, or in this case a professor turned entrepreneur and the operator he was selling to, are rarely the same people scrutinizing what happens if a deadline is missed. That gap between the commercial conversation and the document's literal mechanics is exactly where a lawyer's attention is supposed to sit, and exactly where, in this file, an earlier round of advice from Diego's broker-led process had not looked closely enough.

What we did

1. Reviewed the lapsed agreement immediately to confirm its status. Before advising Diego on anything else, we needed to know with certainty whether the agreement had actually terminated or whether an argument existed that it remained alive. Confirming the lapse was real, rather than assuming it, avoided giving Diego false hope or missing a live option, and it meant our first conversation with him was grounded in the document's actual wording rather than in what either side had assumed the deadline would mean.
2. Assessed whether the informal extension emails created any binding obligation. Katalin's email exchange with Gita's team was the one loose thread that could have complicated an otherwise clean lapse. We concluded the emails did not meet the bar for a written amendment under the agreement's own terms, which meant the lapse stood and neither side could claim the other had breached anything.
3. Confirmed no deposit or break fee was at risk. Some outside date structures expose one party to a forfeited deposit or a break fee when a deal lapses. This agreement did not, but we verified that in writing rather than assuming it, because the cost of being wrong about it would have fallen entirely on Diego, and a founder already worried about unpredictable cost deserved certainty on that point before anything else was decided.
4. Sent a short, factual notice to Gita's side confirming the lapse. Rather than letting the deal's status sit ambiguous, we put in writing that the agreement had terminated by its own terms as of the outside date, closing the door on any later argument that the parties had continued negotiating under a live contract. Keeping the tone factual rather than adversarial mattered too, since nothing about the lapse suggested either side had acted in bad faith.
5. Advised Diego against re-opening negotiations under the same document. Gita's side floated the idea of simply picking the deal back up where it left off. We recommended against treating the lapsed agreement as still operative, because doing so would have revived exactly the ambiguity that caused the problem, and any future deal needed to start from a document written to avoid it.
6. Built a template outside date clause for Diego to use in future negotiations. Given his stated priority on predictability and cost, we gave him language that ties any extension to a defined, low-friction mechanism rather than requiring a fresh negotiated amendment each time a condition runs long, so a future deal would not fail the same way over a deadline nobody meant to enforce so literally.
7. Kept the total legal spend on the wind-down proportionate to what was left to do. Because Diego's central worry was cost, we scoped the wind-down narrowly to confirming the lapse and closing it out cleanly, rather than running a broader review that would have added expense without changing the outcome, and we told him upfront roughly what that scope would cost so nothing about the bill surprised him afterward.
8. Debriefed Diego on the difference between his broker-led attempt and this one. Understanding why the first process failed, and why this one ended differently despite also not producing a sale, gave Diego a clearer sense of what a properly run deal actually looks like, which mattered as much to him going forward as the immediate result of this particular agreement.

The outcome

The sale did not happen. That is the plain result, and it is worth stating without softening it: Diego set out to sell his company, spent real time and money on a second serious attempt, and ended up exactly where he had been before Gita's side ever came forward, minus the cost of the process. For a founder who had already lost confidence in the idea that a sale could go cleanly, a second disappointment of this kind could easily have confirmed his worst assumption about what selling a company actually costs.

What the outcome did not include was liability. No deposit was forfeited, no break fee was owed, and no claim followed from either side once the notice confirming the lapse went out. Diego's earlier experience with the broker had left him worried that a failed deal would leave him exposed to a mess he could not predict the cost of; this one did not, because the termination happened cleanly under mechanics that were sound even though the parties had misjudged how they would apply. Gita's side, for its part, accepted the notice without pushback, which suggested their own read of the situation matched ours once it was put in writing plainly.

Diego has since had preliminary conversations with two other prospective buyers, using the outside date language we built for him. Neither has progressed to a signed agreement yet. The company continues operating as it did before, with Katalin still running day-to-day operations, and Diego treating the lapsed deal less as a failure than as the reason his next agreement will not have the same gap in it. He has said, more than once, that knowing exactly what a failed process would cost him mattered as much as anything else that came out of the file.

What you can learn from this