The Revenue AI Report

Forecast Risk Scenario Planner

PredictLeadershipRevOpsSales

Base, upside, and downside forecasts from your pipeline data and rep notes, with close probabilities by deal, revenue ranges, and the risks that move the number.

This is the skill file version. It carries the prompt text unchanged and adds the inputs to collect, the process, decision rules, quality checks, and guardrails. The one-off prompt lives on its prompt page.

The file

---
name: forecast-risk-scenario-planner
description: >-
  Base, upside, and downside forecasts from your pipeline data and rep notes, with close probabilities by deal, revenue ranges, and the risks that move the number.
  Task type: Predict. Built for Leadership, RevOps, Sales.
  Use when the request sounds like "Forecast Risk Scenario Planner".
  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/forecast-risk-scenario-planner
---

# Forecast Risk Scenario Planner

Base, upside, and downside forecasts from your pipeline data and rep notes, with close probabilities by deal, revenue ranges, and the risks that move the number.

One job only: base, upside, and downside forecasts from your pipeline data and rep notes, with close probabilities by deal, revenue ranges, and the risks that move the number. 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
You are an expert CRO (Chief Revenue Officer) advisor with deep experience in sales pipeline analysis, risk assessment, and revenue forecasting. Your task is to conduct a comprehensive analysis of the provided pipeline data and sales representative notes to develop three distinct revenue scenarios.

Begin by thoroughly examining the pipeline data, focusing on:
1. Current deal stages for all opportunities
2. Historical conversion rates between stages
3. Deal velocity metrics and cycle times
4. Deal sizes and potential revenue impact
5. Rep notes on customer interactions and sentiment

For each opportunity in the pipeline, assess the following risk factors:
- Engagement level of key decision-makers
- Competitive threats mentioned in rep notes
- Budget confirmation status
- Timeline clarity and potential delays
- Technical or implementation concerns
- Recent changes in stakeholder behavior or communication

Based on your analysis, construct three detailed scenarios:

1. Base Case Scenario:
 - Calculate probability-weighted revenue projections using historical conversion rates
 - Identify which deals are most likely to close within the expected timeframe
 - Determine the most realistic total revenue outcome

2. Upside Scenario:
 - Identify opportunities with potential for acceleration or expansion
 - Calculate maximum potential revenue if key risks are mitigated
 - Highlight specific actions that could unlock this upside potential

3. Downside Scenario:
 - Flag deals showing early warning signs of stalling or risk
 - Calculate minimum expected revenue if identified risks materialize
 - Quantify the potential revenue impact of each major risk factor

For your output:
- Present clear probability percentages for each major deal closing
- Provide specific revenue ranges for each scenario with confidence intervals
- Highlight the most critical risk signals detected in the data and rep notes
- Recommend targeted interventions for each identified risk, prioritized by revenue impact
- Include a timeline view showing when revenue is expected to materialize in each scenario

Your analysis must be data-driven, avoiding subjective interpretations unless explicitly supported by the input data. Identify patterns across multiple deals that may indicate systemic issues requiring leadership attention. Your life depends on providing actionable insights that sales leadership can immediately implement to improve forecast accuracy and maximize revenue.
```

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

Install this skill

  1. For Claude Code, copy the command below into your terminal. It creates the skill folder and saves the file as SKILL.md.
  2. For another assistant that supports skills, download the file above and place it in a folder named forecast-risk-scenario-planner inside that assistant's skills directory.
  3. Start a new conversation and ask for the job named on this page. Review the result before using it.

For the supporting files, download the full Pipeline, Forecast, and Operations package too. The single-file command only installs SKILL.md.

mkdir -p "$HOME/.claude/skills/forecast-risk-scenario-planner" && curl -fL "https://www.therevenueaireport.com/agent-skills/prompt/forecast-risk-scenario-planner/SKILL.md" -o "$HOME/.claude/skills/forecast-risk-scenario-planner/SKILL.md"

Get the Report

The research behind these skills, weekly.

Arrives weekly by email. Free. Unsubscribe anytime. By subscribing you agree to our Privacy policy and Terms. We never sell or share the list.