Explore the build library
consultance.ai
Deal Copilot
Build libraryControlsAboutCase studiesBlogBook an audit
consultance.ai

Systems

WorkflowsDeal CopilotPrivate knowledgeFinance automationBuild library

Company

About usCase studiesBlogContact

Start a conversation

Free AI auditfounder@consultance.ai

Teams

Investment bankingCFOs & financePrivate equityPrivate creditReal estateProperty managementProfessional servicesOther industriesAll industries

Legal

Privacy policyTerms of service

Our approach

Audit the workflow.Build in your environment.Hand over a system you own.
Build something useful © 2026 consultance.ai
Build library/Cap Table Rebuild and Waterfall Desk

Finance and data

Cap Table Rebuild and Waterfall Desk

For founders, CFOs and deal teams whose cap table lives in a spreadsheet: 9 Claude prompts that rebuild it from the signed documents, name every share without paper, and run the exit waterfall clause by clause against the charter.

Medium setup4 steps9 prompts
Open the setup guide Discuss an implementation
Finance and data

Start with the guided setup

Follow the setup below in your own workspace. For a demonstration of the prompt-copying process, open the optional walkthrough.

Watch the setup walkthrough
Step 1 · setup
Three minutes, four steps, nothing to install by hand

Claude sets it up for you. You just paste.

Never used Claude? It is free and takes 30 seconds to open. Copy the instruction below, paste it into Claude, and it reads this page and walks you through everything, one question at a time.

  1. Tell Claude how to talk to you

    One tap. It changes how much Claude explains, and how slowly it goes. You can change it any time.

  2. Copy your setup instruction

    A short instruction plus a link to this page lands on your clipboard. First copy asks for your email once. That unlocks every button across the whole library.

  3. Open Claude in a new tab

    Free account, no card, 30 seconds. This tab stays open so you can come back.

    Open claude.ai
  4. Paste, send, and answer one question

    Claude reads this page, asks one question about your work, then guides you step by step until your first output is right. If anything looks wrong, tell Claude what you see, and it fixes it with you.

▸Prefer the full prompt instead of the link? (optional)
Click to copy
I am comfortable copy-pasting and following instructions, but I am not a developer.
There is nothing to install for this one and no commands to type: it all happens inside Claude. If any instruction below implies a Terminal, translate it into the equivalent click path for me instead.
- Plain English. Define jargon the first time it appears.
- One step at a time, then wait for me to confirm before the next one.
- Tell me what success looks like at each step, and diagnose any error before moving on.

Follow the instructions below with those rules applied.

If you can browse the web, open and read this page in full first, it has the complete guide and every prompt you will run (the vault is under the-vault anchor): https://consultance.ai/library/cap-table-desk#the-vault . If you cannot open links, tell me and I will paste the page in, do not guess the prompts.

I want to SET UP the real workflow so Claude rebuilds my cap table from the signed documents and runs the waterfall against the charter, not just a chat demo. Walk me through it step by step. Treat me like a founder, CFO or deal lead who has never built a Claude Project, and define every term once.

**Route me before you set anything up.** There are two surfaces and the right one depends on what I am holding, so ask me first and then commit to one:

- **Claude app, private Project.** One company, the charter and a handful of agreements I can upload. Nothing to install. This is the common case, and if it fits me, say so plainly and do not talk me into anything heavier.
- **Claude Code, pointed at a folder.** A data room export, dozens of PDFs, a Carta or Pulley export, or the same check every quarter. It reads the documents off disk instead of me pasting them, and writes the tables and the waterfall as files. Two ways in: the Claude desktop app's Code tab (no terminal), or the terminal install, which you walk me through one command at a time.

If I describe a folder, a data room or a platform export with many files while asking for the Project path, tell me I am in the wrong place and move me to Claude Code before we start.

## Before any confidential material goes in
My documents go only to my own Claude account, never to the pack's author. Load confidential material only into an account whose data terms my company has approved: a Team or Enterprise plan, or a personal plan with model training turned off (Settings, Privacy, then toggle off "Help Improve our AI models").

## Path 1 (common case), a private Claude Project
This is NOT a Terminal install. Walk me through ONE step at a time, waiting for me to confirm each:

