Choose by the output you need to make

ChatGPT Prompts for Sales Reps

SDRs and account executives writing outreach, discovery, follow-up, and proposal materials.

Where ChatGPT helps this role

Write a cold email from a verified account trigger, buyer role, proof point, and one low-friction ask.
Prepare discovery questions that separate pain, impact, buying path, timeline, and disqualification signals.
Turn call notes into a recap with buyer language, owners, dates, objections, and the agreed next step.
Write a proposal outline that keeps value proof, scope, assumptions, risks, and manager review visible.
Repair outreach that sounds personalized but relies on guessed pain or inflated familiarity.
Create a reusable sales prompt only after the account trigger, deal stage, and buyer-approved language are named.

Main Risks

Guessed personalization can break trust faster than generic wording, so the prompt must label what is verified and what is only a hypothesis.
A polished sales answer can hide missing buyer language, deal stage, or next commitment.
Proposal and follow-up prompts should not invent ROI, urgency, stakeholder agreement, or procurement facts.
Private account details should be summarized or removed before a prompt becomes reusable.

Recommended Workflow

Start with the real buyer situation: account trigger, role, call note, objection, or proposal request.
Choose the task page by the next sales action: outreach, discovery, objection response, recap, or proposal.
Ask ChatGPT to separate verified facts, sales hypotheses, missing proof, and the next human-approved ask.
Run a review prompt against buyer language, proof, tone, and whether the next step is supported by the notes.
Save only the reusable pattern after removing account names, private details, and one-time deal facts.

Choose the first task by situation

Start with Write cold emails when the user has source notes but does not yet know the right output structure, then move to Write LinkedIn outreach or Prepare discovery questions only after the audience and review owner are clear.

Choose by situation

Choose Write cold emails when the main problem is shaping raw context into something a prospect, buyer committee, or sales manager can inspect.
Choose Write LinkedIn outreach when the user already has a first version and needs the next artifact in the same sales reps loop.
Choose Prepare discovery questions when the risk is quality control, review consistency, or a clearer handoff to another person.
Open the role guide when the user cannot name the task yet and needs to decide whether to create, revise, review, or sanitize context first.

Avoid starting with

Do not start from a broad role prompt when the user already knows the concrete task.
Do not start from a writing prompt when the missing piece is source material or reviewer approval.
Do not reuse a sales reps prompt across unrelated tasks without changing inputs, constraints, and review checks.

Sales Reps pages are organized by the decision a person is trying to make, not by a long list of clever prompt phrases. The role page should help the user pick the first useful task, then the task page should carry the details: source material, variable fill, example, stronger prompt, and human review boundary.

Pick the workflow by decision

Write cold emails

Use when the next decision is the shape, review path, or reuse rule for a cold email.

Write cold emails needs account trigger, prospect role, pain hypothesis, proof, and requested action; its review lens is cold email quality, account trigger and pain hypothesis, and recipient-safe next step, not a generic writing pass.

Write LinkedIn outreach

Use when the next decision is the shape, review path, or reuse rule for a LinkedIn outreach message.

Write LinkedIn outreach needs profile context, shared relevance, reason for contact, and low-friction ask; its review lens is LinkedIn outreach message quality, profile relevance and mutual context, and recipient-safe next step, not a generic writing pass.

Prepare discovery questions

Use when the next decision is the shape, review path, or reuse rule for discovery questions.

Prepare discovery questions needs buyer role, suspected pain, account trigger, deal stage, product fit, decision path, and learning goal; its review lens is discovery questions quality, pain qualification and budget path, and buyer-specific next step, not a generic writing pass.

Handle objections

Use when the next decision is the shape, review path, or reuse rule for an objection-handling response.

Handle objections needs objection wording, buyer context, proof, tradeoff, and next commitment; its review lens is objection-handling response quality, objection type and empathy, and buyer-specific next step, not a generic writing pass.

Send follow-up emails

Use when the next decision is the shape, review path, or reuse rule for a follow-up email.

Send follow-up emails needs sales call recap, buyer objection, agreed action, deal stage, and next-meeting goal; its review lens is follow-up email quality, buyer commitment and objection recap, and recipient-safe next step, not a generic writing pass.

Summarize account research

Use when the next decision is the shape, review path, or reuse rule for an account research summary.

Summarize account research needs company page, recent signals, role map, pain hypothesis, and source links; its review lens is account research summary quality, company signals and role map, and learning-integrity check, not a generic writing pass.

Write call summaries

Use when the next decision is the shape, review path, or reuse rule for a call summary.

Write call summaries needs call notes, decisions, objections, owners, dates, and follow-up commitments; its review lens is call summary quality, decisions and objections, and buyer-specific next step, not a generic writing pass.

Write proposals

Use when the next decision is the shape, review path, or reuse rule for a proposal outline.

Write proposals needs buyer problem, decision criteria, deal stage, proof, scope, assumptions, pricing context, and next-step owner; its review lens is proposal outline quality, buyer problem and commercial proof, and scope and value-risk check, not a generic writing pass.

