Build an actionable sales playbook
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Use cases
Methods
Paste into a general LLM and build a sales playbook with stages, talk tracks, examples, and operating guidance.
LLMPrompt
Prompt
Copied 0
## Role
You are an expert sales operations strategist creating a comprehensive Sales Playbook to optimize sales performance and drive consistent execution.
## Task
Build a complete Sales Playbook covering:
1. **Sales Process Stages** – mapped with key activities, success metrics, tools/resources, and duration
2. **Key Roles & Responsibilities** – with KPIs and required skills for each role
3. **Best Practices & Scripts** – dos, don'ts, and sample dialogue
4. **Sales Tools & Technologies** – with purpose, integration points, and priority
5. **Performance Metrics** – targets, measurement frequency, and impact scores
6. **Training & Onboarding** – modules, timelines, resources, evaluation criteria, and a real-world scenario
## Context
{{sales-context}}
Include: sales process stages, team roles, key tools, and any unique aspects of the sales motion (deal size, sales cycle length, customer segments, etc.).
## Output
Deliver the playbook in this structure:
### 1. Sales Process Stages
Present a table with columns: Stage Name, Key Activities, Success Metrics, Tools/Resources, and Duration. Include every stage from the sales context, showing the specific activities, measurable success criteria, tools or collateral needed, and typical time spent in each stage.
### 2. Key Roles & Responsibilities
For each sales role, provide the role title, a bulleted list of responsibilities, the KPIs that role owns, and the required skills. Cover all roles mentioned in the sales context.
### 3. Best Practices & Scripts
Provide a Do list of recommended practices, a Don't list of anti-patterns to avoid, and a sample script showing realistic dialogue for a common sales interaction (discovery call, objection handling, or close). Make the script conversational and specific to the sales context.
### 4. Sales Tools & Technologies
Present a table with columns: Tool Name, Purpose, Integration Points, and Priority (High/Medium/Low). List the key tools from the sales context and any standard sales enablement platforms.
### 5. Performance Metrics
Present a table with columns: Metric Name, Target, Measurement Frequency (daily/weekly/monthly/quarterly), and Impact Score (1-10). Include both activity and outcome metrics aligned to the sales context.
### 6. Training & Onboarding
Describe 3-5 training modules, each with a title, timeline for completion, required resources or materials, and evaluation criteria. Then provide a real-world scenario walkthrough demonstrating how a new rep would apply the playbook to navigate a typical deal from first contact to close.
Use tables, bullet points, and concrete examples throughout. Make every section immediately actionable.No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/sales-playbook-builder - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "sales-playbook-builder",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}