The 2026 version of this story plays out the same way in businesses and firms of every size. Someone is asked to update an agreement for a new arrangement. The AI tool produces a polished rebuild in four minutes — relocated clauses, new protective provisions, modernized structure, market-standard insurance, a tidy schedule. It reads like the work of a careful senior associate. The polish is the problem. Nobody asked for most of it, one of the “new” clauses is the original document’s own language moved to a different section, and the redline the tool generated is colored text rather than tracked changes, so nobody can accept or reject a single mark. The draft gets forwarded as “the updated version” by someone who has not read past page two.

Generative AI has made contract drafting faster than at any point in the history of the profession. It has not changed who answers for the result. The person who sends the draft owns the draft — every relocated clause, every invented cross-reference, every confident summary of a provision that says something else. Here are the guardrails that make AI-assisted drafting reliable, for the person whose name is on the work and the client whose deal is on the page.

Know the failure modes before you trust the output

AI drafting tools fail in characteristic ways, and none of them look like failure on the screen. They relocate provisions to where provisions conventionally belong, which reads as tidiness and functions as change. They add every protective term they can justify, because thoroughness is what their training rewards. They produce comparisons that are imitations — text colored red and blue — rather than genuine tracked changes a reader can accept, reject, and verify. They describe their own output with total confidence, including the parts they got wrong. And they occasionally invent things outright: a cross-reference to a section that does not exist, a defined term that was never defined, a summary of a clause that says the opposite. Public court dockets already carry examples of professionals who filed machine-invented material without checking it; the pattern is not hypothetical. None of this means the tools are unusable. It means the workflow around them has to be built for exactly these failures, the way good deal hygiene is built for human ones.

Guardrail one: real tracked changes, and tests decide

A contract turn from an AI tool should be delivered exactly as a turn from a careful associate would be: a clean draft and a redline against the version the client last saw, with the redline made of real tracked insertions and deletions. Then two mechanical tests get run before anyone reads a word. Rejecting every tracked change must reproduce the base document exactly. Accepting every tracked change must produce exactly the clean draft. If either test fails, the pair is misrepresenting what changed, and it does not go anywhere.

The point of the tests is that they replace trust with proof. A tool will describe every output as “the updated version” with perfect confidence, and a reader moving fast will believe it. The tests do not care about confidence. The same goes for the structural sweep — numbering, cross-references, brackets, leftover internal notes — which is precisely the layer where machine errors hide, because a document can be grammatically flawless and structurally broken at the same time. The full protocol is the one laid out in the version-control discipline most deals skip, and an AI-heavy workflow needs it more, not less.

Guardrail two: the instruction is less, not more

Left to its defaults, a language model drafts the way a nervous first-year drafts: it adds every provision it can justify, because each addition is individually defensible and thoroughness reads as competence. On a working form a business has used for years, that instinct produces exactly the wrong document — one the owner no longer recognizes, with three load-bearing changes buried under thirty that are not. The corrective is a discipline the tool has to be told, explicitly and every time: the form is the baseline; every mark must be required by the structure, requested by the client, or fixing a true defect; a clause that looks like an addition gets traced to the source before it is touched, because it may be the original document’s own term relocated; suggestions go in as bracketed notes to confirm, never as silent operative text; and rates, limits, and other economics do not move without a decision by the person who owns them. The reasoning behind that approach is laid out in a companion piece on what a good redline looks like, and it applies with double force when the drafter is a machine that never gets tired of adding.

Guardrail three: data handling is a configuration decision, made once

The question “is it safe to put this document in the AI” has to be answered before the matter starts, not paragraph by paragraph. Consumer-grade tools that train on what users type are a different category from enterprise deployments with contractual no-training and retention commitments, and anyone using these tools on other people’s documents should be able to say which category they are in and why. Client documents, deal terms, and anything that could identify a transaction do not go into a tool whose data handling you cannot describe. Frameworks like the formalize this instinct — map where the data goes before you rely on the system — and the mapping takes an hour, once, instead of a judgment call every afternoon. The same care extends to what the tool leaves behind: generated drafts and intermediate output live in a clearly separated working area, not commingled with reviewed final documents, so that six months later nobody has to guess which version a human actually adopted.

Guardrail four: every correction becomes doctrine

This is the guardrail with the highest return and the one most users skip. When a reviewer corrects an AI draft — cut the unrequested provision, put the original clause back where it was, restore the coverage requirement the client had chosen, turn the silent addition into a bracketed note — that correction is a rule surfacing. Left in the chat, it evaporates, and the next session makes the same mistake with the same confidence. Written down once, in plain language the tool loads before it touches the next document, it compounds. The operations getting real leverage from these tools keep those rules somewhere they own — a repository under their control, versioned like any other document, readable by every tool and every person in the practice — rather than locked inside a single vendor’s product. The result over a year is a body of drafting doctrine that reflects how the practice actually works, applied consistently by a tool that no longer needs to be re-taught, and improved every time a human catches something new.

Guardrail five: a human reads every page

The last guardrail is the oldest one. Someone reads the document — not the summary of the document, not the tool’s description of its changes, the pages. That reading is where the garbled clause that passed every structural test gets caught, where the relocated fee clause gets recognized as the original document’s own, and where the judgment a client is actually paying for happens. The division of labor that works is the same one that works in agentic M&A diligence: machines for the volume, humans for the decisions. A tool can produce five turns in an afternoon; only a reader can decide which one should exist.

What a client should ask

Clients are entitled to ask about all of this, and increasingly do. The useful questions are concrete. Does the firm or team use AI tools on my documents, and which ones? Where does my information go, and does the tool train on it? How is an AI-produced draft verified before I see it — is there a real redline, and what tests does it pass? Who owns the playbook the tool follows, and does it reflect how my documents should be handled? Anyone who has done the work will answer all four without hesitation. Anyone who cannot is telling you something important about the four-minute draft you are about to sign.

The technology is not going away, and it should not. Used with these guardrails, it lets a small team deliver turns at a pace that used to require a floor of people, without lowering the standard the work has always demanded. Used without them, it produces beautifully formatted documents that nobody read — and in most cases, the market eventually finds out which kind of document it was handed.

If you are evaluating how AI is used on your contracts, or building a drafting workflow that has to survive scrutiny, feel free to reach out to our firm manager, Magda, at Magda@montague.law, or fill out our contact form. Mention you read this post.

Here is the redline story that plays out more often than anyone in the profession likes to admit. A business owner sends her lawyer the subcontractor agreement the company has used for years and asks for it to be refreshed before the next round of hires. What comes back is a document that is forty percent blue and red. Provisions have been relocated to where they “belong.” A fee-adjustment clause has grown bracketed alternatives. There is a new representations section with its own disclosure schedule, a compliance rider, and coverage requirements rewritten to something more realistic. Every change is individually defensible. The owner reads it and asks the only question that matters: why would we have this when I didn’t ask for it?

That question is the whole subject of this post. A redline is not just a document; it is a negotiating signal and a claim about who owns the paper. The best drafting I know of changes less, and the discipline behind changing less is more rigorous than the instinct to improve everything.

The form is the baseline, not raw material

The first principle is a posture. When a client hands over a working form, that form is the baseline against which every mark is judged, not a starting point to be brought up to some external standard. It contains years of business logic in the client’s own voice, and it has been signed, repeatedly, by counterparties who accepted it. A reviser who treats it as a template to be modernized has changed the client’s document into the lawyer’s document, and the client now has to re-review their own form provision by provision to find out what they still own.

This is not an argument against changing anything. New parties, new defined terms, and a genuinely broken clause all require ink. It is an argument about where the burden sits. The default answer to any given mark is no, and the mark has to earn its way onto the page.

Every mark has to answer one question

The test for each change is necessity, and it comes in three flavors. Does the structure require it — a new signatory, a term that must now be defined, a statutory requirement? Did the client actually ask for it? Does it fix a true defect — a garbled sentence, a dropped word, a cross-reference to a section that no longer exists? If a proposed change cannot answer yes to one of those, it does not go in, however well drafted it is.

The reason is not aesthetic. Every provision in a redline is a negotiation surface. A term the other side has to read is a term they can object to, counter, or trade against something that matters. A form that comes back forty percent marked gives the counterparty forty percent more places to push, and it buries the three changes that are load-bearing under thirty that are not. There is also a credibility cost: when a reader recognizes boilerplate overreach in one place, every other demand in the document becomes suspect. Asking for what you do not need damages your standing on what you do. The same logic drives good negotiating on the money terms, which is why it recurs in the cash-free, debt-free traps that catch founders — the side that asks precisely tends to be the side that gets taken seriously.

Trace before you touch

The most embarrassing red ink in practice is the client’s own term, restyled until it looks like the lawyer’s addition. Picture a form in which a late-payment charge sits in an odd location — under the invoicing procedures rather than with the payment terms. A thorough reviser moves it to where it belongs, tidies the language, and brackets the alternatives. The client opens the redline and sees what appears to be a brand-new fee that nobody requested. Moved furniture reads as new furniture.