Open a prompt workbench

Review-first run

Write Cold Emails: use account trigger and prospect role

A role-specific page for cold emails with a recommended prompt, filled scenario, output grader, repair prompt, and related workflows. cold emails catches the failure point where outreach can look personalized while relying on a guessed trigger, because that is where polished answers usually fail.

Turn account trigger, prospect role, pain hypothesis, proof, and requested action into a cold email for a prospect, buyer committee, or sales manager.

Bring first: Need subject lines and one 90-word email. Use trigger from job post, mention scheduling complexity, no fake personalization. Reviewer approval for write cold emails has to compare the first answer with the supplied note. A practical prompt should keep the missing details visible. Start write cold emails from the rough request before shaping a cold email. A usable write cold emails input includes what is known, what is uncertain, and what the reviewer must verify.
Reject if: Ask for a correction if it ignores the original notes and answers from general knowledge instead.

Write LinkedIn outreach Prepare discovery questions Handle objections

Ready-to-run path

Write Linkedin Outreach: avoid customer data minimal and verify account

Build a LinkedIn outreach message from profile context, shared relevance, reason for contact, and low-friction ask, then inspect true experience, measurable proof, and target role fit and the handoff before it reaches a prospect, buyer committee, or sales manager. LinkedIn outreach stays close to a revenue workflow where buyer context and next commitment matter more than polish, which keeps ChatGPT from drifting into generic advice.

Turn profile context, shared relevance, reason for contact, and low-friction ask into a LinkedIn outreach message for a prospect, buyer committee, or sales manager.

Bring first: Need connection note under 250 characters and follow-up message. Mention public post, ask about cleanup process, no fake shared contacts. connection note with relevance proof needs the source note, output shape, and review owner in the same pass. The answer should carry the user's boundary into the final sections. a LinkedIn outreach message should use the note as its source. Before sales reps run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
Reject if: Hold the answer if it blurs what is known, what is assumed, and what still needs evidence.

Write cold emails Prepare discovery questions Handle objections

Ready-to-run path

Prepare Discovery Questions: turn notes into discovery questions

A working prompt pack for sales reps who need discovery questions backed by real notes, clear limits, and reviewable output. discovery questions should only be saved after someone can replace polished filler with source-backed lines inside discovery questions.

Turn buyer role, suspected pain, account trigger, deal stage, product fit, decision path, and learning goal into discovery questions for a prospect, buyer committee, or sales manager.

Bring first: Need questions by theme: current process, incidents, budget, stakeholders, timeline, and disqualification. Keep conversational. a prospect, buyer committee, or sales manager can be misled by polished wording, so the reviewer check needs to stay visible. The copied prompt should keep the rough-note evidence intact. Treat prepare discovery questions as first-pass evidence for discovery questions. Prepare Discovery Questions works better when the context is in named fields, because each variable can be checked before copying.
Reject if: Discard the answer if it cannot trace which details came from the source and which details were inferred.

Write cold emails Write LinkedIn outreach Handle objections

Review-first run

Handle Objections: use objection wording and buyer context

Move from a rough objections request to an objection-handling response formatted as clear sections, bullets, and a review checklist, using runnable prompts plus reject-if and repair rules. objections catches the failure point where objection replies can argue too early instead of separating empathy, proof, and next ask, because that is where polished answers usually fail.

Turn objection wording, buyer context, proof, tradeoff, and next commitment into an objection-handling response for a prospect, buyer committee, or sales manager.

Bring first: Need response options for implementation concern, discovery follow-ups, proof points to request, and when to pause the deal. Reviewer approval for handle objections has to compare the first answer with the supplied note. A useful version should keep the task boundary visible. Start handle objections from the rough request before shaping an objection-handling response. A usable handle objections input includes what is known, what is uncertain, and what the reviewer must verify.
Reject if: Ask for a correction if it ignores the original notes and answers from general knowledge instead.

Write cold emails Write LinkedIn outreach Prepare discovery questions

Ready-to-run path

Send Follow-up Emails: prep prospect, buyer committee, or sales manager handoff

This follow-up emails workflow helps sales reps copy the right prompt, inspect the answer, and hand off only what the source supports. follow-up emails examples stay close to a revenue workflow where buyer context and next commitment matter more than polish, so the prompt has a real work setting.

Turn sales call recap, buyer objection, agreed action, deal stage, and next-meeting goal into a follow-up email for a prospect, buyer committee, or sales manager.

Bring first: Need follow-up email with recap, two pains, promised case study, next meeting ask, and no pressure language. follow-up note with promised item and timing would be weak without the source details, so the evidence has to stay attached. The saved version should keep the one-time details editable. Sales Reps should use the note as the base for a follow-up email. Before sales reps run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
Reject if: Do not use the answer if it hides unsupported claims about source notes, examples, constraints, and reviewer judgment or treats uncertainty as fact.

Write cold emails Write LinkedIn outreach Prepare discovery questions

Ready-to-run path

Summarize Account Research: use company page and recent signals

