Create a Sales Policies Document

The file

---
name: create-sales-policies
description: >-
  A sales policies document covering methodology, lead qualification, engagement rules, reporting, and compliance, drafted and then checked against your criteria.
  Task type: Create. Built for RevOps, Sales, Leadership.
  Use when the request sounds like "Create a Sales Policies Document".
  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-policies
---

# Create a Sales Policies Document

A sales policies document covering methodology, lead qualification, engagement rules, reporting, and compliance, drafted and then checked against your criteria.

One job only: a sales policies document covering methodology, lead qualification, engagement rules, reporting, and compliance, drafted and then checked against your criteria. 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

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

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 comprehensive {$TASK} for the {$DEPARTMENT} department while acting in the role of {$ROLE}. Your goal is to develop a document that provides clear guidelines and procedures to ensure consistency, improve efficiency, and minimize errors in the sales process, as outlined in the {$TASK_DESCRIPTION}.

To accomplish this task, follow these steps:

1. <Understand the Context>
Carefully review the provided {$TASK_DESCRIPTION} to understand the purpose, scope, and success factors for the Sales Policies Document. Familiarize yourself with the {$ROLE} you are assuming and the expectations of the {$DEPARTMENT}.
</Understand the Context>

2. <Gather Insights>
Study the {$KEY_REFERENCES} thoroughly, extracting relevant insights, best practices, and strategies that can be incorporated into the Sales Policies Document. Take note of key points related to sales processes, techniques, enablement, and alignment between different teams.
</Gather Insights>

3. <Outline the Document>
Create an outline for the Sales Policies Document, ensuring it covers all essential aspects of the sales process. Consider including sections on:

- Sales methodology and approach
- Lead generation and qualification
- Customer engagement and value proposition
- Sales enablement tools and resources
- Performance tracking and reporting
- Compliance and ethical guidelines

<Scratchpad>
Jot down your initial thoughts, ideas, and key points to be included in each section of the outline.
</Scratchpad>

4. <Draft the Document>
Using the outline as a guide, draft the Sales Policies Document, incorporating insights from the {$KEY_REFERENCES} and aligning with the {$CRITERIA}. Ensure that the document is clear, comprehensive, and consistent, following the descriptions provided in the {$CRITERIA}.

<Document>
Write the draft of the Sales Policies Document here.
</Document>

5. <Evaluate and Refine>
Evaluate the draft Sales Policies Document against the {$CRITERIA}, providing a rating and detailed feedback for each criterion. Use the following format:

<Criterion Name>
Rating (out of 10): [rating]
Justification: [detailed justification for the rating]
Feedback: [specific feedback for improvement]
</Criterion Name>

<Overall Evaluation>
Overall Rating (out of 10): [overall rating]
Justification: [detailed justification for the overall rating]
Feedback: [overall feedback for improvement]
</Overall Evaluation>

Based on the evaluation, refine and improve the Sales Policies Document, addressing the feedback and incorporating any necessary changes.

<Refined Document>
Write the refined version of the Sales Policies Document here.
</Refined Document>

6. <Iterate and Finalize>
Repeat step 5 (Evaluate and Refine) until you are satisfied with the quality of the Sales Policies Document, ensuring it meets or exceeds the {$CRITERIA} and aligns with the {$TASK_DESCRIPTION}.

Once finalized, present the Sales Policies Document in a clear and organized manner, with appropriate sections and formatting.

<Final Sales Policies Document>
Write the final version of the Sales Policies Document here.
</Final Sales Policies Document>

Remember, your goal is to create a comprehensive and high-quality Sales Policies Document that provides clear guidelines and procedures to streamline sales operations, reduce errors, and improve overall sales performance. Utilize the provided resources effectively and iterate through evaluations and refinements to achieve the best possible outcome.
```

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