So before any clause is treated as an addition, or restructured, trace it to the source document. If it is the client’s own language, conform the entity names and leave it where it sits, in the order the client wrote it. Relocation is a change, and it is almost never a necessary one.

Suggestions are notes; instructions are text

Lawyers see risks clients have not thought about, and they should say so. The question is how. Terms the client has actually decided get drafted tersely, as operative text, exactly as instructed: a non-compete limited to the county where the contractor works, a sixty-day termination right for either side, an annual price adjustment tied to a published index. A suggestion the client has not yet accepted goes into the draft as bracketed text with a short note — “confirm whether to include” — so that it is visible, discussable, and removable in one keystroke. It never becomes operative silently. A client who finds an unrequested restriction quietly in force in their own form has learned something about their lawyer, and it is not the lesson the lawyer intended.

Economics and risk terms do not move on their own

Commission rates, thresholds, insurance limits, indemnities, term and termination economics — these belong to the client. In a representative scenario, a form requires a subcontractor to carry a level of coverage that counsel doubts a small operator can obtain, and counsel quietly lowers it. The reasoning may be sound. The change is still wrong to make unprompted, because it altered the client’s allocation of risk without a decision by the client. When a term looks commercially unrealistic, it becomes a question on the call list, not an edit on the page.

Keep third parties out unless the law needs them in

A related instinct is to pull affiliated companies into an agreement to make protections broader. Sometimes the law genuinely requires it. A parent company that is a party to the old contract being replaced has to sign to terminate it — a two-party document cannot end a contract one of the parties never signed. And in Florida, lets a third-party beneficiary enforce a restrictive covenant only if the contract expressly identifies that person as an intended beneficiary — so an affiliate that needs to enforce a non-solicit has to be named, or the protection is illusory. Those are reasons to bring a third party in, and the drafting should say exactly how far: a joinder “solely for purposes of Section X,” a beneficiary designation for one covenant. Absent a reason like that, the affiliate stays out. Every additional party is additional exposure, additional signature logistics, and, for a client trying to keep entities legally separate, an argument the other side did not have before.

Fix the defects, keep the voice

Minimal ink does not mean tolerating errors. A dropped verb in a waiver clause, a defined term that appears in two spellings, an “in the event that” that never says what event — these get fixed, because a court will read them and a counterparty will exploit them. What does not get fixed is the client’s phrasing where the phrasing is merely informal. The line is defect versus style, and a good reviser can articulate which side of it every mark falls on. This is also where operating agreements and other governance documents reward restraint; the drafting in a Florida LLC deadlock provision works because it does one thing precisely, not because it does everything.

How to read a redline as the client

If you are on the receiving end, here is the pass to run. Check the header first: it should state exactly which version is being compared against which, and the base should be the last document you saw. Then read every insertion and ask whether you asked for it; anything you did not request should either fix a defect you can see or come with a note explaining itself. Look at the economics — rates, caps, limits, dates — and confirm none of them moved without your decision. Look for brackets; every one should be a blank you will fill or a question you will answer, never a decision someone made for you. Look for new parties and schedules and ask what work each is doing. And remember that the most consequential change in a document is often a single word — the holdback that turned on the word “final” is the standing reminder — which is exactly why a redline with less noise is a safer redline. The fewer marks there are, the more likely you are to catch the one that matters.

Less red ink is not laziness. It is the visible result of a reviser who traced every clause, tested every change against necessity, kept the client’s decisions with the client, and left the client’s voice where they found it. In most cases, that document negotiates faster, signs cleaner, and reads, years later, as still belonging to the business that uses it.

If you are updating a form agreement or reviewing a redline you did not expect, feel free to reach out to our firm manager, Magda, at Magda@montague.law, or fill out our contact form. Mention you read this post.

A common Florida deal pattern looks like this: three weeks into negotiating a services agreement, both sides are working from a file named something like Agreement_FINAL_v3_clean_edits(2).docx. The buyer’s counsel sends over “the latest” with a redline attached. The redline shows a change to the indemnity cap that the clean copy does not contain. Nobody can say which version the business owner approved on the phone last Thursday, because the file she approved has since been saved over. Signing is Friday.

Nothing in that scene is exotic. It is what happens when a document moves through a negotiation without version control — the discipline software teams treat as table stakes and most deals still skip. Here is what the discipline actually consists of, why each piece exists, and what it looks like now that AI tools are producing more drafts, faster, than any associate ever could.

Version zero is the document you received, not the one you wrote

Every negotiation starts with a document someone else produced — the counterparty’s form, the client’s decade-old template, the prior deal’s purchase agreement. That document is version zero, and the first rule is that it is never edited. It is saved exactly as received, in its own folder, and every later version is measured against it.

The rule sounds trivial until the base arrives as a PDF. The instinct is to have someone retype it or run it through a converter and start marking up the result. The disciplined move is to convert it to an editable file and then verify the conversion word for word against the PDF before a single change is made. A redline is only as trustworthy as its base; if the base silently dropped a sentence in conversion, every comparison downstream inherits the error and reports it as your change or, worse, hides it entirely.

Nothing gets overwritten, because history is evidence

The second rule is that no version is ever saved over. Each revision that leaves the working session gets a number — v01, v02, v03 — and the prior one is archived, not deleted. Iterating inside a single working session does not require a new number for every save; the boundary is exposure. The moment a draft has been seen by the client, the other side, or a reviewing partner, it is frozen forever.

This matters because a negotiation is a sequence of positions, and disputes are fought over the sequence. A post-closing fight routinely turns on when a word entered the document and who put it there. Consider the eight-figure holdback that turned on the single word “final” — the kind of dispute where the ability to reconstruct exactly which draft introduced a term, and whose redline carried it, is worth more than any argument about what the parties must have meant. If your file history is one overwritten document, you have no history, and you are litigating from memory against someone who kept theirs.

Every version is a pair

A version is not a file. It is two files: the clean draft and a redline showing every change against the base the recipient already knows. Sending a clean copy with the changes described in an email is not version control; it asks the reader to reconstruct the diff by hand and to trust that the description is complete. Sending only a redline is not much better, because the recipient has to accept every change themselves to see what they would be signing.

Three things make the pair trustworthy. First, the redline has to consist of real tracked changes — insertions and deletions the document itself records — not text colored red and blue to look like one. A cosmetic redline cannot be accepted or rejected, cannot be verified, and cannot be relied on. Second, the redline runs against the base the other side last saw. A comparison against your own intermediate draft tells the counterparty nothing useful and, when the two documents disagree, invites the suspicion that something was slipped in between. Third, the header of the redline states exactly which two versions are being compared, so that a reader six months later does not have to guess.

Verification is a test, not a feeling

The clean and the redline are produced separately and can diverge. That divergence is the most dangerous error in document work, because the counterparty reads both and will find the discrepancy at the worst possible moment. So before any version leaves, two mechanical tests get run, and they are tests in the literal sense: they either pass or they do not.

The first test is reject-all. Rejecting every tracked change in the redline must reproduce the base version word for word. If it does not, the redline is misrepresenting what was changed. The second test is accept-all. Accepting every tracked change must produce exactly the clean draft. If it does not, the clean contains something the redline never disclosed, or the redline promises something the clean lacks. The clean, for this reason, is never retyped; it is generated by accepting the tracked file, so that the two cannot drift.

Around those two tests sits a shorter sweep: section numbering is an unbroken sequence, every internal cross-reference points at a section that still exists after the edits, brackets balance and each remaining bracket is a deliberate blank, and nothing intended as an internal note to draft survives in a document headed outside. Then someone reads the rendered redline page by page. Not skims — reads. Software catches structure; only a reader catches a garbled clause that passed every structural check.

The label on the outbound draft is a promise

Internal version numbers are working history and can run high; a heavily negotiated form may pass through a dozen internal turns before the client sees the second one. What the recipient sees should be a clean external counter — the first draft sent is their v1, dated and labeled, whatever it was internally. What actually went out is frozen in its own folder, so that there is never a question about which document a recipient has in hand, and the internal history stays intact behind it.

The label is a promise because Florida law does not wait for signature pages to treat words as binding. Under Florida’s Uniform Electronic Transaction Act, , an email exchange agreeing to a change can be an enforceable record with an enforceable signature. In a representative scenario, an operations manager emails the other side that “the revised exhibit works for us” and the reply says “agreed” — that exchange is a version event whether or not anyone updates a document, and a version log that does not capture it has a hole in it. The discipline is to record, in one line per version, what changed, on whose instruction, and by what medium, including the emails.

What changes when the AI is in the room

Generative AI tools now produce full contract turns in minutes, and the temptation is to treat speed as a reason to loosen the process. It is the opposite. A tool that can generate five drafts in an afternoon can also overwrite, retype, and cosmetically color five drafts in an afternoon, and it will describe each as “the updated version” with perfect confidence. The rules above are exactly the rules that keep a fast tool honest: a frozen base, real tracked changes, the reject-all and accept-all tests reported in plain terms with every delivery, and a human who reads the pages. The firms getting real leverage from these tools are the ones that made the tool follow the discipline, not the ones that let the tool replace it. That is the same conclusion reached in a different setting in what agentic M&A execution changes and what still requires a human, and it holds even more firmly for the document a client will actually sign.

