Skip to main content
command CX Codex

business-scenario-explorer · davepoon — Claude Code command: how to install

business-scenario-explorer models multiple business timelines under specific constraints, stress-tests assumptions, and guides strategic planning.

MIT ★ 3,785 updated 2026-10-25

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add davepoon/buildwithclaude
/plugin install all-commands@buildwithclaude
Open on GitHub

What business-scenario-explorer does

This command runs a business timeline simulation inside Claude Code. It starts by auditing prerequisites like revenue drivers and the chosen planning horizon. Missing parameters trigger follow-up questions from the agent. It avoids guessing critical figures.

The workflow maps external market conditions against internal constraints like burn rate. Next, it generates a baseline projection alongside 2–3 optimistic, pessimistic, and disruption variants. Results feature quarter-by-quarter revenue trajectories, point-of-no-return milestones, and confidence scores from 1 to 10.

Without defined financial drivers and clear timeframes, the command pauses to demand details. Providing concrete scenario inputs directly inside $ARGUMENTS speeds up the process.

What it helps with

  • Stress-test cash flow and runway against potential market downturns
  • Map alternate business timelines across optimistic, pessimistic, and disruption branches
  • Spot point-of-no-return milestones and pivot windows
  • Prioritize capital allocation across planning horizons from 3 months to 5 years

Example prompts for the agent

  • /business-scenario-explorer 1-2 year timeline: enterprise SaaS expansion with $200k runway and rising CAC
  • /business-scenario-explorer Simulate 3-6 month cash flow risks for an e-commerce shop during a supply shock
  • /business-scenario-explorer 3-5 year timeline: market entry strategy evaluating regulatory barriers and pricing pressure

How to install business-scenario-explorer

1Plugin marketplace

/plugin marketplace add davepoon/buildwithclaude
/plugin install all-commands@buildwithclaude

2Manually: put the files in place

.claude/commands/business-scenario-explorer.md

Call it with /business-scenario-explorer. For all projects use ~/.claude/commands/

Questions about business-scenario-explorer

How do I install business-scenario-explorer in Claude Code?

Add the marketplace repository with /plugin marketplace add davepoon/buildwithclaude, then run /plugin install all-commands@buildwithclaude. You can also place the file directly at .claude/commands/business-scenario-explorer.md.

What does business-scenario-explorer do?

It models business projections across multiple timelines under external, internal, and temporal constraints. The command outputs baseline, optimistic, pessimistic, and disruption scenarios paired with risk assessments.

What planning horizons does the command support?

The simulation handles three standard windows: short-term (3–6 months) for product releases, medium-term (1–2 years) for strategic initiatives, and long-term (3–5+ years) for market cycle shifts.

Source text

business-scenario-explorer.md · MIT
---
description: Explore multiple business timeline scenarios with constraint validation and decision optimization.
category: simulation-modeling
argument-hint: "Specify business scenario parameters"
---

# Business Scenario Explorer

Explore multiple business timeline scenarios with constraint validation and decision optimization.

## Instructions

You are tasked with creating a comprehensive business scenario simulation to help explore multiple future timelines and make better strategic decisions. Follow this systematic approach: **$ARGUMENTS**

### 1. Prerequisites Assessment

**Before proceeding, validate these critical inputs:**

- **Business Context**: Is the core business model and industry clearly defined?
- **Time Horizon**: What is the planning timeline (quarters, years, market cycles)?
- **Key Variables**: What are the primary factors that could change outcomes?
- **Success Metrics**: How will you measure scenario success/failure?
- **Decision Points**: What specific decisions need to be made?

**If any of these are unclear, use progressive questioning:**

```
Missing Business Context:
"I need to understand your business model better. Please describe:
- Your primary revenue streams
- Key cost drivers 
- Main competitive advantages
- Target market segments"

Missing Time Horizon:
"What planning period should we simulate?
- Short-term (3-6 months): Market response, product launches
- Medium-term (1-2 years): Strategic initiatives, market expansion  
- Long-term (3-5+ years): Industry transformation, market cycles"

Missing Key Variables:
"What factors could significantly impact your business?
- Market conditions (growth, recession, disruption)
- Competitive landscape changes
- Regulatory shifts
- Technology adoption
- Customer behavior evolution"
```

### 2. Constraint Modeling

**Map the decision environment with systematic constraint analysis:**

#### External Constraints
- Market size and growth dynamics
- Competitive positioning and responses
- Regulatory environment and compliance requirements
- Economic conditions and cycles
- Technology adoption curves
- Supply chain dependencies

#### Internal Constraints  
- Financial resources and burn rate
- Team capabilities and capacity
- Technology infrastructure limitations
- Brand positioning and reputation
- Customer base characteristics
- Operational scalability factors

