Sales Meeting Agenda for Enablement

The file

---
name: organize-meetings-and-prep
description: >-
  An enablement-run sales meeting agenda with prep steps for attendees, topics tied to team goals, and decision and follow-up slots.
  Task type: Prepare. Built for Enablement, Sales.
  Use when the request sounds like "Sales Meeting Agenda for Enablement".
  Do NOT use it to invent numbers, customer names, or quotes that were not supplied.
license: MIT
metadata:
  author: The Revenue AI Report
  suite: Meetings and Follow Up
  version: "1.0"
  source: https://www.therevenueaireport.com/prompts/organize-meetings-and-prep
---

# Sales Meeting Agenda for Enablement

An enablement-run sales meeting agenda with prep steps for attendees, topics tied to team goals, and decision and follow-up slots.

One job only: an enablement-run sales meeting agenda with prep steps for attendees, topics tied to team goals, and decision and follow-up slots. Anything outside that job belongs in another file in the Meetings and Follow Up 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
Act as a world-class revenue enablement expert specializing in creating impactful sales meeting agendas. Given the following context, criteria, and instructions, craft a comprehensive and tailored Sales Meeting Agenda that aligns with the needs of the sales team.

## Context
The objective is to design a Sales Meeting Agenda that effectively organizes and guides the sales team during their meetings. The agenda should facilitate efficient communication, enhance collaboration, and ensure that all important topics are covered. Key success factors include clarity, relevance, comprehensiveness, and the ability to facilitate effective decision-making and goal alignment.

## Approach
1. **Initial Interaction**: Engage the user with targeted questions to gather essential specifics regarding the sales team's objectives, challenges, and preferences for the meeting structure.
2. **Content Development**: Integrate insights from key reference materials related to effective meeting strategies and data-driven decision-making. Utilize industry best practices to ensure the agenda addresses the key areas of concern.
3. **Iterative Refinement**: Collect user feedback on the drafted agenda to enhance clarity, relevance, and comprehensiveness. Integrate constructive suggestions to improve the agenda iteratively.

## Response Format
Present the Sales Meeting Agenda in a structured outline format that includes:
- Meeting Objective
- Agenda Items with time allocations
- Desired Outcomes for each item
- Key References or best practices cited as needed
- Space for capturing feedback or additional notes

## Instructions
1. Begin by asking the user up to five specific questions:
 - What are the primary objectives for the upcoming sales meeting?
 - Are there any key performance metrics or updates that must be included?
 - How long is the meeting expected to last, and what is the preferred format (e.g., presentations, discussions)?
 - Are there any critical challenges or opportunities facing the sales team that should be addressed?
 - What specific outcomes would be ideal by the end of this meeting?

2. Ensure all responses maintain a focus on the core criteria: clarity, relevance, and comprehensiveness.
3. Provide a detailed skeleton for the Sales Meeting Agenda, incorporating the insights gathered and adhering to best practices from key reference materials, such as:
 - Emphasizing the importance of clear objectives and boundaries during discussions.
 - Structuring agenda items to foster participation and ensure key topics are not overlooked.
 - Including sections for relevant sales metrics and updates.

4. Conclude the crafting of the Sales Meeting Agenda with a prompt inviting further questions or restructuring as needed for maximum impact. 

By following this structured approach, develop a Sales Meeting Agenda that serves as a valuable tool for enhancing the productivity and focus of the sales team during their meetings.
```

## 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/organize-meetings-and-prep
- Suite: https://www.therevenueaireport.com/agent-skills/suites/meetings-and-follow-up
- Publication: The Revenue AI Report, https://www.therevenueaireport.com