None of this is glamorous, and none of it shows up in a term sheet. It shows up when a deal goes sideways and one side can say, with a file to prove it, exactly what every draft said and when — and the other side cannot. The likely outcome in that fight favors the side that kept the versions.

If you are negotiating an agreement and want the drafting process run with this kind of discipline, feel free to reach out to our firm manager, Magda, at Magda@montague.law, or fill out our contact form. Mention you read this post.

Download: Florida Crypto HQ Formation Checklist (.docx) — a companion resource for this post. Adapt with counsel before use.

A common 2026 relocation conversation looks like this. A crypto company — Series A closed, headcount around thirty, mainnet six months out — is spending too much time in Delaware for the equity and too much time in California or New York for the operations. The founders are exhausted by the state-income-tax posture, the noncompete question, and the banking rejections. Somebody at a conference in Miami mentions that a peer moved operations to Florida and never looked back. The founders start the diligence. Within a week they hit the DBPR money-transmission question, the Ch. 605 series-LLC question, the FL SB 314 stablecoin posture, and the banking-relationship question. Some of those answer well. Some do not. Here is the version that walks a founder through the actual Florida statute stack and the actual 2026 posture, in the order the decisions get made.

First — FL Chapter 560 and the DBPR money-transmission analysis

The single most important preliminary question for any crypto company evaluating Florida is whether the company’s activities require licensure as a money transmitter under FL Chapter 560, the Money Services Businesses Act. The Department of Business and Professional Regulation, through the Division of Consumer Finance, administers the license. The 2023 amendments to Chapter 560 modernized the definition of money transmission to cover certain crypto activities — custody of customer crypto, exchange, and payment facilitation — and left others outside the license. The safe harbor for pure peer-to-peer software provisioning remains, and pure-payment stablecoin activity in a limited compliance posture may be exempt under narrow readings of the statute.

The DBPR posture in 2026 is that the licensing framework is applied literally. If the company holds customer funds — in fiat, in stablecoin, or in any crypto asset — the license is required. If the company facilitates transfers between users, the license is required. If the company is a pure protocol operator that never holds user funds and never controls user assets, the license may not be required, but the analysis has to be documented and reconfirmed annually. Attempting to operate without a license on an aggressive reading of the exemption is not viable — DBPR enforcement has been active, and the prior enforcement actions against unlicensed money-transmission activity carry real fine and shutdown authority.

The application itself requires a surety bond scaled to volume, a BSA/AML program approved by DBPR, and ongoing quarterly reporting. Renewal is annual. For a well-run crypto company that intends to operate at scale, the license is not a barrier — it is a compliance stack that the company builds once and maintains. For a company that wants to avoid licensure, the operational structure has to be genuinely non-custodial and genuinely non-facilitating, and the compliance memo supporting the exemption position has to be in the file.

Second — the FL Digital Assets Act posture and the SB 314 stablecoin question

Florida’s legislature has been active on crypto regulation without landing on a single comprehensive statute in the mold of Wyoming or Texas. The FL Digital Assets Act was introduced and refined across the 2024, 2025, and 2026 legislative sessions, moving toward a framework that recognizes crypto as property for state-law purposes, provides an exemption structure for certain protocol activities, and coordinates with the DBPR licensing regime for anything that overlaps money transmission. The current 2026 posture is that the Digital Assets Act pieces exist across several statutes rather than a single chapter, and reading them together requires coordination between Chapter 560, Chapter 501 (consumer protection), and any provisions the legislature adds in the current session.

FL SB 314 and its successor bills addressed the stablecoin question in a Florida-specific frame. The federal GENIUS Act, once fully in force, provides a national framework for payment stablecoins, but Florida SB 314 explored a state-level layer for stablecoin issuers or operators with a Florida nexus. The current status of that layer — whether preempted by the GENIUS Act, whether adopted, whether modified in the 2026 session — is a moving target as of publication and needs to be reconfirmed with counsel at the time of any Florida stablecoin operation.

Third — the business-friendly incorporation posture

Florida’s appeal to a crypto company is not primarily the licensing framework. It is the combination of no state income tax on individuals, no franchise tax on LLCs, and a favorable LLC statute at FL Ch. 605. A founder resident in Florida pays no state tax on personal income from any source. A Florida LLC pays no Ch. 220 corporate income tax. A Florida corporation does pay Ch. 220 income tax, but at rates and structures that are broadly competitive with Delaware.

FL Ch. 605 — the Florida Revised Limited Liability Company Act — carries a modern statute with flexibility on management structure, member classes, and manager fiduciary duty modifications. FL Ch. 607 — the Business Corporation Act — has been steadily updated to preserve corporate governance flexibility, including provisions relevant to crypto boards that want to build an oversight architecture different from a traditional public-company board. Neither statute forces a crypto company into an off-the-rack governance form, and the flexibility matters for a company that operates a foundation-plus-C-corp stack.

Fourth — the series-LLC posture for isolating protocol, foundation, and treasury

Florida’s series LLC — added to Ch. 605 and refined in subsequent legislative sessions — permits a single LLC to establish multiple series, each with its own assets, liabilities, and members, and each isolated from the liabilities of the other series. For a crypto stack that wants to isolate the protocol from the foundation from the treasury without incurring the cost of multiple separate entities, the series LLC has become an increasingly common vehicle in 2026.

The doctrine is not perfectly settled — the enforceability of series-LLC liability isolation in a non-Florida bankruptcy or a non-Florida litigation is still developing, and courts outside Florida have not uniformly recognized the internal-shield rule. For a crypto operation with genuinely Florida-based operations and a manageable litigation exposure profile, the series structure is defensible. For a company with meaningful non-Florida contacts, the series may not carry the liability isolation the company was counting on, and separate LLCs may be safer.

Fifth — employment and non-compete posture under FL § 542.335

FL § 542.335 is one of the most employer-friendly noncompete statutes in the country. The statute permits restrictive covenants that protect a “legitimate business interest” — trade secrets, valuable confidential information, substantial relationships with specific existing or prospective customers, customer or client goodwill associated with a specific geographic location, and extraordinary or specialized training. It permits time restrictions of six months to two years without additional showing, and up to five years with adequate showing. The statute directs courts to modify overbroad restrictions rather than void them entirely — the blue-pencil rule is codified.

For a crypto company that wants meaningful non-compete coverage on senior engineers, protocol architects, and founding team members, FL § 542.335 supports what few other states support. The California posture under Bus. & Prof. Code § 16600 is near-per-se against non-competes. New York has narrowed its statute and its case law is skeptical. The FTC’s federal noncompete rulemaking, whatever its ultimate scope after the various pending challenges, does not eliminate FL § 542.335 as a matter of state law. Florida remains the favorable jurisdiction, and structuring the employment agreements at the Florida entity — with the covenant subject to Florida law and Florida venue — captures the benefit.

Sixth — real property considerations for Bitcoin mining and infrastructure

For crypto companies with mining or infrastructure operations, the real-property analysis in Florida rewards specific attention. Energy pricing varies significantly across utilities — Duke Energy in the north-central corridor, FPL across the peninsula, Gulf Power in the western Panhandle, and the municipal utilities in Jacksonville and Orlando each carry different industrial rates and demand structures. The Panhandle’s lower energy costs and lower ambient temperatures have made it attractive for mining operations willing to accept the reduced infrastructure and workforce depth. South Florida’s higher energy costs limit mining but do not limit infrastructure operations that are less energy-intensive.

Zoning is county-by-county and often city-by-city. Industrial-use zoning is the modal fit for large mining operations; agricultural-with-conditional-use has been used successfully for smaller operations in more rural counties. Noise ordinances vary and mining fans generate real noise — the operational plan needs to survive the specific ordinance where the facility sits. Florida DEP environmental compliance matters for cooling water use, emergency generator emissions, and any wastewater discharge. Diligence the specific site with counsel who has done Florida mining-facility work before signing any lease or purchase.

Seventh — the banking relationship, still the hardest step

Every crypto company relocating to Florida hits the banking question, and the honest answer in 2026 is that it remains the hardest operational step. A small set of Florida-chartered banks has developed a crypto-company practice. A larger set of national banks has crypto verticals that will consider Florida-domiciled companies. A larger still set of banks will decline the account without articulating why. The GENIUS Act’s federal framework for stablecoin operators has helped at the margins, but the residual bank-side reputational and BSA/AML compliance concerns still narrow the set of willing banks.

The practical playbook is to open the banking relationship before finalizing the entity structure, to lead with a clean compliance narrative and a documented BSA/AML program, and to have a fallback plan through a fintech or off-ramp partner. Ripple’s Florida office, Coinbase’s Florida nexus, and other named crypto operators in the state have established that the model can work — but each of them fought for the banking relationship on the front end, and every new entrant fights for it too.

Download: Florida Crypto HQ Formation Checklist (.docx) — a companion resource for this post. Adapt with counsel before use.