1. **What I need.** A Claude account. Pick **Claude Opus 5.5** in the model picker.
2. **Create the workspace.** In Claude, open Projects and create a new Project named for the company. A Project is a workspace with its own uploaded files (its "knowledge"). On a Team or Enterprise plan, choose to keep it private when you create it.
3. **First-session drill, before my own documents: run prompt 01, then the sample in prompt 02.** The sample is a made-up company with known answers. Good output: common, Seed, Series A and the options tie; "Series A-1" (400,000 shares) is UNSOURCED because no charter class and no purchase agreement exist, tagged CHANGES THE DECISION; three normal things (headroom in authorized shares, the pool rising after a leaver, fully diluted above outstanding) are listed once as EXPLAINED BY CONTEXT and not flagged. Any other result means stop and tell me which line.
4. **Then run prompt 03 on the sample.** It must refuse the payout because Series A-1 has no paper. When I write "exclude Series A-1, it was never issued", it must reproduce $1.52 per converting share and total $20,000,000.
5. **Load my documents.** The charter and every amendment, stock purchase agreements, SAFEs and notes, the option plan and grants, warrants, board and stockholder consents, the stock ledger, and my working spreadsheet (it is checked, not trusted).
6. **Run the pack.** CONVERSATION mode (the default) runs only what my question needs. FULL RUN goes 02 to 09: the tie-out, the waterfall behind its gate, the option pool, the next round three ways, the dilution ranking, the rights page, the fund fee and carry check (only if I am a fund), and the verdict.
7. **Gate it.** Prompt 03 produces no payout while any class lacks a signed document. A named person signs the verdict in prompt 09. Not legal, tax or accounting advice.

## Path 2, Claude Code on a folder
Claude Code needs a paid plan (Pro, Max, Team or Enterprise) or a Console account. The free Claude plan does not include it. If I am on the free plan, say so and offer the Project path.
1. Easiest: download the Claude desktop app and use its Code tab. No terminal. The Code tab needs a Pro, Max, Team or Enterprise subscription; a Console-only account uses the terminal install.
2. Terminal instead: on Mac or Linux paste `curl -fsSL https://claude.ai/install.sh | bash`. On Windows PowerShell paste `irm https://claude.ai/install.ps1 | iex`. Success: `claude --version` prints a version number. If it does not, open the Troubleshoot installation page in the Claude Code docs.
3. Open the company's folder, start Claude Code there, and paste prompt 01. Then continue from Path 1 step 3. In prompt 03 it writes `classes.csv` and `waterfall.py` and runs `python3 waterfall.py` on the sample first. It needs Python 3 on my machine and nothing else. If `python3` is not found, stop and tell me; the waterfall then runs in the Project path instead, by hand with the working shown.

## Rules for walking me through this
- One step at a time. Define every term once: Project, charter, preferred series, SAFE, fully diluted, waterfall, conversion, option pool, `<review_gate>`, `{{TOKEN}}`.
- Do NOT tell me a step is "not possible." If something does not run on my plan or device, say so plainly and offer the other path.
- Claude Opus 5.5 for every step. Claude Sonnet 5 only for a first pass that indexes a very large document set. Never switch model in the middle of a prompt.
- If the documents outgrow the surface we picked, stop and say so rather than working from the part you could read.
- A named person signs anything that moves money. Claude rebuilds and checks; a person owns the decision.

First message: ask me one question only, "What are you holding right now: one company's charter and a few agreements you can upload, or a folder or data room with many files?" My answer decides the surface. Confirm the surface back to me in one line, then start step 1 on that path.
Step 2 · run it on your data

Step 1 set it up. These 9 prompts do the work.

the vault

The 9 prompts

Grab the whole pack as one file, or tap any prompt below to copy it on its own. Placeholders that look like {{THIS}} get swapped for your own numbers — and if you ran Step 1, Claude fills them in for you.

One .md file · all 9 prompts, numbered, in order · nothing left out.
Click to copy
<role>Colleague who has rebuilt many cap tables for financings, exits and audits. Neutral: the spreadsheet is not assumed wrong, it is just not a source. You work for the human.</role>

<privacy>Nothing here is hosted by the pack's author: documents go only to the human's own Claude account. Before confidential material is loaded, remind them to use a Team or Enterprise plan, or a personal plan with model training turned off.</privacy>

<surface>
First, in one short paragraph, say whether the human is in the right place.
- One company, a charter and a handful of agreements they can upload: Claude app, private Project. Chat is correct here.
- A data room folder, many PDFs, a Carta or Pulley export, or the same pass every quarter: Claude Code pointed at the folder. It reads files off disk and writes the tables as files.
MODEL: Claude Opus 5.5 for every step. Claude Sonnet 5 only for a first pass that lists and indexes a very large document set. Never switch model inside a prompt.
WHOLE-JOB STOPS: the human pastes a file path, folder name or file listing instead of contents (that is a Claude Code job), or the documents are more than this conversation can hold. Say so, name Claude Code, stop.
ITEM STOPS never end the job: a document that is truncated, unsigned or not provided. Name it, ask once, mark what depends on it OPEN, and keep working on the rest. Never fill a term from memory of how these deals usually go.
Advise, do not apologise, and do not continue past a whole-job stop.
</surface>

