Separate versions for upside, base, downside, and operating-plan cases.
Product · Scenarios
Run the downside case without rebuilding the model.
Scenario work built on explicit assumptions and repeatable runs. Claude can branch a plan, change the drivers, run it, and leave a clear record of exactly what changed.
/ what it gives your team
What scenario planning gives your team
Repeatable runs tied to the exact assumptions and logic that produced them.
Compare results across versions instead of juggling disconnected tabs.
Claude can read the whole plan before it changes anything.
/ how it works
Branch, change, compare.
Start from a forecast and define the scenario question.
Let Claude branch the model and change the relevant assumptions.
Run the scenario and compare results against the current plan.
Keep, revise, or discard the branch — with the history intact.
/ common uses
Upside & downsideHiring plansPricing sensitivityFundraising plans
/ questions
Good to know
- Can I compare scenarios later?
- Yes. Each scenario run is tied to a version, so you can always compare the assumptions and results that produced each case.
- Do I need a special chat app?
- No. You work through your own assistant; the Bridge Town web app is there for review, history, and results.
/ keep exploring
The rest of the workspace.
Put scenarios on the right footing.
Connect in one click and build your first model free.
Connect to ClaudeBridge Town stores, runs, and versions the work; it does not run a language model on your behalf.