Estimate financing dilution scenarios
Estimate financing dilution with a scenario cap-table waterfall that solves pre-money option-pool top-ups and capped or discounted convertible claims before allocating post-money ownership.
What it's for
Makes hidden dilution from option-pool refreshes and convertible claims visible before founders, boards, or investors compare financing scenarios.
What you give it
Inputs split into evidence read from your connected systems, calibration your team owns, and numerical controls that affect precision but never the result's meaning.
| Field | Type | Role | Required |
|---|---|---|---|
| confidence_level | number ≥ 0.5, ≤ 0.999 | Your calibration | Optional |
| convertibles | array of objects (4 fields) | Evidence | Optional |
| current_unallocated_option_pool_units | number ≥ 0 | Your calibration | Optional |
| holders | array of objects (2 fields) ≥ 1 item | Evidence | Yes |
| max_detail_rows | integer ≥ 1, ≤ 500 | Numerical control | Optional |
| maximum_expected_relative_dilution | any | Your calibration | Optional |
| scenarios | array of objects (5 fields) ≥ 2 items | Evidence | Yes |
Each scenarios
record
| Field | Type | Required |
|---|---|---|
| id | string (non-empty) | Yes |
| new_money | number (≥ 0) | Yes |
| pre_money_valuation | number (> 0) | Yes |
| probability | number (≥ 0, ≤ 1) | Yes |
| target_post_money_unallocated_option_pool | number (≥ 0, ≤ 1) | Yes |
{
"convertibles": [
{
"conversion_claim": 500000,
"discount_rate": 0.2,
"id": "convertible-note",
"valuation_cap": 8000000
}
],
"current_unallocated_option_pool_units": 1000000,
"holders": [
{
"id": "founders",
"ownership_units": 8000000
},
{
"id": "seed-investors",
"ownership_units": 1000000
}
],
"maximum_expected_relative_dilution": 0.3,
"scenarios": [
{
"id": "base",
"new_money": 2000000,
"pre_money_valuation": 10000000,
"probability": 0.6,
"target_post_money_unallocated_option_pool": 0.1
},
{
"id": "upside",
"new_money": 2000000,
"pre_money_valuation": 15000000,
"probability": 0.4,
"target_post_money_unallocated_option_pool": 0.1
}
]
} What you get back
This is the actual output of running the example above — computed by the same function the platform calls, not an illustration.
{
"assumptions": [
"Holder units plus the current unallocated pool are the complete pre-financing fully diluted base; all scenario probabilities, valuations, claims, and currencies share one as-of date.",
"The option-pool top-up occurs pre-money, new money buys at the round price, and each convertible is modeled as a fixed claim converting at the lower of its discounted round valuation and valuation cap.",
"The simplified waterfall does not implement pre-money versus post-money SAFE variants, MFN clauses, interest, liquidation preference, participation, anti-dilution, taxes, secondary sales, or legal priority; counsel and the canonical cap-table system remain authoritative."
],
"configuration": {
"confidence_level": 0.9,
"current_unallocated_option_pool_units": 1000000,
"existing_fully_diluted_units": 10000000,
"maximum_expected_relative_dilution": 0.3
},
"decision": "financing_dilution_within_gate",
"holder_diagnostics": [
{
"expected_post_financing_ownership": 0.6309,
"holder_id": "founders",
"post_financing_ownership_interval": [
0.6152,
0.6544
],
"pre_financing_fully_diluted_ownership": 0.8
},
{
"expected_post_financing_ownership": 0.0789,
"holder_id": "seed-investors",
"post_financing_ownership_interval": [
0.0769,
0.0818
],
"pre_financing_fully_diluted_ownership": 0.1
}
],
"method": "scenario_cap_table_option_pool_convertible_waterfall_v1",
"scenario_diagnostics": [
{
"convertible_ownership": 0.0495,
"existing_stakeholder_ownership": 0.6921,
"existing_stakeholder_relative_dilution": 0.231,
"new_money": 2000000,
"new_money_investor_ownership": 0.1584,
"post_money_fully_diluted_units": 13004291.8455,
"pre_money_valuation": 10000000,
"price_per_ownership_unit": 0.9708, Truncated for display — the full payload is 78 lines.
How it works
Statistical audit & measurement — Check whether a number is fit to decide on: coverage, timing, reconciliation, and the gaps a dashboard hides.
- 1 Freeze the canonical fully diluted holder and unallocated-pool units, fixed convertible claims and terms, and probability-weighted financing scenarios at one cap-table as-of date.
- 2 For each scenario solve the circular pre-money pool top-up, calculate the round price, convert fixed claims at the lower capped or discounted valuation, and reconcile every post-money ownership component to one.
- 3 Report holder ownership intervals and relative dilution, applying the optional expected-dilution gate without choosing legal terms or treating the simplified waterfall as the authoritative cap table.
Before you trust it
Every tool in the catalog ships with the conditions under which its answer is meaningful — and the conditions under which it should abstain instead of guessing.
Assumptions & guardrails
- Metric definitions, weights, aggregate grain, sampling, missingness, dependence, and comparison windows correspond to the management claim being audited.
- The ownership base is fully diluted and complete, option-pool top-up is pre-money, convertible instruments fit the fixed-claim cap/discount model, and all terms share one currency and as-of date.
- Association, instability, or measurement quality is not a causal effect and must not be converted directly into an individual employment decision.
- The kernel omits SAFE variants, MFN, interest, preferences, participation, anti-dilution, taxes, secondaries, and legal priority; it is scenario arithmetic, not legal advice or a fundraising recommendation.
Minimum evidence
- holders: at least 1 rows/items
- scenarios: at least 2 rows/items
How to validate it
Validate on future periods or held-out aggregate units, compare with a simple baseline, and require stability across plausible metric definitions and decision thresholds.
Calibrating it to your org
Same for everyone
The mathematical kernel, validation rules, method version, and JSON output semantics are organization-independent; no tenant-trained coefficients or company benchmark is embedded in the function.
Specific to you
- reconciled holder units, fixed conversion claims, and probability-weighted pre-money, new-money, and post-money pool cases
- cap-table as-of date and currency, fully diluted perimeter, instrument classification, claim/cap/discount treatment, pool top-up convention, scenario probabilities, dilution gate, and legal exclusions
Calibration workflow
- 1 Define the management decision, target outcome, aggregate unit, privacy boundary, cadence, and prediction/intervention horizon for this organization.
- 2 Build a tenant-scoped historical cohort using only information available before each prediction or decision; preserve zero periods, censoring, assignment probabilities, and unresolved outcomes when the method requires them.
- 3 Estimate statistical parameters on training history, but obtain costs, utilities, risk tolerance, practical-effect thresholds, capacity, and policy constraints from accountable decision owners.
- 4 Validate on later time windows or held-out aggregate units at the deployment grain, against a simple baseline and the function-specific validation strategy.
- 5 Deploy only if the returned decision clears evidence, overlap, calibration, robustness, and guardrail checks; warning, unsupported, schema-gap, and fallback decisions are abstentions.
- 6 Monitor realized outcomes, data drift, coverage, and decision regret; recalibrate at a governed cadence or after a detected regime/definition change, never merely because a stakeholder dislikes the result.
Call it from your AI
You don't wire up 388 tools in your MCP client. The GitRevio MCP server exposes 18 tools, three of which let an agent search the catalog, read a tool's schema, and run it — so the assistant finds this one on its own.
gitrevio_capabilities_search
{ "q": "estimate financing dilution with a scenario" }
→ finds "estimate_financing_dilution_scenarios"
gitrevio_capability_describe
{ "capability_id": "estimate_financing_dilution_scenarios" }
→ returns the input schema and agent guidance shown on this page
gitrevio_capability_run
{ "capability_id": "estimate_financing_dilution_scenarios", "arguments": { ... } }
→ returns the result shown above Works in Claude Desktop, Claude Code, Cursor, Cline, Continue.dev, Goose and Aider. See the MCP server.
Related tools
Calculate venture milestone efficiency
Compare evidence-adjusted milestone progress and scenario value uplift per cash consumed, preserving efficiency, value, and downside as a Pareto frontier instead of one opaque portfolio-company score.
Value next round option
Value raising now versus delaying for a milestone by simulating posterior milestone success, bridge-capacity failure, conditional future dilution, terminal stakeholder value, and lower-tail delay loss.
Allocate budget with CVAR constraint
Maximize expected portfolio return while keeping probability-weighted loss CVaR below a finance-owned tail-risk ceiling across aligned joint scenarios.
Audit budget constraint binding
Audit whether a claimed budget constraint genuinely blocks value after dependency-feasible portfolio reallocation, separating current-plan inefficiency from scarcity with scenario CVaR and a discrete budget shadow price.
Audit financing term sheet integrity
Audit startup financing terms as exact share, price, proceeds and ownership identities: include pre-money option-pool increases and converting instruments in the pricing denominator, keep secondary purchases out of company cash and post-money share creation, reconcile primary issuance, post-money equity value and reported investor ownership, and retain evidence failures and impossible fees or secondary sales.
Audit fundraising pipeline integrity
Audit a fundraising pipeline as point-in-time evidence rather than CRM theater: reconstruct monotone stage events, terminal status and primary proceeds, retain open opportunities as censored, reject forecasts made after resolution, detect duplicate active investor accounts, and gate the portfolio on mature-forecast support, Brier loss and calibration gap.