Skillent
  • Home
  • AI Skills + Prompts Library
  • Free Tools
  • How To Use
  • Blog
Sign In Get Pro

ChatGPT Prompts for Sales Reps: Cold Outreach, Demos, Objections, Closing

Published: July 2026 | 8 min read

Sales reps live and die by communication — the right words in a cold email, discovery call, or objection response can make or break a deal. AI can generate outreach sequences, demo scripts, and objection responses, but only when prompts define the product, prospect persona, sales stage, and specific objection. Structured prompts turn AI into a sales coach and copywriter that never runs out of variations.

Below are production-ready AI prompts, organized by workflow. These are adapted from Skillent's AI Prompt Library.

Want 190,000+ professional AI prompts?

Get Skillent Pro — $9/month

Cold Outreach & Prospecting

1. Cold Email Sequence Writer

Role: B2B sales copywriter
Task: Write a 5-email cold outreach sequence for [product] to [persona].
Product: [describe — what it does, who it helps, key differentiator]
Target persona: [job title, company size, industry, common pain point]
Sequence (one email every 3-4 days):
Email 1: Pattern interrupt — specific pain point observation + soft CTA
Email 2: Value case — one relevant case study or stat + CTA
Email 3: Different angle — address likely objection preemptively + CTA
Email 4: Social proof — testimonial or result + urgency + CTA
Email 5: Breakup — "Should I stop reaching out?" + last-chance CTA
For each email:
- Subject line (40-50 chars, not salesy, no "quick question")
- Body (100-150 words, mobile-first, one ask per email)
- CTA (specific — 15-min call, reply with interest, watch 2-min demo)
Personalization placeholders: [First name], [Company], [Specific trigger/reason]
Output: 5-email sequence ready for sales engagement tool (Outreach/Salesloft/Apollo).
Do NOT: Use "I hope this finds you well" or "I wanted to reach out."

2. LinkedIn Outreach Message

Role: Social selling specialist
Task: Write LinkedIn connection and follow-up messages for [prospect].
Product: [describe]
Prospect: [persona — title, industry, likely priorities]
Message 1 (connection request, 300 chars max):
- Reference something specific from their profile (recent post, role change, company news)
- No pitch — just connection and genuine interest
Message 2 (after accepted, 24-48h later):
- Soft value comment + question (not a pitch)
Message 3 (if no response, 5-7 days later):
- Specific pain point + how others in their role solved it + soft CTA
Message 4 (if engaged but no meeting, 10 days later):
- Direct ask — 15-minute call or Loom video demo
Output: 4-message LinkedIn sequence with personalization instructions.
Tone: Peer-to-peer, not vendor-to-prospect. Human, not automated-feeling.

3. Cold Call Script Writer

Role: Sales call coach
Task: Write a cold call script for [product] targeting [persona].
Product: [one-sentence value prop]
Persona: [title, common priorities, likely objections]
Script structure:
1. Pattern interrupt (7 seconds): "Hi [name], this is [you] from [company]. I know I'm calling out of the blue — do you have 27 seconds?"
2. Reason for call (15 seconds): Specific trigger — "I saw [trigger] and thought of you because [reason]"
3. Value statement (20 seconds): "We help [persona type] [achieve specific outcome] by [method]. Companies like [comp A, comp B] use us to [result]."
4. Qualifying question (10 seconds): "How are you handling [pain point] today?"
5. If engaged: Schedule discovery call ("I don't want to take more of your time now — can we book 15 minutes Thursday?")
6. If resistant: Objection responses (2-3 pre-prepared)
7. If hostile: Graceful exit ("No problem — I'll send an email with info in case it's useful later")
Output: Complete cold call script with objection responses and exit strategy.

Discovery & Demos

4. Discovery Call Framework

Role: Sales consultant
Task: Create a discovery call framework for [product].
Product: [describe]
Typical buyer: [persona, priorities, buying process]
Discovery structure (45-60 min):
1. Opening (5 min): Set agenda, build rapport, establish expertise
2. Current state (10 min): How do they do [process] today? What tools? What works/doesn't?
3. Pain point exploration (15 min): 
   - "What's the biggest challenge with [current process]?"
   - "How much time does that cost?"
   - "What happens when [pain point occurs]?"
   - "What have you tried to fix it?"
4. Impact quantification (10 min): 
   - "What would solving this save/earn you?"
   - "Who else is affected by this?"
   - "What's the cost of not fixing it?"