For related discussion, see our overview of the foundation and DAO wrapper for high-growth crypto companies, our note on accepting stablecoin payments in Florida under the GENIUS Act, and our earlier piece on the SEC and CFTC crypto taxonomy in Florida for 2026. FL Chapter 560 is available from the .

If you are relocating or forming a high-growth crypto company in Florida and want a second view on the DBPR, § 542.335, series-LLC, or banking questions, feel free to reach out to our firm manager, Magda, at Magda@montague.law, or fill out our contact form. Mention you read this post.

Download: Crypto Tax Posture Checklist (.docx) — a companion resource for this post. Adapt with counsel before use.

A common 2026 crypto founder tax conversation looks like this. A Delaware C-corp is a year past its Series A. Tokens have been issued out of a Cayman foundation. The founder team took a token allocation from the foundation, subject to vesting, before mainnet. The company has been earning fees, holding a treasury denominated in the native token plus a mix of stablecoins, and lending some of that treasury to a market maker for exchange-liquidity purposes. The founders assume the tax story is simple because “we’re just holding tokens” — and the CFO opens the return and finds that the story is not simple at all. There are five separate tax issues in the file, and every one of them was decided months or years earlier by drafting choices that the founders had never seen framed as tax questions.

Here is the version of the crypto founder tax story that gets told after the founders discover it, laid out in the sequence the doctrinal decisions actually get made.

First — income recognition on token receipt under § 61

IRC § 61(a) sweeps into gross income all “income from whatever source derived.” The IRS has, over the last several years, applied that principle to virtually every mode of crypto token receipt. Rev. Rul. 2019-24 confirmed that hard-fork airdrops are ordinary income at fair market value at the moment of dominion and control. Rev. Rul. 2023-14 extended the same treatment to staking rewards, taxing them at receipt rather than at sale. IRS Notice 2014-21 established the underlying framework that crypto is property, not currency, and that transactions in crypto are taxable events under normal property principles.

The one case that could have narrowed this framework — Jarrett v. United States, No. 3:21-cv-419 (M.D. Tenn.) — was the taxpayers’ attempt to argue that newly-created tokens received through Tezos staking were not income until sold, on the theory that a taxpayer who bakes a loaf of bread does not recognize income by baking it. The IRS refunded the Jarretts’ tax rather than defend a merits ruling, and the case was ultimately dismissed as moot after Rev. Rul. 2023-14 was issued to formalize the government’s position. Practitioners took the sequence as instructive rather than dispositive — the IRS was unwilling to lose the point on a fully-briefed merits ruling, and Rev. Rul. 2023-14 papered over the ambiguity, but the underlying question is not fully resolved.

The practical impact on a high-growth crypto company is that every token receipt event on the company’s books — protocol fees denominated in the native token, staking rewards, ecosystem-partner airdrops — is potentially ordinary income at fair market value at the moment of receipt. The valuation methodology matters. Volume-weighted average price over a defined interval, midpoint of a bid-ask, or oracle price at a specific block — the company needs one method, documented in a tax memo, and applied consistently. The tax provision in every agreement involving a US-person token transfer needs to address who bears the tax cost if the characterization goes the wrong way.

Second — the § 83 problem on founder token grants

IRC § 83 treats property transferred in connection with the performance of services as ordinary income at the time it becomes substantially vested, at the fair market value on that date. IRC § 83(b) allows the recipient to accelerate the income recognition to the grant date, capturing all subsequent appreciation as capital gain. For equity, this is well-trodden ground — file the 83(b) within thirty days of grant, pay tax on the low grant-date value, and later exit at long-term capital gain rates.

For token grants, § 83 is harder. The token often does not exist on mainnet at the grant date. The company holds a right to allocate tokens to the founder at TGE, subject to a vesting schedule that runs before and after mainnet launch. Whether the founder has received “property” for § 83 purposes on the grant date, or has instead received only a contractual right that ripens into property later, is a live question. The industry consensus, informed by informal IRS guidance and PLR 202124008-style discussion, has coalesced around treating the token grant as a § 83 event at the moment of grant, filing an 83(b) election, and paying tax on the discounted grant-date fair market value.

The 83(b) election is only valuable if the IRS honors it. The company documents this by preserving a formal valuation memo at grant — a discounted-cash-flow analysis of the protocol’s projected fee generation, a comparable-transaction analysis referencing other pre-TGE token allocations, or an option-pricing model treating the token grant as an option on the eventual mainnet launch. The founder files the 83(b) within thirty days, retains proof of certified mailing, and both parties agree in the Token Grant Agreement not to take an inconsistent position on their own returns. If the election fails on audit, the founder faces ordinary income at each vesting event at the then-current — likely much higher — fair market value.

Third — treasury token lending v. sale under § 1058

IRC § 1058 permits a nontaxable loan of securities where the loan agreement satisfies each of four conditions — return of identical securities, no reduction of the lender’s opportunity for gain or loss, callable on notice, and no other legal or economic transfer. If the loan satisfies § 1058, the transfer is not a disposition and the treasury holdings retain their basis and holding period. If any condition fails, the transfer is a sale, recognized at fair market value at the moment of transfer.

For a crypto company that lends treasury tokens to a market maker for exchange-liquidity purposes, the § 1058 question is central. If the loan is properly documented — the market maker returns identical tokens, cannot substitute a variant or a fork, cannot re-hypothecate in a way that changes the lender’s economic position, and the loan is callable — the position that the transfer is a nontaxable loan is defensible. If any of those conditions is not documented, the transfer is potentially a taxable disposition, and the company owes tax on the appreciation.

The treatment gets harder when the loan crosses a fork or a governance-driven token change. The MicroStrategy and Grayscale posture on crypto treasury reserves has been that lending is § 1058-eligible if properly structured; the IRS has not directly opined for crypto, and the analogy to securities lending is contested but widely followed in practice. The tax memo supporting the position needs to be in the file at the moment the loan closes, not reconstructed at audit.

Fourth — sourcing of crypto income under § 863 and state nexus

IRC § 863 and its regulations govern sourcing of income for federal purposes, and every state applies its own nexus and apportionment rules on top of it. For a Delaware C-corp with a Cayman foundation, a Florida operations office, and remote engineers across five states, the sourcing analysis quickly becomes non-trivial. Fee income denominated in the native token — where is it sourced when the fee is paid on-chain by a user in Singapore, to a protocol governed by a Cayman foundation, for services rendered by an engineer in Miami?

The federal analysis under § 863 typically starts with the services-rendered analysis of Treas. Reg. § 1.863-3, but there is no crypto-specific guidance, and reasonable positions vary. The state analysis is where the money actually moves. Florida has no state corporate income tax on LLCs and imposes Ch. 220 income tax on corporations with defined nexus. Delaware imposes franchise tax and, for headquartered corporations, income tax on Delaware-source income. States with economic-nexus statutes patterned on South Dakota v. Wayfair, Inc., 585 U.S. 162 (2018), have extended nexus theories to businesses without physical presence — a doctrine that applies awkwardly but not obviously against a protocol business.

The foreign-tax-credit posture matters when the foundation pays foreign tax and US owners want to credit it. IRC § 901 permits the FTC, but the credit requires that the foreign tax be a compulsory levy on income, and the sourcing analysis has to align US and foreign characterizations of the income. Documentation preserved at the time of the foreign tax payment, and coordination with the US owner’s return, are what make the FTC survive audit.

Fifth — foundation choice-of-vehicle tax posture

The choice among Cayman Foundation, Panama Private-Interest Foundation, Swiss Foundation, and Wyoming DUNA is not driven by tax alone, but tax posture is dispositive on several sub-questions. The check-the-box election under Treas. Reg. § 301.7701-3 determines whether the foundation is treated as a corporation, a partnership, or a disregarded entity for US federal tax purposes. Left as a corporation, a Cayman foundation is generally not a controlled foreign corporation for US purposes because it typically has no “shareholders” in the US-tax sense, sidestepping Subpart F and GILTI inclusions under IRC §§ 951-965. But if US persons receive tokens characterized as equity-like interests in the foundation, PFIC exposure under IRC §§ 1291-1298 attaches and generates ugly annual reporting and interest-charge outcomes.

The Effectively Connected Income analysis runs the other direction. If the foundation performs services in the US, holds US real property, or otherwise develops a US trade or business, ECI is subject to US tax and branch-profits tax at the entity level. The service-agreement architecture between the foundation and the C-corp — who does what, where, for whose account, at what transfer price — controls the ECI analysis. That is not window-dressing, and a transfer-pricing study becomes part of the file when the intercompany amounts are material.

The Wyoming DUNA sits in a different tax posture entirely. Because it is a domestic unincorporated nonprofit association, its US tax treatment tracks the entity classification rules and any tax-exempt qualification it can support. For US-based projects that want simpler US tax reporting and are willing to give up the offshore optionality, the DUNA has become the domestic default in 2026. For projects with meaningful non-US token-holder bases and non-US ecosystem operations, the Cayman foundation remains the modal choice.

Download: Crypto Tax Posture Checklist (.docx) — a companion resource for this post. Adapt with counsel before use.

For related discussion, see our overview of the foundation and DAO wrapper choice for high-growth crypto companies, our note on founder token vesting, and our earlier piece on the token warrant in a crypto equity round. IRS Notice 2014-21 is available from the .

