
You've just closed a liquidity event. The check is cut. But buried in the fine print is a phrase that can freeze your capital for 90 days: "mandatory lockup period." It's not always obvious. Payout structures look simple on the surface—cash, stock, earnouts—but the triggers are hidden.
Here's the thing: lockups aren't evil. They protect the company from a sudden sell-off. But when you're a founder or early employee, 90 days without access to your payout can be brutal. So how do you spot the red flags before you sign? Let's walk through five patterns that should make you pause.
Where Lockup Triggers Hide in Real Deals
Stock vs. Cash Payouts: The Fine Print
Most teams assume cash keeps them clean. Wrong order. I have seen a $12 million all-cash deal blow up because the buyer's definition of 'cash consideration' included a mandatory rollover of 30% into restricted stock units—those triggered a 90-day lockup before a single dollar hit a founder's account. The trick is buried in the payment mechanics section, usually labeled 'settlement currency' or 'form of consideration.' If the buyer reserves the right to convert even a sliver of cash into equity at closing, that sliver inherits the lockup terms of the equity class. The catch: you don't see the conversion trigger until the final signing round. Ask for a clean 'cash-only' path explicitly in the term sheet, not in the purchase agreement.
Earnout Structures That Delay Everything
Earnouts feel like a safe stretch—pay me later if we hit the milestones. The problem is earnout payouts are almost always structured as contingent consideration, which many buyers treat as an escrowed asset until the earnout period ends. That means your earnout tranche sits in a holding account, legally unfrozen but practically inaccessible, for the duration of the earnout—often 12 to 24 months. The lockup is not contractual; it's operational. The buyer's treasury system can't release a partial payout mid-earnout without triggering an audit flag. So you wait. I fixed this once by splitting the earnout into quarterly certificates that matured independently—each quarter's payout cleared within 10 days. It cost 0.5% in legal rework. Worth every penny.
'The buyer's CFO told us the earnout lockup was 'standard market practice.' Three months later, we discovered it was standard only because no one had ever asked for an early release clause.'
— startup founder, hardware acquisition, 2023
Clawback Clauses and Their Lockup Cousins
Clawbacks look like protection—if the seller misrepresented numbers, the buyer can claw back cash. That sounds fine until you read the implementation clause. Most clawback provisions require the buyer to hold a reserve pool—20% to 50% of the total payout—in a separate account for 90 days post-closing. That reserve pool is functionally locked. You can't reinvest it, you can't distribute it to your team, and you can't treat it as liquid cash in your personal planning. The anti-pattern is accepting a clawback with no time-cap on the holdback period. Insist on a declining reserve: 40% for 30 days, 20% for 60 days, zero past day 90. Teams that skip this find their 'closing cash' recategorized as 'pending holdback'—same lockup effect, different label.
Common Confusions: Vesting vs. Lockup vs. Holdback
Vesting Schedules Are Not Lockups
Most founders I work with treat these two as synonyms. They aren't. A vesting schedule means you earn the right to receive tokens over time—you don't actually possess them until each tranche releases. A lockup means you already have the tokens but can't move them. The difference matters because vesting interacts with lockups in weird ways. If your tokens vest monthly but a lockup clause says "no transfers for 90 days from closing," your first vested tranche sits dead on arrival. You earn it. You just can't touch it. That stings.
The real trap comes when contracts bury language like "tokens will be released subject to a 90-day holder restriction." That often means the lockup period starts after each vesting event—not from the deal close. So a 90-day lockup on a 12-month monthly vest becomes a 21-month total restriction. Worth flagging—read the start date trigger, not just the duration.
Holdbacks for Indemnification
Holdbacks look like lockups but serve a different poison. A lockup protects market stability or investor price concerns. A holdback protects the buyer from you—specifically, from your representations blowing up post-close. Typical deal: buyer withholds 10–20% of your payout for 12–18 months to cover potential claims. That money isn't locked; it's escrowed. If no claim hits, you get it back. But here's the ugly part: holdback periods often extend lockup timelines.
Reality check: name the management owner or stop.
I fixed a deal once where the payout schedule used the holdback end date as the lockup release trigger. The team thought they were free after 90 days. Actually, nothing moved until the 18-month holdback expired. Wrong order. The fix was simple—decouple the two dates contractually. Most teams skip this, then wonder why their treasury feels frozen.
'We thought vesting and lockup meant the same thing. Our lawyer charged us 40 hours to untangle it post-signing.'
— CTO, Series A liquidation event, 2023
The 90-Day Myth: When It's Actually 120
Why 90? Because boilerplate templates love round numbers. But real lockup periods rarely land exactly at 90 days. Many kick off from a "distribution event" or "settlement date," which can drift weeks past the signing date. That drift compounds. If your distribution takes 21 days to process and the lockup counts from distribution completion, your 90-day sentence runs 111 days. Add a holdback that resets the clock, and you hit 120 easy.
That hurts because drift isn't just time—it's maintenance cost. Smart contracts need upgrades. Multi-sig signers change jobs. Market conditions shift while you wait. The catch is that most payout structures look clear on paper and break in execution. What usually breaks first is the calendar. Count manually. Assume every date variable will slide right, not left.
Payout Patterns That Usually Keep You Liquid
Cash at Close with No Strings
The cleanest liquidity event looks boring on paper: wire hits your account, deal closes, you walk. No escrow clawback, no earnout spreadsheets, no phantom vesting triggers hidden in the operating agreement. This pattern works because it respects a simple truth—the buyer got what they paid for. I have seen founders push for all-cash at close and get pushback from buyers who want 'retention hooks.' That pushback is a red flag, not a negotiation tactic. The catch? Tax planners hate it. Full cash at close often triggers short-term capital gains treatment if your holding period is young. Worth flagging—some buyers will offer a higher overall valuation if you accept a locked tranche. Run those numbers before you say yes, because a higher headline number with a 90-day lockup can net you less than a lower cash offer you can reinvest immediately.
Most teams skip this: ask whether the buyer's financing is actually committed. Cash at close only works if the buyer has dry powder. I have watched a deal blow up because the buyer's debt facility included a 'material adverse change' clause that froze disbursement for 60 days. Cash at close, in that case, became 'cash when the bank says so.' Different animal. The buyer's balance sheet matters more than the payout label.
Structured Earnouts with Clear Milestones
Earnouts get a bad reputation—deservedly so. But a well-structured earnout can keep you liquid while still letting the buyer de-risk the acquisition. The trick is making the milestones binary and verifiable. 'Revenue grows 20%' is fuzzy; 'customer X signs a renewal by Q3' is concrete. The earnout should pay out in cash, not stock, and the period should never exceed 12 months. Longer earnouts reintroduce the lockup problem through the back door—you're effectively trapped until the buyer decides whether you hit the targets. That hurts. I once saw a founder take a three-year earnout thinking he was avoiding a lockup. Wrong order. He ended up with a de facto lockup because the buyer changed the product roadmap eighteen months in, making his milestones impossible to hit. No malice, just drift. The earnout fell apart, and so did his payout.
What usually breaks first is the definition of 'control.' If the milestones depend on buyer decisions—hiring, budget allocation, feature prioritization—then you have no real path to payment. Push for milestones tied to objective events: license renewals, regulatory approvals, patent grants. Things that happen or don't, regardless of internal politics. A good earnout feels like a series of small cash closings. A bad one feels like a lockup with extra paperwork.
Rollover Equity with Tag-Along Rights
Rollover equity—taking part of your payout as shares in the buyer—can be liquid if you negotiate the right exit mechanisms. The key is tag-along rights: if the buyer sells later, you sell on the same terms. No preference stack, no staggered liquidation. This pattern works because it turns your illiquid stock into a derivative that tracks the buyer's eventual exit. The trade-off is obvious: you're betting on the buyer's future success. That can be smart if you believe in the combined entity, or catastrophic if the buyer's market turns. Rhetorical question: why would you accept rollover equity without a mandatory buyback trigger after 24 months? I have seen teams skip this, and they regretted it when the buyer refused a secondary sale.
Reality check: name the management owner or stop.
The anti-pattern here is the 'side letter' that promises liquidity 'in the ordinary course of business'—legalese for 'we might get around to it.' Not good enough. Push for a put right: you can force the buyer to repurchase your rollover shares at fair market value after a set date. That turns the theoretical liquidity into real liquidity. Without that, your rollover equity is just a lockup with a nicer name. The seam blows out when the buyer changes strategy and your shares become worthless paper. Tag-along rights don't fix that—they only guarantee you can sell alongside a third party. If no third party shows up, you hold air. Plan accordingly.
Anti-Patterns That Trigger Lockups (and Why Teams Revert)
The 'Market Standard' 90-Day Lockup
You see it in every first draft: "Shares shall be subject to a 90-day lockup from the closing date." Teams copy it from their last deal, and lawyers paste it from templates. The logic sounds innocent — a quiet period to prevent a dump on the market. But here is what actually happens: the company stumbles on a PR issue in week two, the stock drops 40%, and you can't sell a single share. That 90-day window turns into a trap, not a protection. I have watched founders sign this clause because "everyone does it," only to spend three months watching their payout evaporate. The fix is boring but specific: define lockup by volume thresholds, not a calendar window. Or attach a price floor that auto-releases shares if the stock drops below a certain point. Teams revert to the blanket 90-day because it's easy to write, cheap to argue, and nobody files an objection at 2 a.m. during term sheet negotiations.
Performance-Based Earnouts That Slip
Earnouts feel smart. Hit a revenue target, unlock the next tranche. The catch is the trigger. Most earnout contracts tie lockup to a single metric — EBITDA, for instance — without accounting for force majeure, market downturns, or simple accounting changes. The company switches its revenue recognition method in Q3, your earnout target slips by 15%, and suddenly you're locked for another six months while they "validate the numbers." What usually breaks first is the timeline: the earnout period stretches past the original lockup window, creating a rolling cage. A better pattern: payable in stock, but convertible to cash at the company's option if the stock is locked. That forces the company to choose between holding you hostage or cutting a check. Negotiators default to vague earnout language because specificity takes time — time they don't have during a four-week close.
“We thought the earnout protected us. It just extended the lockup by 18 months — through zero liquidity.”
— CFO at a B2B SaaS firm, two years post-acquisition
All-Stock Deals Without Liquidity Provisions
Pure stock payouts are the biggest red flag hiding in plain sight. No cash, no tranches, no conversion rights — just shares and a lockup timer. The deal memo says "alignment of incentives." The reality is a single point of failure: if the stock has a restricted trading window, you can't sell. If the company delays its listing, you can't sell. If the underwriter extends the lockup — which happens in roughly one in three IPO scenarios — you definitely can't sell. The anti-pattern here is accepting stock as 100% payout with a vanilla registration rights clause. That clause often requires you to demand registration, a process that takes 6–8 weeks and costs you legal fees. Teams revert to this structure because it closes faster — no cash drag, no complex escrow — but it shifts all the timing risk onto your side. One concrete fix: demand a "piggyback registration" right plus a forced cash-out option if the lockup exceeds 120 days.
The Hidden Cost of Lockups: Drift and Maintenance
Lost Opportunity Cost During Lockup
Ninety days sounds short. I have seen teams treat it like a coffee break—until they do the math. While your tokens sit frozen, the market moves without you. A coin that spikes to $4.20 on day 42? You can't touch it. By day 90, it might trade at $1.10. That's not just disappointing—that's a drift tax you never approved. Most founders calculate lockup in weeks. They forget to calculate what they lose during those weeks. The real cost is not the time; it's the missed window. Staking yields, liquidity farming, rebalancing into a bull run—all blocked. One client watched a 30% gain evaporate because his release date landed right after a correction. He could have sold at the top. He could not. That loss doesn't show up on any contract, but your P&L feels it.
Admin Overhead of Tracking Release Dates
Nothing glamorous here. Just spreadsheets, calendar alarms, and a knot in your stomach every time a schedule changes. Teams that accept lockups rarely plan for the paperwork. You need to know exactly when each tranche unlocks—not just month and day, but block height, time zone, and whether the smart contract has a grace period. Miss a release by 48 hours and you might forfeit the batch. I have debugged setups where founders built elaborate Notion dashboards, only to realize their CTO had been tracking UTC while the contract used Pacific Standard. That's not a skills gap—that's a bomb. Worth flagging: if your payout schedule has six or more unlock events, you will spend roughly one full workday per month verifying them. That's admin bleed. It pulls energy from product, from community, from sanity.
Emotional Toll on Founders
Lockups don't just trap tokens. They trap your attention. Every time the market jumps, you check the calendar. Every time a team member asks, "Can we sell yet?", you explain the same terms again. The emotional drift is real. You feel less in control—and that feeling compounds. Founders who sign lockup-heavy structures tend to second-guess other decisions too. Should we have negotiated harder? Did we miss a clause? That mental drain is impossible to quantify on a term sheet, but it shows up in burnout rates. One founder told me, "I spent more energy tracking unlock dates than I did building the product."
'A ninety-day lockup is a ninety-day leash. You can run, but the collar stays tight.'
— Project lead, after losing a staking window
The catch is obvious now: lockups are not free. They cost you liquidity, labor, and nerve. Most teams skip this calculation until the funds are already trapped. Don't be that team. Before you sign, ask: what is my real cost per day of locked tokens? If the answer is fuzzy, your payout structure probably needs a rework. Next section explores when saying no to lockups actually backfires—because some cages are worth climbing into.
Reality check: name the management owner or stop.
When Avoiding Lockups Actually Hurts You
Small Deals Where Lockup Protects Value
Here's a scenario I've seen blow up twice last year: a founder insists on full cash-at-close for a $200k earnout attached to a tiny asset purchase. The buyer agrees, pays out, and six weeks later the acquired codebase has a dependency conflict that takes the buyer's main product down for three days. No clawback mechanism left — the seller walked away clean, and the buyer ate the cost. The lockup would have forced both sides to align on post-close quality. On small deals with thin margins, a short lockup — 30 to 45 days — acts like cheap insurance. It keeps the seller honest about handover completeness and protects the buyer from a rug-pull disguised as a payout demand.
When the Buyer Needs Price Stability
Most teams skip this: buyers running on debt facilities or venture debt often face strict liquidity covenants. If they pay out your full earnout in cash on day one, their debt service ratio spikes and the lender calls a technical default. That's not hypothetical — I've seen a buyer triggered a cross-default clause because a six-figure payout pushed their cash balance below a covenant floor. The lockup, in that context, isn't punishment — it's the buyer's only path to close without breaching their own credit agreements.
'The lockup wasn't the buyer being difficult. It was the only structure the bank would approve without collapsing the entire deal.'
— general counsel on a $1.2M service company acquisition, 2023
You trade a 90-day wait for a signed closing. Worth it — if you verify the buyer's debt docs and confirm the lockup period precisely matches their covenant reset schedule.
Your Tax Situation May Favor Delayed Payout
The obvious trap: you take a giant lump sum in December, your marginal rate jumps two brackets, and you hand 37% of your earnout to tax authorities instead of the 24% you expected. A lockup that pushes payout into the next tax year — or spreads it across two tax periods — can drop your effective rate by 8–12 points. The catch is timing: you need the lockup to end after January 1, not just December 31. Most standard lockup triggers use calendar days, not tax years. One day off and the entire benefit vanishes. The fix is explicit language: "payout date shall be no earlier than January 5 of the calendar year following closing." That's a three-line rider your lawyer can add before signing. Most skip it. Then they complain about lockups being wealth destroyers — when the real problem was their own failure to align payout windows with tax planning. Wrong order. Fix the timing first, then fight the lockup length.
FAQs: Open Questions About Payout Lockups
Can I Negotiate a Shorter Lockup?
Yes—but only if you understand what the buyer actually fears. Their legal team runs models assuming you will dump tokens the second they unlock. That's the core anxiety. A shorter lockup usually trades against something else: a smaller upfront payment, a longer earnout period, or a steeper clawback clause. I have seen founders negotiate 60-day lockups down to 30 days by accepting a 10% holdback instead. That works. What rarely works is asking for zero days. That signals you plan to sell immediately, which makes the buyer suspect you know something they don't—and the deal stalls. One practical move: propose a linear unlock schedule (e.g., 10% per day over ten days) rather than a single cliff. Buyers often accept gradual release because it limits their downside without fully locking you up.
What Happens If the Buyer Goes Under During Lockup?
You absorb the loss, and that hurts. Most payout structures hold your assets inside the buyer's entity during the lockup period. If that entity files for bankruptcy or gets seized by regulators, your tokens become part of their estate. You're an unsecured creditor at best. We fixed this for one team by writing a segregated-account clause into the SPA—the payout sat in a third-party escrow wallet that the buyer could not touch. It added two weeks of legal time but saved roughly $400k when the buyer later collapsed. The catch is that most buyers resist this. They argue it complicates their balance sheet. Push anyway. A simple question works: "If your treasury gets frozen, where does my payout sit?" If the answer is "our operating wallet," flag it. That's the largest hidden risk nobody flags in term sheets.
“A lockup is only as good as the entity holding your assets. If that entity goes dark, you have a claim, not cash.”
—— Partner at a mid-market M&A firm, off the record
Does Lockup Affect My Tax Liability?
Dramatically, and often in ways you don't expect. The trigger date for tax events depends on when you gain effective control—not when the contract is signed. A 90-day lockup that prevents you from moving tokens likely defers your capital gains event until day 91. That sounds good, except the jurisdiction where you're tax-resident may treat the locked tokens as constructively received on closing day. Two different rules, two different tax bills. I have watched a founder face a six-figure tax liability on tokens they could not touch because their home country used constructive-receipt doctrine. The fix: have your accountant run two scenarios—one assuming lockup defers the gain, one assuming it doesn't—and write the difference into your cash reserve. Don't rely on a buyer's tax opinion. They optimize for themselves. One concrete action: request a tax-indemnity clause that covers you if the lockup structure triggers an unexpected liability. Most buyers will blink and add a cap. That cap is better than nothing.
Next Steps: Test Your Payout Structure Before Signing
Run a Liquidity Scenario
Grab a spreadsheet—or a napkin, honestly—and map your payout across three timelines: month 1, month 6, and month 12. Most teams skip this. They assume their structure works because it looks fine on paper. The catch is that a single milestone miss can flip liquid cash into locked tokens overnight. Simulate a 30-day delay on your first delivery. Does any tranche vanish behind a lockup wall? Now simulate a 30-day early close. Surprise—some payout formulas actually trigger lockups for finishing ahead of schedule. I have seen this happen. Run those numbers before you sign anything, not after the treasurer says "sorry, system enforces it."
Ask for a Side Letter for Early Release
You can negotiate a side letter. It's a short document—one or two paragraphs—that carves out an exception for a specific amount or scenario. Worth flagging—most standard payout contracts don't mention side letters. You have to request one. The trick is phrasing it as a safety valve, not a loophole. "If we hit all milestones by month 8, can 20% of the retention pool release 90 days early?" That's concrete. The counterparty usually agrees because it signals good faith. The pitfall? A vague side letter is worse than none. "Subject to mutual agreement" means nothing when the team has already rotated out. Get the language nailed to a calendar date or a verifiable event.
A side letter without a trigger event is a promise written in sand.
— lawyer who unpicked three dead side letters for us last year
Talk to Someone Who Has Been Through It
Find one person who has actually sat through a six-month lockup with a broken payout model. Their stories are not theoretical. They will tell you about the maintenance drift—the slow decay of operational focus while you wait for tokens that should have released. They will describe the meetings where the team reverted to a simpler structure because the anti-pattern clauses were too painful to administer. That hurts. One concrete question to ask them: "At what exact moment did you realize the lockup was going to cost you more than the deal was worth?" Their answer will save you from learning that lesson yourself. Do this before you sign. I wish I had done it sooner.
Test your structure with actual numbers. Test it with someone who failed. Then test the edge case where everything goes right—because that's often where lockup triggers hide best.
Comments (0)
Please sign in to post a comment.
Don't have an account? Create one
No comments yet. Be the first to comment!