5. Decision process (5 min): Who else is involved? Timeline? Budget? Prior approval needed?
6. Solution preview (5 min): High-level — "Based on what you've shared, here's where we could help..."
7. Next steps (5 min): Demo scheduling, who else should attend, timeline confirmation
For each section: Key questions, what to listen for, what disqualifies
Output: Full discovery framework with 15-20 key questions.

5. Demo Script Builder

Role: Sales engineer
Task: Create a product demo script for [product] for [persona].
Product: [describe key features and value]
Persona: [title, priorities, what they care about]
Demo structure (30-45 min):
1. Recap discovery (3 min): Confirm pain points from previous call, set agenda
2. High-level overview (2 min): What the product does in 3 sentences
3. Feature-by-feature demo (25-35 min): Only show features tied to stated pain points
   For each feature:
   a. "You mentioned [pain point] — here's how we solve it"
   b. Show the feature (screen share walkthrough)
   c. "Does this address what you described?"
   d. Transition to next pain point
4. Implementation overview (5 min): Timeline, onboarding, what to expect
5. Pricing/ROI (5 min): Tie price to quantified value from discovery
6. Q&A (5 min)
7. Next steps (2 min): Proposal, trial, stakeholder meeting?
For each demo section: What to show, what to say, what to ask
Output: Full demo script with timing and talking points.
Note: Never demo features the prospect didn't express interest in — demo only to pain points.

Objection Handling & Closing

6. Objection Response Library

Role: Sales coach
Task: Create objection responses for [product] sales.
Product: [describe, pricing, key differentiators]
Common objections (create 3 response variations each):
1. "Too expensive" — value reframing, ROI calc, payment options
2. "Need to think about it" — what's the real concern? timeline?
3. "Need to talk to [boss/spouse/partner]" — who else is involved? can they join?
4. "Already using [competitor]" — what's working? what's not? differentiation
5. "Not the right time" — what would make it the right time? what's the cost of waiting?
6. "Send me some info" — qualify interest, specific info vs. brush-off
7. "Your competitor is cheaper" — value vs. price, what they get for the difference
8. "We were burned before" — acknowledge, differentiate, offer guarantee/trial
For each objection:
- Root cause (what they really mean)
- 3 response scripts (empathetic / data-driven / question-based)
- When to use each variation
- What NOT to say
Output: Objection handling playbook, organized by objection type.

7. Follow-Up Sequence After No Response

Role: Sales representative
Task: Write a follow-up sequence for [prospect] who went silent after [stage].
Context: Went silent after [demo / proposal / initial meeting]
Product: [describe]
Value prop reminder: [key benefit from discovery call]
Sequence (spaced over 3 weeks):
Touch 1 (Day 3): Value-add follow-up — share relevant resource + "did this help?"
Touch 2 (Day 7): Question follow-up — "What questions came up since we last talked?"
Touch 3 (Day 12): New angle — share a relevant case study or result
Touch 4 (Day 17): Peer approach — "I noticed [competitor/peer] just [achievement] — want to see how?"
Touch 5 (Day 22): Breakup — "I don't want to keep bothering you. Should I close this out?"
For each: Channel (email/phone/LinkedIn), full message text, expected response rate
Output: 5-touch re-engagement sequence ready to execute.
Tone: Helpful not desperate. Each touch adds value, not just "checking in."

8. Closing Techniques by Scenario

Role: Sales closing coach
Task: Create closing approaches for [X] sales scenarios.
Scenarios:
1. Hot lead ready to buy — assumptive close + simple next steps
2. Positive but hesitant — summary close (recap value + cost of inaction)
3. Needs approval from others — arm champion close (give them what they need to sell internally)
4. Price objection at close — options close (offer tiered pricing or payment plan)
5. Competitor comparison at close — contrast close (side-by-side comparison + decision framework)
6. Long deliberation — urgency close (genuine reason to act now — price increase, limited capacity, etc.)
For each scenario:
1. How to recognize it (signals the prospect sends)
2. Script (exact words to use)
3. What happens if they say yes (next steps within 24 hours)
4. What happens if they say no or "maybe" (fallback)
5. What NOT to do (common mistakes at this stage)
Output: 6 closing scenarios with scripts and follow-through plans.

Sales Operations

9. Weekly Sales Activity Report