If you are structuring the tax posture of a high-growth crypto company and want a second view on § 61, § 83, § 1058, § 863, or foundation-choice questions, feel free to reach out to our firm manager, Magda, at Magda@montague.law, or fill out our contact form. Mention you read this post.

Download: Protocol Acquisition Diligence Checklist (.docx) — a companion resource for this post. Adapt with counsel before use.

A common 2026 crypto M&A conversation looks like this. A well-funded acquirer — a public company chasing a stablecoin rail, a hedge fund building an on-chain treasury strategy, a larger protocol looking to absorb a competitor — decides it wants to buy a protocol. Not a company that owns a protocol. The protocol itself. The smart contracts, the brand, the community, the token supply, the treasury, and whatever share of governance can be transferred in a single transaction. The acquirer’s M&A team opens a familiar playbook — SPA, escrow, indemnification, disclosure schedules — and immediately runs into a target that has no clean cap table, no corporate seller, and a governance body that is not a board of directors but a rolling token-holder vote. The playbook does not fit.

Protocol-level M&A is real, closing at increasing frequency in 2026, and the deals that work follow a pattern that looks nothing like what a traditional M&A lawyer expects on day one. Here is how it maps out in practice.

First — the three flavors of crypto M&A

Both sides often use the phrase “acquire the protocol” to mean three different transactions. The paper has to reflect which. The traditional acqui-hire is closest to standard M&A — the target is a Delaware C-corp or a Cayman foundation that owns the protocol IP, employs the engineers, controls the admin keys, and holds the treasury. The buyer executes a stock purchase or a merger, steps into the corporate seat, and inherits the protocol relationship. This flavor works when the protocol has never really been decentralized and the buyer wants to preserve the operational team, which is often the actual value.

The protocol-only acquisition is a different animal. The buyer is not buying the corporate seller. The buyer is buying a defined bundle — the smart contract admin authority, the trademark, the reference-client repository, the front-end domain, the governance-facilitation contracts, and sometimes an agreement from the founding team not to build a competing protocol for a period of years. The corporate seller may continue to exist as a services company, may be wound down, or may be spun into a separate deal. The Protocol Purchase Agreement — which is not any standard M&A form — has to enumerate what is being transferred and how, because there is no corporate wrapper carrying the assets.

The treasury acquisition is the newest and the strangest. The target is a DAO — a Wyoming DUNA, a Marshall Islands DAO LLC, a Cayman foundation with an on-chain governance overlay — that has accumulated a large treasury and either wants to sell it, wants to acquire another protocol using it, or wants to be acquired by a buyer who is really only interested in the treasury. The transaction papers itself in on-chain governance votes, token swaps, and treasury-migration ceremonies, and the traditional-M&A concept of “closing” collapses into a series of block-height events.

Second — what “ownership” even means when there’s no cap table

In a corporate deal, the answer to “what does the buyer own after closing” is a share certificate and a board seat. In protocol M&A the question splits into four separate ownership layers. Token allocation is the first — a defined share of the outstanding supply transferred, vested, or held in a treasury pool the buyer directs. Governance rights are the second — a council seat, a veto over parameter changes, or a temporary supermajority during transition, all of which have to be encoded in the governance contracts, the foundation charter, or a side agreement with the DAO. Treasury custody is the third — diligence of every wallet, multisig, timelock, and off-chain custody arrangement, with a ceremony at close that transfers control. Admin-key authority is the fourth and most underestimated — proxy upgrade keys, guardian keys, emergency-shutdown authority, oracle-update permissions. The transfer of those keys is the transfer of the protocol. If the ceremony is done wrong, the buyer owns a set of wallets and a treasury but does not own the ability to change the protocol.

Third — diligence looks nothing like corporate diligence

The diligence process on a protocol acquisition breaks the traditional M&A checklist. Code audit is now central — not because the buyer wants to know whether the software works, but because unresolved audit findings are exploitable liabilities that survive closing. Every audit engagement, every finding, every remediation status, every follow-up audit becomes part of the diligence file.

Protocol history is the second addition. The buyer needs to walk every past incident — exploits, near-misses, white-hat rescues, bug-bounty payouts, admin-key mistakes, governance attacks. This is not a hypothetical exercise; on-chain history is public and the buyer will be judged post-close by what the community already knows.

Governance vote history is the third. Every past proposal, every vote outcome, every quorum result, every unusual voting pattern. The diligence file has to include a governance memo that would survive review by a securities regulator asking whether the protocol has ever been meaningfully decentralized.

Treasury reconstitution rights and admin-key transfer mechanics round out the diligence file. The buyer needs a written key-rotation plan reviewed by counsel and by security engineers, executed with witness-adequate documentation, and audited against on-chain events after close. Every meaningful protocol M&A deal that has gone wrong post-close has an admin-key story at the center of it.

Fourth — the regulatory posture is the whole conversation

Every protocol acquisition sits inside a regulatory posture that the deal cannot ignore. The SEC’s theory that a protocol issuer is a securities issuer runs through SEC v. Kik Interactive, Inc., No. 19-cv-5244 (S.D.N.Y. 2020), SEC v. Telegram Group Inc., No. 19-cv-9439 (S.D.N.Y. 2020), SEC v. LBRY, Inc., No. 21-cv-260 (D.N.H. 2022), and SEC v. Terraform Labs Pte. Ltd., No. 23-cv-1346 (S.D.N.Y. 2024). If the buyer becomes the “issuer” post-transaction, the buyer inherits the securities exposure. If the buyer’s purchase itself involves the distribution of tokens as consideration, the transaction may be an issuance of unregistered securities on the buy side. The CFTC angle emerges when the protocol involves a commodity token or a derivatives product — the CFTC v. Ooki DAO default judgment, No. 22-cv-05416 (N.D. Cal. 2023), extended DAO liability directly to token-holders participating in governance, and Sarcuni v. bZx DAO, No. 22-cv-618 (S.D. Cal. 2023), carries the same posture in private litigation. FinCEN reaches the transaction when the protocol operates as a money transmitter, with state MSB registrations layering on top — Florida’s DBPR under FL Ch. 560, New York’s BitLicense, California’s DFPI. A protocol acquisition that does not diligence the state MSB stack has not diligenced its own regulatory ceiling.

Fifth — how the DAO actually approves being sold

The mechanics of the sale vote turn a protocol M&A conversation from a two-party negotiation into a governance event. If the target is a DAO or a foundation with a token-holder overlay, the transaction requires a governance vote — and the vote has to pass under the DAO’s own rules. Quorum is the first mechanical question; many DAOs have never had a vote reach quorum on an important question. Passage thresholds vary widely, and the deal cannot proceed if the threshold is unreachable. Sybil protection is the second. Nothing prevents a sophisticated actor from borrowing enough tokens to swing a vote unless the governance architecture is designed to prevent it — snapshot at a pre-announcement block, delegated voting, quadratic voting, or a foundation-council override on a hostile vote are the common defenses. Deal announcements have to be timed around this risk.

Sixth — deal papering in the absence of a clean corporate seller

The Protocol Purchase Agreement is not a form document. It borrows from the SPA, from the asset-purchase agreement, and from the technology-transfer agreement, and it has to solve four problems that traditional M&A does not.

Reps and warranties keyed to on-chain state is the first. The seller’s reps have to speak to smart-contract security, admin-key custody, treasury holdings verifiable on-chain, governance-vote history, and the absence of undisclosed exploits or unresolved audit findings. The buyer’s reliance is meaningful only if the reps track on-chain observable facts and the buyer performs the observation.

Indemnification without a corporate obligor and its escrow substitute is the second. If the target is a DAO, there is no continuing corporate entity to sue. The workaround is a treasury holdback governed by a smart-contract escrow that releases over time and can be clawed back on defined breach events. The clawback conditions have to be codeable, not just definable, and the choice of oracle, custodian for the multisig, and dispute-resolution mechanism are all deal terms.

Founder rollover and retention is the third. In a foundation-plus-C-corp target, the founders are often paid partially in continued token vesting, key-person retention agreements, and non-compete undertakings. The non-compete has to be enforceable in the founders’ home jurisdictions — a Florida-based founder benefits from FL § 542.335’s employer-friendly posture; a California-based founder faces Bus. & Prof. Code § 16600’s near-per-se ban.

Seventh — what goes wrong post-close

The failure modes on a protocol acquisition are predictable. Treasury drift is the first — after close, the treasury composition begins to shift because the new owner is trading, staking, or deploying it into strategies the community did not anticipate; written treasury policies, publicly communicated at announcement, mitigate this. Orphaned admin keys are the second — somewhere in the transaction a signer transfers keys and something in the ceremony misfires, leaving a wallet that should have been retired with residual authority. Detailed key-transfer documentation and independent post-close verification prevent this. Community exodus is the third; retention conversations that begin at announcement, not at close, are what keep the community intact. Governance capture attempts are the fourth — the acquirer often needs to hold a permanent stake sufficient to defeat a hostile vote, at least during the transition period, and that stake has to be modeled into the deal economics.