Use the account research workbench to move from company page, recent signals, role map, pain hypothesis, and source links to a structured analysis table with claims, evidence, gaps, and recommended next step with assumptions and reviewer checks exposed. account research catches the failure point where account research for sales can sound useful while hiding the missing detail a reviewer needs, because that is where polished answers usually fail.

Turn company page, recent signals, role map, pain hypothesis, and source links into an account research summary for a prospect, buyer committee, or sales manager.

Bring first: Need account brief with public triggers, possible hypotheses, questions to validate, stakeholders, and risks. Label assumptions clearly. Reviewer approval for summarize account research has to compare the first answer with the supplied note. The output should carry the user's limits into every section. Start summarize account research from the rough request before shaping an account research summary. A usable summarize account research input includes what is known, what is uncertain, and what the reviewer must verify.
Reject if: Ask for a correction if it ignores the original notes and answers from general knowledge instead.

Write cold emails Write LinkedIn outreach Prepare discovery questions

Review-first run

Write Call Summaries: use call notes and decisions

Move from a rough call summaries request to a call summary formatted as clear sections, bullets, and a review checklist, using runnable prompts plus reject-if and repair rules. call summaries catches the failure point where call summaries can hide owners, dates, objections, or next-step commitments, because that is where polished answers usually fail.

Turn call notes, decisions, objections, owners, dates, and follow-up commitments into a call summary for a prospect, buyer committee, or sales manager.

Bring first: Need summary with pain, current process, stakeholders, objections, success criteria, next steps, owner, and follow-up email bullets. Reviewer approval for write call summaries has to compare the first answer with the supplied note. The response should keep the actual request visible through the edit. Start write call summaries from the rough request before shaping a call summary. A usable write call summaries input includes what is known, what is uncertain, and what the reviewer must verify.
Reject if: Ask for a correction if it ignores the original notes and answers from general knowledge instead.

Write cold emails Write LinkedIn outreach Prepare discovery questions

Ready-to-run path

Write Proposals: turn notes into proposal outline

A working prompt pack for sales reps who need a proposal outline backed by real notes, clear limits, and reviewable output. proposals should only be saved after someone can replace polished filler with source-backed lines inside a proposal outline.

Turn buyer problem, decision criteria, deal stage, proof, scope, assumptions, pricing context, and next-step owner into a proposal outline for a prospect, buyer committee, or sales manager.

Bring first: Need proposal outline, executive summary, scope, timeline, proof, assumptions, risks, and next step. No made-up ROI. a prospect, buyer committee, or sales manager can be misled by polished wording, so the reviewer check needs to stay visible. The copied prompt should keep the rough-note evidence intact. Treat write proposals as first-pass evidence for a proposal outline. Write Proposals works better when the context is in named fields, because each variable can be checked before copying.
Reject if: Discard the answer if it cannot trace which details came from the source and which details were inferred.

Write cold emails Write LinkedIn outreach Prepare discovery questions

Where to go next

Write cold emailsWrite cold emails fits when the next decision is the shape, review path, or reuse rule for a cold email. Keep it separate because write cold emails needs account trigger, prospect role, pain hypothesis, proof, and requested action; its review lens is cold email quality, account trigger and pain hypothesis, and recipient-safe next step, not a generic writing pass.Write LinkedIn outreachWrite LinkedIn outreach fits when the next decision is the shape, review path, or reuse rule for a LinkedIn outreach message. Keep it separate because write LinkedIn outreach needs profile context, shared relevance, reason for contact, and low-friction ask; its review lens is LinkedIn outreach message quality, profile relevance and mutual context, and recipient-safe next step, not a generic writing pass.Prepare discovery questionsPrepare discovery questions fits when the next decision is the shape, review path, or reuse rule for discovery questions. Keep it separate because prepare discovery questions needs buyer role, suspected pain, account trigger, deal stage, product fit, decision path, and learning goal; its review lens is discovery questions quality, pain qualification and budget path, and buyer-specific next step, not a generic writing pass.Handle objectionsHandle objections fits when the next decision is the shape, review path, or reuse rule for an objection-handling response. Keep it separate because handle objections needs objection wording, buyer context, proof, tradeoff, and next commitment; its review lens is objection-handling response quality, objection type and empathy, and buyer-specific next step, not a generic writing pass.Send follow-up emailsSend follow-up emails fits when the next decision is the shape, review path, or reuse rule for a follow-up email. Keep it separate because send follow-up emails needs sales call recap, buyer objection, agreed action, deal stage, and next-meeting goal; its review lens is follow-up email quality, buyer commitment and objection recap, and recipient-safe next step, not a generic writing pass.Summarize account researchSummarize account research fits when the next decision is the shape, review path, or reuse rule for an account research summary. Keep it separate because summarize account research needs company page, recent signals, role map, pain hypothesis, and source links; its review lens is account research summary quality, company signals and role map, and learning-integrity check, not a generic writing pass.How to Use ChatGPT for Sales RepsUse this when the user needs a role-level workflow before opening a single task page.