How to Terminate a Business Contract Legally in Missouri

The exit is part of the deal too

Illustration: The exit is part of the deal too

Most of the energy in business contracting goes into the beginning. Negotiating terms, redlining drafts, getting signatures. The ending tends to get an email: "We're not renewing," or "Effective today, this relationship is over," or sometimes nothing at all — just a stopped payment and silence.

That's backwards. A huge share of business litigation isn't about whether a relationship should end. Often both sides agree on that part. The fight is about how it ended — whether the right clause was used, whether notice was proper, whether anything still has to be paid, whether old obligations followed someone to a new owner, and whether anyone's reaction to all of it crossed a legal line.

The seven Missouri cases below cover a real estate development deal, an agricultural equipment manufacturer's bankruptcy-driven asset sale, a foundation-repair dealership, a downtown restaurant lease, an accounting firm's departing employee, a 1910 retail clothing salesman, and a mobile home park sale with an unfinished sewage lagoon. Different decades, different industries, same underlying question: what does it take to end a business relationship cleanly?

Here's the roadmap.

Figure out whether you're terminating the contract or forfeiting someone's rights under it
Use the exit the contract actually gives you — or the one the law defaults to
Ask whether "clean" still means "free" (recoupment)
Make sure your damages-for-default clause is liquidated damages, not a penalty
Know what can legally follow someone out the door
When the other side sells, merges, or restructures, know where the old contract stands
Define the last mile before you call it done

Step 1: Figure Out Whether You're Terminating the Contract or Forfeiting Someone's Rights Under It

L & K Realty Co. v. R. W. Farmer Const. Co., 633 S.W.2d 274 (Mo. App. 1982), is a case about two companies who spent five years arguing about whether their deal was alive — and the answer turned entirely on a distinction most people never think to make.

L&K and Farmer signed two related agreements in 1974 to develop mobile home parks on adjoining land. Farmer would build a park on its own tract, build a second park on L&K's tract, and construct a shared sewage plant — partly on L&K's land, under a separate easement — to serve both. Section 6 of the lease set the starting gun: Farmer had to "commence... the good faith construction and development" of the park on its own land by September 1, 1974. If it didn't, the section said, "this Agreement shall automatically terminate and neither party shall have any rights, obligations or liabilities under or arising out of this Lease Agreement."

Farmer didn't start construction by that date — the trial court believed Farmer's own testimony that work didn't begin until late September or October, over conflicting evidence from L&K's witness. So, by its own terms, the lease ended on September 1, 1974.

Except nobody acted like it had. For the next five years, L&K sent letters demanding Farmer perform under the lease. Farmer's lawyer told L&K in 1976 the lease was "still in force." Farmer even tendered a $5,000 payment under one of the lease's provisions. When L&K finally sued in 1980, it argued that all of this conduct showed the parties' own understanding of the deal — and that understanding should control.

The court didn't buy it, and the reasoning matters for any business relying on years of "we've always done it this way" practice. The rule that lets a court look at how parties behaved under a contract to figure out what an ambiguous term means only applies when the term is actually in doubt. Section 6 wasn't. "When the language of a contract is plain, there can be no construction because there is nothing to construct." Five years of correspondence couldn't revive a lease that had already, automatically, stopped existing.

L&K's second argument is the one worth slowing down on. Realizing it had lost the "the lease never really ended" fight, L&K pivoted: fine, maybe Section 6 could have ended the lease — but it's a forfeiture clause, and forfeiture clauses only operate "at the option of the party for whose benefit the covenant was inserted." L&K, as the party losing out on the trailer park and rent it was promised, should get to decide whether Section 6 kicked in. And L&K never elected to invoke it.

The court rejected this too, and drew a line that's easy to miss when you're reading your own contract:

"[I]t is not [a forfeiture clause], but is simply a termination clause, with substantially different consequences. The term 'forfeiture' is a comprehensive term which means a divestiture of specific property without compensation... A forfeiture imposes a loss by the taking away of some preexisting valid right without compensation... The contract section in issue here did not purport to impose any sanction for default nor did it create any privilege for either party to invoke divestiture of accrued rights. It merely announced that the agreement would end upon a certain condition."

Forfeiture is about taking something away from someone who already has it. Termination is about the agreement ending. They sound similar, but they come with completely different rulebooks — forfeiture clauses can carry waiver, election, and notice requirements; a straight termination clause generally doesn't, because there's nothing to "waive" or "elect" when the deal simply stops existing on its own terms.

The court backed this up with two older cases worth knowing: a contract that terminates automatically if a client misses a payment is enforceable "no matter how unusual or bizarre," so long as it doesn't violate public policy — "[i]f parties agree that the happening of that event shall work a change in their legal relations... it is certainly their privilege to do so as long as freedom of contract exists." And a contract that says it's "cancelled" if either party sells their business is a valid termination clause, even though it effectively gives each side a unilateral exit hatch through their own voluntary act.

One more piece of this case deserves attention, because it's the flip side of the lesson. L&K also argued that, even if Section 6 ended the lease, Farmer shouldn't get to keep the easement — the right to build and maintain the sewer plant on L&K's land — for free. But the lease and easement weren't interdependent; nothing tied Farmer's easement rights to whether the L&K trailer park ever got built. And critically, the lease itself anticipated early termination: a separate section specified that certain rights — L&K's right to connect to the sewer system — would survive as covenants running with the land, binding on both parties' successors, even if the lease ended early. The lesson isn't subtle: if you want something to outlive termination, the contract has to say so. Courts won't infer survival from what seems fair in hindsight.

Step 2: Use the Exit the Contract Actually Gives You — Or the One the Law Defaults To

Illustration: Step 2: Use the Exit the Contract Actually Gives You — Or the One the Law Defaults To

Once you know what kind of clause you're working with, the next question is mechanical: how, exactly, does this contract say a party gets out?

