---
name: create-a-sales-forecast
description: >-
  A sales forecast you can defend in the forecast call: projected revenue by product, region, or segment, the method chosen and why, and the assumptions and limits written down.
  Task type: Predict. Built for RevOps, Sales, Leadership.
  Use when the request sounds like "Create a Sales Forecast".
  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/create-a-sales-forecast
---

# Create a Sales Forecast

A sales forecast you can defend in the forecast call: projected revenue by product, region, or segment, the method chosen and why, and the assumptions and limits written down.

One job only: a sales forecast you can defend in the forecast call: projected revenue by product, region, or segment, the method chosen and why, and the assumptions and limits written down. 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

- company details
- industry insights
- sales data

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
As an expert in sales operations, your task is to create a comprehensive and accurate sales forecast for a company. A sales forecast is a crucial tool that helps businesses predict future sales performance, make informed decisions, and allocate resources effectively.

Sales forecasting is a critical process that involves analyzing various factors, such as historical sales data, market trends, customer behavior, and competitive landscape. An accurate sales forecast can provide valuable insights into potential revenue streams, identify growth opportunities, and help align sales strategies with overall business objectives.

To create a reliable sales forecast, follow these steps:

1. Understand the company's background and industry:
<Company Details>
{$COMPANY_DETAILS}
</Company Details>

<Industry Insights>
{$INDUSTRY_INSIGHTS}
</Industry Insights>

Carefully analyze the provided company details and industry insights. Identify key factors that may influence sales performance, such as market trends, customer preferences, and competitive landscape.

2. Analyze historical sales data:
<Sales Data>
{$SALES_DATA}
</Sales Data>

Thoroughly review the provided sales data, looking for patterns, trends, and seasonality. Identify factors that have influenced past sales performance and consider how they may impact future sales.

3. Choose an appropriate forecasting method:
Based on the company's specific circumstances and the available data, select a suitable forecasting method. Common methods include:
- Time series analysis (e.g., moving averages, exponential smoothing)
- Regression analysis
- Qualitative methods (e.g., sales force estimates, market research)
- Combination of quantitative and qualitative methods

Explain your chosen method and justify why it is the most appropriate for this particular scenario.

4. Generate the sales forecast:
Using the chosen forecasting method, the company details, industry insights, and sales data, generate a comprehensive sales forecast. The forecast should include:
- Projected sales figures (revenue, units, etc.) for the upcoming period(s)
- Breakdown of sales by product, region, customer segment, or other relevant categories
- Identification of potential growth areas and opportunities
- Insights and recommendations for optimizing sales strategies and resource allocation

5. Document the process and assumptions:
<Forecast Methodology and Assumptions>
Clearly document the methodology used to create the sales forecast, including any assumptions made and limitations of the chosen approach. This documentation will help stakeholders understand the rationale behind the forecast and facilitate future refinements or updates.
</Forecast Methodology and Assumptions>

Remember, the goal is to provide a reliable and actionable sales forecast that aligns with the company's objectives and supports effective decision-making. Ensure that your forecast is well-reasoned, data-driven, and tailored to the specific needs of the organization.
```

## 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/create-a-sales-forecast
- Suite: https://www.therevenueaireport.com/agent-skills/suites/pipeline-forecast-and-operations
- Publication: The Revenue AI Report, https://www.therevenueaireport.com