Download: Protocol Acquisition Diligence Checklist (.docx) — a companion resource for this post. Adapt with counsel before use.

For related discussion, see our overview of the foundation and DAO wrapper choice for high-growth crypto companies, our note on the board consent that supports a token generation event, and our earlier piece on a foundation-led acquisition of a spun-out protocol. For the CFTC’s DAO liability posture, see the .

If you are structuring a protocol-level M&A transaction — as buyer, seller, or DAO council — feel free to reach out to our firm manager, Magda, at Magda@montague.law, or fill out our contact form. Mention you read this post.

The discovery usually happens on a Tuesday, three weeks before signing. Buyer’s counsel is building the capitalization representation and asks for the board consent approving the Series A option pool increase. There isn’t one. Or the minute book shows 12 million shares outstanding against 10 million authorized. Or the charter amendment everyone operated under for six years was approved by the board but never filed. Or an entire director class was “elected” at a meeting that never had a quorum, and that board approved everything since. The company has been running for years on corporate actions that were never properly authorized — and now a buyer’s diligence team is staring at the question every deal lawyer dreads: is this stock even valid?

Delaware’s old answer was terrifying; the modern answer is a procedure.

Under the pre-2014 case law, the answer could be catastrophic. Decisions like STAAR Surgical Co. v. Waggoner treated stock issued without valid authorization as void — not voidable, void — and void acts couldn’t be fixed by good intentions, the passage of time, or everyone’s shared assumption that the shares existed. A technical foot-fault could unwind a cap table. Delaware’s response was Sections 204 and 205 of the DGCL, effective in 2014: a statutory machine for ratifying “defective corporate acts,” with the core rule that no defective corporate act or putative stock is void or voidable solely because of a failure of authorization, if properly ratified under § 204 or validated by the Court of Chancery under § 205. The full text of both sections is on the state’s site .

The § 204 mechanics are precise, and precision is the point. The board adopts resolutions identifying each defective act, its date, the shares of putative stock involved, and the exact nature of the failure of authorization, then approves ratification. If the underlying act would have required stockholder approval — a charter amendment, a merger, an overissuance requiring more authorized shares — the ratification goes to stockholders too, with notice. If the defective act originally required a filing with the Secretary of State, the company files a certificate of validation. Done correctly, the ratification is retroactive: the act is treated as valid as of the date it originally occurred, and downstream acts that relied on it inherit that validity. Challenges get a short fuse — claims attacking a ratification generally must be brought within 120 days of the validation effective time. For situations self-help can’t reach — no functioning board, disputed control, ratification votes that can’t practically be assembled — § 205 lets the company or other interested parties petition the Court of Chancery to validate acts directly, the route made famous by the cap-table cleanups in cases like In re Numoda Corp. The important limit: the statute cures failures of authorization, not deliberate defiance — Chancery made clear in Nguyen v. View, Inc. that an act taken in conscious disregard of a required approval isn’t a “defective corporate act” eligible for ratification at all.

Florida now has the same machine, and almost nobody uses it on purpose.

Florida imported this framework into the Business Corporation Act, at sections 607.0145 through 607.0152 — definitions, the substantive rule that ratified or validated defective acts are not void or voidable, board ratification with the same required statements (s. 607.0147), quorum and voting rules keyed to the action being ratified (s. 607.0148), notice to holders of valid and putative shares (s. 607.0149), retroactive effect to the date of the original defective action (s. 607.0150), articles of validation filed with the Department of State where the underlying act required a filing (s. 607.0151), and judicial validation in circuit court plus the 120-day claim window (s. 607.0152). The Florida statute is expressly nonexclusive — common-law ratification survives alongside it — but for anything touching putative shares, the statutory route is the one that produces a paper trail a buyer will accept. For Florida targets, this pairs naturally with the other pre-closing housekeeping we’ve written about, like reinstating an administratively dissolved target: same genre of problem, same lesson that the fix is cheap before signing and expensive after.

In a deal, the question is never just “can we fix it” — it’s who bears the fix.

First, diligence has to find the defects, which means someone actually reconciles authorized against issued shares across every amendment, traces each equity grant to a board or committee approval, and checks that written consents satisfied the statute when they were used — the consent-mechanics traps we covered in our post on DGCL 228 written consents are a leading source of quiet defects. Option-plan hygiene is its own defect factory: grants approved after the fact, evergreen increases never ratified, exercises honored against a plan that had expired. Those problems compound at closing, when every option must be cashed out or assumed against a cap table everyone has to certify — the mechanics in our post on option treatment in a sale assume the underlying grants were valid in the first place.

Second, sequencing. A ratification takes real calendar time — board action, stockholder approval if required, notice, filings — and the 120-day challenge window doesn’t close before most deals need to. Buyers respond in a few standard ways. They make completed ratification a signing or closing condition, with the resolutions and certificates of validation as scheduled deliverables. They insist the ratification happen far enough ahead that notice has gone out and no challenge has surfaced, even if the window remains technically open. And they backstop the residual risk with a specific indemnity or escrow tied to capitalization claims — which, unlike general rep breaches, are the kind of fundamental exposure that survives caps and baskets in most private deals. Where a stockholder vote on the ratification can’t be quietly obtained — because the putative holders and the valid holders disagree about who gets to vote — the parties are usually headed to a § 205 or s. 607.0152 proceeding, and the deal timeline has to absorb a court’s schedule.

Third, the seller-side lesson, which is really a founder lesson: run the ratification before the buyer finds the defect. A company that shows up with a clean validation package — resolutions identifying each defect, the votes, the filed certificates, the notice, the expired challenge window — has converted a price-chip into a footnote. A company that learns about its own cap table from the buyer’s associate has handed the other side leverage measured in escrow points and closing delay. The difference is a few weeks of corporate work done a year early. This belongs on the same pre-LOI punch list as entity standing, minute-book completeness, and the consent inventory in our Florida M&A diligence checklist.

Treat the statutes as deal infrastructure, not emergency equipment.

There’s a reason these provisions exist in both states: growing companies make paperwork mistakes at a fairly predictable rate, and the law decided that punishing everyone with void stock served nobody. But the statutes reward the orderly. They demand specificity about each defect, they impose real approval and notice mechanics, and they distinguish sharply between the company that failed to get an authorization and the company that knew it needed one and proceeded anyway — only the first gets the cure. For buyers, the practical rule is to treat any material defect as unratified until the certificates are filed and the window has run, and to price the residual tail. For founders, the practical rule is simpler: your cap table is a legal instrument, not a spreadsheet, and the cheapest time to make it true is before anyone with leverage is reading it.

If you are heading into a sale with cap table or corporate-authorization questions — on either side of the table — feel free to reach out to our firm manager, Magda, at Magda@montague.law, or fill out our contact form. Mention you read this post.

Here is a deal pattern that surfaces more often than anyone plans for: a Florida business owner dies — mid-negotiation, mid-LOI, or simply mid-career — and within months the company is on the market. Sometimes the family can’t run it. Sometimes the will directs a sale. Sometimes a buyer who circled for years sees the moment. Either way, the counterparty across the table is no longer a founder; it’s a personal representative operating under Florida’s Probate Code, and the deal now runs on Chapter 733 as much as on the purchase agreement. Buyers who treat an estate sale like an ordinary founder sale miss both the traps and the leverage.

Start with whether the personal representative can sign at all.

Florida gives personal representatives a long menu of powers exercisable without court order. Under section 733.612, acting reasonably for the benefit of interested persons, a PR may dispose of assets other than real property at public or private sale (subsection (5)), sell any personal property of the estate for cash or credit (subsection (21)), perform or compromise the decedent’s contracts (subsection (2)), consent to the merger, dissolution, or reorganization of a corporation or other business enterprise (subsection (17)), and execute whatever instruments the exercise of those powers requires (subsection (27)). Because corporate stock and LLC membership interests are personal property, an equity sale of the decedent’s company generally sits comfortably inside the PR’s no-court-order authority.

But the statute opens with the qualifier that decides real deals: these powers exist “[e]xcept as otherwise provided by the will or court order.” Read the will. A will that requires the business be offered to a child first, or held in trust, or sold only with the consent of named beneficiaries, overrides the statutory menu. Buyer’s counsel should ask for letters of administration, confirm they’re unrestricted, and check the will’s dispositive and administrative provisions before spending diligence money. Two adjacent rules matter too. If the decedent ran the business as an unincorporated venture — a sole proprietorship, common in trades — subsection (22) lets the PR continue it in the same form for only four months from appointment, with longer periods requiring court approval, which puts a statutory clock on the sale process itself. And if the decedent had already signed a letter of intent or purchase agreement, subsection (2) empowers the PR to perform or compromise it — the deal your counterparty signed before dying is still very much alive. On the sell side, a decedent who signed a binding LOI has bound the estate; that’s one more reason to be careful about what an LOI actually promises before anyone’s health is assumed.

Real property runs on different rails than the operating company.

