---
name: sales-forecasting-and-analysis
description: >-
  A forecast and pipeline review in tables: historical trends, pipeline quality by stage and age, key risks, and 30, 90, and 180-day actions, so you know where the number stands.
  Task type: Predict. Built for Sales, RevOps, Leadership.
  Use when the request sounds like "Sales Forecasting and Analysis".
  Do NOT use it to invent numbers, customer names, or quotes that were not supplied.
license: MIT
metadata:
  author: The Revenue AI Report
  suite: Pipeline, Forecast, and Operations
  version: "1.0"
  source: https://www.therevenueaireport.com/prompts/sales-forecasting-and-analysis
---

# Sales Forecasting and Analysis

A forecast and pipeline review in tables: historical trends, pipeline quality by stage and age, key risks, and 30, 90, and 180-day actions, so you know where the number stands.

One job only: a forecast and pipeline review in tables: historical trends, pipeline quality by stage and age, key risks, and 30, 90, and 180-day actions, so you know where the number stands. Anything outside that job belongs in another file in the Pipeline, Forecast, and Operations suite.

## When to use this skill

- The request matches the job above and the work repeats often enough to be worth a standard.
- You have, or can ask for, the inputs listed below.
- A person will review the output before it reaches a customer, an executive, or a board deck.

## When not to use it

- The answer needs a number, a benchmark, or a quote nobody supplied. Ask for it instead of producing one.
- The task is a different job in the same suite. Open that file rather than stretching this one.
- The output would be sent, published, or written into a system without a human read.

## Inputs to collect first

- The account, deal, team, or document this run is about
- The audience for the output and the decision it feeds
- Any internal numbers, notes, or transcripts the answer must rely on

Ask for anything missing before running. Do not fill a gap with a plausible guess.

## Process

1. Confirm the job, the audience, and the decision the output feeds.
2. Collect the inputs above. Name anything still missing out loud.
3. Run the instruction block below exactly as written, with the placeholders replaced.
4. Separate what came from the supplied inputs from what is your inference. Label the inference.
5. Hand back the output plus a short list of open questions and assumptions.

## Instruction block

Run this text with the placeholders filled in.

```text
# SALES ANALYSIS Framework

INITIAL DATA REQUIREMENTS
Category | Essential Data
------------|----------------
Revenue | Last 6 months
Pipeline | Current stages
Conversion | Win rates
Goals | Growth targets
Risks | Key blockers

QUANTITATIVE ANALYSIS
Create these core metric tables:

1. Performance Dashboard
Metric | Current | Target | Gap
-----------|---------|--------|----
Revenue | | |
Growth | | |
Pipeline | | |

2. Pipeline Health
Stage | Value | Deals | Conv%
-----------|-------|-------|------
Lead | | |
Qualified | | |
Closing | | |

STRATEGIC INSIGHTS
Analyze and provide bullets for:

Market Position:
• Current market share
• Competitive advantages
• Growth opportunities
• Market penetration strategy

Customer Analysis:
• Top customer segments
• Buying patterns
• Churn indicators
• Expansion potential

Product Performance:
• Feature adoption
• Value proposition
• Competitive gaps
• Innovation needs

RISK EVALUATION
Address critical areas:

Internal Challenges:
• Resource constraints
• Process bottlenecks
• Technical limitations
• Team capabilities

External Factors:
• Market conditions
• Competitive threats
• Industry changes
• Economic impacts

GROWTH STRATEGY
Break down by timeframe:

Immediate Actions (30 days):
• Critical fixes needed
• Quick wins possible
• Resource needs
• Process changes

Mid-term Focus (90 days):
• Strategic initiatives
• Team expansion
• Market opportunities
• Product development

Long-term Vision (180+ days):
• Market expansion
• Product roadmap
• Partnership strategy
• Scale planning

SUCCESS METRICS
Track these KPIs:

Revenue Metrics:
• Monthly recurring revenue
• Average deal size
• Pipeline coverage
• Win rate changes

Customer Metrics:
• Acquisition cost
• Lifetime value
• Churn rate
• Expansion revenue

Operational Metrics:
• Sales cycle length
• Conversion rates
• Team productivity
• Feature adoption

REQUIRED ANALYSIS SECTIONS
1. Historical Performance:
• Trend analysis
• Growth patterns
• Seasonal factors
• Market correlation

2. Pipeline Quality:
• Stage distribution
• Aging analysis
• Conversion trends
• Deal characteristics

3. Strategic Recommendations:
• Priority actions
• Resource needs
• Timeline
• Expected outcomes

VALIDATION POINTS
Element | Check
-----------|----------------
Data | Completeness
Trends | Realistic
Actions | Prioritized
Impact | Quantified

If you understand, You must Begin by asking questions and gathering these key business context from the user:
• Current business model
• Primary growth blockers
• Available resources
• Major market factors

Then proceed with systematic analysis of each section, focusing on the top 20% of factors that will drive 80% of results.

Take a deep breath and go step by step.
```

## Decision rules

- Supplied evidence beats inference. If the two disagree, say so and keep the evidence.
- Unknown is a valid answer. Write "unknown" rather than estimating.
- Keep one recommendation per output. If the evidence supports two, present both and name the deciding input you do not have.
- Match the reading level of a working operator. Short sentences. Explain any term the reader may not use daily.

## Quality checks

- Every number, name, date, and quote traces to an input the user supplied.
- No vendor claim is repeated as fact without naming the source.
- Assumptions are listed separately from findings.
- The output answers the original request and nothing else.
- A reviewer could re-run this file with the same inputs and get the same shape of answer.

## Guardrails

- Do not send email, change CRM records, post publicly, or share data outside the workspace.
- Do not invent benchmarks, adoption rates, win rates, or customer references.
- Flag anything that needs a human decision instead of deciding it.

## Source

- Prompt page: https://www.therevenueaireport.com/prompts/sales-forecasting-and-analysis
- Suite: https://www.therevenueaireport.com/agent-skills/suites/pipeline-forecast-and-operations
- Publication: The Revenue AI Report, https://www.therevenueaireport.com