Sales ChatGPT Prompts
Sales strategy, prospecting, and customer engagement prompts
Design a Sales Presentation
Design a 12-slide sales presentation for {product} aimed at {buyer_role} at {company_type}. Open on the prospect's problem, not your company. Slide plan: the shift in their market, the cost of the status quo in their numbers, the specific gap that creates, your approach in one sentence, how it works in three steps, proof from a comparable customer with a measured result, what changes in their first 90 days, pricing anchored to the cost of inaction, implementation timeline, risk reversal, and a single explicit ask. For each slide give the headline as a full assertion (not a label), the one visual that carries it, and the sentence the presenter says out loud. Cap body text at 20 words per slide.
Create a Discovery Call Question Framework
Design a 30-minute discovery call framework for selling {product} to {buyer_role}. Structure it in five blocks with timings: rapport and agenda (2 min), current-state mapping (8 min), problem quantification (8 min), decision process and buying committee (7 min), and mutual next steps (5 min). Give 4–6 open questions per block, ordered so each one earns the right to ask the next. Include the specific follow-up probe for every question, the numbers a rep must leave the call holding (cost of the current process, timeline, budget owner), and three disqualification signals that should end the call early rather than book a second one.
Write Follow-Up Email Templates for Every Deal Stage
Write follow-up email templates for {product} covering seven moments: after a first discovery call, after a demo, after sending pricing, after a champion goes quiet for 7 days, after a verbal yes with no signature, after a loss, and a 90-day re-engagement. Each under 80 words, each adding new information rather than 'just checking in' — a relevant benchmark, a customer story, an answer to a question they did not ask yet, or a deadline that is genuinely real. Give each a subject line, the ideal send delay, and the one signal that means you should call instead of email.
Develop a Closing Strategy for Enterprise Deals
Build a closing strategy for a {deal_size} enterprise deal for {product} with a buying committee of {committee_size}. Map every role — economic buyer, champion, technical evaluator, legal, procurement, security review — with what each one needs to say yes and what each is personally risking. Produce a mutual action plan working backwards from the target signature date with owners and dates for security review, legal redlines, procurement onboarding and budget approval. Add: how to arm a champion to sell internally when you are not in the room, the three questions that reveal whether your champion actually has power, and the concessions to hold back for the final week rather than spending early.
Create a Value Proposition Statement
Write value proposition statements for {product} serving {target_customer}. Produce five variants, each under 25 words, each built on a different axis: outcome achieved, time or cost saved, risk removed, status gained, and work eliminated. For every variant state the specific customer belief it depends on, and the competitor claim it differentiates against. Then stress-test all five: mark any that a direct competitor could copy word-for-word onto their own homepage, and rewrite those until they cannot. Finish with the single strongest variant plus a 50-word supporting paragraph for the hero section.
Write a Business Proposal Template
Write a business proposal template for delivering {service} to {client_type} at {price_range}. Order it the way a buyer reads, not the way a vendor writes: their situation in their own words first, the measurable outcome being bought, scope with explicit inclusions AND exclusions, delivery phases with dates and named owners, what you need from them to hit those dates, investment presented as three tiered options, terms, and a signature block. Add a one-page executive summary that stands alone if nobody reads further. Flag every place a vague word ('as needed', 'ongoing support', 'best effort') would later cause a scope dispute.
Design a Sales Onboarding Program for New Reps
Design a 30/60/90-day onboarding program for a new {role} selling {product}. For each phase define: what they must be able to do by the end (demonstrated, not attended), the certification that proves it, the shadowing and reverse-shadowing schedule, and the ramped quota. Week 1–2 covers product and ICP with a recorded pitch certification; week 3–4 covers discovery with two live calls under supervision; days 31–60 add demo certification and first self-sourced pipeline; days 61–90 target first closed deal. List the ten artefacts they need on day one, the named owner for each phase, and the leading indicators that predict a rep will miss ramp so a manager can intervene in week 4 rather than month 6.
Create a Sales Playbook
Create a sales playbook for selling {product} into {target_market}. Include: an ideal customer profile with disqualifying criteria stated as plainly as qualifying ones, the three buyer personas and what each actually cares about, a stage-by-stage pipeline definition where every stage has an exit criterion the buyer must demonstrate (not something the rep asserts), qualification questions per stage, competitive battlecards for the top three alternatives including 'do nothing', pricing and discount guardrails, and the five metrics a manager inspects weekly. Write it so a new rep can run a first call from it in week two.
Write a Cold Email Sequence for B2B SaaS Outreach
Write a five-email cold outreach sequence selling {product} to {job_title} at {company_size} B2B SaaS companies. Email 1: a single observed trigger (funding, hiring, tech-stack change) and one question — no pitch. Email 2: a one-sentence customer outcome with a number. Email 3: a short, specific teardown of a problem they likely have. Email 4: social proof from a named-industry peer. Email 5: a permission-to-close break-up. Keep every email under 90 words, subject lines under 6 words, one CTA each, no adjectives like 'revolutionary' or 'game-changing', and write at an 8th-grade reading level. Output as a table: send day, subject, body, the behavioural signal that should stop the sequence.
Develop Objection Handling Scripts
Build objection-handling scripts for a {product} sold at {price_point} to {buyer_role}. Cover the eight objections that actually stall deals: too expensive, no budget this quarter, already using a competitor, need to ask my boss, send me information, not a priority right now, worried about migration effort, and unsure it will work for our use case. For each, give: the real concern hiding under the stated words, one clarifying question that surfaces it, a 2–3 sentence response that reframes rather than argues, and a concrete next step. Add a short section on which objections signal genuine disqualification so reps stop chasing dead deals.