Prompts / Sales & Business Development

ChatGPT prompts for sales development

This prompt creates a prospect-specific sales development brief and outreach sequence grounded in evidence you provide. Use it when you need a useful next conversation, not generic personalization or inflated claims.

PromptOpen ChatGPTOpen Claude
Act as a sales development strategist. Build a prospect-specific outreach plan that earns a relevant next step without inventing research, mutual connections, results, customer stories, or buying intent.

Inputs:
[OUR OFFER AND PROOF]
[IDEAL CUSTOMER AND USE CASE]
[PROSPECT AND ACCOUNT RESEARCH]
[BUYING COMMITTEE]
[OUTREACH CONSTRAINTS]
[CURRENT SALES CONTEXT]

Start with an account brief. Separate verified facts from hypotheses. Identify the prospect's likely business priority, the operational consequence of leaving it unchanged, and the narrowest relevant capability in our offer. If evidence is thin, write a research gap instead of a personalized assertion.

Then produce:
1. A qualification view using a practical framework: business problem, potential impact, current approach, stakeholders, timing signal, and disqualifiers. Mark unknowns as discovery questions, not facts.
2. A message map with one primary value hypothesis, two supporting proof points from [OUR OFFER AND PROOF], and three discovery questions. Connect every proof point to a stated prospect problem; do not use a logo list as proof.
3. A five-touch sequence over 12 business days: email 1, LinkedIn connection note, call opener and voicemail, email 2, and breakup/permission-to-close email. Give each touch a distinct purpose. Emails must have a subject line, 70-120 words, one concrete observation or carefully labeled hypothesis, and one low-friction call to action. Avoid "just checking in," false familiarity, exaggerated urgency, and vague claims such as "save time."
4. A 20-minute discovery-call agenda with opening, problem exploration, impact questions, current-process questions, stakeholders, next-step criteria, and a close. Include exact questions but do not script the prospect's answers.
5. Objection preparation for "we already have a vendor," "no priority," and "send information," including an honest response and a question that tests fit.

Before answering, audit every personalized statement against [PROSPECT AND ACCOUNT RESEARCH], and label unsupported statements as hypotheses. Check that every call to action asks for one specific next step. Ask up to 3 clarifying questions only if a required input is missing.

Fill in

PlaceholderWhat to enterExample
[OUR OFFER AND PROOF]Describe your product or service, capabilities, implementation limits, pricing range if usable, and substantiated proof points.CloudCall QA analyzes support calls for coaching; a documented customer case reduced manual call-review time from 12 hours to 4 hours weekly after 60 days; no claim about CSAT improvement.
[IDEAL CUSTOMER AND USE CASE]Describe the target segment, job roles, workflow, trigger events, and problems you solve.Support leaders at 100-500 person SaaS companies reviewing QA samples manually after headcount growth or new support locations.
[PROSPECT AND ACCOUNT RESEARCH]Paste public facts, recent announcements, job posts, earnings notes, website details, or call notes about the account and person.Maya Chen, VP Customer Experience at Arclight HR; company posted three support manager roles and announced expansion into Canada in August; no direct evidence of QA tooling.
[BUYING COMMITTEE]List known or likely decision makers, users, blockers, and their responsibilities.Maya likely owns support outcomes; support operations may own workflow; IT security may review vendors.
[OUTREACH CONSTRAINTS]State channels, cadence rules, brand voice, regulated claims, geography, and any words or offers to avoid.Email and LinkedIn only; no discount language; respectful, direct tone; do not claim access to their call data.
[CURRENT SALES CONTEXT]Describe prior touches, CRM stage, known competitor, existing vendor, meeting goal, and recent prospect responses.No prior contact; goal is a 20-minute discovery call; competitor is unknown.

How to use

  1. Paste only research you can trace to a source or a real call note, then let the prompt distinguish facts from hypotheses.
  2. Read each first sentence aloud and remove anything that assumes the prospect's pain, tools, or authority.
  3. Choose one call to action that fits the evidence level, such as a 20-minute comparison call rather than a product demo.
  4. Follow up with: "Rewrite touch two for a prospect who accepted my connection but did not reply to the first email."

Variations

Account plan

Use this when several stakeholders must be mapped before outreach begins.

Variation
Create an account plan for [ACCOUNT] using [ACCOUNT RESEARCH], [OUR OFFER], [KNOWN STAKEHOLDERS], and [SALES GOAL]. Separate verified facts, reasonable hypotheses, and research gaps. Map economic buyer, champion, users, technical reviewers, blockers, and missing roles; do not state a person has authority without evidence. Provide problem hypotheses, role-specific discovery questions, proof points matched to each role, entry paths, risks, and the next three actions. End with a mutual-action-plan outline only if the account has an active opportunity.

Cold email

Use this for a single researched email rather than a full cadence.

Variation
Write three cold-email options to [PROSPECT NAME AND ROLE] at [ACCOUNT] using [VERIFIED RESEARCH], [OFFER], and [PROOF]. Each option must be 90 words or fewer, contain one accurate observation or a clearly marked hypothesis, explain a role-relevant consequence, and ask for one specific 15- or 20-minute next step. Give each a different angle: operational, financial, and customer impact. Do not invent priorities, mutual contacts, results, or urgency. Add a source note for every personalized claim.

Discovery call

Use this when a meeting is booked and you need a useful conversation plan.

Variation
Prepare a 25-minute discovery call for [PROSPECT], [ACCOUNT], and [OFFER], based on [RESEARCH] and [CURRENT CONTEXT]. Create a timed agenda, opening permission statement, 10 open questions grouped by current process, pain, impact, stakeholders, and timing, plus concise follow-ups. Include disqualifying signals and a next-step decision tree. Do not turn assumptions into claims or prescribe a solution before discovery. End with a call-note template that separates direct quotes, facts, hypotheses, and agreed actions.

Tips

  • Personalization should point to an observable business change and a plausible workflow consequence, not repeat the prospect's biography.
  • A message with one testable problem hypothesis is stronger than a catalog of features; save other capabilities for discovery.
  • Ask about the current process before asking about pain, because process details reveal ownership, workarounds, and the cost of inaction.
  • Keep proof scoped to its actual conditions; a result from one customer is a case example, not a promised outcome.

FAQ

Can AI research prospects for outreach?

It can organize reliable research you provide or retrieve from credible public sources, but it should label uncertainty. Never present a guess about priorities or tools as a known fact.

How many touches should a sales development sequence have?

Five purposeful touches is often enough for an initial sequence when each adds a different reason to respond. Adjust cadence to your market, channel rules, and prior engagement.

Should I ask for a demo in the first cold email?

Ask for the smallest useful next step. If fit is unproven, a short discovery conversation is usually more credible than a full demo request.

Related prompts

All Sales & Business Development prompts →

Get a few prompts like this every week

Something Big is a free AI newsletter read by 70,000+ professionals. About three short emails a week with prompts and tools that work, plus what changed in AI and what to do about it.