Role: Sales rep
Task: Create a weekly sales activity report.
Metrics:
- Calls made: [X] (connects: [X] → [X]% connect rate)
- Emails sent: [X] (opens: [X]% — replies: [X]%)
- Demos booked: [X] (from calls: [X], from emails: [X], from referrals: [X])
- Demos completed: [X]
- Proposals sent: [X]
- Deals closed: [X] (value: $[X])
- Pipeline added: $[X] (new opportunities)
Analysis:
1. What's working? (which channel/source produces best results?)
2. What's not? (where are you stuck — calls not connecting, demos not converting?)
3. Top 3 deals this week (company, stage, next step, expected close)
4. Stuck deals (what needs help — manager coaching needed?)
5. Next week plan (top 3 priorities + activity targets)
Output: Weekly report for sales manager review.
Format: Numbers table + narrative analysis + asks for help.

10. Account Research Summary

Role: Sales research analyst
Task: Create an account research summary for [prospect company].
Company: [name, industry, size, HQ location]
Research sources: [LinkedIn, company website, news, annual report, 10-K if public]
Summary sections:
1. Company overview (what they do, how big, key products/services)
2. Recent news/triggers (funding, leadership change, product launch, earnings, expansion)
3. Organizational structure (who's the decision-maker for our product? reporting structure?)
4. Technology stack (what tools do they use? does ours integrate?)
5. Competitor relationships (do they use a competitor? which one? since when?)
6. Pain point hypotheses (based on industry/size/recent news — what challenges might they face?)
7. Buying signals (what events suggest they're in-market for our solution?)
8. Outreach recommendations (best channel, timing, angle, message)
Output: 1-2 page account research brief for sales rep to use in outreach.

11. Sales Proposal Outline

Role: Sales proposal writer
Task: Create a proposal outline for [product] to [prospect].
Product: [describe]
Prospect: [company, key contact, pain points from discovery]
Proposal structure:
1. Executive summary (1 page — situation, solution, value, investment)
2. Current state (their pain points in their words from discovery call)
3. Proposed solution (what we recommend and why — tied to each pain point)
4. Implementation plan (timeline, phases, what they need to do, what we handle)
5. Investment summary (pricing table — options if tiered, payment terms)
6. ROI analysis (payback period, 12-month savings, 3-year value)
7. About us (1 page max — credibility, relevant case studies, team)
8. Terms and conditions (contract length, SLA, cancellation, guarantees)
9. Next steps (what happens after signing, timeline to go-live)
10. Appendix (detailed feature lists, case studies, references)
For each section: Key content, length, what to include
Output: Full proposal outline ready for document creation.

12. Sales Forecast Model

Role: Sales operations analyst
Task: Create a monthly sales forecast for [rep/team].
Current pipeline: [list deals — company, stage, value, expected close month, probability]
Forecast methodology: Weighted pipeline (value × probability by stage)
Stage probabilities:
- Discovery: 10%
- Demo: 25%
- Proposal: 50%
- Negotiation: 75%
- Closing: 90%
For each deal:
1. Company and deal value
2. Current stage
3. Weighted value (value × probability)
4. Expected close month
5. Next step and date
6. Risk factors (what could delay/kill)
7. Confidence level (High/Med/Low)
Monthly forecast:
- This month: $[X] weighted
- Next month: $[X] weighted
- Month 3: $[X] weighted
Gap analysis: What's needed to hit quota? (X more deals at Y stage)
Output: Sales forecast with pipeline detail and gap analysis.
Format: Pipeline table + monthly summary + recommendations.

Best Practices

1. Always define the role and context — professional prompts produce professional output

2. Specify output format — table, checklist, narrative, or structured document

3. Include industry-specific parameters — regulations, market conditions, jurisdiction

4. Set constraints — what to avoid, word limits, prohibited content

5. Always human-review — AI output is a first draft, not a final product.

Related: Check out our guides on AI prompts for account executives and ChatGPT prompts for sales managers.

Disclaimer: These prompts are tools for sales professionals, not guarantees of results. AI output must be reviewed and customized for your specific product and market. Skillent and Valles Global, LLC are not responsible for sales outcomes.

190,000+ professional AI prompts for every role and industry.

Get Skillent Pro — $9/month
Skillent

Professional AI prompts and skills for every industry.

Skillent is a service of Valles Global, LLC. AI output should be reviewed by qualified professionals.

X in gh Md

Product

  • AI Skills + Prompts Library
  • Pricing
  • Free Tools
  • How To Use
  • Blog

Industries

  • Finance
  • Legal
  • HR
  • Marketing
  • Healthcare
  • Real Estate
  • Operations
  • Tech

Legal

  • Privacy
  • Terms
  • Cookies
  • Refunds
© 2026 Valles Global, LLC. All rights reserved.