Strategic foresight, end to end

See.Simulate.Steer.

Most planning tools ask you to predict one future. ScenarioPilot builds four, gives each its own strategies and the signals to watch, and tells you when reality starts picking a side.

One cycle, five steps

The same loop a foresight team runs by hand — with the tedious parts automated and the reasoning kept where you can inspect it.

  1. 1

    Scan

    Weak signals pulled from news, research and open data — not a keyword alert, a structured sweep across STEEP categories.

  2. 2

    Cluster

    Signals resolve into drivers, each rated for impact and uncertainty. The two critical uncertainties (highest on impact and uncertainty) become your axes.

  3. 3

    Map

    Four scenarios, one per quadrant. Plausible futures you can argue with, not a single forecast to be wrong about.

  4. 4

    Strategise

    Two strategies for each future, each with its kind, an accountable role, a trigger and the assumptions it rests on.

  5. 5

    Monitor

    Indicators with thresholds. When a reading you log crosses one, the scenario it belongs to raises a trigger.

Built to be argued with

Every output is traceable

Each scenario, driver and strategy keeps a link back to the signals and sources it came from.

Decisions are recorded

Assumptions, forecasts and the triggers that fired are written down as they happen, not reconstructed later.

Your project data is scoped to you

Row-level security on every project table, with a CI check that compares the deployed policies against the migrations on each push — so drift is caught, not discovered.

Start with one uncertainty

Pick the question that keeps changing the answer, and run a full cycle on it.