Create a copy-paste prompt pack for an SDR selling [PRODUCT OR SERVICE] to [TARGET BUYER]. Build 8 prompt cards for: account research brief, contact hypothesis, first outbound email, LinkedIn connection note, call opener and discovery questions, post-call recap, objection-response draft, and multistep follow-up sequence. Use these inputs: - Ideal customer profile and disqualifiers: [ICP AND DISQUALIFIERS] - Approved value claims, proof, and customer stories: [APPROVED MESSAGING] - Offer, pricing boundaries, and call to action: [OFFER AND CTA]
- Prospect or account information: [ACCOUNT NOTES] - Outreach and compliance rules: [OUTREACH RULES] For each card, provide a task name, ready-to-paste prompt with square-bracket inputs, required output format, and a factual check before sending. Require account research to label each item as verified, inferred, or unknown and to cite supplied sources only. Require outbound messages to connect one specific observed business fact to one approved value claim, use one low-friction CTA, and stay under the specified channel limit. Discovery prompts must ask open questions, not lead prospects into a problem they did not state. Never invent a trigger event, mutual connection, personal detail, customer result, ROI, integration, discount, or buying authority. Respect [OUTREACH RULES], including opt-outs, approved contact data, and limits on automated sequences. Do not imply that a prospect has a problem based on weak signals. Before answering, check that each message contains only supportable personalization and approved claims. Flag missing account evidence rather than filling it with a generic compliment.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [PRODUCT OR SERVICE] | Describe what you sell and the business problem it is designed to address. | A platform that routes support tickets to product specialists using customer-plan and issue data |
| [TARGET BUYER] | Name the usual buyer role, company profile, and operating context. | VPs of Customer Support at B2B SaaS companies with 50 to 300 support agents |
| [ICP AND DISQUALIFIERS] | List fit signals, exclusions, and qualification criteria used by your team. | Fit: high ticket volume and multiple product lines; exclude companies using fully outsourced support |
| [APPROVED MESSAGING] | Paste approved value propositions, proof points, customer stories, and claim limits. | Customer case study: Brightdesk cut first-response routing time by 31%; do not claim resolution-time improvement |
| [OFFER AND CTA] | State the approved offer, pricing boundaries, and desired next step. | Offer a 20-minute workflow review; no pricing in outbound without an AE |
| [ACCOUNT NOTES] | Provide verified account facts, contact context, and source links or notes. | RadianHQ careers page lists support operations manager and 24/7 enterprise support; source captured September 22 |
| [OUTREACH RULES] | Describe consent, opt-out, cadence, channel, and data-use rules that apply. | Use business contact data only; honor opt-outs immediately; maximum four emails in 21 days |
How to use
- Paste the full prompt and use only verified account notes and approved messaging.
- Select the card for the channel and stage, then replace its bracketed fields with current evidence.
- Check that the personalization is a fact, not an inference disguised as a fact, and confirm the CTA matches policy.
- Then send: “Write two first-email options for this account, each under 90 words and with no result claim.”
Variations
Account research brief
Use this when preparing for a new account before choosing a contact or writing outreach.
Create an SDR account brief for [ACCOUNT] using only these source notes: [SOURCES]. Assess fit against [ICP]. Return: verified company facts, likely relevant teams, stated initiatives, fit signals, disqualifiers, unanswered questions, and a recommended first contact role. Label every item verified, inferred, or unknown. Do not invent news, technology, headcount, pain points, or buying intent. End with one approved value hypothesis drawn from [APPROVED MESSAGING] and the evidence that supports it.
Discovery call prep
Use this when you have a scheduled first conversation and need a focused plan.
Prepare a 20-minute SDR discovery call for [CONTACT ROLE] at [ACCOUNT]. Known facts: [ACCOUNT NOTES]. Our approved positioning: [APPROVED MESSAGING]. Return an agenda, a concise opening, six open discovery questions grouped by workflow, impact, and decision process, listening cues, and qualification notes tied to [QUALIFICATION FRAMEWORK]. Do not state or imply pains that the prospect has not confirmed. Include a respectful next-step ask only if the call reveals a fit.
Post-call follow-up
Use this after a discovery conversation and only with confirmed call notes.
Draft a post-call email to [CONTACT] using these confirmed notes: [CALL NOTES]. Our approved next step is [NEXT STEP]. Keep it under [WORD LIMIT] words. Include the prospect’s stated priority in their terms, a neutral summary of agreed actions and owners, and the scheduled date if confirmed. Do not add product capabilities, commitments, or outcomes not discussed. Return a subject line and email, then list any note that is too ambiguous to state as fact.
Tips
- A role title is not proof of buying authority; use it to choose questions, not to claim someone owns the decision.
- Personalization should be traceable to a source note, such as a public product launch or a stated hiring need, not a flattering guess about the company.
- Keep ROI claims out of first-touch outreach unless the exact claim is approved and the conditions behind it are clear.
- When a prospect objects, summarize their concern before proposing a next step; an AI-generated rebuttal should not turn a “not now” into a false qualification.
FAQ
Can AI find reasons a company needs my product?
It can organize supplied research into hypotheses, but it should label inferences and never present an assumed pain point as a fact.
Can I use AI to personalize outbound at scale?
Only with verified, permitted data and approval rules for your channels. Keep claims and cadence within your organization’s policies and applicable law.
What should an SDR give AI after a call?
Provide cleaned, confirmed notes: stated goals, current process, stakeholders, objections, agreed actions, and dates. Do not rely on a vague memory of the conversation.