Simulate startup financing survival

What it's for

Simulates milestone execution, correlated fundraising conditions and burn together, to separate 'we need more time' from 'we need more money'.

Creates an investor-grade bridge from engineering execution uncertainty to financing survival and capital-at-risk without exposing contributor-level data.

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.

{
  "financing_rounds": [
    {
      "amount": 2000,
      "base_close_probability": 1,
      "deadline_days": 60,
      "id": "series_a",
      "requires_milestones": [
        "enterprise_pilot"
      ]
    }
  ],
  "horizon_days": 90,
  "initial_cash": 700,
  "milestones": [
    {
      "cost_log_sigma": 0,
      "cost_median": 100,
      "depends_on": [],
      "duration_log_sigma": 0,
      "duration_median_days": 30,
      "id": "enterprise_pilot",
      "success_probability": 1
    }
  ],
  "monthly_burn_high": 300,
  "monthly_burn_likely": 300,
  "monthly_burn_low": 300,
  "seed": 3,
  "simulations": 200
}

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": [
    "Milestone costs are paid at start; success inflows and financing arrive only at their modeled event times.",
    "A cash balance below zero at any time is insolvency even if a later financing event would replenish it.",
    "Execution and market dependence is represented by one correlated latent-factor pair; scenario calibration must be refreshed.",
    "This is company planning and investor risk analysis, not investment advice."
  ],
  "ending_cash": {
    "p05": 1700,
    "p50": 1700,
    "p95": 1700
  },
  "financing_rounds": [
    {
      "conditional_close_probability": 1,
      "probability_closed_by_horizon": 1,
      "probability_triggered_by_horizon": 1,
      "round_id": "series_a"
    }
  ],
  "insolvency_day_p50_if_failed": null,
  "method": "correlated_dependency_financing_cash_survival_v1",
  "milestones": [
    {
      "completion_day_p50_if_successful": 30,
      "completion_day_p90_if_successful": 30,
      "milestone_id": "enterprise_pilot",
      "probability_success_by_horizon": 1
    }
  ],
  "probability_insolvency": 0,
  "probability_survival_to_horizon": 1,
  "probability_survival_without_financing": 0,
  "rescue_capital": {
    "p50": 0,
    "p90": 0,
    "p95": 0
  },
  "simulation": {
    "draws": 200,
    "execution_market_correlation": 0.25,
    "horizon_days": 90,
    "parallel_teams": 1
  },

How it works

Forecasting & survival — Estimate when something completes or fails, with censoring and unresolved work handled honestly rather than dropped.

1. 1 Simulate dependency-gated milestone execution, correlated fundraising conditions, event-timed burn and insolvency to quantify survival, financing dependence, and rescue capital.
2. 2 Evaluate the method-specific diagnostics and gates returned by the function, then abstain unless the declared decision clears them under locally governed thresholds.

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.

Calibrating it to your org

Calibration workflow

1. 1 Define the management decision, target outcome, aggregate unit, privacy boundary, cadence, and prediction/intervention horizon for this organization.
2. 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. 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. 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. 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. 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": "simulate dependencygated milestone execution correlated fundraising" }
  → finds "simulate_startup_financing_survival"

gitrevio_capability_describe
  { "capability_id": "simulate_startup_financing_survival" }
  → returns the input schema and agent guidance shown on this page

gitrevio_capability_run
  { "capability_id": "simulate_startup_financing_survival", "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

See every tool in Investment & portfolio choice →