Sales Performance Report with Self-Review

The file

---
name: analyze-a-sales-funnel
description: >-
  A sales performance and revenue report that the AI scores against your own criteria and then revises, so you get a second draft before you review it.
  Task type: Analyze. Built for RevOps, Sales.
  Use when the request sounds like "Sales Performance Report with Self-Review".
  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/analyze-a-sales-funnel
---

# Sales Performance Report with Self-Review

A sales performance and revenue report that the AI scores against your own criteria and then revises, so you get a second draft before you review it.

One job only: a sales performance and revenue report that the AI scores against your own criteria and then revises, so you get a second draft before you review it. 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

- department
- role
- task description
- key references
- criteria
- justification
- rating

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 AI assistant tasked with creating a revenue plan and report for the {$DEPARTMENT} department as an {$ROLE}. Your goal is to develop a comprehensive and insightful report that will aid the sales team and management in analyzing sales performance, identifying trends, and making informed strategic decisions to drive revenue growth.

Here are the key steps to follow:

1. Begin by thoroughly reviewing the {$TASK_DESCRIPTION} to understand the requirements, success factors, and objectives of the revenue plan and report.

2. Next, carefully study the {$KEY_REFERENCES} provided. These references contain valuable insights, frameworks, and best practices related to data-driven decision-making, sales management, and effective data visualization. Make notes on how you can incorporate the key insights from these references into your revenue plan and report.

3. Start drafting the revenue plan and report, keeping the following in mind:
 a. Collect and analyze relevant sales data, ensuring accuracy and reliability.
 b. Identify trends, patterns, and correlations in the data that can provide actionable insights.
 c. Present the data and insights in a visually appealing and well-organized manner, using appropriate charts, graphs, and visuals.
 d. Integrate the key insights and best practices from the provided references to enhance the quality and relevance of your work.
 e. Ensure that the report is comprehensive, addressing all aspects of sales performance and providing a clear roadmap for revenue growth strategies.

4. Once you have a draft of the revenue plan and report, evaluate your work against the provided {$CRITERIA}. For each criterion, provide a detailed justification explaining how your work meets or falls short of the criterion's description. Then, assign a rating from 1 to 10 based on the provided evaluation rubric.

<justification>Write your justification for how well the work meets each criterion here.</justification>
<rating>Assign a rating from 1 to 10 here.</rating>

5. After evaluating your work, consider the following options for iterative improvement:

- Refine the revenue plan and report based on the feedback and justifications provided in the evaluation.
- Conduct a more stringent evaluation, applying a higher standard or seeking additional perspectives.
- Gather more personalized information or clarification from the user to further tailor the report.
- Emulate feedback from a focus group or a group of experts to identify areas for improvement.
- Explore creative approaches or alternative formats to present the information more effectively.
- Request modifications to the format, style, or length of the report to better align with user preferences.

6. Implement the chosen option(s) and update the revenue plan and report accordingly. Document the changes made in a "Change Log" section at the end of the report.

7. Repeat steps 4-6 until you are satisfied with the quality of the revenue plan and report, ensuring it meets or exceeds the criteria and aligns with the user's expectations.

Remember, the key to success is to leverage the provided resources, apply industry best practices, and continuously refine your work through iterative evaluations and improvements. Aim to create a revenue plan and report that is accurate, insightful, and visually compelling, enabling the sales team and management to make data-driven decisions and drive revenue growth effectively.
```

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