What changed
Predictive scenario generation now builds coherent downside and upside cases — flexing revenue, DSO, rates and FX together — and reports the liquidity and covenant impact, so stress testing is continuous rather than an annual exercise.
Try it
Illustrative demoWorked example of "Scenario & Stress Testing" on synthetic data — edit the inputs to tailor it. Edit the inputs to tailor the output — it's baked synthetic data, so nothing leaves your browser until you run it live.
Synthetic demo company (a ~$5B high-growth US AI SaaS) — swap in any name to tailor the output.
What this run should concentrate on.
Workflow
- 1.Take the base plan and the variables to stress (revenue, DSO/DIO, rates, FX).
- 2.Generate coherent downside / base / upside scenarios with linked assumptions.
- 3.Compute liquidity, covenant-headroom and FCF impact per scenario.
- 4.Highlight breach thresholds and the earliest breach horizon.
- 5.Draft a scenario summary for the CFO and treasury.
Prompt / agent recipe
From the attached base plan, build downside, base and upside scenarios stressing [revenue, DSO, rates, FX]. Keep assumptions internally consistent. For each scenario, report liquidity, covenant headroom and FCF, and flag any covenant breach with its timing. List the assumptions you used.
Controls required
- Scenario assumptions documented and approved
- Treasury/CFO review before scenarios inform decisions
- Covenant definitions validated against agreements
- No automated funding/hedging action without sign-off