#### Temporal Constraints
- Product development cycles
- Market timing windows
- Seasonal business patterns
- Contract and partnership timelines
- Regulatory approval processes

**Quality Gate**: Validate that constraints are:
- Specific and measurable
- Based on real data where possible
- Include ranges/uncertainty bounds
- Account for interdependencies

### 3. Scenario Architecture

**Design multiple timeline branches systematically:**

#### Base Case Scenario
- Most likely outcome given current trajectory
- Conservative assumptions about key variables
- Historical pattern extrapolation
- Risk-adjusted projections

#### Optimistic Scenarios (2-3 variants)
- Best-case market conditions
- Successful execution of all initiatives
- Favorable competitive dynamics
- Accelerated adoption/growth

#### Pessimistic Scenarios (2-3 variants)
- Economic downturn impact
- Increased competition
- Execution challenges
- Regulatory headwinds

#### Disruption Scenarios (2-3 variants)
- Technology breakthrough impacts
- New market entrants
- Business model shifts
- Black swan events

**Progressive Depth**: Start with 3-5 high-level scenarios, then drill into the most impactful ones.

### 4. Timeline Compression Simulation

**Run accelerated scenario testing:**

#### Quarter-by-Quarter Analysis
- Revenue progression under each scenario
- Cost structure evolution
- Market share dynamics
- Key milestone achievement

#### Decision Point Mapping
- Critical decisions required at each timeline juncture
- Option values and decision trees
- Point-of-no-return identification
- Pivot opportunity windows

#### Feedback Loop Modeling
- How early results would inform later decisions
- Adaptive strategy adjustments
- Learning and refinement cycles

### 5. Quantitative Modeling

**Apply systematic measurement to scenarios:**

#### Financial Projections
- Revenue growth trajectories
- Profit margin evolution
- Cash flow dynamics
- Investment requirements
- ROI calculations across timelines

#### Market Dynamics
- Market share progression
- Customer acquisition costs
- Lifetime value evolution
- Competitive response modeling

#### Operational Metrics
- Team scaling requirements
- Infrastructure capacity needs
- Efficiency improvements
- Quality indicators

**Confidence Scoring**: Rate each projection 1-10 based on:
- Data quality supporting the assumption
- Historical precedent availability  
- Expert validation received
- Logical consistency with other assumptions

### 6. Risk Assessment & Mitigation

**Systematically evaluate scenario risks:**

#### Probability Weighting
- Assign realistic probabilities to each scenario
- Use base rate analysis from similar situations
- Account for planning fallacy and optimism bias
- Include expert opinion and market research

#### Impact Analysis
- Quantify potential upside/downside for each scenario
- Identify business-critical failure modes
- Map cascade effects and domino risks
- Calculate expected value across scenarios

#### Mitigation Strategies
- Identify early warning indicators for each scenario
- Design adaptive responses and pivot strategies
- Build option values and flexibility into plans
- Create risk monitoring dashboards

### 7. Decision Optimization

**Generate actionable strategic guidance:**

#### Strategy Robustness Testing
- Which strategies perform well across multiple scenarios?
- What are the key sensitivity factors?
- Where are the highest-leverage decision points?
- What creates competitive moats in each timeline?

#### Resource Allocation Optimization
- Optimal budget allocation across scenarios
- Investment sequencing and timing
- Capability building priorities
- Partnership and acquisition strategies

#### Contingency Planning
- Specific action triggers for each scenario
- Resource reallocation frameworks
- Communication strategies for different outcomes
- Stakeholder management approaches

### 8. Calibration and Validation

**Ensure simulation quality and accuracy:**

#### Assumption Testing
- Compare key assumptions to historical data
- Validate with domain experts and stakeholders
- Stress-test critical assumptions
- Document confidence levels and sources

#### Scenario Plausibility Check
- Do scenarios follow logical progression?
- Are interdependencies properly modeled?
- Do financial projections balance?
- Are timelines realistic given constraints?

#### Bias Detection
- Check for anchoring on current state
- Identify confirmation bias in favorable scenarios  
- Validate pessimistic scenarios aren't too extreme
- Ensure scenarios cover full possibility space

### 9. Output Generation

**Present findings in structured, actionable format:**

