Scenario & Policy
Macro → sector → issuer roll-ups
Model how macro scenarios and policy changes cascade through sectors to individual holdings, with systematic impact assessment and response planning.
Macro assumptions to cited issuer-level impact pack
Source map
Ingest trusted sources
Claim engine
Map claims to evidence
Workflow engine
Apply your methodology
Draft artifact
Generate cited output
Reviewer loop
Human validates
Decision pack
Export memo · brief · board pack
Macro Modeling
Test portfolio resilience across interest rate, inflation, and growth scenarios.
Policy Impact
Assess regulatory changes, tax reforms, and trade policy effects systematically.
Sector Cascades
Understand how macro changes flow through to specific sectors and companies.
Response Plans
Generate actionable mitigation strategies for different scenarios.
How the workflow runs
- 1Define scenario parameters and sensitivity factors
- 2Map dependencies from macro to micro levels
- 3Run scenario simulations across portfolio
- 4Quantify impacts and identify vulnerabilities
- 5Generate response strategies and hedging options
Start with a prototype
We'll help you build scenario planning capabilities tailored to your portfolio in 2-6 weeks.
How the workflow runs
Six terms you'll see across the product. Each maps to a concrete artifact, not a marketing concept.
Source map
Every trusted input — filings, broker research, internal models, regulatory data — registered and verified before it can be cited.
Claim engine
Maps each assertion in a draft to the evidence span it came from. Unsupported claims surface before review.
Workflow engine
Your methodology — IC framework, scoring rubric, red-flag library — running as a repeatable workflow, not a prompt.
Reviewer loop
Analyst review at the claim level. Approve, flag, or rewrite — every action recorded against the evidence.
Decision pack
The output: memo, brief, or board pack — every paragraph traceable to its source.
Audit trail
Every source ingestion, claim mapping, reviewer action, and export — captured and exportable with the artifact.
Start small
Most teams begin with one workflow, one source set, and one output.
