Forecast
Generate a weighted sales forecast with best/likely/worst scenarios, commit vs. upside breakdown, and gap analysis. Use when preparing a quarterly forecast call, assessing gap-to-quota from a pipeline CSV, deciding which deals to commit vs. call upside, or checking pipeline coverage against your number.
MCP get_skill({ skillId: "forecast-2d7f02d9" })Use this skill with your agent
Create a free account and connect via MCP
# /forecast > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). Generate a weighted sales forecast with risk analysis and commit recommendations. ## Usage ``` /forecast [period] ``` Generate a forecast for: $ARGUMENTS If a file is referenced: @$1 --- ## How It Works ``` ┌─────────────────────────────────────────────────────────────────┐ │ FORECAST │ ├─────────────────────────────────────────────────────────────────┤ │ STANDALONE (always works) │ │ ✓ Upload CSV export from your CRM │ │ ✓ Or paste/describe your pipeline deals │ │ ✓ Set your quota and timeline │ │ ✓ Get weighted forecast with stage probabilities │ │ ✓ Risk-adjusted projections (best/likely/worst case) │ │ ✓ Commit vs. upside breakdown │ │ ✓ Gap analysis and recommendations │ ├─────────────────────────────────────────────────────────────────┤ │ SUPERCHARGED (when you connect your tools) │ │ + CRM: Pull pipeline automatically, real-time data │ │ + Historical win rates by stage, segment, deal size │ │ + Activity signals for risk scoring │ │ + Automatic refresh and tracking over time │ └─────────────────────────────────────────────────────────────────┘ ``` --- ## What I Need From You ### Step 1: Your Pipeline Data **Option A: Upload a CSV** Export your pipeline from your CRM (e.g. Salesforce, HubSpot). I need at minimum: - Deal/Opportunity name - Amount - Stage - Close date Helpful if you have: - Owner (if team forecast) - Last activity date - Created date - Account name **Option B: Paste your deals** ``` Acme Corp - $50K - Negotiation - closes Jan 31 TechStart - $25K - Demo scheduled - closes Feb 15 BigCo - $100K - Discovery - closes Mar 30 ``` **Option C: Describe your territory** "I have 8 deals in pipeline totaling $400K. Two are in negotiation ($120K), three in evaluation ($180K), three in discovery ($100K)." ### Step 2: Your Targets - **Quota**: What's your number? (e.g., "$500K this quarter") - **Timeline**: When does the period end? (e.g., "Q1 ends March 31") - **Already closed**: How much have you already booked this period? --- ## Output ```markdown # Sales Forecast: [Period] **Generated:** [Date] **Data Source:** [CSV upload / Manual input / CRM] --- ## Summary | Metric | Value | |--------|-------| | **Quota** | $[X] | | **Closed to Date** | $[X] ([X]% of quota) | | **Open Pipeline** | $[X] | | **Weighted Forecast** | $[X] | | **Gap to Quota** | $[X] | | **Coverage Ratio** | [X]x | --- ## Forecast Scenarios | Scenario | Amount | % of Quota | Assumptions | |----------|--------|------------|-------------| | **Best Case** | $[X] | [X]% | All deals close as expected | | **Likely Case** | $[X] | [X]% | Stage-weighted probabilities | | **Worst Case** | $[X] | [X]% | Only commit deals close | --- ## Pipeline by Stage | Stage | # Deals | Total Value | Probability | Weighted Value | |-------|---------|-------------|-------------|----------------| | Negotiation | [X] | $[X] | 80% | $[X] | | Proposal | [X] | $[X] | 60% | $[X] | | Evaluation | [X] | $[X] | 40% | $[X] | | Discovery | [X] | $[X] | 20% | $[X] | | **Total** | [X] | $[X] | — | $[X] | --- ## Commit vs. Upside ### Commit (High Confidence) Deals you'd stake your forecast on: | Deal | Amount | Stage | Close Date | Why Commit | |------|--------|-------|------------|------------| | [Deal] | $[X] | [Stage] | [Date] | [Reason] | **Total Commit:** $[X] ### Upside (Lower Confidence) Deals that could close but have risk: | Deal | Amount | Stage | Close Date | Risk Factor | |------|--------|-------|------------|-------------| | [Deal] | $[X] | [Stage] | [Date] | [Risk] | **Total Upside:** $[X] --- ## Risk Flags | Deal | Amount | Risk | Recommendation | |------|--------|------|----------------| | [Deal] | $[X] | Close date passed | Update close date or move to lost | | [Deal] | $[X] | No activity in 14+ days | Re-engage or downgrade stage | | [Deal] | $[X] | Close date this week, still in discovery | Unlikely to close — push out | --- ## Gap Analysis **To hit quota, you need:** $[X] more **Options to close the gap:** 1. **Accelerate [Deal]** — Currently [stage], worth $[X]. If you can close by [date], you're at [X]% of quota. 2. **Revive [Stalled Deal]** — Last active [date]. Worth $[X]. Reach out to [contact]. 3. **New pipeline needed** — You need $[X] in new opportunities at [X]x coverage to be safe. --- ## Recommendations 1. [ ] [Specific action for highest-impact deal] 2. [ ] [Action for at-risk deal] 3. [ ] [Pipeline generation recommendation if gap exists] ``` --- ## Stage Probabilities (Default) If you don't provide custom probabilities, I'll use: | Stage | Default Probability | |-------|---------------------| | Closed Won | 100% | | Negotiation / Contract | 80% | | Proposal / Quote | 60% | | Evaluation / Demo | 40% | | Discovery / Qualification | 20% | | Prospecting / Lead | 10% | Tell me if your stages or probabilities are different. --- ## If CRM Connected - I'll pull your pipeline automatically - Use your actual historical win rates - Factor in activity recency for risk scoring - Track forecast changes over time - Compare to previous forecasts --- ## Tips 1. **Be honest about commit** — Only commit deals you'd bet on. Upside is for everything else. 2. **Update close dates** — Stale close dates kill forecast accuracy. Push out deals that won't close in time. 3. **Coverage matters** — 3x pipeline coverage is healthy. Below 2x is risky. 4. **Activity = signal** — Deals with no recent activity are at higher risk than stage suggests.
Related Skills
More skills in Business, Marketing & Sales
Ab Testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.
Ab Test Setup
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.
Ab Test Setup
Ab Test Setup linked from Corey Haines marketing skills, with the upstream skill instructions available on GitHub.
Ab Test Store Listing
When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.
Account Research
Research a company or person and get actionable sales intel. Works standalone with web search, supercharged when you connect enrichment tools or your CRM. Trigger with "research [company]", "look up [person]", "intel on [prospect]", "who is [name] at [company]", or "tell me about [company]".
Account Research
Research a company using Common Room data. Triggers on 'research [company]', 'tell me about [domain]', 'pull up signals for [account]', 'what's going on with [company]', or any account-level question.
Explore Other Categories
Skills from other categories with shared topics
Audit Support
Support SOX 404 compliance with control testing methodology, sample selection, and documentation standards. Use when generating testing workpapers, selecting audit samples, classifying control deficiencies, or preparing for internal or external audits.
Compliance Check
Run a compliance check on a proposed action, product feature, or business initiative, surfacing applicable regulations, required approvals, and risk areas. Use when launching a feature that touches personal data, when marketing or product proposes something with regulatory implications, or when you need to know which approvals and jurisdictional requirements apply before proceeding.
Compliance Tracking
Track compliance requirements and audit readiness. Trigger with "compliance", "audit prep", "SOC 2", "ISO 27001", "GDPR", "regulatory requirement", or when the user needs help tracking, preparing for, or documenting compliance activities.