<onboarding>
Ask each block, wait for the answer, never assume.
1. DECISION: what is this for? (A) a financing (B) an exit or sale (C) an audit, 409A or board clean-up (D) a fund reporting to LPs.
2. THESIS: in one or two lines, what do you expect? Example: "the sheet is right and all preferred converts at this price". Everything is weighed against it.
3. DOCUMENTS: (A) uploaded here (B) pasted (C) a folder, so Claude Code (D) a cap table platform export plus the PDFs (E) a mix. List what you have: charter and every amendment, stock purchase agreements, SAFEs and notes, option plan and grants, warrants, board and stockholder consents, stock ledger, the working spreadsheet.
4. TOKENS: {{COMPANY}} {{STATE_OF_INCORPORATION}} (the pack assumes Delaware; for another state, say which rules you are applying and ask the human to confirm them) {{AS_OF_DATE}} {{EXIT_OR_ROUND_TERMS}} {{SIGNER}} (the person who signs the result, required).
5. MODE: (A) CONVERSATION, the default: say the question, and I run only the prompts that bear on it. (B) FULL RUN: 02 to 09 in order.
First time using this pack: run the calibration sample in prompt 02 before loading real documents.
</onboarding>

<evidence_tiers>
TIER 1 primary: the filed charter, every amendment and any certificate of designations, executed purchase agreements, SAFEs, notes, warrants, option grant notices, board and stockholder consents, the plan, the LPA. For shares outstanding per class, a filed registration statement or the audited equity note also counts; the missing purchase agreements behind it are then a question, not a block.
TIER 2 records: the stock ledger, transfer agent statements, the cap table platform export, the 409A report.
TIER 3 claims: the working spreadsheet, term sheets, emails, decks, memory. A Tier 3 figure generates a question, never a number.
When sources disagree, the higher tier governs. Record both figures and carry the difference as a reconciling item. Every figure carries its tier and source (document, section, page). Every derived figure shows its arithmetic so a human can redo it by hand.
</evidence_tiers>

<flag_discipline>
1. Test every flag against NORMAL PATTERNS first. If explained, list it once as EXPLAINED BY CONTEXT, then drop it.
2. One tag per flag: CHANGES THE DECISION, WORTH A QUESTION, or EXPLAINED BY CONTEXT. Only the first reaches the verdict.
3. A missing document is a question with its name on it, not a verdict. The share stays on the table marked UNSOURCED. The exception: a class the charter does not authorise at all, or shares above the authorized count. That is an integrity gap, CHANGES THE DECISION for any payout, and only a document closes it.
4. A flag the human or a document closes is closed for good and never colours a later prompt.
5. "Never explain a break away" applies to arithmetic that does not tie, never to judgment flags.
6. A block stops the number it blocks, not the analysis. Keep running everything else and say what happens by default if nobody acts.
7. WORTH A QUESTION only if the answer could change a figure the human will use by more than 0.1 percent, or change the verdict. Stated basis conventions, rounding of a few shares, presentation and naming go in one BASIS NOTES line, not as flags. Missing documents that sit behind a Tier 1 count go in the open documents list, not as flags.
</flag_discipline>

<normal_patterns>
Looks wrong, is normal, unless the stated condition holds.
- Fully diluted above outstanding: options, warrants, pool and as-converted preferred. Abnormal if the gap cannot be itemised.
- Authorized far above issued: headroom. Abnormal if authorized common is below outstanding common plus shares reserved for conversion, options and warrants.
- SAFEs not in the share count: not stock until they convert. Abnormal if a pro forma or exit ignores them.
- Conversion price differs from original issue price: after a split or an anti-dilution adjustment. Abnormal if no split, down round or amendment explains it.
- Every count changed after a split: restated. Abnormal if some classes or grants were not.
- Pool "available" rose after a leaver: forfeited options recycle if the plan says so. Abnormal with no cancellation record.
- No preference paid at an IPO: preferred converts on the charter's trigger (a qualified IPO, a vote of the required preferred holders, or another event the charter names). Abnormal if no trigger is met and no signed vote is on file.
- Non-participating preferred gets more than its preference at a high exit: it takes the greater of preference or as-converted. Abnormal if it takes both.
- Ledger differs from the platform's fully diluted count: the ledger shows issued stock only. Abnormal if outstanding stock differs.
- A filed or audited count stated on a basis (an as-of date, over-allotment not exercised, notes converted at an assumed date): a convention, carry it as stated. Abnormal if the human's use needs a different basis and the difference is material.
- A few shares' gap between a formula and a filed figure: per-holder rounding. Abnormal if it exceeds one share per holder.
- An exchange or market tier named differently from the charter (a segment of the named market): normal. Abnormal if the listing is on a different exchange.
- Different series at different prices, common paid nothing at a low exit, early-exercised unvested shares in outstanding stock: normal. Abnormal only on the conditions in prompt 03 and 04.
</normal_patterns>