Many lower-middle-market deals bundle an operating company with the land it sits on. The equity is personalty; the land is not — and section 733.613 governs. If the will confers a specific power to sell real property, or even a general power to sell any asset of the estate, the PR may sell without court authorization, and the statute adds a sentence buyers should frame: under , a purchaser in a sale under a specific power, or under a court order authorizing or confirming the sale, takes title free of claims of estate creditors and beneficiary entitlements, existing recorded liens excepted. If instead the estate is intestate, or the will lacks a workable power of sale, the PR may still contract to sell — but no title passes until the court authorizes or confirms the sale. That court order is not a formality to schedule casually; it’s a closing condition with notice dynamics, and the purchase agreement should treat it as one, with an outside date and clarity about who bears the delay risk. Title underwriters in Florida know these rules cold and will drive the requirements list; get them into the file early.

One more authority wrinkle deserves respect: self-dealing. Under section 733.610, a sale or encumbrance to the personal representative or the PR’s spouse, agent, or attorney — or any transaction shadowed by a conflict of interest — is voidable by interested persons unless the will or a contract of the decedent expressly authorized it or the court approves it after notice. That pattern is not exotic. The longtime general manager who is also the decedent’s child and now the PR, buying the company from the estate, is a management buyout wrapped in a statutory conflict. The clean path is court approval with notice to everyone with standing to complain later. Skipping it leaves the buyer owning a voidable deal.

The creditor clock changes how you paper indemnities.

Florida probate runs a compressed statute of limitations regime that deal lawyers can actually use. Claims against the decedent must be presented within three months after first publication of the notice to creditors — thirty days after service, for creditors who must be individually served — under section 733.702, and section 733.710 drops an absolute two-year bar after death regardless of notice, with narrow exceptions for timely-filed claims and recorded liens. For a buyer, that timetable cuts both ways. Early in administration, the universe of claims against the estate is genuinely unknown; late in administration, it is statutorily frozen in a way no ordinary founder sale can match. Timing the closing against the claims window — or at least pricing where the process stands — is real leverage.

The structural problem is what happens after closing. An estate is a dissolving counterparty: it will pay claims, distribute to beneficiaries, and close. A seller indemnity from an entity designed to disappear is worth what’s left when you make the claim. Buyers respond the usual ways — holdbacks and escrows that survive the estate’s closing, distribution agreements with beneficiary joinder so the recipients of the proceeds stand behind post-closing obligations, or R&W insurance in place of a seller indemnity that was never going to be collectible. Sellers’ counsel, for their part, should resist survival periods that outrun the estate’s practical life without a funding mechanism, because a PR has fiduciary reasons not to hold an estate open as an indemnity reserve.

The tax posture is unusually seller-friendly — and the buy-sell should have handled this.

Two tax facts shape estate-side deal economics. First, under IRC § 1014, the basis of the decedent’s equity steps up to fair market value at death. An estate selling shortly after death often recognizes little or no gain on the equity — which changes the negotiation over purchase price allocation, earnout appetite, and installment structures, and can make the estate more indifferent between structures than a living founder with a seven-figure built-in gain would ever be. Second, for S corporations, an estate is a permitted shareholder under IRC § 1361, so death alone doesn’t blow the S election during administration — though where shares pass into trusts, the QSST and ESBT election deadlines become the live issue, a set of traps we walked through in our post on trust shareholders and S-election diligence.

Step back, though, and the larger lesson is that many estate sales are what happens when succession documents failed. A funded buy-sell agreement would have fixed price, buyer, and mechanics the day before death — and the redemption-versus-cross-purchase structure now carries the estate-tax lesson of Connelly v. United States, which we covered in our post on buy-sell agreements and life insurance. Owners who hold equity in a revocable trust avoid this entire probate apparatus, which is one reason buyers increasingly see a trustee rather than a PR across the table. And married Florida owners holding shares as tenants by the entireties add a spousal dimension at death and at closing that we’ve addressed in our post on entireties stock and spousal joinder. If you’re a buyer, none of this planning is your problem — until it’s absent, at which point Chapter 733 is your problem.

The practical checklist is short: read the letters and the will before the LOI; classify each asset as personalty or realty and map the authority for each; put court orders on the critical path where the statute rewards them; assume the seller disappears and secure post-closing recourse accordingly; and let the step-up do quiet work in the price negotiation. Estates sell companies every week in Florida. The buyers who do well are the ones who treat the Probate Code as deal architecture rather than an afterthought.

If you are buying a business from an estate, or serving as a personal representative who needs to sell one, feel free to reach out to our firm manager, Magda, at Magda@montague.law, or fill out our contact form. Mention you read this post.

Picture a founder-owned services company whose three biggest customers are federal agencies. The buyer’s model assumes the government revenue transfers at closing like any other contract. Then, somewhere in diligence, a lawyer says the quiet part: you cannot assign a federal contract. Not with consent language, not with a well-drafted assignment clause, not at all — a statute prohibits it. The room goes quiet, the timeline slips, and the deal team discovers a federal process with its own paperwork, its own timing, and its own leverage dynamics that nobody priced into the letter of intent.

The statute is 41 U.S.C. § 6305, the Anti-Assignment Act, and the process is the novation procedure in . If you buy or sell a business that holds federal contracts — defense, space, IT services, logistics, construction, health — this regulation quietly reorganizes your deal structure, your closing mechanics, and your post-closing risk allocation. Here’s how it actually works, and where deals go sideways.

Asset deals need the government’s blessing; stock deals mostly don’t.

The Anti-Assignment Act flatly prohibits transferring a government contract to a third party. The safety valve is that the government may — the word is permissive — recognize a third party as the successor in interest when the third party’s interest arises from a transfer of all the contractor’s assets, or the entire portion of the assets involved in performing the contract. FAR 42.1204(a) lists the qualifying transactions: an asset sale with assumption of liabilities, an asset transfer incident to a merger or consolidation, the incorporation of a proprietorship. That recognition happens through a trilateral novation agreement among transferor, transferee, and the United States, signed by the responsible contracting officer.

The structural fork comes in FAR 42.1204(b): a novation agreement is unnecessary when ownership changes through a stock purchase, with no legal change in the contracting party, where that party keeps control of the assets and keeps performing. Buy the equity, leave the legal entity intact, and the contract never moves — the same principle that makes reverse triangular mergers attractive under ordinary commercial anti-assignment clauses, which we unpacked in our post on anti-assignment clauses and the Meso Scale line of cases. For a government contractor, this single regulation often decides the threshold question that usually turns on tax and liability factors — the tradeoffs in our asset-versus-stock decision framework. Sellers of federal-heavy businesses have a structural argument for equity deals that has nothing to do with capital gain: the buyer avoids months of novation exposure. A change of ownership still gets reported and may prompt the government to address related issues in a formal agreement, but the contract itself stays put.

The novation package is a diligence exercise the government runs on your deal.

When an asset structure is unavoidable — carve-outs, divisional sales, liability-driven structures — the contractor must submit a package under FAR 42.1204(e) and (f) that reads like a second closing checklist. Three signed copies of the proposed novation agreement. The purchase agreement itself. A list of every affected contract with dollar values and unpaid balances. Evidence of the transferee’s capability to perform. Then, as they become available: the authenticated bill of sale or certificate of merger, certified board resolutions from each party, an opinion of counsel for both transferor and transferee that the transfer was properly effected, balance sheets of both parties immediately before and after the transfer audited by independent accountants, evidence that security clearance requirements have been met, and surety consents where bonds are required.

Read that list again as a deal lawyer and three consequences jump out. First, the government sees your transaction documents. The purchase agreement goes to the contracting officer, so draft with that audience in mind. Second, the audited before-and-after balance sheets are a real cost and a real timeline item that first-time sellers never anticipate — order them early. Third, the package can’t even be finalized until closing has happened, which means the novation is almost always executed after the deal closes. You close into uncertainty. The contracting officer has discretion, takes weeks or months, and under FAR 42.1204(c), if the government declines to concur, the original contractor remains obligated to the government — and the contract can be terminated for default if that original contractor, now an empty shell that sold its operating assets, fails to perform.

The interim period runs on subcontracts, and the seller stays on the hook.

Deals bridge the gap with performance mechanics: the seller remains the contractor of record while the buyer performs behind the scenes, through a subcontract or back-to-back agreement, until the novation is executed. That interim arrangement deserves as much drafting attention as the purchase agreement’s reps — it’s where invoicing, payment flow, compliance responsibility, and audit exposure actually live for months. Pair it with covenants requiring both parties to pursue the novation diligently, to submit the package promptly, and to maintain the seller entity’s existence until execution. A seller who wants to dissolve, distribute, and disappear at closing cannot — winding up the transferor before novation is a self-inflicted default risk. The same interim logic shows up in the operating covenants between signing and closing generally, where buyers police the business they’ve priced but don’t yet own — see our post on material contract covenants and buyer consent rights.

Now the provision sellers underestimate most. The standard-form novation agreement in FAR 42.1204(h) and (i) — reproduced verbatim in the regulation — requires that the transferee assume all obligations, that the transferor waive its claims against the government, and that the transferor guarantee performance of the contract by the transferee. A performance bond may be accepted instead. Sit with that: the founder who just sold the business remains a guarantor of the buyer’s performance to the United States, indefinitely, on contracts the founder no longer controls. Sophisticated sellers negotiate for the bond alternative, or extract a back-to-back indemnity from the buyer covering any liability under the guarantee, sized and secured with the same seriousness as any special indemnity. Sellers who skip this discover their exit has a tail.

