What is a liquidation preference stack? A practical definition
Glossary · founder · 5 min read · last verified 2026-07-21
A liquidation preference stack is the combined set of claims that each round of preferred stock has on exit proceeds, typically paid out in reverse order of investment — most recent round first — before common stockholders, including founders and employees, receive anything. At a modest exit, the stack can consume the entire proceeds before common gets paid at all; at a large exit, a "participating" stack can still take a meaningful bite out of what founders would otherwise expect.
General information about common market structure for liquidation preferences, not legal or financial advice — actual terms are set by each round's specific stock purchase agreement and certificate of incorporation, and should be reviewed with counsel.
What a liquidation preference is, in one round
The standard structure is a "1x non-participating" preference: at exit, that class of preferred stock gets the greater of (a) its stated preference amount (commonly the original investment, i.e., 1x) or (b) what it would receive if converted to common stock and paid its pro-rata share. It chooses one or the other, not both.
A "participating" preference is different: that class gets its preference amount and a pro-rata share of whatever proceeds remain afterward, calculated as if it had also converted — commonly called a "double dip." Participating preferences are sometimes capped at a multiple of the original investment (for example, 2x or 3x total return), after which the holder would rather convert to straight common.
How the stack forms across multiple rounds
Each financing round negotiates its own preference terms independently. When a company has raised several rounds, those preferences typically stack in reverse-chronological seniority — the most recently raised round is paid first, then the round before it, and so on — unless the rounds are explicitly negotiated as "pari passu," meaning they're paid pro-rata together rather than in strict seniority order. Seniority stacking is the more common default absent specific negotiation otherwise.
Worked example 1: a low exit wipes out common, even in a "real" sale
Suppose a company raised three rounds, each with a standard 1x non-participating preference, paid in reverse-chronological seniority:
| Round | Raised (1x preference) |
|---|---|
| Seed | $1,000,000 |
| Series A | $4,000,000 |
| Series B | $10,000,000 |
| Total preference stack | $15,000,000 |
The company sells for $12,000,000 — below the total preference stack, but still a real, non-zero exit.
Paying preferences in seniority order (Series B first, since it's the most recent):
- Series B claims its $10,000,000 preference first: paid in full. Remaining: $12,000,000 − $10,000,000 = $2,000,000.
- Series A claims its $4,000,000 preference next, but only $2,000,000 remains: Series A gets $2,000,000 (partial). Remaining: $0.
- Seed claims its $1,000,000 preference: nothing remains. Seed gets $0.
- Common (founders and employees): $0.
Check: $10,000,000 + $2,000,000 + $0 + $0 = $12,000,000 ✓. A $12,000,000 sale — which can sound like a genuine outcome, not a failure — leaves seed investors and everyone holding common stock with nothing, purely because of seniority order in the preference stack.
Worked example 2: a high exit still costs common under a participating stack
Now suppose the same company sells for $100,000,000 — well above the $15,000,000 preference stack — and assume a fully diluted cap table split of common 50%, seed 10%, Series A 15%, Series B 25% (which sums to 100%).
If preferred is non-participating, every class converts to common because converting is worth more than taking the small preference:
- Common: 50% × $100,000,000 = $50,000,000
- Seed: 10% × $100,000,000 = $10,000,000
- Series A: 15% × $100,000,000 = $15,000,000
- Series B: 25% × $100,000,000 = $25,000,000
- Check: $50M + $10M + $15M + $25M = $100,000,000 ✓
If preferred is participating (uncapped), each class takes its preference off the top, then shares pro-rata in what's left:
- Pay preferences first: $10,000,000 (B) + $4,000,000 (A) + $1,000,000 (Seed) = $15,000,000. Remaining: $100,000,000 − $15,000,000 = $85,000,000.
- Split the $85,000,000 remainder by fully diluted ownership percentage: common gets 50% × $85M = $42,500,000; seed gets 10% × $85M = $8,500,000; Series A gets 15% × $85M = $12,750,000; Series B gets 25% × $85M = $21,250,000.
- Add each class's preference back on top: seed total = $8,500,000 + $1,000,000 = $9,500,000; Series A total = $12,750,000 + $4,000,000 = $16,750,000; Series B total = $21,250,000 + $10,000,000 = $31,250,000; common total (no preference) = $42,500,000.
- Check: $42,500,000 + $9,500,000 + $16,750,000 + $31,250,000 = $100,000,000 ✓
Common's cost of participation: $50,000,000 (non-participating) − $42,500,000 (participating) = $7,500,000, a 15% haircut — purely from the participation feature, at an exit nearly seven times the size of the entire preference stack. That cost follows a clean pattern: common's ownership percentage × the total preference stack (50% × $15,000,000 = $7,500,000), which is the entire amount common gives up under participation regardless of exit size, as long as the exit is large enough that everyone would otherwise convert.
Note that the effect isn't distributed evenly among the preferred classes either — Series B's $10,000,000 preference is large relative to its 25% ownership, so it captures more from participation than Seed does relative to Seed's own conversion value. Only common is guaranteed to be worse off under participation; individual preferred classes can gain more or less depending on how their preference size compares to their ownership share.
Seniority vs. pari passu
Whether a stack pays in strict reverse-chronological order (seniority) or all preferred classes share proceeds pro-rata together (pari passu) is negotiated, not automatic. Seniority stacking is the more common default when nothing else is specified, and it's what drives the low-exit outcome in the first worked example above — the most recent, usually largest, round is protected first.
Why this matters for every new round founders negotiate
Each new round's preference terms don't just affect that round's own investors — as the hypothetical examples above show, they change how the entire stack behaves at every future exit scenario, including ones far above the total amount raised. Before agreeing to participating terms, an unusual seniority structure, or a large new round on top of an existing stack, it's worth modeling outcomes across a range of exit values — not just an optimistic one — the same way the two worked examples above do. This connects directly to how stacked SAFEs convert into that stack and how the option pool created alongside a round affects the same cap table.
A $12,000,000 sale and a $100,000,000 sale can both leave founders with far less than the headline exit number suggests — for opposite reasons, and both visible well before either exit happens if the stack is modeled honestly.