<how_to_adapt>Decision types: block 1. Evidence rules: the tier block. Your house normal patterns: add a line to the list. Exit mechanics your deals use: prompt 03 only. A question you always ask: append it to any task.</how_to_adapt>

<task>
When onboarding is done, build the picture before any check:
1. One paragraph: the company, the decision, the thesis, the as-of date.
2. The charter first: authorized shares per class and series, original issue price, conversion price, preference, participation, seniority, deemed liquidation and mandatory conversion clauses, each with its section. Use the charter as last amended.
3. The rebuilt cap table in date order from issuance documents and board consents, splits applied. One row per holder per instrument: holder, class, shares, price or conversion terms, date, source document and section, tier. Options, warrants, SAFEs and notes in their own schedules.
4. Any line you could not source: keep it, mark UNSOURCED, name the document that would source it.
Do not compare to the spreadsheet yet. That is prompt 02.
</task>

<rules>Never invent a figure, term, clause or document. Ask, or mark OPEN with the document expected. End every prompt with "Next step:".</rules>
Click to copy
<role>Same colleague. Neutral.</role>

<calibration>
Run this once, the first time, on the sample below and NOT on real documents. Run the task steps below on the sample and print your table in the EXPECTED OUTPUT columns, with the flag lists and the default line. Then compare line by line, on substance not wording. A normal pattern you tested and cleared counts as EXPLAINED BY CONTEXT even if you never raised it. If one figure or tag does not match, say which and STOP. Do not load real documents until it matches.

SAMPLE (synthetic company, Delaware):
Charter as amended, Art. IV: Common 15,000,000 authorized. Series Seed Preferred 2,000,000 authorized, original issue price $0.50. Series A Preferred 3,000,000 authorized, original issue price $2.00. Both series 1x, non-participating, pari passu, conversion price equal to issue price. No other class is authorized. This summary stands in for the full charter: treat dividends, deemed liquidation and election-out clauses as absent. The sample has no dates, so skip the at-each-financing test.
Documents: Founder A 4,000,000 common (stock purchase agreement). Founder B 3,000,000 common (stock purchase agreement). Fund S 2,000,000 Seed (Seed SPA). Fund A 2,500,000 Series A (Series A SPA). Option plan reserve 1,500,000 (plan and board consent). Grant notices: 1,100,000 at $0.20 strike, of which 100,000 were forfeited by a leaver (cancellation record on file, plan returns forfeited options to the reserve). No options exercised.
Working spreadsheet (Tier 3): Common 7,000,000. Seed 2,000,000. Series A 2,500,000. "Series A-1" 400,000 to Angel X at $2.00 with a 1x preference. Options outstanding 1,000,000. Available 500,000.

EXPECTED OUTPUT:
| Class | Sheet | Documents | Status | Tag |
| Common | 7,000,000 | 7,000,000 (4,000,000 + 3,000,000) | SOURCED | none |
| Seed | 2,000,000 | 2,000,000 | SOURCED | none |
| Series A | 2,500,000 | 2,500,000 | SOURCED | none |
| Series A-1 | 400,000 | 0 | UNSOURCED: no charter class, no purchase agreement | CHANGES THE DECISION for any waterfall |
| Options outstanding | 1,000,000 | 1,000,000 (1,100,000 granted less 100,000 forfeited) | SOURCED | none |
| Pool available | 500,000 | 500,000 (1,500,000 less 1,000,000 outstanding less 0 exercised) | SOURCED | none |
EXPLAINED BY CONTEXT, listed once: authorized common 15,000,000 far above 7,000,000 issued (headroom: 7,000,000 + 4,500,000 preferred as converted + 1,500,000 reserve = 13,000,000, which fits). Pool available rose after the leaver (forfeiture recorded, plan recycles). Fully diluted 13,000,000 (with the 500,000 unissued pool) above outstanding 11,500,000 (the options and the pool).
Any other flag on this sample is a mismatch.
Default if nobody acts: prompt 03 refuses to produce a payout because Series A-1 has no paper.
</calibration>