Price the process, don’t just paper it.

A few allocation questions belong in the LOI, not the eleventh-hour markup. Whether novation execution is a closing condition (almost never achievable, since the government generally won’t act until after transfer) or a post-closing covenant with an escrow or holdback against non-recognition. Who bears the revenue risk if an agency declines to novate a particular contract — a purchase price adjustment, a clawback, or buyer’s risk. How change-of-control notices, clearance issues for classified work, and organizational conflict-of-interest reviews under FAR subpart 9.5 sequence against the closing date. And for set-aside work, whether the buyer’s size or status jeopardizes contracts priced into the model — small business eligibility does not automatically travel with an acquisition, and that diligence belongs at the term sheet stage. Regulated-transfer choreography isn’t unique to federal work — state-regulated industries have their own versions, like the FMCSA and tax-clearance sequencing in our post on buying or selling a Florida trucking company — but the federal version is distinctive in one respect: the counterparty whose consent you need is also a sovereign with discretion, a form it will not negotiate much, and no closing deadline but yours. In a defense-heavy state like Florida, with its concentration of contractors around the Space Coast, the Panhandle bases, and the ports, this process shows up in lower-middle-market deals far more often than founders expect.

The government contractor M&A market prices these mechanics fluently at the top end. In founder deals, they surface late, get handled in a rushed amendment, and leave someone holding a guarantee they didn’t understand. The regulation is public, the form agreement is printed in it, and the traps are all avoidable with sequencing and candor about who bears which risk.

If you are buying or selling a business that holds federal government contracts, feel free to reach out to our firm manager, Magda, at Magda@montague.law, or fill out our contact form. Mention you read this post.

A common holdback story goes like this: the target carries one existential legal risk — a pending case, a license challenge, a regulatory review — and the buyer won’t pay full price until it resolves. So the parties carve $10 million out of the purchase price, write a definition describing the bad outcome, and agree the money moves one way if the bad thing happens and the other way if it doesn’t. Everyone signs believing the definition means what they privately assume it means. Five years later, a court reads the sentence one comma at a time.

That is essentially what happened in Kentucky Downs Management, Inc. v. Kentucky Downs, LLC, C.A. No. 2021-0251-NAC (Del. Ch. Aug. 13, 2026), Vice Chancellor Cook’s post-trial opinion about a $10 million holdback in the $185 million sale of the Kentucky Downs racetrack and its historical horse racing gaming operation. The court opened by calling the case “a photo finish,” and the description fits — the outcome turned on the words final, non-appealable, and unfavorable, plus one participial phrase. The buyers kept the $10 million. The opinion is a free masterclass in how Delaware courts construe deal language, and it’s worth reading closely if you ever paper a holdback around pending litigation. The full opinion is on the court’s site .

The deal bet $10 million on someone else’s lawsuit.

The target operated historical horse racing terminals — slot-like machines that replay old races — under a Kentucky regulatory framework that was being challenged in a case the industry watched nervously, the Family Foundation litigation. At signing in November 2018, that case was on appeal. If the machines were held not to be lawful pari-mutuel wagering, the crown jewel of the business was arguably illegal. The buyers agreed to pay roughly ten times EBITDA anyway — well above market multiples — and managed the litigation risk through deal structure instead of price.

The first draft of that structure looked familiar: a $20 million escrow, with the buyers’ recovery tied to indemnifiable losses actually flowing from an unfavorable ruling. Classic loss-linked protection — no harm, no forfeiture. Then the buyers’ lenders balked, and the parties signed an amendment that rebuilt the mechanism as a straight $10 million conditional deferred payment. Sellers would be paid if the case ended favorably, or if no “final non-appealable Unfavorable Ruling” existed by the second anniversary of closing. If such a ruling did exist, no payment. The reference to indemnifiable losses disappeared. Almost no one seems to have focused on what that deletion meant until it decided the case.

Every word in the trigger definition ended up load-bearing.

The Kentucky Supreme Court ruled in September 2020 that the terminals were not pari-mutuel wagering. Rehearing was denied in January 2021, and under Kentucky procedure the decision became final at that moment — weeks before the March 2021 deadline in the holdback definition. Then something remarkable happened: the buyers lobbied the Kentucky legislature for five months, a bill legalizing historical horse racing passed in February 2021, and the feared catastrophe never materialized. The machines never shut down. The business never lost a dollar of the projected revenue.

The sellers’ argument was intuitive: the ruling can’t have been “unfavorable” in any meaningful sense, because the buyers ended up unharmed, and it wasn’t “final” until the trial court finished remand proceedings. The court took each word in turn. “Final” carried its established procedural meaning under Kentucky’s own rules — final upon denial of rehearing — in part because Delaware treats established legal terminology in a definition referencing a specific lawsuit as importing its established legal meaning. “Non-appealable” was satisfied because there was no good-faith path to the U.S. Supreme Court on a pure question of state law. And “unfavorable” was defined by the contract itself: a ruling finding one of two enumerated things. The comma and the participial phrase narrowed the universe to two specified findings — an event trigger, not a harm trigger.

Because an earlier ruling in the case had found the language ambiguous, the court also weighed extrinsic evidence, and here the amendment history was devastating for the sellers. Emails showed the lenders demanded the escrow-and-indemnity concept be replaced with a flat obligation. The deletion of the indemnifiable-losses linkage was deliberate. Deposition testimony from both sides confirmed the purpose. Even the buyers’ own panicked post-ruling conduct — shutdown advice, lobbying, litigation exposure analysis — was consistent with reading the ruling as the defined trigger event. The court closed the loop with an observation sellers everywhere should tape to the monitor: hindsight regret about the words you accepted is not a theory of contract interpretation. Delaware enforces the bargain that was papered, not the one either side later prefers.

Event triggers and loss triggers are different products.

The doctrinal spine of the opinion is standard — objective theory of contract, plain meaning, extrinsic evidence only after ambiguity, the drafting-history canon from cases like Eagle Industries v. DeVilbiss and United Rentals v. RAM Holdings, and the instruction from Chicago Bridge & Iron v. Westinghouse to read provisions in a way that gives sensible life to the whole deal. What makes it useful for private-company practice is how cleanly it separates two structures that get casually treated as interchangeable.

First, a loss-linked holdback. The buyer recovers only to the extent an identified risk produces actual, quantifiable losses — an indemnity with a pre-funded source. If the risk resolves harmlessly, the seller gets the money. That was the original $20 million escrow design, and it’s the structure sellers should fight for when they believe the sky won’t actually fall. We’ve written about how these reserves are sized in escrow and holdback market practice and how layered recovery limits interact in indemnification cap architecture.

Second, an event-triggered conditional payment. The money moves on the occurrence or non-occurrence of a defined event, full stop. No loss requirement, no causation fight, no damages proof. It’s cleaner, lenders prefer it, and it pays out in binary fashion even when the real-world outcome diverges wildly from what everyone feared — as it did here, where the buyers kept $10 million despite suffering, in the end, no apparent economic harm from the ruling. That’s not a bug the court missed. It’s the structure the parties chose when they amended.

Third, the hybrid failure mode: parties draft an event trigger while privately assuming loss-linked economics. That mismatch is exactly what surfaced at trial, and it is common in earnout drafting too — a topic with its own version of this trap, covered in our plain-English earnout guide and in the case law on implied covenant fights over contingent consideration.

If the trigger is a lawsuit, draft it like a proceduralist.

A few concrete drafting practices fall straight out of the opinion. Define the litigation endpoint with procedural precision: rehearing denied, mandate issued, judgment entered on remand, certiorari deadline expired — pick the benchmark you actually mean, in the procedural vocabulary of the forum whose rules will supply the meaning. Decide explicitly whether the trigger is the ruling itself or its consequences, and say so — “regardless of any subsequent legislative, regulatory, or commercial development” is an available sentence, and so is “only to the extent of Losses actually incurred.” Watch intra-document variation: the agreement here used “ruling” in one definition and “court judgment” in another on the same page, and the court presumed the difference was intentional. And treat amendments as the most dangerous drafting moments in the deal’s life, because a court will read what was deleted as evidence of what the parties meant to abandon. The negotiation file — the emails, the drafts, the redlines — became the decisive trial exhibits. Yours will too, one way or the other.

There’s also a sobering lesson about leverage timing. The sellers accepted the amendment under closing pressure because the buyers’ financing required it. That’s an ordinary story — lender-driven restructuring at the eleventh hour — but the parties rarely reprice the risk they’re reallocating. A $10 million shift in litigation-outcome risk deserves a $10 million conversation, not a conformed-copy footnote.

If you are negotiating a holdback, escrow, or contingent payment around pending litigation or a regulatory contingency, feel free to reach out to our firm manager, Magda, at Magda@montague.law, or fill out our contact form. Mention you read this post.