17 ready-to-use ChatGPT prompts for sales development representatives. Fill in the bracketed fields, paste into ChatGPT, and go.
Sales · 17 prompts
01
Design an SDR First-Call Framework that Qualifies Without Burning the Account
Design an SDR first-call framework that opens credibly, tests fit, handles light qualification, and earns the next step without sounding scripted or overpitching.
You are an SDR enablement strategist.
Design a first-call framework using the context below.
Context:
- Offer or service: [offer]
- Target prospect: [prospect]
- Likely pain point: [pain point]
- Qualification goal: [qualification goal]
- Desired next-step CTA: [cta]
- Tone constraints: [tone]
Instructions:
1. Open with a reason for the call that's specific to the prospect, not a generic script opener — generic openers get hung up on in the first 10 seconds.
2. Build in a natural permission-based transition before qualification questions, so the call doesn't feel like an interrogation.
3. Distinguish questions that qualify fit from questions that just collect information the prospect will resent answering on a cold call.
4. Note what to do if the prospect is guarded or short — a framework that only works when the prospect is receptive isn't a real framework.
5. End on a specific, low-friction next step rather than a vague "can I follow up."
Output format:
- Call opener (with reasoning)
- Permission transition
- Qualification questions (fit-testing, not interrogation)
- Guarded-prospect adjustment
- Close and next-step CTA
Missing information policy:
Ask up to 2 concise questions only if the offer or prospect is unclear.
Quality bar:
- Opener is specific, not generic.
- Questions test fit, not just collect data.
- Includes a guarded-prospect adjustment.
02
Design an SDR LinkedIn Outreach Playbook with Personalization and Follow-Up Discipline
Design an SDR LinkedIn outreach playbook with personalization tiers, message sequencing, follow-up discipline, and clear boundaries for when to disengage.
You are an SDR enablement strategist specializing in LinkedIn outreach.
Design a LinkedIn outreach playbook using the context below.
Context:
- Offer or service: [offer]
- Target prospect: [prospect]
- Goal: [goal]
- Proof or credibility: [proof]
- Tone constraints: [tone]
- Follow-up constraints: [constraints]
Instructions:
1. Define personalization tiers (light, moderate, deep) tied to account value, since deep personalization on every prospect doesn't scale and light personalization on a priority account wastes the opportunity.
2. Sequence the connection request, first message, and follow-ups so each builds on the last rather than repeating the same pitch.
3. Respect LinkedIn's connection-request and messaging limits in the plan so it's actually executable at volume, not just a good idea on paper.
4. Set explicit disengagement rules — how many touches before stopping, and what response signals mean stop versus keep going.
5. Note where this differs from cold email (shorter messages, more casual register, profile context as a personalization source).
Output format:
- Personalization tiers
- Message sequence (connection request through follow-ups)
- Platform-limit-aware cadence
- Disengagement rules
Missing information policy:
Ask up to 2 concise questions only if the offer or prospect is unclear.
Quality bar:
- Personalization tiers tied to account value.
- Cadence respects platform limits.
- Explicit disengagement rules.
03
Design SDR Qualification Questions that Surface Fit, Timing, and Buying Friction
Design SDR qualification questions that surface fit, timing, urgency, stakeholder shape, and buying friction instead of collecting generic discovery trivia.
You are an SDR enablement strategist.
Design a set of qualification questions using the context below.
Context:
- Offer or service: [offer]
- Target buyer: [buyer]
- Qualification goal: [qualification goal]
- Sales motion: [motion]
- Handoff expectations to the next stage: [handoff]
Instructions:
1. Separate questions that test genuine fit and urgency from questions that just collect background information the prospect will find tedious on a short call.
2. Include at least one question designed to surface buying friction (budget reality, competing priorities, internal politics) rather than only positive-signal questions.
3. Include a stakeholder-mapping question early, since missing this is the most common reason handoffs fail later.
4. Note which questions are safe to skip if the call is running short, and which are non-negotiable for a valid handoff.
5. Keep the question count realistic for the call length implied by the sales motion.
Output format:
- Fit and urgency questions
- Buying-friction questions
- Stakeholder-mapping question
- Non-negotiable vs skippable questions
- Handoff-readiness bar
Missing information policy:
Ask up to 2 concise questions only if the qualification goal is unclear.
Quality bar:
- Friction questions included, not just positive-signal ones.
- Stakeholder mapping included.
- Realistic for actual call length.
04
Design a New SDR Training Module
Create a training module for new SDRs focused on lead generation and qualification fundamentals.
You are a sales enablement strategist designing SDR onboarding.
Design a training module using the context below.
Context:
- Team context: [team]
- Training goal: [goal]
- New hire experience level: [experience level]
- Sales motion: [motion]
- Tools the SDR will use: [tools]
Instructions:
1. Sequence the module so fundamentals (offer knowledge, buyer persona, tool basics) come before live prospecting, since sending a new hire into live calls too early burns real accounts.
2. Build in a shadowing or role-play checkpoint before the SDR touches live prospects independently.
3. Distinguish what a new hire needs to know in week one from what can wait until week three, so the module doesn't try to teach everything at once.
4. Include a way to measure readiness (a specific milestone or assessment) rather than a fixed calendar-based graduation.
5. Note common early mistakes new SDRs make (over-scripting, skipping qualification, poor CRM hygiene) and where the module should address them.
Output format:
- Module sequence (week by week)
- Shadowing/role-play checkpoint
- Readiness milestone
- Common early-mistake coverage
- Tools and resources needed
Missing information policy:
Ask up to 2 concise questions only if the training goal or experience level is unclear.
Quality bar:
- Fundamentals before live prospecting.
- Readiness measured by milestone, not just calendar time.
- Common early mistakes addressed explicitly.
05
Write SDR Lead Nurture Email Templates
Create SDR emails for different stages of lead nurturing with clear progression logic.
You are an SDR specializing in lead nurturing.
Write nurture email templates using the context below.
Context:
- Offer or service: [offer]
- Target prospect: [prospect]
- Nurture stage (early interest, evaluating, gone quiet): [stage]
- Pain point: [pain point]
- Proof or credibility: [proof]
- CTA: [cta]
Instructions:
1. Write a distinct email for each nurture stage, since an early-interest lead and a gone-quiet lead need different framing — don't reuse the same template with a different subject line.
2. Make each email add new value (an insight, a resource, a relevant update) rather than just repeating the pitch with more urgency.
3. For the gone-quiet stage, include a low-pressure "should I stop reaching out" option, since forcing engagement from a cold lead usually backfires.
4. Keep the CTA proportional to the stage — an early-stage lead gets a lighter ask than one who's actively evaluating.
5. Note the logical trigger that should move a lead from one nurture stage to the next.
Output format:
- Early-interest email
- Evaluating-stage email
- Gone-quiet email (with low-pressure opt-out)
- Stage-transition triggers
Missing information policy:
Ask up to 2 concise questions only if the offer or prospect is unclear.
Quality bar:
- Each stage's email is genuinely distinct.
- CTA proportional to stage.
- Gone-quiet email includes a graceful exit option.
06
Design an SDR Objection-Handling Framework for Early Prospect Conversations
Design an SDR objection-handling framework for early prospect conversations that distinguishes brush-offs from real concerns and protects future deal access.
You are an SDR enablement strategist.
Design an objection-handling framework using the context below.
Context:
- Offer or service: [offer]
- Buyer type: [buyer]
- Common objections encountered: [objections]
- Tone constraints: [tone]
- Qualification goal: [qualification goal]
Instructions:
1. Separate reflexive brush-offs ("not interested," "send me info") from substantive objections (budget, timing, authority) since pushing back hard on a brush-off just burns the account, while a substantive objection deserves a real response.
2. For each real objection, give a response that acknowledges it honestly rather than immediately pivoting to a rebuttal — early-stage prospects disengage fast from anything that feels like a scripted counter.
3. Note which objections are actually disqualifying (this is not a fit) versus which are surmountable, since pushing on a genuine disqualifier wastes both sides' time.
4. Include guidance on when to back off entirely and preserve the relationship for a future touch rather than force the conversation.
5. Keep the framework short enough to internalize, not a script to read verbatim.
Output format:
- Brush-off vs real-objection triage
- Responses to common real objections
- Disqualifying vs surmountable objection guide
- When to back off
Missing information policy:
Ask up to 2 concise questions only if the offer or common objections are unclear.
Quality bar:
- Brush-offs and real objections handled differently.
- Disqualifying objections identified honestly.
- Includes explicit back-off guidance.
07
Build an SDR Time Management Playbook
Create a playbook for SDR productivity, time blocking, and task prioritization.
You are a sales operations strategist focused on SDR productivity.
Build a time management playbook using the context below.
Context:
- Team context: [team]
- Productivity goal: [goal]
- Current issues (e.g. reactive task-switching, admin overload): [issues]
- Tooling available: [tools]
Instructions:
1. Address task-switching directly — constant switching between calling, emailing, and CRM admin is usually the actual productivity killer, more than any single task taking too long.
2. Recommend time blocks that match energy and call-readiness (e.g. batch dialing during peak-connect windows) rather than generic even splits across the day.
3. Separate high-leverage prospecting time from low-leverage admin time and protect the former explicitly.
4. Note what to do when the plan breaks (an urgent inbound lead, a manager request) so the playbook survives real interruptions instead of being theoretical.
5. Keep the plan realistic for a full SDR workload, not an idealized schedule nobody follows past week one.
Output format:
- Time-block structure
- Task-switching reduction rules
- Protected prospecting time
- Interruption-handling guidance
Missing information policy:
Ask up to 2 concise questions only if the goal or current issues are unclear.
Quality bar:
- Addresses task-switching directly.
- Protects high-leverage time explicitly.
- Realistic under real interruptions.
08
Create a Structured Daily Plan for an SDR
Design a realistic daily plan for calling, emailing, research, and follow-up work.
You are a sales operations strategist.
Create a daily plan using the context below.
Context:
- Team context: [team]
- Quota pressure level: [quota pressure]
- Working hours: [hours]
- Tools available: [tools]
Instructions:
1. Build the plan around actual prospect availability (peak-connect call windows) rather than an even split of activities across the day.
2. Account for quota pressure explicitly — a plan for someone comfortably ahead of quota looks different from one for someone behind, and the plan should say which it's optimizing for.
3. Include buffer time for the unplanned (inbound leads, manager check-ins, CRM cleanup), since a fully packed schedule breaks on day one.
4. Distinguish must-do daily activities from ones that can slip to catch up later without real damage.
5. Keep it to a single realistic day, not a theoretical ideal.
Output format:
- Time-blocked daily schedule
- Quota-pressure adjustment notes
- Buffer time allocation
- Must-do vs flexible activities
Missing information policy:
Ask up to 2 concise questions only if quota pressure or working hours are unclear.
Quality bar:
- Built around real call-connect windows.
- Quota pressure explicitly addressed.
- Includes buffer time, not fully packed.
09
Plan Social Media Research and Prospecting for SDRs
Create a strategy for using social platforms to research and connect with potential leads.
You’ll needtarget marketplatformsgoalconstraints
Prompt
You are a sales operations strategist.
Design a social research and prospecting strategy using the context below.
Context:
- Target market: [market]
- Platforms in scope: [platforms]
- Goal: [goal]
- Constraints: [constraints]
Instructions:
1. Time-box the research step per prospect — without a limit, social research expands to fill available time and cuts into actual outreach volume.
2. Define what a "useful" research signal looks like (a recent post, a role change, a shared connection) versus generic profile browsing that doesn't change the outreach approach.
3. Note platform-specific research limits (visibility settings, rate limits on profile views) that affect what's actually findable at scale.
4. Separate research done before first contact from research that should happen only after a response, to avoid over-investing in cold prospects.
5. Keep the strategy scalable across a full prospecting list, not just a one-off deep dive.
Output format:
- Time-boxed research process
- Useful-signal criteria
- Platform-specific limits and workarounds
- Pre-contact vs post-response research split
Missing information policy:
Ask up to 2 concise questions only if the target market or platforms are unclear.
Quality bar:
- Research is explicitly time-boxed.
- Useful signals distinguished from generic browsing.
- Scalable across a full list, not just one prospect.
10
Create an SDR-to-AE Handoff Framework
Build a practical framework for handing qualified leads to the sales team with clear context transfer.
You are a sales operations strategist.
Design an SDR-to-AE handoff framework using the context below.
Context:
- Sales process: [process]
- Handoff goal: [goal]
- Current handoff issues: [issues]
- CRM context: [crm]
Instructions:
1. Define the minimum context an AE needs to not repeat the SDR's discovery questions on the first call — stakeholder names, stated pain, timing, and objections raised so far.
2. Specify a warm handoff mechanism (call, recorded intro, live intro) rather than assuming a CRM note alone will get read before the AE's first touch.
3. Set a clear ownership boundary: at what point does the SDR stop being responsible and the AE start, and what happens if the AE doesn't follow up in time.
4. Include a feedback loop back to the SDR when a handoff was too early, too late, or missing key context, so handoff quality improves over time.
5. Keep the framework lightweight enough that SDRs will actually use it under volume pressure.
Output format:
- Minimum context checklist
- Warm handoff mechanism
- Ownership boundary and SLA
- Feedback loop to SDR
Missing information policy:
Ask up to 2 concise questions only if the handoff goal or current issues are unclear.
Quality bar:
- Minimum context checklist is concrete, not vague.
- Ownership boundary is explicit.
- Includes a feedback loop, not one-way handoff.
11
Write SDR Follow-Up Emails After Initial Contact
Create follow-up emails SDRs can send after a first prospect interaction.
You are an SDR.
Write follow-up emails using the context below.
Context:
- Offer or service: [offer]
- Target prospect: [prospect]
- Initial interaction (call, DM, form fill): [initial interaction]
- Goal: [goal]
- CTA: [cta]
- Tone constraints: [tone]
Instructions:
1. Reference the specific initial interaction rather than a generic "following up" opener, since that's what separates a real follow-up from spam.
2. Vary the angle across the sequence (new information, a different pain point, a lighter ask) instead of resending the same pitch with escalating urgency.
3. Make the final email in the sequence a graceful breakup email with a genuine opt-out, since persistence past that point damages the relationship more than it helps.
4. Keep each email short — a follow-up after no response earns less of the prospect's attention than the first message did.
5. Note the appropriate spacing between emails given the initial interaction type.
Output format:
- Follow-up 1 (references initial interaction)
- Follow-up 2 (new angle)
- Follow-up 3 / breakup email (graceful opt-out)
- Recommended spacing
Missing information policy:
Ask up to 2 concise questions only if the offer or initial interaction is unclear.
Quality bar:
- References the specific initial interaction.
- Angles vary across the sequence.
- Includes a genuine breakup email.
12
Design an SDR Lead Quality Gate with Handoff, Recycle, and Disqualification Rules
Design an SDR lead quality gate with explicit handoff, recycle, and disqualification rules so the team stops passing weak opportunities downstream and can audit qualification quality.
You are a sales operations strategist.
Design a lead quality gate using the context below.
Context:
- Qualification goal: [qualification goal]
- Sales qualification criteria: [criteria]
- CRM process: [crm]
- Handoff expectations: [handoff]
- Manager review needs: [review needs]
Instructions:
1. Define the minimum bar a lead must clear to be handed off, stated concretely enough that two different SDRs would apply it the same way.
2. Create a recycle path for leads that are real but not yet ready, distinct from outright disqualification, so good-fit-wrong-timing leads aren't lost.
3. Define explicit disqualification criteria to stop weak leads from being passed just to hit activity metrics.
4. Build in a manager review or audit mechanism to catch pattern issues (an SDR passing too many weak leads, or being too conservative and starving the pipeline).
5. Keep the gate fast enough to apply on every lead without becoming its own bottleneck.
Output format:
- Minimum handoff bar (concrete criteria)
- Recycle path and criteria
- Disqualification criteria
- Manager audit mechanism
Missing information policy:
Ask up to 2 concise questions only if the qualification goal or criteria are unclear.
Quality bar:
- Handoff bar is concrete, not subjective.
- Recycle path distinct from disqualification.
- Includes a manager audit mechanism.
13
Create an SDR CRM Usage Guide
Write a practical guide for using CRM tools to track and manage SDR leads.
You are a sales operations strategist.
Create a CRM usage guide using the context below.
Context:
- CRM setup: [crm]
- Team workflow: [workflow]
- Tracking goals: [goals]
- Current CRM problems (e.g. stale data, inconsistent logging): [problems]
Instructions:
1. Identify the minimum fields an SDR must update after every interaction, since asking for too much logging is why CRM data goes stale in the first place.
2. Build logging into the natural workflow (log right after the call, not batched at end of day) since batched logging is where accuracy breaks down.
3. Address the specific current problems named, not a generic "keep your CRM updated" instruction.
4. Note what data downstream teams (AEs, marketing, leadership) actually rely on, so the guide prioritizes fields that matter over ones that don't.
5. Include a simple way for a manager to spot-check data quality without auditing every record.
Output format:
- Minimum required fields per interaction
- Logging workflow (when, not just what)
- Fixes for the named current problems
- Manager spot-check method
Missing information policy:
Ask up to 2 concise questions only if the CRM setup or current problems are unclear.
Quality bar:
- Minimum fields kept genuinely minimal.
- Logging tied to a specific workflow moment.
- Addresses the named problems directly.
14
Design SDR Role-Play Scenarios that Train Qualification Judgment and Coaching Review
Design SDR role-play scenarios that train qualification judgment, objection recovery, and next-step control, with enough structure for consistent coaching review.
You are a sales enablement strategist.
Design role-play scenarios using the context below.
Context:
- Sales motion: [motion]
- Training goal: [goal]
- Scenario types needed: [scenario types]
- Difficulty level: [difficulty]
- Coaching focus: [coaching focus]
- Evaluation criteria: [evaluation criteria]
Instructions:
1. Build scenarios around judgment calls (is this a real objection or a brush-off, is this lead worth pursuing) rather than only testing whether the SDR can recite a script.
2. Include at least one scenario with an ambiguous signal, since real calls rarely give a clean textbook response.
3. Give the role-play partner (manager or peer) explicit behavior notes so the scenario plays out consistently across different coaching sessions.
4. Define what "good" looks like in the evaluation criteria concretely enough that two managers would score the same performance similarly.
5. Escalate difficulty across the scenario set so it works for both new hires and tenured reps.
Output format:
- Scenario set (with role-play partner behavior notes)
- Ambiguous-signal scenario
- Evaluation criteria (concrete)
- Difficulty progression
Missing information policy:
Ask up to 2 concise questions only if the training goal or scenario types are unclear.
Quality bar:
- Tests judgment, not just script recall.
- Includes an ambiguous-signal scenario.
- Evaluation criteria are concrete and consistent.
15
Align SDR Outreach to the Buyer's Process
Build an SDR playbook for aligning outreach with the prospect's buying process.
You are a sales strategist.
Build a buying-process alignment playbook using the context below.
Context:
- Offer or service: [offer]
- Buyer type: [buyer]
- Sales cycle length and shape: [cycle]
- Common buying stages for this segment: [stages]
Instructions:
1. Map what signals indicate which buying stage a prospect is in, since pushing a "just researching" prospect toward a demo as hard as an "actively evaluating" one usually backfires.
2. Recommend a different SDR ask per stage — lighter for early-stage, more direct for late-stage — rather than one universal CTA.
3. Note where the SDR's outreach should defer to marketing content or nurture instead of a direct sales push, for prospects clearly early in their process.
4. Address how to re-assess stage if new information contradicts the initial read (a prospect who seemed early turns out to have an active RFP).
5. Keep the playbook usable in real time during a call or email exchange, not just as a planning document.
Output format:
- Stage-signal map
- Stage-appropriate SDR ask
- When to defer to nurture/marketing
- Re-assessment triggers
Missing information policy:
Ask up to 2 concise questions only if the buyer type or sales cycle is unclear.
Quality bar:
- Stage signals are concrete, not vague.
- CTA varies meaningfully by stage.
- Includes re-assessment logic.
16
Turn Call Notes into a Summary for Sales and Customer Success
Build a post-call summary for sales and customer success with risks, opportunities, ownership, and follow-up needs.
You are a sales operations strategist turning call notes into a shareable summary.
Build a post-call summary using the context below.
Context:
- Raw call notes: [call notes]
- Account context: [account]
- Main customer signals (risk, expansion, satisfaction): [signals]
- Commercial implications: [implications]
- Owners who need to act: [owners]
- Next steps: [next steps]
Instructions:
1. Separate what the customer explicitly said from your interpretation of it, so AE and CS teams can trust the summary without re-listening to the call.
2. Flag anything with commercial implications (churn risk, expansion signal, competitive mention) at the top, since that's what busy owners need to see first.
3. Assign next steps to specific owners with a timeframe, not a general "someone should follow up."
4. Keep the summary short enough to be read in under a minute — a long summary of a single call won't get read consistently.
5. Note anything the SDR is uncertain about rather than presenting a guess as fact.
Output format:
- Headline signal (risk/expansion/other)
- What the customer said (facts)
- Interpretation and implications
- Owned next steps with timeframe
Missing information policy:
Ask up to 2 concise questions only if the call notes or account context are too thin.
Quality bar:
- Facts separated from interpretation.
- Commercial implications surfaced first.
- Next steps have named owners and timeframes.
17
Write a Cold Outreach Email from Account Signals
Write a cold outreach email from account signals with a specific hypothesis, relevant value, and a low-friction ask.
You’ll needoffertarget buyeraccount signalspain or opportunity hypothesisproofCTA
Prompt
You are an SDR writing signal-based cold outreach.
Write a cold outreach email using the context below.
Context:
- Offer or service: [offer]
- Target buyer: [buyer]
- Account signals observed (funding, hiring, tech change, news): [signals]
- Pain or opportunity hypothesis from those signals: [hypothesis]
- Proof or credibility: [proof]
- CTA: [cta]
Instructions:
1. State the hypothesis explicitly and let the prospect confirm or correct it, rather than asserting it as fact — signal-based outreach that overclaims what a signal means reads as generic "I saw you raised funding" spam.
2. Reference the signal specifically enough that it couldn't be copy-pasted to a different account with the same signal type.
3. Connect the signal to the offer through the hypothesis, not as two separate facts stapled together.
4. Keep the CTA low-friction and proportional to a cold first touch, not a hard sales ask.
5. Note what to do if the hypothesis turns out to be wrong when the prospect replies, so the SDR doesn't awkwardly insist on it.
Output format:
- Email copy
- Hypothesis framing rationale
- CTA
- Reply-handling note if hypothesis is wrong
Missing information policy:
Ask up to 2 concise questions only if the account signals or hypothesis are unclear.
Quality bar:
- Hypothesis stated as testable, not asserted as fact.
- Signal reference is account-specific.
- CTA is low-friction for a cold first touch.