<task>
On the real documents, after the sample matches:
1. Put the rebuilt table from prompt 01 next to the spreadsheet or platform export, class by class, then holder by holder.
2. Two-way tie: every sheet line to a document, every document to a sheet line.
3. Authorized against outstanding plus reserved, per class, at today's date and at each financing.
4. For every difference: direction, size, likely cause (missing document, stale line, split not applied, converted instrument never removed, unapproved grant), the document that would settle it, and one tag.
5. The UNSOURCED list: class, holder, shares, what is missing, which document would close it. This list feeds the gate in prompt 03. Shares issued without valid approval or above the authorized count are for counsel, who may repair them by board ratification (DGCL 204) or a court petition (DGCL 205). Name the candidate; do not decide it.
</task>

<trap>The sheet and the platform export agreeing proves nothing: both are records typed from the same memory. The tie that matters is to the charter's authorized count and to a signed issuance with board approval.</trap>

<stop>If the charter or its latest amendment is not provided, say so and stop the authorized-share test; do not infer authorized shares from the sheet. Keep tying holders to their issuance documents.</stop>

<review_gate>Re-add each class two ways, by holder and by document. If the totals differ, show both and stop that class.</review_gate>
Click to copy
<role>Same colleague. Neutral.</role>

<gate>
Run this first. No payout figure is produced until it passes.
1. List every class and series that shares in the proceeds: common, each preferred series, options, warrants, SAFEs and notes that convert or get paid at the event. Use prompts 01 and 02. If they were not run, ask me for the class list and its source, once.
2. For each class name the documents behind it, with the section: the charter or amendment that authorises it, and for the shares, the agreement, SAFE, note or grant that issued them, or a filed registration statement or audited equity note that states them. A spreadsheet, a summary, a data room index or memory is not a document. Shares above the class's authorized count are unsourced for that excess.
3. If any class has no document, STOP the payout. Print: class, shares claimed, what is missing, which document would close it. Do not assume its terms.
4. Keep going on everything that does not need the payout: read the clauses in the analysis steps below and list every ambiguity, so nothing real hides behind the gate.
5. Print the default: "No payout figure is issued. The spreadsheet's waterfall stays unverified." The gate lifts only when a human supplies the document, or tells you to exclude the class and says why in writing.
</gate>

<task>
When every class traces:
1. The event: liquidation, deemed liquidation event as the charter defines it, or IPO triggering mandatory conversion. Quote the clause. Check for an election out.
2. The proceeds bridge from {{EXIT_OR_ROUND_TERMS}}: headline price less debt, transaction expenses, any carve-out plan, escrow and earn-out held back, per the charter's escrow clause and the deal terms given.
3. Per preferred series: preference (multiple times original issue price plus declared or accruing dividends), seniority, participation and any cap. Quote each.
4. The conversion test: each non-participating series takes the greater of its preference or its as-converted share. One series converting changes the others, so iterate until no series wants to switch. Show each iteration.
5. SAFEs and notes per their own terms at this event. Options per the plan and deal terms: in-the-money only, strike added back if treated as exercised.
6. The exhibit: per class and per holder payout, price per share by class, and the same table at two other exit values that sit either side of a conversion breakpoint.
7. The spreadsheet's figure next to yours, the difference by class, and the clause that explains it.
If a clause reads two ways, show the payout under both and mark it for counsel. Do not pick one silently.
In Claude Code: write classes.csv (one row per class with terms and source) and waterfall.py that reads it and prints the exhibit, save them to the folder, then run the script (python3 waterfall.py) on the prompt 02 sample first. It must reproduce the sample's check figure before you trust it on real terms.
</task>

<check_figure>Sample from prompt 02, Series A-1 excluded by the human in writing, net proceeds $20,000,000, all 1,000,000 options vested and cashed out net of the $0.20 strike. All convert: (20,000,000 + 200,000) / 12,500,000 = $1.616 per share, below Series A's $2.00, so Series A takes its preference $5,000,000. The rest converts: (20,000,000 - 5,000,000 + 200,000) / 10,000,000 = $1.52 per share, above Seed's $0.50. Payouts: Series A $5,000,000, Seed $3,040,000, common $10,640,000 (Founder A $6,080,000, Founder B $4,560,000), options $1,320,000 net of strike. Total $20,000,000. The tables at other exit values are not graded here.</check_figure>

<trap>Paying each series its 1x and giving the rest to common pro rata. Non-participating preferred take the greater of preference or as-converted, one series converting moves everyone else, and the charter's seniority and deemed liquidation language set the order, not last year's model.</trap>

<stop>If the charter's liquidation section is not provided, say so and stop; do not run a generic waterfall template. If the deal terms leave escrow or the option treatment open, stop the per-holder table and ask.</stop>

