🔥🔥🔥 JOIN OUR STARTUP AMBASSADOR PROGRAM 🔥🔥🔥
    📣 Spread the news & get a PRO membership 3 months for FREE with all features🚀📈💵500 vouchers left • 3 months free
    Exit & Liquidation

    The Preference Stack: How Multiple Funding Rounds Create a Seniority Hierarchy

    Each priced round adds a new class of preferred shares to your cap table — and each new class brings its own liquidation preference. The order in which those preferences are paid at exit is the preference stack, and by the time a company reaches Series B the stack often decides whether founders receive anything at all in a mid-sized exit.

    What Is the Preference Stack?

    The preference stack is the ordered list of liquidation preferences that must be paid out before common shareholders receive anything in an exit. Every time a company raises a priced round, a new class of preferred shares is created (Seed Preferred, Series A Preferred, Series B Preferred, and so on) and each class has its own liquidation preference clause.

    By default, in most European venture term sheets, later rounds sit senior to earlier rounds — the most recent investors are paid first, then the previous round, and so on down to the seed investors, and only then do common shareholders share what remains. This is called a "stacked" or "standard" seniority structure.

    The alternative is "pari passu" seniority, where all preferred classes rank equally and share any shortfall pro-rata to their preference amounts. Pari passu is dramatically more founder-friendly in distressed exits because the most recent (largest) preference does not vacuum up the entire pool on its own.

    How Seniority Accumulates Round by Round

    At incorporation, the cap table contains only common stock — no stack. After the seed round, a single layer of Seed Preferred sits above common. After Series A, the stack typically becomes Series A → Seed → Common, with Series A senior. After Series B, the standard order is Series B → Series A → Seed → Common.

    Each new round inherits the precedent set by the previous one. A Seed term sheet that allowed a 1× non-participating preference establishes a market for that company — Series A investors will demand at least the same and usually structure their preference to sit above Seed. This compounding makes early term-sheet decisions disproportionately important.

    The cumulative preference burden grows with every round. By Series C it is not unusual for the preference stack to consume the first €30–80M of an exit, depending on how much capital was raised and at what multiples.

    Worked example — €5M exit with stacked preferences
    Cap table: Seed raised €500K with 1× preference, Series A raised €3M with 1× preference, Series B raised €4M with 1× preference. Total stack: €7.5M. Exit: €5M sale. Stacked (Series B senior): Series B takes the first €4M → €1M remains. Series A takes its €3M preference but only €1M is available → Series A receives €1M. Seed and common receive zero. Pari passu: Total preference €7.5M but pool only €5M, so each preferred class receives 5/7.5 = 66.7% of their preference. Series B: €2.67M. Series A: €2M. Seed: €333K. Common still receives zero — but at least Seed investors get something.

    The Series B Overhang Problem

    When a startup raises a large Series B at a step-up valuation, the cap table accumulates a large preference that sits at the top of the stack. If subsequent growth disappoints and the company is eventually sold at less than the cumulative preference, the entire exit is consumed by Series B alone — and earlier rounds, founders, and employees all receive nothing.

    This is the "Series B overhang" problem and it is one of the most common destroyers of founder economics in European outcomes. It typically becomes acute when the company raises Series B at a frothy valuation, then the market turns and an exit happens at 30–60% of the Series B post-money.

    Founders can defend against the overhang at the term-sheet stage by negotiating: pari passu seniority instead of stacked; a sunset on multi-x preferences after a milestone (revenue, IPO, time); or a "tip" provision that guarantees common a minimum percentage of any exit regardless of preference math.

    Negotiating Pari Passu Treatment

    Pari passu is the strongest single defence founders have against preference-stack damage. The argument: pari passu preserves seed and Series A investor economics, which keeps early backers aligned and willing to support future rounds — including following on, exercising pro-rata rights, and signalling commitment to new investors.

    In practice, pari passu is hardest to negotiate when raising from a single new lead investor at growth stage. Multi-investor rounds and rounds where existing investors are participating heavily are more amenable. The compromise often lands as "pari passu within a class, stacked across classes" — meaning all Series B investors share equally, but Series B as a class sits above Series A as a class.

    Founders should also negotiate the seniority language explicitly in the term sheet. Vague language like "subject to definitive documentation" almost always resolves in the new investor's favour in the long-form documents. See the [liquidation preference guide](/captable/liquidation-preference) for how the underlying multiple and participation terms interact with the stack.

    Interaction with Participating Preferred

    When the preference stack contains participating preferred shares, the damage compounds dramatically. Each participating class takes its preference off the top AND shares pro-rata in the residual pool — and that pool feeds the next class down only after the most senior participating class has taken its share.

    Worked walk-through: Series B has 1× participating preferred for €4M and 40% of the fully-diluted equity. At a €10M exit, Series B takes €4M as preference, then participates in 40% of the remaining €6M = €2.4M, for €6.4M total. Only €3.6M cascades down to Series A. Series A has 1× participating preferred for €3M and 30% of equity — Series A takes its €3M preference, leaving €600K for everyone else. Seed, common and employees split €600K.

    The combination of stacked seniority and participating preferred can wipe out 90%+ of founder economics in mid-sized exits. The single most valuable founder-side negotiation point is converting participating preferred to non-participating, or at minimum capping participation. See the [participating preferred guide](/captable/participating-preferred) and the [exit waterfall guide](/captable/exit-waterfall) for the full math.

    How CAPLINK Models Your Preference Stack

    CAPLINK's cap table module captures each class's liquidation preference, seniority position, participation flag, and cap. The exit waterfall simulator runs scenarios at any exit price and shows exactly how the stack distributes proceeds across classes — including the conversion-vs-preference choice for non-participating holders.

    The simulator surfaces breakeven thresholds (the minimum exit at which common starts receiving proceeds) and stress-tests the stack at the valuations that matter: 1×, 2×, and 3× total capital invested. Founders use this in board meetings and in fundraising conversations to demonstrate the long-term consequences of term-sheet decisions before they sign.

    Existing investors also benefit. A clear, modelled preference stack reduces friction in future rounds because incoming investors can see exactly what they are stepping into. See [recapitalization](/captable/recapitalization) for how the stack can be restructured when it becomes a blocker, and [series-b-growth-rounds](/captable/series-b-growth-rounds) for stack negotiation strategies at the round where the problem most often appears.

    Frequently Asked Questions

    Related Topics

    Keep going — these guides cover the closest topics to what you just read.

    Back to Cap Table Hub

    Manage your cap table the right way from day one

    CAPLINK keeps every grant, conversion and round investor-ready — so the next term-sheet conversation starts from facts, not from a scramble.

    We use cookies to enhance your experience. Read our Privacy Policy