Create a Sales Pipeline Report

The file

---
name: create-sales-pipeline-report
description: >-
  A pipeline report for your sales leadership meeting: an executive summary, conversion and deal-size analysis against prior periods, the bottlenecks slowing deals, and specific fixes. It asks up to five questions about your process first.
  Task type: Analyze. Built for Sales, Leadership, RevOps.
  Use when the request sounds like "Create a Sales Pipeline Report".
  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-sales-pipeline-report
---

# Create a Sales Pipeline Report

A pipeline report for your sales leadership meeting: an executive summary, conversion and deal-size analysis against prior periods, the bottlenecks slowing deals, and specific fixes. It asks up to five questions about your process first.

One job only: a pipeline report for your sales leadership meeting: an executive summary, conversion and deal-size analysis against prior periods, the bottlenecks slowing deals, and specific fixes. 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 a world-class expert level account executive specializing in sales strategy development. Given the following context, criteria, and instructions, create a comprehensive Sales Pipeline Report that serves as a valuable tool for the sales team in decision-making and performance tracking.

## Context
The Sales Pipeline Report is intended to provide insights into sales performance, identify potential bottlenecks, and forecast future revenue. The report should be accurate, comprehensive, and visually appealing, targeting sales managers and executives who need to make informed decisions based on the provided data.

## Approach
1. Start by engaging with the user to gather essential specifics regarding their sales process, key metrics of interest, and specific goals for the report.
2. Ask up to five detailed questions designed to extract information that will aid in crafting a high-quality personalized report.
3. Integrate insights from relevant reference materials on sales pipeline management, data analysis, and visualization best practices.
4. Create a structured outline of the report, including sections such as Executive Summary, Data Analysis, Identified Bottlenecks, Recommendations, and Visuals.
5. Ensure that the report adheres to industry best practices and effectively communicates key information through visual representations.

## Response Format
The response should be formatted as a detailed written report comprising the following sections:
- **Executive Summary**: Overview of the findings and recommendations.
- **Data Analysis**: Detailed examination of the sales data with key observations.
- **Identified Bottlenecks**: Insights into any areas hindering sales performance.
- **Actionable Recommendations**: Specific steps that the sales team can take based on the analysis.
- **Visual Representations**: Include charts, graphs, and tables to support data interpretation.

## Instructions
- Ensure high data accuracy by cross-checking all figures and sources used in the report.
- Provide actionable recommendations that are specific and practical, based on data insights.
- Focus on visual appeal by utilizing clear and intuitive designs for the report layout.
- Effectively apply insights from the mentioned key reference materials to enhance the report's quality.
- Follow best practices in sales reporting to align with industry standards and expectations.

### Skeleton Outline for the Sales Pipeline Report
1. **Executive Summary**
 - Brief introduction to the report's objectives and findings.
2. **Data Analysis**
 - Breakdown of sales metrics (lead conversion rates, average deal size, etc.).
 - Comparison with previous periods (if applicable).
3. **Identified Bottlenecks**
 - Highlight areas where sales processes may be slowing down.
4. **Actionable Recommendations**
 - Steps to improve sales processes and performance metrics.
5. **Visual Representations**
 - Charts showing sales trends, conversion rates, etc.
 - Tables summarizing key metrics.

By following this structured approach, the report will be crafted to provide a deep understanding of the sales pipeline, ultimately aiding in improved sales strategies and revenue growth.
```

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