Ernst v. Ford Motor Co., 813 S.W.2d 910 (Mo. App. 1991), gives a clean example of a termination done by the book — almost as a warm-up act for the messier issues later in the same case (which we'll come back to in Step 3 and Step 6).

The plaintiffs were dealers of Versatile-branded agricultural equipment, operating under written dealership agreements with Versatile's U.S. subsidiary (VFEC). Paragraph 21.3 of those agreements said: "This Agreement may be terminated by either party at any time after the date of its approval, with or without cause, by not less than 90 days written notice." When Versatile's financial troubles led to a sale of its assets to Ford New Holland — a sale that excluded 150 dealers, including these plaintiffs — VFEC sent each of them written notice citing paragraph 21.3 and terminating their agreements 90 days out.

That's it. No ambiguity, no dispute about whether VFEC could do this — because the contract said exactly when and how either side could walk away, and VFEC did precisely that. The lesson here isn't complicated, but it's the foundation everything else is built on: if your contract has a termination clause, that clause is your instructions. Follow them, and the termination itself generally isn't where your legal exposure will come from.

Newco Atlas v. Park Range Const., 272 S.W.3d 886 (Mo. App. 2008), covers what happens when the instructions are missing entirely — and what arguments don't work to fill that gap.

Atlas manufactured a steel piering system used to stabilize building foundations, and had run two dealership contracts with Park Range Construction for over a decade — one covering the Colorado Springs market (terminable by either party, any time, on 60 days' written notice) and one covering Denver (silent on both duration and termination). After years of Park Range successfully growing the Denver market, Atlas decided it wanted to go non-exclusive and chase larger national accounts. Park Range said no to a renegotiation, so Atlas sent 60 days' notice terminating both contracts — importing the Colorado Springs notice period into the Denver contract, which had no notice provision of its own.

Park Range's counter wasn't that Atlas lacked the right to terminate — it was that Atlas exercised that right for the wrong reason, in a way that wiped out years of Park Range's marketing investment, and that this breached an implied covenant of good faith and fair dealing that exists in every Missouri contract.

The court's answer is one every business relying on an informal, "we never really wrote down how this ends" arrangement should know. When a distributorship agreement says nothing about duration or termination, Missouri law treats it as terminable at will by either side. And — this is the key move — Missouri does not let a party challenge the termination itself of an at-will arrangement by invoking the good-faith covenant, because doing so "would be inconsistent with and destructive of the unfettered right to terminate at will." The court draws a direct line to at-will employment: nobody can sue an at-will employer for firing them "in bad faith," because the whole point of at-will is that no reason is required. The remedy for an at-will employee is a wrongful-termination claim under specific, narrow circumstances — not a generalized good-faith argument. For an at-will distributor, as we'll see next, the analogous remedy has a name too.

The takeaway for Step 2: if your contract spells out how to end it, that's your playbook, and following it (like VFEC did) is usually the easy part. If your contract is silent, you're not stuck — but don't expect "we acted for a self-interested business reason" to be the argument that gets you in trouble. In Missouri, that's exactly what at-will means.

Step 3: Ask Whether "Clean" Still Means "Free" — Recoupment

A termination that's procedurally perfect doesn't always mean the financial relationship is over. This is the part of Ernst v. Ford Motor Co. that gets less attention than the headline asset-sale dispute, but it matters just as much for any business that operates through dealers, distributors, or franchise-style arrangements.

Beyond suing Ford New Holland, the Ernst plaintiffs also brought a claim against VFEC itself for "recoupment" — even though VFEC had used the 90-day notice clause exactly as written. The court explained the doctrine this way:

"The recoupment doctrine imputes into a contract a duration equal to the length of time reasonably necessary for a dealer to recoup its investment, plus a reasonable notice period before termination."

The doctrine applies to agreements that are, in substance, terminable at will — and here's the part that surprises people: an agreement can have crisp "with or without cause, on 90 days' notice" language and still be "at will" for recoupment purposes. The court pointed to another case where a contract allowing termination "for any reason at any time upon sixty days notice" was treated as at-will under this doctrine despite its specific notice term. The notice period in the termination clause and the notice period a dealer might be owed under recoupment aren't automatically the same thing — "reasonable," for recoupment purposes, is a question of fact, generally for a jury, based on how long it would actually take a dealer to recover what it invested in the relationship.

Because the trial court hadn't yet resolved whether the plaintiffs' agreements had been modified to require "good cause" for termination — which would take them out of "at will" territory altogether — the appellate court sent the recoupment claim back for trial rather than resolving it.

Newco Atlas shows the other side of this coin. The same recoupment doctrine applied to Atlas's termination of Park Range's Denver dealership. But the trial court had already found — and Park Range didn't even appeal the finding — that Park Range had recouped its investment over its long run as Atlas's dealer. Recoupment doesn't mean "you get something extra just because the relationship ended"; it means a dealer gets a fair shot to recover what it put in. If that's already happened, termination — even termination for reasons the dealer doesn't like — closes the book with nothing further owed.

For any business on either side of a dealer, distributor, sales-rep, or similar relationship: a termination notice that complies with the contract's notice period is necessary, but it isn't automatically sufficient. The real question courts may ask is whether the other side has had a genuine opportunity to get back what it put into the relationship. That's worth thinking through before the notice goes out — not after the lawsuit arrives.

Step 4: Make Sure Your Damages-for-Default Clause Is Liquidated Damages, Not a Penalty

This is where a lot of termination clauses quietly become unenforceable — not because the right to terminate was wrong, but because the price tag attached to default was.

The legal standard, as Missouri courts apply it, has two parts. First, something — anything — has to actually go wrong before a liquidated damages clause kicks in at all: "a plaintiff must show the existence of actual harm or damages before a 'liquidated damages clause can be triggered.'" That showing doesn't require a precise dollar figure, just proof that some harm occurred. Second, and separately, the amount the clause specifies has to be "a reasonable forecast of just compensation for the harm... not unreasonably disproportionate to the amount of harm anticipated when the contract was made." Get either part wrong, and what you drafted as "liquidated damages" gets re-labeled a "penalty" — which Missouri courts simply won't enforce.

When the Math Works: Werner v. Finley

Werner v. Finley, 129 S.W. 73, 144 Mo. App. 554 (Mo. App. 1910), is over a century old, but it's still one of the cleanest illustrations of a damages clause that survives scrutiny.

Camillus Finley signed on as a salesman for Werner Bros., a St. Louis clothing retailer, for 160 weeks at $60 a week — a notably high salary for the time, which the court took as a signal of how much the employer valued the role. The contract said that if Finley breached any of his covenants, Werner Bros. could terminate him and collect, as liquidated damages, $10 per week for whatever was left of the 160-week term.

After about 42 weeks, Finley walked off the job without notice — to take a position with a direct competitor he'd secretly signed a contract with four months earlier. Werner Bros. sued for the 118 weeks remaining on the term, at $10 a week: $1,180.

The court enforced it in full, and its reasoning is the template for "this works":

"The true question is whether, in view of the actual breach complained of, the sum nominated in the contract is to be fairly regarded as a penalty, or as a fair measure of the real damage in the estimation of the parties most familiar with the probable effects of its breach."

Two things made $10 a week — one-sixth of Finley's salary — defensible. First, the actual damages from losing a key salesman were genuinely hard to pin down: the gap between what Finley was worth to the business and what he was paid, the cost and disruption of finding a replacement, the harm of him taking his relationships to a direct competitor. Second, $10 a week wasn't wildly out of proportion to $60 a week — it was a fraction, not a multiple, of the value the parties had already agreed the role was worth.

The court added one more piece worth remembering: liquidated damages only attach where there's been a substantial breach causing more than nominal harm — and a contract covering several covenants, some weighty and some trivial, with the same liquidated-damages figure attached to a breach of any of them, isn't automatically thrown out on that basis alone. Here, the breach — secretly committing to a rival and then walking out — was about as substantial as it gets, so the question never became close.

When the Math Doesn't: Two Provisions in One Lease

Kan. City Live Block 139 Retail, LLC v. Fran's K.C. LTD, 504 S.W.3d 725 (Mo. App. 2016), shows what happens when the proportionality piece fails — twice, in the same lease.

Fran's K.C. signed a ten-year restaurant lease in the Kansas City Power & Light District. The relationship deteriorated into a string of default notices, and eventually the tenant owed roughly $3.6 million and the landlord, KC Live, took back possession. Two of the lease's damages provisions came under the microscope on appeal.

The first was a "go dark" clause: if Fran's failed to operate during required hours for more than three consecutive business days, KC Live could collect, "as liquidated damages (and not as a penalty)," three times the monthly rent for every month the closure continued — on top of, not instead of, every other remedy in the lease. The premises sat empty for roughly eight months. KC Live showed real, if hard-to-quantify, harm: re-letting the space required a $400,000 tenant-improvement allowance to the new tenant, and KC Live's own witness admitted there was no way to isolate how much of the lower rent from the new tenant was caused specifically by the vacancy. That was enough to trigger the clause — "the unquantifiable harm stemming from the vacancy was clearly shown."

But triggering the clause isn't the same as the amount being enforceable. Courts look for liquidated damages figures that land somewhere in the range of a small percentage of the contract's value — prior Missouri cases had upheld figures in roughly the 3% to 10% range. Here, treble rent stacked on top of the base rent KC Live was also separately awarded worked out to roughly 400% of a month's value for every dark month, with no evidence at all connecting that multiple to what the parties might have anticipated when they signed. The court struck it down as an unenforceable penalty.

The second provision was a late-payment charge: 5% of the overdue amount (or $250, whichever was greater) per month the rent remained unpaid — calculated, each month, on the entire growing arrearage — plus a separate interest charge of up to 18% on the same unpaid balance. Because the 5% compounded onto an ever-larger base, it ballooned from under $600 in its first month to over $46,000 in its last, ultimately totaling more than the unpaid rent itself and roughly five times the separately-charged interest.

The court contrasted this with a different case, cited within the opinion, where a one-time 15% late fee had been upheld — because that lease said, in plain language, that the fee was meant to cover the landlord's administrative costs of chasing late rent, and the landlord actually proved those costs at trial. Here, the late-fee clause said nothing about administrative costs — and, as it turned out, this lease already had a separate 20% administrative fee baked into the tenant's common-area charges. So the compounding late fee would have compensated KC Live twice for the same administrative burden, on top of separately-charged interest, on top of the underlying rent recovery. "[T]he late-charges provision appears to compel performance rather than compensate for damages" — which is, almost word for word, the definition of a penalty.

Both provisions being struck had a real downstream effect: KC Live's lease also entitled it to recover attorney's fees as the "prevailing party," but because it wasn't the prevailing party as to these two unenforceable provisions, the fee award had to be recalculated on remand too.

When There's No Harm to Measure At All

Schmersahl, Treloar & Co. v. McHugh, 28 S.W.3d 345 (Mo. App. 2000) — which we'll look at more closely in Step 5 — adds one more flavor of penalty to watch for. The accounting firm's employment agreement included liquidated damages equal to 30% of a coworker's salary, triggered any time a departed employee "solicited, persuaded, induced, or encouraged" a former colleague to leave — regardless of whether that colleague actually left, got a raise, or the firm experienced any measurable loss at all. A clause that fires no matter what actually happens isn't measuring damages. It's punishing conduct. Same problem, different mechanism.

The Drafting Takeaway

Put together, these cases suggest a short checklist for any termination-related damages clause: tie the trigger to something that could plausibly cause real harm (a key salesman leaving, a storefront sitting dark); keep the amount in the neighborhood of what that harm could reasonably be expected to cost at signing, not an arbitrary multiple; avoid stacking a "liquidated damages" remedy on top of other provisions that already address the same loss; and if there's a specific reason for the number — administrative costs, lost goodwill, replacement costs — say so in the contract, the way the surviving 15% late-fee provision did, and be ready to back it up.

If your contracts include termination penalties, late fees, or "liquidated damages" provisions that haven't been looked at since they were drafted — especially anything that compounds, stacks with other remedies, or was copied from a template years ago — it's worth having them reviewed before they're ever tested in a dispute. A provision that looks aggressive on paper but doesn't survive a penalty challenge can end up being worse than no provision at all, because it can cost you "prevailing party" status on the fees that come with it.

Step 5: Know What Can Legally Follow Someone Out the Door

Ending an employment relationship raises a version of the termination question that's easy to get backwards: not "how do we end this," but "what, if anything, still applies after it ends."

Schmersahl, Treloar & Co. v. McHugh, 28 S.W.3d 345 (Mo. App. 2000), involved an accounting firm that required every employee — professional and clerical alike — to sign a "Confidentiality and Non-Solicitation Agreement." One piece of it prohibited soliciting the firm's clients for three years after leaving. A separate piece prohibited soliciting or even encouraging the firm's other employees to leave, also for three years, backed by the 30%-of-salary liquidated damages provision discussed above.

Tim McHugh left for a competing firm in late 1996. About twenty-one months later, he had lunch with a former coworker, Mark Graves, and mentioned that his new firm was looking for someone with Graves's experience — sounded like a good opportunity. Graves told his supervisor about the conversation, decided to stay where he was, didn't get a raise, and the other firm never actually made him an offer. Schmersahl sued McHugh anyway, seeking the contractual damages for violating the non-solicitation-of-employees clause.

The court's analysis starts with a question Missouri hadn't squarely answered before: is a promise not to mention job openings to former coworkers even the kind of thing that gets restricted by a "restrictive covenant"? The answer was yes — "[c]ompetition in the marketplace encompasses competition in the labor market," and a covenant like this "restricts the flow of competitive information about the labor market." The court leaned on a famous line from Judge Learned Hand: absent some monopolistic purpose, everyone has the right to offer better terms to someone else's at-will employee, so long as that employee remains free to leave — a contrary rule would be "intolerable," both to employers who could use that person more effectively and to the employee who might get a raise out of it.

So the covenant was a restraint of trade — which means it only survives if it protects one of two narrow, specific interests Missouri law recognizes:

"[A]n employer may only 'fairly require' the protection of certain narrowly defined and well recognized interests against possible appropriation by a former employee. These protectable interests are limited to trade secrets and customer contacts, the latter being essentially the influence an employee acquires over his employer's customers through personal contact."

Trade secrets. Customer relationships the employee built on the company's behalf. That's the list. An employer's interest in keeping its workforce stable — not having departing employees mention openings to people they used to work with — isn't on it, no matter how understandable that interest is from a business standpoint. The court was direct: "an employer does not have a proprietary interest in its employees at will or in their skills." If a firm wants to protect against a wave of departures, the tool the law actually recognizes is getting its remaining employees to agree not to misuse client relationships or trade secrets — not extracting a promise from someone on their way out the door that they'll never again mention a job opening to a former colleague.

Because the covenant didn't fit into either protected category, it failed before the court even had to ask whether three years was a reasonable length of time. An otherwise "reasonable" restriction on something the law doesn't let you restrict in the first place is still unenforceable.

For any business with standard separation paperwork — non-solicitation agreements, non-competes, confidentiality provisions that get handed to every departing employee as a matter of routine — this case is a reminder to ask what each clause is actually protecting, in the terms the law uses. "We don't want our people poaching each other" is a completely understandable business goal. It's also not, by itself, a legal basis for a covenant that survives the end of someone's employment.

Step 6: When the Other Side Sells, Merges, or Restructures, Know Where the Old Contract Stands

Sometimes a contract doesn't end because either party to it wanted out — it ends because one side gets bought, sold, or reorganized, and the new structure doesn't include the old deal. Ernst v. Ford Motor Co., 813 S.W.2d 910 (Mo. App. 1991), is built around exactly this situation, and it answers three separate questions that come up whenever a counterparty changes hands.

Excluding What You Don't Want: Successor Liability

Recall the setup from Step 2: VFEC properly terminated 150 dealer agreements — including the Ernst plaintiffs' — on 90 days' notice after Versatile sold its assets to Ford New Holland. The dealers didn't stop at suing VFEC. They sued Ford New Holland too, on the theory that FNH, having effectively taken over Versatile's business, had inherited responsibility for what happened to these dealers.

The general rule cuts the other way: a company that buys another company's assets doesn't automatically inherit that company's liabilities. Missouri recognizes four exceptions — where the buyer expressly or impliedly agreed to assume the debts; where the deal amounts to a merger or consolidation; where the buyer is really just a "mere continuation" of the seller under a new name; or where the deal was structured to fraudulently dodge liabilities. The dealers leaned on the first exception, pointing to a South Dakota case where a similar buyer had been held to have impliedly assumed dealer obligations. But the court distinguished it cleanly: in that case, the purchase agreement actually required the buyer to handle the dealer terminations itself. Here, FNH's asset purchase agreement did the opposite — it expressly excluded these 150 dealer agreements from what FNH was buying. No assumption, implied or otherwise.

The fraud argument fared no better. The dealers pointed to FNH's communications with the U.S. and Canadian governments — made to secure a loan needed to facilitate the purchase — describing a plan to "retain the existing Canadian Versatile dealer network." But that same loan agreement explicitly preserved "the right of FNH... to terminate specific Versatile dealers for non-performance or other valid business reasons or objectives." Nothing in the record suggested FNH paid less than fair value, or that Versatile's sale was anything other than a legitimate response to its own financial decline. As the court put it, the record showed "an arms-length transaction entered into for legitimate business purposes" — full stop.

The lesson for anyone buying or selling a business with existing contracts attached — dealer networks, vendor agreements, leases, you name it — is to make the list of what's not coming along explicit, in writing, in the purchase agreement itself. FNH's express exclusion of these 150 agreements is the single biggest reason the successor-liability claim against it went nowhere.

There's a timing wrinkle worth tucking in here from Werner v. Finley, decided decades earlier on a very different set of facts. Finley argued that the Werner Bros. partnership that sued him had already transferred its assets — including its claim against him — to a newly formed corporation, and so the partnership had no standing to sue. The court looked at the actual dates: the lawsuit was filed October 10, 1906; the partnership's assets weren't actually transferred to the corporation until October 25. "[E]vidence of an intention... to transfer the assets of a partnership... without evidence that such intention was actually consummated, does not show that the legal title to the claim was ever vested in the corporation." Planning to restructure isn't the same as having restructured — and which entity owns a given claim or obligation can turn on which side of that line a lawsuit happens to fall.

"But They Said..." — The Limits of Equitable Estoppel

Back to the Ernst dealers. Their next theory was equitable estoppel: FNH had told the governments it would "retain" the Versatile dealer network, so FNH shouldn't be allowed to act inconsistently with that now.

Estoppel has three elements, and the court was crisp about all of them: an admission or statement by one party that's inconsistent with a position it later takes; action by the other party in reliance on that statement; and injury to that party if the first party is allowed to contradict itself. The dealers fell apart on element two — they "offered no evidence that they relied on such statements or even knew of them." You can't rely on something you didn't know existed.

"The law does not favor and one may not lightly invoke estoppel... a court should permit invocation of estoppel with care and caution and only when all elements clearly appear."

If you're on the receiving end of a termination and you're tempted to argue the other side is "estopped" because of something they said somewhere else, the threshold question is simple: did you know about that statement at the time, and did you do something — or refrain from doing something — because of it? If the honest answer is no, estoppel isn't going to be the path forward, regardless of how inconsistent the other side's later conduct looks.

"They Made Them Do It" — The Limits of Tortious Interference

The dealers' last angle was tortious interference: an internal FNH memo listed which Versatile dealer agreements FNH would and wouldn't accept as part of the purchase, and the dealers argued FNH had effectively "directed" VFEC to terminate them.

Tortious interference requires showing a contract or valid business expectancy; the defendant's knowledge of it; intentional interference that induces or causes a breach; absence of justification; and damages. The "absence of justification" element is where this claim died. A party with a legitimate economic interest in a contract or expectancy "may with propriety interfere in [its] own self-interest," and "[n]o liability arises for interfering with a contract or business expectancy if the action complained of was an act which the defendant had a definite legal right to do without any qualification." FNH had every legal right to decide, in an arm's-length asset purchase, which existing dealer agreements it would and wouldn't take on. The court cited an Eighth Circuit decision involving the same transaction and a different set of terminated Versatile dealers, which had reached the identical conclusion: "the facts do not demonstrate that any interference... was anything other than an incidental result of the bona fide purchase agreement... It would be unsound to hold that a purchasing company's failure to acquire every dealership contract results in a cognizable claim of tortious interference."

The throughline across all three of these issues is the same: when a counterparty's business changes hands, the new owner's decisions about what to keep and what to leave behind are not, by themselves, wrongs against the people left behind — provided the new owner didn't expressly agree to take on those obligations, didn't misrepresent anything to the people who relied on it, and had a legitimate reason for the line it drew. If you're the one being left behind, your strongest ground is almost always your original contract with the original party — not a claim against whoever bought them out.

Step 7: Define the Last Mile Before You Call It Done

Sometimes the relationship everyone thinks is "over" still has one piece of unfinished business — and how that piece is defined determines whether the ending stays clean.

Jake C. Byers, Inc. v. J.B.C. Investments, 834 S.W.2d 806 (Mo. App. 1992), is about exactly that kind of loose end. Byers sold a mobile home park to JBC Investments. At closing, Byers still owed one thing: filling in a sewage lagoon on the property. So the parties set up an escrow — $36,000 held by a title company, to be released to Byers if the work was done by April 1, 1985, or kept by JBC if it wasn't. Critically, the escrow agreement didn't just say "fill the sewage lagoon" and leave it there. It defined the phrase: "Fill the sewage lagoon is defined by having the lagoon filled with dirt and compressed by a tractor," using fill dirt from a specified source.

Byers had a contractor do exactly that — push dirt in from both sides, run equipment over it repeatedly to compact it, add fly ash to solidify the underlying sludge. JBC said it wasn't enough. At trial, JBC's position was that "fill" should have meant something more specific — placing the dirt in one-foot "lifts," each separately compacted — sufficient to support mobile home pads, based on conversations the parties had when the escrow agreement was signed.

The court wouldn't go there, and the reasoning is the parol evidence rule in action. An agreement that's complete on its face — and this one was, because it didn't just use the word "fill," it defined it — is "conclusively presumed to be the final as well as the complete agreement between the parties." It didn't matter that there was no merger clause; a writing can be complete without one. "Any oral agreement about additional obligations should have been included in the written agreement." JBC's evidence about "lifts" and mobile-home-pad suitability would have added an obligation that the definition, as written, didn't contain — and that's not interpreting a contract, that's rewriting it.

JBC also tried "trade usage" — arguing that "fill," in construction work, customarily means the lifts-and-compaction method. That failed for a more basic reason: JBC never actually proved any such usage was "general, uniform, certain, and notorious" in the industry. And even if it had, trade usage can fill in a term the contract left blank — it can't override a definition the contract already gave.

There's a final piece worth knowing if your business is on the performing side of a wind-down obligation like this one. Every contract to perform work carries an implied promise that the work will be done in a "workmanlike" manner — skillfully, without defects. JBC argued Byers needed expert testimony to prove the lagoon-filling met that standard, especially given the unstated mobile-home-pad purpose. The court disagreed: "workmanlike" is measured against the work as the contract defines it — dirt, compacted with a tractor — not against a purpose that never made it into the writing. And filling a hole with dirt and packing it down with a tractor is well within what an ordinary person can evaluate; no engineering expert required. Byers's evidence — testimony about how the work was done, plus photos, plus the fact that repeated site visits showed no settling or sinkholes — was enough.

The broader point for anyone closing out a business relationship: the big decision — sell the property, end the contract, wind down the partnership — often isn't the last thing that has to happen. There's frequently a tail: a final deliverable, a holdback, an escrow, a punch list. That tail item is its own little contract, and it deserves the same precision as the main deal. If there's a specific standard you're expecting — not just "filled," but "suitable for X" — that standard needs to be written into the document that defines when the escrow releases or the holdback gets paid. Otherwise, when it comes time to ask "was this actually finished?", the answer will be measured against what got written down, not what anyone assumed at the closing table.

Bringing It Together

None of these seven cases are really about whether a relationship should end — in every one of them, by the time the dispute reached an appellate court, everyone agreed it had. What they're about is the mechanics: was this a termination or a forfeiture, did the notice match what the contract required, is there a recoupment obligation hiding behind a clean notice period, does the damages clause hold up as written, what (if anything) survives, and who — if a sale or restructuring is involved — actually stands in whose shoes afterward.

Every one of those questions is easier to get right before the notice goes out than after someone's filed a counterclaim. If your business is heading toward the end of a lease, a dealership, a vendor relationship, an employment agreement, or a sale — or if you've already sent (or received) a termination notice and aren't sure what happens next — our attorneys can walk through the specific language you're working with and help make sure the ending holds up as well as the deal did. Reach out, and let's make sure your exit is as solid as your entrance.

This article is for informational purposes only and does not constitute legal advice. For advice specific to your situation, please consult a qualified attorney.