```
## Business Scenario Analysis: [Business Name]

### Executive Summary
- Planning horizon: [timeline]
- Scenarios modeled: [count and types]
- Key decision points: [critical decisions]
- Recommended strategy: [specific approach]

### Scenario Outcomes Matrix

| Scenario | Probability | Year 1 Revenue | Year 2 Revenue | Key Risks | Success Factors |
|----------|-------------|----------------|----------------|-----------|-----------------|
| Base Case | 40% | $X | $Y | [risks] | [factors] |
| Optimistic A | 20% | $X | $Y | [risks] | [factors] |
| Pessimistic A | 25% | $X | $Y | [risks] | [factors] |
| Disruption A | 15% | $X | $Y | [risks] | [factors] |

### Strategic Recommendations

**Robust Strategies** (perform well across scenarios):
1. [Strategy with confidence score]
2. [Strategy with confidence score]
3. [Strategy with confidence score]

**Scenario-Specific Tactics**:
- If Base Case: [specific actions]
- If Optimistic: [specific actions]  
- If Pessimistic: [specific actions]
- If Disruption: [specific actions]

**Critical Decision Points**:
- Month 3: [decision] - Leading indicators: [metrics]
- Month 9: [decision] - Leading indicators: [metrics]
- Month 18: [decision] - Leading indicators: [metrics]

### Risk Mitigation Framework
- Early warning indicators for each scenario
- Specific response triggers and actions
- Resource reallocation procedures
- Stakeholder communication protocols

### Confidence Assessment
- High confidence projections: [list]
- Medium confidence projections: [list]  
- Low confidence projections: [list]
- Areas requiring additional research: [list]
```

### 10. Iteration and Refinement

**Establish ongoing scenario improvement:**

#### Feedback Integration
- Monthly assumption validation against actual results
- Quarterly scenario probability updates
- Annual comprehensive scenario refresh
- Continuous learning from scenario accuracy

#### Model Enhancement
- Incorporate new data sources as available
- Refine constraint modeling based on experience
- Update probability assessments based on outcomes
- Enhance decision point identification

**Success Metrics**: 
- Scenario accuracy over time
- Decision quality improvement
- Strategic option value realization
- Risk event prediction success

## Usage Examples

```bash
# Strategic business planning
/simulation:business-scenario-explorer Evaluate SaaS expansion into European markets over next 2 years

# Product launch planning
/simulation:business-scenario-explorer Model outcomes for AI-powered feature launch across different market conditions

# Investment decision
/simulation:business-scenario-explorer Analyze ROI scenarios for $5M Series A funding across market conditions

# Market entry strategy
/simulation:business-scenario-explorer Explore timeline scenarios for entering fintech market as established player
```

## Quality Indicators

- **Green**: 80%+ confidence in key assumptions, full constraint modeling, 5+ scenarios analyzed
- **Yellow**: 60-80% confidence, partial constraint mapping, 3-4 scenarios
- **Red**: <60% confidence, missing critical constraints, <3 scenarios

## Common Pitfalls to Avoid

- Planning fallacy: Overly optimistic timelines
- Anchoring bias: Scenarios too close to current state
- Confirmation bias: Favoring pleasant outcomes
- Missing constraints: Ignoring regulatory/competitive factors
- Point estimates: Not using probability distributions
- Static thinking: Not modeling adaptive responses

Transform your 10-year market cycle into a 10-hour simulation and make exponentially better strategic decisions.

© BuildWithClaude Community · MIT · davepoon/buildwithclaude

Similar slash commands

All slash commands for Finance and business →

business-scenario-explorer by other authors comes first.

From the same set235

The whole set →
setup-cdn-optimization setup-cdn-optimization is a Claude Code command for configuring CDN delivery, caching, and static assets. It runs on requests to tune an application's CDN setup. CX Codex +1 ★ 3,785repo stars opus-reviewer The opus-reviewer subagent for Claude Code performs a tier 3 architectural review after initial logic and syntax checks pass. It flags contract issues, null propagation, and task drift without editing code. CX Codex ★ 3,785repo stars certificate-monitoring The certificate-monitoring skill routes TLS certificate requests to TLS Radar, from one-off domain scans to certificate issuance and expiry monitoring. CX Codex +1 ★ 3,785repo stars pagerduty-automation The pagerduty-automation skill automates PagerDuty tasks via the Rube MCP server: manage incidents, services, on-call schedules, and escalation policies. Requires an active PagerDuty account and connected Rube MCP. CX Codex +1 ★ 3,785repo stars calendly-automation calendly-automation is a Claude Code skill that manages Calendly events, invitees, availability, and booking links through Rube MCP. CX Codex +1 ★ 3,785repo stars zoom-automation zoom-automation automates Zoom meeting scheduling, participant tracking, and cloud recording retrieval via Rube MCP. CX Codex +1 ★ 3,785repo stars bulk-import-issues bulk-import-issues moves GitHub issues into Linear in batches, with duplicate checks, progress reporting, retries, and API limit handling. CX Codex +1 ★ 3,785repo stars gsd-ui-checker gsd-ui-checker verifies UI-SPEC.md design contracts across six dimensions: copy, visuals, color, typography, spacing, third-party registries. Returns BLOCK/FLAG/PASS verdicts. CX Codex ★ 3,785repo stars

Project sponsors

Companies that keep this analytics open