Here are 14 ready-to-use prompts designed to help you start (and structure) almost any playbook—sales, operations, founder, personal productivity, content, customer success, or team process.
Copy, paste, and fill in the brackets. Use them sequentially or pick the ones that match your needs.
1. Playbook Scope & Purpose
Act as an experienced operations / enablement specialist.
Help me define the exact scope of a new playbook for [company / team / role].
Product/service: [brief description]
Audience who will use it: [who]
Main goal of the playbook: [e.g., shorten ramp time, standardize process, increase win rate]
Output:
1. One-sentence purpose statement
2. Who it is for and who it is not for
3. Success metrics for the playbook itself
4. Recommended core sections (with 1-sentence rationale each) Open >>>
2. Ideal Structure Outline
Design a clean, practical table of contents for a [sales / ops / customer success / personal] playbook.
Context: [2–3 sentences about the business or situation]
Make the structure scannable, actionable, and easy to update.
Include suggested subsections and note which ones are must-have vs nice-to-have for a first version.
3. Ideal Customer / User Profile
Create a detailed Ideal Customer Profile (or Ideal User Profile) section for my playbook.
Product/service: [description]
Known good-fit customers/users: [list any data or examples]
Include: firmographics/demographics, pain points, triggers, buying/using process, red flags, and qualification questions.
4. Core Process Mapping
Map the end-to-end process that this playbook should cover.
Process: [e.g., from first touch to closed-won, or from onboarding to first value]
Break it into clear stages. For each stage list: goal, key activities, owner, tools, exit criteria, and common failure points.
5. Messaging & Value Proposition
Write the messaging section of the playbook.
Product: [description]
Target: [ICP]
Include: core value proposition, 3–5 key benefits with proof points, elevator pitch (30 sec), discovery questions, and talk tracks for the top 3 use cases.
6. Objection Handling Playbook
Create a complete objection-handling section.
List the 8–12 most common objections we hear (or that you expect).
For each: the real underlying concern, recommended response, supporting evidence/questions, and when to escalate.
7. Competitive Battle Cards
Build competitive battle cards for the top 3–5 competitors or alternatives.
Our offering: [brief]
For each competitor include: strengths, weaknesses, when we win, when we lose, landmines to avoid, and recommended position
8. Tools, Templates & Assets Inventory
List every tool, template, script, deck, checklist, and resource that should live inside or be linked from this playbook.
Group them by stage of the process. Flag which ones we already have vs need to create.
9. Onboarding / Ramp Plan
Design a 30/60/90-day ramp plan for new [reps / team members / users] using this playbook.
Include weekly focus areas, required activities, knowledge checks, and success milestones.
10. Metrics & Cadence
Define the performance metrics and operating cadence section.
What leading and lagging indicators should people track?
What weekly/monthly rituals (pipeline review, win-loss, etc.) should the playbook prescribe?
11. Win / Loss & Continuous Improvement
Create a simple win-loss and playbook improvement process.
Include: how and when to capture feedback, questions to ask after deals or projects, how insights get turned into playbook updates, and ownership.
12. Quick-Start Version (MVP Playbook)
I don’t need the full version yet. Create a lightweight “Day 1” MVP version of the playbook that a new person can use immediately.
Keep it under 8 pages equivalent. Prioritize the highest-leverage sections only.
13. Role-Specific Variants
Take the core playbook structure and create tailored versions or addendums for these roles: [list roles, e.g., SDR, AE, CSM, manager].
Highlight what stays the same and what changes for each.
14. Playbook Maintenance & Ownership
Design the living system for this playbook:
- Who owns it?
- How often is it reviewed?
- How do people suggest changes?
- Version control and communication of updates
- How we measure whether the playbook is actually being used and delivering value
How to use these effectively
Start with prompts 1 + 2 to lock scope and structure. Then run 3–7 to fill the high-value content. Use 12 if you need something usable this week. Re-run any prompt later with more real data for better results.
Want me to run any of these right now with your specific details, or adapt the list for a particular type of playbook (sales, content, personal, engineering, etc.)? Just give me the context.
