lev-os Analyzing Seed And Anchor Investor Terms
When To Use
- Evaluating a proposed seed or anchor investor side letter or separate class terms before fund closing
- Comparing competing anchor commitments to determine which arrangement best serves the GP's long-term economics
- Reviewing existing seed/anchor deals during a successor fund raise to assess legacy obligations
- Advising an investor on whether seed/anchor economics adequately compensate for early commitment risk and illiquidity
Inputs To Gather
- Fund term sheet or LPA draft — target fund size, management fee schedule, carried interest waterfall, GP commitment percentage
- Seed/anchor side letter or term sheet — all proposed economic and governance concessions
- Capital commitment details — anchor commitment amount, percentage of target fund size, timing of commitment relative to fund launch
- Revenue share specifics — percentage of management fee or GP revenue shared, duration (fund life vs. fixed term), whether it applies to successor funds
- Fee discount terms — reduced management fee rate, fee holiday periods, step-down schedules, whether discounts apply during commitment and/or investment period only
- Capacity reservation rights — reserved allocation in successor funds, co-investment rights, first-look or priority allocation provisions
- Governance rights — LPAC seat, key-person event triggers, consent rights over fund terms, removal or no-fault termination provisions
- Exclusivity and restriction terms — most-favored-nation (MFN) clauses, restrictions on offering similar terms to others, anti-dilution on economics
Workflow
Map the full economic package. Quantify every concession: model the management fee discount as a dollar amount over fund life, calculate revenue share payments under base-case and upside AUM scenarios, and value capacity reservations using expected successor fund sizes. Express each element as a percentage of total GP economics to enable comparison.
Stress-test revenue share economics. Model revenue share under multiple scenarios — target raise, first close only, and oversubscribed fund. Determine whether the share is calculated on gross management fees or net (after fund expenses). Identify whether the revenue share survives GP entity restructuring or key-person departures. [VERIFY] whether revenue share constitutes a profits interest or a contractual payment for tax treatment purposes in the applicable jurisdiction.
Evaluate fee discount structure. Compare the discounted rate against the fund's standard fee schedule across the full fund life cycle (investment period, harvest period, extensions). Calculate breakeven — at what AUM level do aggregate fee discounts erode the GP's ability to operate the fund. Flag any fee discounts that compound with other MFN-triggered reductions.
Assess capacity reservation and co-investment rights. Determine whether capacity reservations in successor funds are binding commitments or best-efforts. Evaluate whether co-investment rights are deal-by-deal or programmatic, and whether they carry fee/carry or are offered on a no-fee/no-carry basis. Identify conflicts with future fundraising — a large capacity reservation can deter new LPs who see limited allocation availability.
Analyze governance concessions. Catalog all governance rights granted: LPAC membership, consent rights over key decisions (fund extensions, fee changes, GP removal), information rights beyond standard LP reporting. Assess whether governance rights give the anchor effective veto power over fund operations. [VERIFY] whether advisory committee participation triggers fiduciary or regulatory issues for the anchor investor.
Benchmark against market terms. Compare the overall package to prevailing seed/anchor structures for comparable fund strategies (e.g., first-time fund vs. spin-out vs. established manager launching a new strategy). Flag any terms that are materially off-market in either direction — overly generous terms may signal GP desperation; below-market terms may fail to attract the anchor.
Assess successor fund implications. Determine which terms carry over to subsequent funds (revenue share tails, capacity reservations, MFN protections). Model the cumulative drag on GP economics across a multi-fund franchise. Identify sunset provisions or renegotiation triggers.
Identify structural risks and misalignments. Flag terms that create conflicts: revenue shares that incentivize AUM growth over performance, governance rights that slow decision-making, capacity reservations that limit the GP's flexibility to manage fund size. Note any terms that could trigger regulatory disclosure requirements. [VERIFY] whether seed investor economics require disclosure in the fund's Form ADV or offering documents.
Output
Produce an Analysis Report containing:
- Executive summary — overall assessment of whether the seed/anchor package is market-appropriate, with a clear recommendation (accept, reject, or counter-propose with specific modifications)
- Economic impact table — side-by-side comparison of GP economics with and without the anchor arrangement across base, downside, and upside scenarios
- Term-by-term analysis — each concession evaluated for reasonableness, with market comparables cited
- Successor fund modeling — projected impact of carry-forward terms on Fund II and Fund III economics
- Risk register — governance, regulatory, and structural risks ranked by likelihood and severity
- Negotiation priorities — ranked list of terms to push back on, with suggested alternative formulations
Quality Checks
- Confirm all fee calculations use the correct base (committed capital vs. invested capital vs. NAV) and time periods
- Verify revenue share mechanics match the actual LPA language, not just the term sheet summary
- Ensure scenario models use realistic assumptions for deployment pace, fund size, and performance
- Cross-check that MFN provisions do not inadvertently extend anchor economics to other LPs
- Validate that governance rights analysis accounts for the interaction between side letter terms and LPA default provisions
- Confirm tax treatment assumptions are flagged with [VERIFY] where jurisdiction-dependent