Build a sales playbook for selling [OFFER] to [IDEAL CUSTOMER PROFILE]. Our sales motion and deal context are: [SALES CONTEXT]. The buyer problems we can solve are: [CUSTOMER PROBLEMS]. Our verified proof, limits, and differentiators are: [EVIDENCE AND CONSTRAINTS]. The desired next step is [NEXT STEP]. Create a field-ready playbook for a salesperson who needs to earn the next conversation, not force a premature close. Start with a 100-word positioning statement that names the buyer’s operating problem, the outcome we can support, and who is not a fit. Then produce these sections: 1. Account and contact hypotheses: five research signals to check before outreach, labeled as hypotheses rather than facts. 2. Discovery: 10 open questions grouped under current process, business impact, stakeholders, timing, and decision process. Include follow-up questions that quantify cost, risk, or opportunity without leading the buyer. 3. Qualification: a compact scorecard covering problem, authority, urgency, fit, technical or operational constraints, and agreed next step; specify what evidence earns each judgment. 4. Messaging: three talk tracks for different buyer roles, each with a problem, relevant proof, and one question. 5. Objections: responses to five likely objections using acknowledge, clarify, evidence, and next-step structure. 6. Mutual action plan: the next three meetings, their purpose, owner, required inputs, and exit criteria. Do not invent customer logos, ROI, integrations, pricing, security certifications, competitor claims, or buyer intent. Mark assertions that require internal validation. Before answering, check that every message ties to an input problem and that every stage has a concrete buyer-approved next step. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [OFFER] | Describe the product or service, including its scope. | a SaaS tool that automates monthly close task tracking and evidence collection |
| [IDEAL CUSTOMER PROFILE] | Describe the target company type, buyer roles, and relevant characteristics. | US companies with 200–1,000 employees; controllers and finance operations leaders; multi-entity accounting |
| [SALES CONTEXT] | State the sales cycle, average deal size or complexity, and current stage if known. | mid-market, 60–120 day cycle, typically a controller champion and CFO approver |
| [CUSTOMER PROBLEMS] | List the customer problems your offer can credibly address. | manual spreadsheet checklists, unclear task ownership, late reconciliation evidence, audit preparation burden |
| [EVIDENCE AND CONSTRAINTS] | List verified outcomes, case evidence, capabilities, limitations, and approved claims. | two approved case studies show fewer overdue close tasks; integrates with NetSuite only; no claim about reduced audit fees |
| [NEXT STEP] | Enter the specific buyer action or meeting you want to secure. | a 45-minute workflow review with the controller and one close-process owner |
How to use
- Use verified customer evidence and product limits, not sales slogans, as the source material.
- Ask the AI to separate account hypotheses from known facts before reps use the playbook.
- Have a sales leader test the discovery questions against three recent wins and losses.
- Follow up with: "Turn the qualification scorecard into a CRM note template with required evidence for each field."
Variations
Discovery call plan
Use this for preparing one first or second discovery conversation.
Prepare a discovery-call plan for [PROSPECT COMPANY] and [BUYER ROLE] regarding [OFFER]. Known information is [KNOWN FACTS]. Our hypothesis is [HYPOTHESIS], and the next step we want is [NEXT STEP]. Produce a 30-minute agenda, eight open questions in the right sequence, three value hypotheses labeled as unverified, and a closing script that confirms mutual next steps. Do not state research assumptions as facts or promise outcomes not supported by [EVIDENCE]. Ask up to 3 questions only if required inputs are missing.
Outbound sequence
Use this when creating a short, research-led sequence for a defined account segment.
Create a three-touch outbound sequence for [ICP] about [OFFER]. The relevant trigger or operating problem is [TRIGGER]. Approved proof is [PROOF], and the CTA is [CTA]. Produce email one, a LinkedIn message, and a breakup email, each under [WORD LIMIT] words. Each message must use one specific, supportable relevance point and ask for one low-friction next step. Do not invent company initiatives, personal details, results, or mutual connections. Ask up to 3 questions only if required inputs are missing.
Deal rescue plan
Use this when a qualified deal has stalled or lost momentum.
Create a deal-recovery plan for [ACCOUNT] buying [OFFER]. The deal history is [HISTORY], current stakeholders are [STAKEHOLDERS], unresolved risks are [RISKS], and our intended next step is [NEXT STEP]. Produce a diagnosis with evidence versus assumptions, a stakeholder map with missing roles, two re-engagement messages, and a mutual action plan. Do not claim the buyer has a priority or budget without evidence. Flag any action that needs manager or legal approval. Ask up to 3 questions only if required inputs are missing.
Tips
- A playbook should distinguish what a rep knows from what they should test; treating research guesses as facts damages trust early.
- Require a buyer-confirmed next step with an owner and purpose at every stage, not a vague promise to “follow up.”
- Use proof that matches the buyer’s situation, such as implementation evidence for operations leaders or risk evidence for executives, and retain the limitations.
- Write objection handling as a conversation path, not a rebuttal script; the clarification question is often more useful than the response.
FAQ
Can AI create a sales playbook from a product description alone?
It can create a starting structure, but it needs actual buyer problems, evidence, and sales context to be useful. Treat unsupported account details and market claims as hypotheses.
Should a playbook include scripts?
Include short talk tracks and question paths, not speeches to memorize. Reps should adapt the language to what the buyer has said.
How often should a sales playbook change?
Review it after meaningful win-loss patterns, product changes, or shifts in the ideal customer profile. Update claims only when approved evidence changes.