ChatGPT Prompts for Sales
AI is most useful in sales before the conversation happens — in prep, in drafting, and in analysis. These prompts are built around the real workflow of a B2B sales professional: preparing for discovery, handling the objections that kill deals, following up without being annoying, and reviewing pipeline with clear eyes. Each one includes the context that separates a useful output from a generic one.
Example Prompts
Discovery call questions for a specific ICP
You are a senior enterprise sales coach who specializes in SaaS discovery calls. Help me prepare for a discovery call. My product: a data observability platform that helps data engineering teams detect, triage, and resolve data quality issues before they reach business stakeholders. Prospect profile: - Company: a Series C fintech company (~400 employees) - Contact: Director of Data Engineering - Context: they recently had a public data incident — a dashboard showed incorrect revenue figures during a board meeting - Their current stack likely includes: dbt, Snowflake, and possibly Fivetran - They have not purchased a dedicated data observability tool before (based on LinkedIn job postings that ask for manual QA skills) Generate a discovery call question set structured as follows: Situation questions (3): to understand their current environment without wasting time on things I already know Problem questions (4): to surface the pain behind the incident and what it's costing them — in money, reputation, and team time Implication questions (3): to help them articulate the downstream impact of unresolved data quality issues Need-payoff questions (3): to let them describe what a solution looks like in their own words After the questions, give me 2 "landmines to avoid" — common mistakes salespeople make in discovery calls with data engineering leaders.
Objection handling: 'it's too expensive'
You are a sales trainer who specializes in helping B2B SaaS reps handle price objections without discounting. Context for my situation: - Product: a sales enablement platform ($18,000/year for teams of 5–20 reps) - The prospect is a VP of Sales at a 60-person B2B company - They said: "I think the price is a bit high for where we are right now" - Their current setup: reps use a mix of Google Docs and Notion for playbooks, no formal onboarding tool - Deal stage: after a demo, they expressed interest but this was in the follow-up email after - What I know about their situation: they hired 4 new reps in the last 90 days and the VP mentioned onboarding speed as a priority Help me build a response to this objection. Give me: 1. The "acknowledge and reframe" response (2–3 sentences): validate their concern, then shift the frame from cost to cost of the status quo — based on what I know about their situation. 2. A discovery question to ask before responding: sometimes "it's too expensive" is not really about price. What question would reveal what's really going on? 3. A value-building bridge (3–4 sentences): connect the specific pain they mentioned (onboarding 4 new reps) to a concrete outcome our platform delivers — with an estimate of the ROI if I can make one. 4. The "trial balloon" close: a low-pressure way to test whether price is the real blocker or whether there's something else. Do not suggest discounting as a strategy.
Follow-up email after a demo with no response
You are a B2B sales email specialist who helps reps stay top of mind without being annoying. Situation: - I gave a product demo 8 days ago to a Director of Operations at a logistics company - The demo went well — they asked specific technical questions and the champion (an ops manager on the call) was engaged - I sent a recap email the day after the demo with next steps — no response - I sent a brief check-in 4 days later — no response - I know from LinkedIn that the director has been traveling to a conference this week This is my third touchpoint. I need to write a follow-up email that: - Acknowledges I've been in touch a couple of times without sounding passive-aggressive about it - Doesn't ask "did you get my last email?" - Adds a small amount of value (suggest an approach, not just a link) - Makes it easy for them to reply with a quick status update or ask me to follow up later - Is under 100 words I sell a warehouse operations management platform. One thing I know from the demo: they were manually reconciling shift schedules in spreadsheets, which takes their ops team about 6–8 hours per week. Write the email with a subject line. The subject line should not be "Following up" or a variation of it.
Proposal executive summary
You are a proposal writer who specializes in executive-level B2B sales documents. I need you to write the executive summary section of a proposal. Background: - My company: Meridian Analytics — a data analytics consulting firm - The client: a regional hospital network with 8 hospitals and ~6,000 employees - The project: a 6-month engagement to redesign their patient flow reporting infrastructure. Currently their clinical operations team gets reports that are 48 hours delayed, built in a legacy tool that requires IT involvement for every new query. - What we're proposing: migrate their reporting to a modern BI stack (Snowflake + Looker), build 12 standardized dashboards for clinical ops, and train their internal team to be self-sufficient - Contract value: $340,000 - Decision-makers who will read this: CFO, VP of Clinical Operations, and Chief Information Officer - Their primary concern (from discovery): the CFO wants to see ROI, the VP of Clinical Ops wants faster access to data, the CIO wants to know the migration won't disrupt current systems Write an executive summary (300–400 words) that: - Opens with their problem, not our company introduction - Speaks to all three stakeholders' concerns without being a list - States our recommendation clearly (what we're proposing and why this approach) - Includes one specific, tangible outcome they can expect (use a number or time frame) - Closes with a sentence that gives them confidence in our ability to deliver — without being boastful Write in a professional, direct tone. No buzzwords. This will be read by a CFO.
Weekly pipeline review analysis
You are a sales operations analyst helping a sales manager run a structured weekly pipeline review. I will give you my current pipeline data. Your job is to help me identify where to focus my team's attention this week and what actions to prioritize. Pipeline context: - Team: 4 AEs, each with 8–15 active opportunities - Sales cycle: average 45 days for SMB (under $20k ACV), 90 days for mid-market - Quota: $280,000 per rep per quarter, current quarter ends in 6 weeks - CRM stage definitions: Qualified → Discovery → Demo Completed → Proposal Sent → Negotiation → Closed Won/Lost This week's pipeline summary: - 6 deals in Negotiation (combined value: $420k) — 3 have been in this stage for 30+ days with no movement - 14 deals in "Demo Completed" — 5 were demoed more than 3 weeks ago with no proposal sent yet - 2 deals in "Proposal Sent" stage have seen the proposal opened (via tracking) 5+ times but no response - 1 deal ($85k) has a verbal yes but the legal review has stalled for 2 weeks Based on this data, give me: 1. A "this week's top 3 priorities" list with the specific action for each 2. A "stalled deal diagnosis" for the 3 Negotiation deals stuck over 30 days — what's likely happening and what's the right move for each scenario 3. One process observation: a pattern in this pipeline that suggests a systemic issue I should address at the team level, not the deal level
Tips for Sales Prompts
The most useful thing you can give a sales prompt is specific context about the prospect — not just their job title, but what you already know about their pain, what they've said, and what stage the deal is at. AI-generated sales content gets generic fast without prospect context. If you mention the specific incident that triggered their search (like a board meeting data error or a failed audit), the model will write to that situation rather than a hypothetical one.
For objection handling, resist asking the model to "respond to the objection." Instead, ask it to help you understand what the objection might really mean, then develop a response. Price objections often aren't about price — they're about unclear ROI, internal politics, or timing. Prompting the model to surface the underlying concern before drafting a response leads to more useful outputs.
Pipeline analysis prompts work best when you give structured data, not a narrative description. List your deals, stages, ages, and dollar values in a consistent format — even rough data in a table or numbered list gives the model enough to identify patterns and prioritize recommendations. The more structured your input, the more structured and actionable the analysis.
Why use PromptBro for sales prompts?
Sales prompts live or die on prospect context — and context is exactly what PromptBro's voice-first flow is designed to capture. Speak the deal situation, the prospect's pain, and the goal of the output in 60 seconds. PromptBro structures it into a prompt that covers role, context, constraints, and format so you get a first draft that's actually specific to your deal, not a template your prospect could spot from a mile away.
Try PromptBro free — build your first prompt in 60 seconds →