<review_gate>Payouts must sum to net proceeds to the dollar. Re-derive two classes by hand. On a break, show both figures and do not issue the exhibit.</review_gate>
Click to copy
<role>Same colleague. Neutral.</role>

<task>
1. Reserve: the plan plus every board and stockholder increase, each with its date and source.
2. Roll-forward that ties: reserve, granted, exercised, cancelled, forfeited, expired, repurchased and returned (only if the plan's recycling clause allows), available.
3. Per grant: holder, date, shares, strike, vesting start, cliff, schedule, acceleration, post-termination exercise window, vested at {{AS_OF_DATE}}, board approval (or approval by a delegate the board authorised under DGCL 157(c)) on or before the grant date.
4. Leavers: apply the plan and the grant notice for what is forfeited at termination and when vested options lapse. List any grant still shown as outstanding after the plan says it ended.
5. Early exercise: unvested shares issued under a repurchase right, with an 83(b) election filed within 30 days of the transfer.
6. Strike against the 409A value in effect on the grant date. Question any grant priced off an appraisal more than 12 months old, or one issued after a material event the appraisal did not reflect. If the grants are ISOs: shares first exercisable in one calendar year above $100,000 of grant-date value are treated as non-qualified options.
Tag each finding and say whether it moves the fully diluted count used in 03 and 05.
</task>

<trap>Available equals reserve less granted. It ignores exercises, cancellations and the plan's recycling clause, and the grants of people who left years ago still sit in outstanding and inflate fully diluted.</trap>

<stop>If the plan document or a grant's board approval is missing, say so and mark that grant OPEN; do not treat a grant notice as approved on its own.</stop>

<review_gate>The roll-forward must tie to the reserve. On a break, show the gap and stop the available figure.</review_gate>
Click to copy
<role>Same colleague. Neutral.</role>

<task>
From the tied fully diluted table and {{EXIT_OR_ROUND_TERMS}} (raise, pre-money, pool target, and what the term sheet puts in the pre-money share count):
1. Priced round with the pool increase inside the pre-money.
2. The same round with the pool increase outside it. Show the price per share and every holder's percentage under both.
3. The same round with conversions and anti-dilution applied: each SAFE on its own form (a post-money SAFE converts on its company capitalization, which excludes the new pool increase except options promised before the financing), each note with interest to the closing date, and any series whose conversion price sits above the new price adjusted per its charter formula (broad-based weighted average CP2 = CP1 x (A + B) / (A + C) with the charter's own definitions, or full ratchet). Check exempted securities.
Price depends on converted shares, which depend on price: solve by iteration and show the steps.
Output: one table, every holder pre and post under all three, price per share, and the pool after closing.
</task>

<trap>Price equals pre-money over today's fully diluted shares. The new pool and converting SAFEs and notes usually sit inside the pre-money count, so the headline valuation overstates the price existing holders effectively receive.</trap>

<stop>If a SAFE or note is not provided in signed form, say so and stop that instrument's conversion; do not model it from the sheet's cap and discount.</stop>

<review_gate>Post-money ownership must total 100.00 percent under each case. Re-derive the price per share for case 1 by hand.</review_gate>
Click to copy
<role>Same colleague. Neutral.</role>

<task>
Using the history from 01 and the case chosen in 05, split each founder's and the common holders' change in fully diluted percentage into: new money, pool increases, SAFE and note conversions, anti-dilution adjustments, warrants, and grants from the existing pool. Change one driver at a time holding the rest fixed, then show the interaction left over so the bridge sums to the total change. Rank by percentage points lost. Separate ownership lost from value lost. One sentence: which term the founder should negotiate first, and why.
</task>

<trap>Blaming the new round. The pool top-up and the SAFE conversions often cost common more than the new money, and they are set by terms the founder can still negotiate.</trap>

<stop>If prompt 05 has not produced a tied pro forma, stop; do not rank drivers on the spreadsheet's figures.</stop>

<review_gate>The bridge must sum to the total change in each holder's percentage.</review_gate>
Click to copy
<role>Same colleague. Neutral.</role>

<task>
One table, one row per series: preference multiple, seniority, participation and cap, dividends, conversion price, anti-dilution type, protective provisions, board seats and who designates them, pro rata, information and registration rights, ROFR, co-sale, drag-along thresholds, redemption. Each cell cites the charter, investors' rights agreement, voting agreement, co-sale agreement or side letter and section.
Below it: rights that appear in a side letter but not the charter; rights where the term sheet differs from the signed documents; and the two or three rights that would matter most for {{EXIT_OR_ROUND_TERMS}}. Tag each.
</task>

<trap>Reading rights off the term sheet. It is usually non-binding on the economic terms. The filed charter and signed agreements govern, and side letters add rights nobody put in the sheet.</trap>

<stop>If the investors' rights agreement or voting agreement is missing, say so and mark those columns OPEN; do not fill them from the model form.</stop>

<review_gate>Every cell cites a section, or reads OPEN.</review_gate>
Click to copy
<role>Same colleague, working on the fund's side. Neutral. Run only if the human is a fund or reports to LPs.</role>

<task>
From the LPA and the reported figures for {{AS_OF_DATE}}:
1. Management fee by period: basis (commitments, invested cost, unrealised cost or NAV), rate, step-down trigger and date, offsets for transaction, monitoring and director fees at the LPA percentage. Recompute and show the arithmetic.
2. Carry: whole-of-fund or deal-by-deal, preferred return rate, compounding and start date, catch-up percentage, split, profit measured after fund expenses. Run the tiers on the figures given.
3. Clawback and escrow: look-back, gross or net of tax, holdback, GP guarantee.
4. Tie the reported figures to the fund's ILPA Reporting Template lines if it uses one. Reported against recomputed: variance, direction (favours GP or LPs), and the LPA section that explains it. Tag each.
</task>

<normal_patterns_fund>Test fund flags against these first, unless the stated condition holds.
- Fee falls after the investment period: the step-down. Abnormal if earlier or later than the LPA trigger.
- Fee below rate times base: offsets. Abnormal if the offset percentage differs from the LPA.
- No carry while below the hurdle in a whole-of-fund waterfall. Abnormal if carry was paid before capital and preferred return came back.
- GP receives more than its split for a period: the catch-up. Abnormal if it runs past the target split.
- The GP commitment pays no fee or carry: usual. Abnormal if the LPA says otherwise.
</normal_patterns_fund>

<check_figure>Run this before real figures. $100,000,000 commitments; LPA: 2.0 percent of commitments in the investment period, then 1.5 percent of invested cost; 100 percent offset of monitoring fees. Year 6 (after the investment period): invested cost $60,000,000, monitoring fees received $150,000. Fee = 1.5% x 60,000,000 = $900,000, less offset $150,000 = $750,000. Whole-of-fund, 8 percent preferred return: contributed $80,000,000, preferred return accrued $12,000,000, cumulative distributions $85,000,000. Carry = $0, because 85,000,000 is below 80,000,000 + 12,000,000 = 92,000,000. The step-down, the offset and the zero carry are EXPLAINED BY CONTEXT, not flags. Any other result: say which line and stop. This checks steps 1 and 2 only; clawback and the ILPA tie need real inputs.</check_figure>

<trap>2 percent of commitments for the life of the fund, 20 percent of profit. The base steps down after the investment period, offsets cut the fee, and carry depends on the waterfall type, the hurdle start date and the catch-up.</trap>

<stop>If the LPA's fee or distribution section is missing, say so and stop that recompute; do not use market-standard terms.</stop>

<review_gate>Re-derive the fee for one period by hand. On a variance you cannot explain from the LPA, show it and do not call the reporting correct.</review_gate>
Click to copy
<role>Same colleague. Neutral.</role>

<task>
1. Self-check first. Re-derive the load-bearing figures independently: outstanding per class, fully diluted total, the waterfall total and two class payouts, the post-round price. Any break blocks the verdict until {{SIGNER}} resolves it in writing. Keep the rest of the output.
2. Verdict against the thesis from prompt 01 in three lines: holds, holds with conditions, or does not hold, and why.
3. CHANGES THE DECISION items, each with its evidence and tier. WORTH A QUESTION items as a list of questions addressed to the person who can answer them. EXPLAINED BY CONTEXT once, in one line each.
4. The open documents list: document, who holds it, what it would settle.
5. What happens by default if nobody acts.
6. A one-page HTML view, self-contained, no network: the tied cap table, the waterfall exhibit, the unsourced list. In Claude Code write it to cap-table-view.html in the folder.
</task>

<trap>A clean summary over an unresolved break. A verdict that reads well while a class is still UNSOURCED gives the room a number the documents do not support.</trap>

<stop>If the prompt 03 gate has not passed, do not state any payout in the verdict; say the waterfall is withheld and name the missing documents.</stop>

<review_gate>{{SIGNER}} signs the verdict. The desk prepares it; a named person owns it.</review_gate>

From a working build to an operating system.

For founders, CFOs and deal teams whose cap table lives in a spreadsheet: 9 Claude prompts that rebuild it from the signed documents, name every share without paper, and run the exit waterfall clause by clause against the charter.

Path A · free

Run the build independently

The setup rail and every prompt above are free and stay free. The cost is your time, and the risk of wiring it wrong on live data.

Back to the prompts
Path B · done with you

Connect it to your operation

The desk runs on documents you load. Consultance wires the last mile inside your own environment: the cap table platform or data room pulled under access control, the waterfall rerun whenever the record changes, and counsel sign off as a real gate before anything becomes the record. Reply "wire it" for a 30-minute slot.

Book a build call
data safety

Before you use live numbers

  • • Run last quarter's numbers first. Live data is not a test bed.
  • • Nothing here uploads to us. It runs in your own Claude account, on your own machine.
  • • A named human reviews and signs every output before it reaches a board, lender, or client.
  • • Mask account numbers and names to the minimum the task needs.
the fine print

Straight answers on ownership

Prompt set authored by consultance.ai. Decision support, not legal, tax or accounting advice, and not a substitute for counsel or the company's stock ledger. Ambiguous clauses are shown both ways, never silently resolved. A named human signs anything that moves money. Documents go only to your own Claude account or your own tenant, never to us.

Bring this workflow into your operation.

Book a build callBack to the library

Want this wired into your stack instead of running it yourself? That is our AI deal desk and finance automation service.

Newsletter

New builds, as they ship

One short note when a new build ships: what it does, who it is for, and how to run it in your own Claude.

Free. One email a week at most. Unsubscribe in one click.

More like this

Related builds

All builds
Finance and data
Finance and data

Month End Close AI Agent Team

For controllers and CFOs: a 12 agent month end close team in your own Claude that preps reconciliations, accruals, entries and flux notes as a structured review. You approve every ledger post.

Setup guide
Finance and data
Finance and data

Ramp Claude Connector Setup Guide

For controllers and finance ops teams on Ramp: Claude setup steps plus 12 read only prompts for spend baseline, close readiness, accruals and flux. Replaces the manual Ramp export to Excel.

Setup guide
Finance and data
Finance and data

Claude and NetSuite Setup Guide

For controllers, CFOs and FP&A leads on NetSuite: the setup steps for Oracle's Claude connector plus 12 read only prompts for close, receivables, payables and cash.

Setup guide
Get the free kitBook a call

From independent build to integrated workflow

What you have

The free version above. It runs this read on a file you paste in, in your own Claude. Yours to keep.

What we install

The same read, wired into your private equity stack, running the second a report lands. Nothing to upload, no new login.

See the installed version

Share with your workflow owner.

Bring the relevant team into the conversation with the build and setup guide.

Forward by email
in one line

What is Cap Table Rebuild and Waterfall Desk?

Cap Table Rebuild and Waterfall Desk is a finance and data build in the consultance.ai AI Build Library. For founders, CFOs and deal teams whose cap table lives in a spreadsheet: 9 Claude prompts that rebuild it from the signed documents, name every share without paper, and run the exit waterfall clause by clause against the charter. It fits founders, CFOs, fund CFOs and deal teams pricing a round or an exit off a cap table spreadsheet that was never tied back to the charter and the signed instruments. Setup difficulty is Medium, with 4 plain-English steps.

What does Cap Table Rebuild and Waterfall Desk do?

For founders, CFOs and deal teams whose cap table lives in a spreadsheet: 9 Claude prompts that rebuild it from the signed documents, name every share without paper, and run the exit waterfall clause by clause against the charter.

Who is Cap Table Rebuild and Waterfall Desk for?

It fits founders, CFOs, fund CFOs and deal teams pricing a round or an exit off a cap table spreadsheet that was never tied back to the charter and the signed instruments.

How hard is Cap Table Rebuild and Waterfall Desk to set up?

Medium to set up — one guided setup instruction covering 4 plain-English steps, plus 9 ready-to-run prompts on the resource page.

How would consultance.ai build this out?

The desk runs on documents you load. Consultance wires the last mile inside your own environment: the cap table platform or data room pulled under access control, the waterfall rerun whenever the record changes, and counsel sign off as a real gate before anything becomes the record. Reply "wire it" for a 30-minute slot.

What are the licensing terms?

Prompt set authored by consultance.ai. Decision support, not legal, tax or accounting advice, and not a substitute for counsel or the company's stock ledger. Ambiguous clauses are shown both ways, never silently resolved. A named human signs anything that moves money. Documents go only to your own Claude account or your own tenant, never to us.

Connect this build to your workflow.

Discuss how Cap Table Rebuild and Waterfall Desk fits your systems, controls, and team. We define the integration, review process, and deployment requirements with you.

This build comes from our AI consulting and AI implementation practice — see the full AI in finance guide and how we work with CFO teams.

Book an audit