Efficient Market Response Modeler
Production-ready command that handles model, comprehensive, market, customer. Includes structured workflows, validation checks, and reusable patterns for simulation.
Efficient Market Response Modeler
Model customer and market responses to business actions with behavioral prediction, segment analysis, and competitive reaction forecasting for go-to-market decisions.
When to Use This Command
Run this command when...
- You are planning a product launch, pricing change, or marketing campaign and need to predict how different market segments will respond
- You want to model competitive reactions to your strategic moves before committing to a go-to-market plan
- Your team needs quantified response estimates across customer segments to set realistic KPI targets and allocate budget
Do NOT use this command when...
- You need real-time A/B test analysis with live user data rather than predictive modeling
- You are modeling internal operational responses rather than external market behavior
Quick Start
# .claude/commands/efficient-market-response-modeler.md # Model market responses efficiently Model market response to: $ARGUMENTS
# Run the command claude "efficient-market-response-modeler 20% price increase on premium tier with competitor at current pricing"
Expected output:
- Segment-level response predictions (retention, churn, upgrade)
- Price elasticity estimates by customer cohort
- Competitive response probability matrix
- Revenue impact projections across scenarios
- Recommended pricing strategy with risk mitigation
Core Concepts
| Concept | Description |
|---|---|
| Response Trigger | The business action (price change, launch, campaign) being modeled |
| Segment Analysis | Breaks market response into distinct customer cohorts with different behaviors |
| Elasticity Modeling | Quantifies how sensitive demand is to the change being proposed |
| Competitive Reaction | Predicts likely competitor responses and their second-order effects |
| Response Curve | Maps expected response magnitude over time post-trigger |
Market Response Model:
Business Action (Trigger)
|
[Segment Identification]
|
+----+----+----+
| | | |
Seg1 Seg2 Seg3 Seg4
| | | |
[Elasticity Analysis]
|
[Competitive Reaction]
|
[Aggregate Response Curve]
|
Revenue & KPI Projections
Configuration
| Parameter | Default | Description |
|---|---|---|
| Segment Count | 3-5 | Number of customer cohorts modeled separately |
| Response Horizon | 6 months | Time window over which market response is projected |
| Competitive Depth | Direct competitors | Whether to include indirect and potential competitors |
| Data Inputs | Docs + market data | Customer behavior data and market intelligence sources |
| Confidence Bands | 80% interval | Width of uncertainty ranges around response predictions |
Best Practices
- Quantify the trigger -- state the exact magnitude of your planned action (e.g., "15% price increase" not "price increase") for precise elasticity modeling
- Describe your segments -- include information about customer cohorts like enterprise vs. SMB, price-sensitive vs. premium to enable segment-specific predictions
- Name your competitors -- mentioning specific competitors and their current positioning enables more realistic competitive reaction modeling
- Include historical precedent -- if you have done similar actions before, describe the outcomes to calibrate the model against observed behavior
- Model sequentially -- test the primary response first, then feed competitive reactions back in to model second-order effects
Common Issues
- Response predictions seem too optimistic -- the model may lack churn data. Explicitly state known churn rates or customer satisfaction scores for grounding
- Competitive reactions feel speculative -- provide competitor financials, recent moves, or strategic positioning to constrain the prediction space
- Segments are too coarse -- add behavioral dimensions like usage frequency, contract length, or acquisition channel to create more actionable cohorts
Reviews
No reviews yet. Be the first to review this template!
Similar Templates
Git Commit Message Generator
Generates well-structured conventional commit messages by analyzing staged changes. Follows Conventional Commits spec with scope detection.
React Component Scaffolder
Scaffolds a complete React component with TypeScript types, Tailwind styles, Storybook stories, and unit tests. Follows project conventions automatically.
CI/CD Pipeline Generator
Generates GitHub Actions workflows for CI/CD including linting, testing, building, and deploying. Detects project stack automatically.