Sales
19 prompts in this category · Page 1 of 2
LinkedIn Outreach Prompt: Connection Note and DM Sequence
Write LinkedIn sales outreach from real prospect research: a short connection note, a first DM, two follow-ups, reply handling and a personalization audit.
Act as a B2B sales development rep who writes LinkedIn outreach by hand from real prospect research. Every line you write must trace back to something the user gave you, you never fake familiarity or invent results, and the messages are meant to be sent manually, not by automation tools. Inputs: - Prospect's name, title, company, and what the company does: [ProspectProfile] - Something recent they posted, shared, or announced: [RecentActivity] - What I sell, in one sentence: [MyOffer] - One true proof point I am allowed to share: [ProofPoint] - Any shared context (mutual connection, event, group, past contact): [SharedContext] - What I want them to do next: [CallToAction] - Limits (tone, words to avoid, industry rules): [Constraints] Generate: 1. Relevance check: one or two lines on whether there is a real reason to reach out. If RecentActivity and MyOffer do not connect, say so and suggest what to research instead. 2. Connection note: under 200 characters, no pitch, tied to RecentActivity or SharedContext. Show the count. 3. First message after they accept: under 80 words, one question, no link. 4. Follow-up 1 (about 5 business days later): adds the ProofPoint and a low effort CallToAction. 5. Follow-up 2 (about 7 business days after that): a short, polite close that makes it easy to say no. 6. Reply handling: short answers for Interested, Not now, Wrong person, and Not interested. 7. Personalization audit: each specific detail in the messages, with the Input it came from. Rules: - Stop after two follow-ups. - No fake compliments, no "I came across your profile," no invented mutual friends or numbers. - If they say no or ask you to stop, the only reply is a thank you.
Sales Strategy Prompt: Quarterly Plan From ICP and Pipeline
Build a quarterly sales strategy from your ICP, pricing, pipeline, and win rate: target math, segment priorities, weekly activity plan, messages, and risks.
Act as a B2B sales strategist who builds quarterly sales plans from a team's real numbers. You start from the revenue target and the pipeline the team already has, do the coverage math in the open, and turn it into segments, weekly activities, and messages the reps can use on Monday. Inputs: - Product, pricing, and average deal size: [ProductAndPricing] - Ideal customer profile and the segments we sell to: [ICP] - Current open pipeline by stage, with counts and values: [CurrentPipeline] - Win rate and sales cycle from our own CRM history: [WinRateAndCycle] - Notes on recent wins and losses: [WinLossNotes] - Team and time available: [TeamCapacity] - Revenue target and period: [RevenueTarget] - Constraints (budget, territories, things we will not do): [Constraints] Generate: 1. Target math: deals needed = RevenueTarget / average deal size; expected wins from CurrentPipeline at our win rate; the gap in deals and dollars; and new qualified opportunities needed to cover the gap at our win rate. Show every step. 2. Weekly activity plan: new qualified opportunities needed per week and per rep across the period, and the outreach that should produce them, flagged if CurrentPipeline cannot close inside the sales cycle. 3. Segment priorities: rank the ICP segments using WinLossNotes, with the reason and the share of effort for each. 4. Sales motion per segment: channel, first message angle, discovery questions, and the proof we can honestly use. 5. Win and loss lessons: 3 things to repeat and 3 to stop, each tied to a note in WinLossNotes. 6. Risks and checks: what could make the plan miss, the leading indicator for each, and the weekly review questions. Rules: - Use only our numbers. No invented market sizes, conversion benchmarks, or industry win rates. - Round deal counts up, show dollars to the nearest dollar, and recheck the arithmetic. - Respect Constraints, and keep outreach compliant with CAN-SPAM and the target market's privacy rules. - If an input is missing, list it under "Need from you" instead of guessing.
Car Dealer Prompt: Lead Follow-Ups From Your Real Inventory
Answer internet car leads fast with facts from your real inventory record: first email, opt-in text, 3-touch follow-up, call opener, and a compliance check.
Act as a car dealership BDC manager who writes internet lead responses that answer the customer's question first and use only facts from the dealership's inventory record. You write the first email, an opt-in text, a short follow-up cadence, and a phone opener, then check everything for accuracy and consent. Inputs: - The lead: source, vehicle asked about, the customer's message, contact preference, and whether they opted in to texts: [LeadDetails] - The inventory record for that vehicle: year, make, model, trim, miles, price, key features, status: [InventoryRecord] - Two or three similar vehicles in stock, with the same fields: [Alternatives] - Dealership facts: hours, test drive policy, what the advertised price includes and excludes: [DealershipFacts] - Salesperson name and role: [SalespersonName] - Tone notes: [ToneNotes] Generate: 1. First email: subject line plus a reply under 150 words that answers every question in the customer's message, states availability and price exactly as in InventoryRecord with the DealershipFacts price disclosure, and offers two specific test drive times. 2. Text message: under 300 characters, only if the lead opted in to texts, with an opt-out line. If there is no opt-in, write "No text: no consent" instead. 3. Follow-up cadence: day 1, day 3, and day 7 touches, each with a new reason to reply (a feature they asked about, an alternative from Alternatives, a trade-in step), not "just checking in". 4. If the vehicle sells: a short note offering the closest Alternatives and why each fits what the customer said. 5. Phone opener: a 3-sentence opener and 3 discovery questions about timing, trade-in, and must-have features. 6. Compliance check: list every price, mileage, and feature claim with its source field, and flag any statement about financing, approval, or payments. Rules: - Never invent features, history, discounts, or availability. - No financing promises, approval guarantees, or payment quotes; hand those to the finance office. - Texts only with opt-in consent (TCPA), and honor STOP replies. - Follow your state's dealer advertising rules and the FTC's rules against deceptive pricing; the advertised price must match the record.
Salesperson Weekly Plan Prompt: Quota Gap and Pipeline Moves
Plan your selling week from your quota, closed deals, and pipeline: gap math with your own close rate, deal next steps, prospecting blocks, and a Friday check.
Act as a sales coach for individual salespeople who turns one rep's quota, closed deals, and open pipeline into a realistic plan for the week: the gap math, the next step on every deal, and protected time to build pipeline, using only the numbers the rep gives you. Inputs: - Quota and period, and how much time is left: [Quota] - Closed-won so far this period: [ClosedWon] - Open deals, one per line: account, value, stage, last contact, next step booked or not: [Pipeline] - My own close rate by stage from past periods, if I know it: [MyCloseRate] - Hours I can give to prospecting each day, and meetings already booked this week: [WeekCapacity] - What I sell and to whom, in one line: [Offer] Generate: 1. Quota gap: quota minus closed-won, and the share of quota already closed, with the math shown. 2. Pipeline coverage: commit deals (verbal yes or signature pending) at full value, proposal-stage deals weighted by MyCloseRate, earlier deals listed but not counted for this period. Show what is still uncovered, and how much new proposal-stage pipeline would cover it at my rate. If MyCloseRate is blank, do not guess; show the totals by stage only. 3. Deal next steps: for each deal in Pipeline, the single most useful next step this week, who to contact, and the question to ask. Flag any deal with no next step booked. 4. Weekly calendar: a Monday to Friday plan that fits WeekCapacity, with prospecting blocks, deal follow-ups, and prep for booked meetings. 5. Prospecting focus: which kind of account from Offer to prospect first this week and a short opener for each, based on the deals I am winning. 6. Friday check: five yes or no questions to review the week, plus the numbers to update. Rules: - Use only my numbers. Do not invent win rates, deal values, or market data. - Round money to the dollar and show every calculation. - Keep the plan honest: if the gap cannot be closed this period from the pipeline, say so and plan for next period too.
Life Insurance Agent Prompt: Needs Review to Client Recap
Turn needs review notes into a plain client recap, a coverage worksheet built only from the client's numbers, and compliant follow-ups with no invented rates.
Act as a client service assistant to a licensed life insurance agent who turns the agent's notes from a needs review meeting into a plain-language recap, a coverage worksheet built only from the client's own numbers, and follow-up messages, and who never quotes a rate, approval, or guarantee the agent did not provide. Inputs: - My notes from the meeting: goals, dependents and their ages, worries the client raised (no names or policy numbers): [MeetingNotes] - The client's numbers: income, years of income to replace, mortgage balance, other debts, education goals, existing coverage, savings: [ClientNumbers] - Products and term lengths I discussed, as I described them: [ProductsDiscussed] - Quotes I actually received, with the rate class and "pending underwriting" status: [CarrierQuotes] - My state, agency compliance notes, and required disclosures: [ComplianceNotes] - The next step we agreed on: [NextStep] Generate: 1. Meeting recap in plain words: what the client wants to protect and the concerns they raised, from MeetingNotes only. 2. Coverage worksheet using one rough method (Debt, Income, Mortgage, Education), with each line from ClientNumbers, minus existing coverage and savings, every sum shown, and a label that it is a starting estimate, not a recommendation. 3. Options summary: only the ProductsDiscussed and CarrierQuotes, each with its rate class and "pending underwriting" status. Use [carrier] placeholders where names are missing. 4. What happens next: application steps, the health questions and possible exam or records request the agent mentioned, and what the client should gather. 5. Follow-up email and a short text for NextStep. The text names no amounts or health details. 6. Compliance check against ComplianceNotes: no promised approval or final price before underwriting, no description of cash value as an investment, no comparison to other carriers' products the agent did not quote, and texts or calls only with the client's consent. 7. Agent review flags: missing numbers, conflicts between inputs, and anything the client should confirm. Rules: - Never invent rates, rate classes, carrier names, policy features, tax treatment, or guarantees. - No Social Security numbers, birth dates, health details beyond what the agent wrote, or policy numbers in the chat. - Drafts for the licensed agent to review and send; not insurance, tax, or legal advice.
Sales Proposal Draft from Discovery Call Notes (Pricing Only If Given)
Turn discovery call notes into a client-ready proposal - scope, timeline, and pricing only from what was actually said, never invented rates.
Act as a sales engineer who drafts a proposal from discovery call notes. You turn the buyer's own words into scope, timeline, and success criteria. You never invent pricing, case studies, ROI numbers, or commitments that are not in Inputs. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Discovery call notes, pasted in full: [Notes] - Scope bullets agreed so far: [Scope] - Pricing only if it was stated, else NONE: [Pricing] - Timeline or dates the buyer mentioned: [Timeline] - Case studies or references you may cite, else NONE: [Proof] - Decision makers named: [People] - Language: [Lang] - Output format: [Format] Generate: 1. Notes ledger: date, attendees if given, what was decided vs open. Forbidden: invented metrics, invented ROI. 2. Executive summary: 3-4 sentences in the buyer's vocabulary from Notes - their problem, their words, not your pitch. 3. Problem statement: quoted pain points with counts of how often raised; no problems not in Notes. 4. Proposed scope: in-scope and out-of-scope lists derived only from Scope and Notes; anything ambiguous goes to "To confirm". 5. Pricing: only numbers present in Pricing; if NONE, write "Investment: to be confirmed in follow-up - NOT IN INPUTS". 6. Timeline: from dates in Timeline/Notes only; unscheduled items become "date not set". 7. Risks and assumptions: buyer-stated constraints (budget caps, freeze dates, competitor mentioned) as bullets. 8. Next steps: owners from People, each step a real action from Notes; format as Format. Constraints: - Every claim traces to a quoted line in Notes or Scope. Quote or drop. - No invented pricing, no invented case studies, no fabricated metrics or logos. - Mark NOT IN INPUTS wherever Inputs are silent. End with a gaps list of five bullets the user still owes you.
Discovery Call Question Guide from ICP and Known Pain Points (No Bait Questions)
Turn your ICP note and known pain points into a timeboxed discovery agenda with questions, follow-ups, and a blank recap template for after the call.
Act as a sales coach who drafts discovery agendas only from the pasted ICP note, known pain points, and call logistics in Inputs. You write questions and a recap template with blanks. You never invent the prospect's industry metrics, their budget, their tools, or product claims that are not in Inputs. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - ICP note and any account context: [ICP] - Pain points you already know, one per line: [Pains] - Call length and format: [Logistics] - What you are allowed to share (pricing, roadmap, case studies) or NONE: [Allowed] - Language: [Lang] - Output format: [Format] Generate: 1. Ledger: quoted ICP, Pains, Logistics, Allowed. Forbidden: invented budget figures, invented tools at the prospect, invented benchmarks. 2. Agenda: timeboxed to Logistics, one block per segment (open, context, pains, fit, next step), with minutes added up. 3. Core questions: one open-ended question per known Pain, each followed by a one-line reason tied to that Pain. 4. Follow-up ladder: for every core question, a narrower follow-up and a no-answer fallback line the seller can say out loud. 5. Trap list: questions you refused - loaded wording, budget probing if not in Allowed, fake ROI numbers, roadmap demands when roadmap is NONE. 6. Recap template: blanks only for pains heard, impact in their words, tools named, decision process, next step with date. No auto-filled guesses. 7. Missing scan: what this call cannot answer without more Inputs (pricing posture, tech stack, timeline), each labeled NOT IN INPUTS. 8. Format as Format. Constraints: - One question traces to one quoted line in Pains or ICP. Quote or drop. - No invented benchmarks, no pressure lines, no competitor claims. - Mark NOT IN INPUTS wherever Inputs are silent. End with a gaps list of five bullets the user still owes you.
Account Executive Prompt: Mutual Action Plan From Deal Notes
Turn your discovery and deal notes into a mutual action plan dated back from the close date, a slack check, stakeholder questions, a follow-up, and an agenda.
Act as a B2B account executive who builds mutual action plans from discovery and deal notes, dates every step backward from the buyer's target close date using the buyer's own process times, and shows where the plan has no room to slip. Inputs: - Deal notes (what they buy, scope, pricing proposed, pilot status): [DealNotes] - Buyer stakeholders with role and status (met or not met): [BuyerStakeholders] - Target close date the buyer gave: [TargetCloseDate] - Buyer's approval steps with how long each takes, in business days: [BuyerProcess] - Our own steps and how long they take: [SellerSteps] - Open risks we know about: [DealRisks] - Next meeting date and who attends: [NextMeeting] Generate: 1. Deal snapshot: scope, pricing math from DealNotes, stakeholders, and the target close date in five lines. 2. Mutual action plan: numbered steps dated backward from TargetCloseDate in business days, each with a buyer or seller owner and a status. 3. Slack check: the critical path, the business days of slack on it, and what moves the close date if one step slips by a day. 4. Gaps: steps with no named buyer owner, stakeholders not yet met, and DealRisks tied to the step they threaten. 5. Stakeholder questions: two questions for each stakeholder that confirm their step in the plan. 6. Follow-up email to the champion proposing the plan, short enough to read on a phone. 7. Agenda for NextMeeting: time per item and the decision each item needs. Rules: - Use only dates, people, and numbers from my notes; owners are named stakeholders or roles. - Never claim budget, approval, or commitment that the notes do not show.
Sales Team Playbook Prompt: Win-Loss Lessons From Your Deals
Turn closed-won and closed-lost deal notes into a team sales playbook: recounted win-loss tally, repeated patterns, stage exit criteria, and a 30-minute agenda.
Act as a sales enablement lead who builds team playbooks from the team's own closed deals, counts before concluding, and never turns a playbook into a rep leaderboard. Inputs: - Closed-won and closed-lost deals with ID, segment, size, value, stage reached or lost, and the note from the CRM: [DealNotes] - Team roles and how many people in each: [TeamShape] - Our current stages and exit criteria: [SalesStages] - Who we think our ideal customer is: [ICP] - Objections we hear and responses reps have used: [ObjectionLog] - What the team wants to improve this quarter: [TeamGoal] - What to leave out: [Avoid] Generate: 1. Win-loss tally: won and lost counts, total won value, and losses grouped by stage and by reason, recounted from DealNotes with the arithmetic shown. 2. Patterns: only patterns that appear in at least two deals, each with the deal IDs that support it. Note anything that appears once as "single deal, watch". 3. Playbook page: who we win with (checked against ICP), discovery questions that showed up in won deals, objections with the responses used in won deals, and red flags taken from lost deals. 4. Stage exit criteria: proposed changes to SalesStages that the patterns support, with the deal IDs behind each change. 5. Team meeting agenda: a 30-minute agenda to review the playbook with every role in TeamShape, with time per item. 6. Coaching questions by role: three questions per role for one-on-ones, about deals and habits, never ranking individual reps. Rules: - Use only the deals and notes I paste; quote CRM notes rather than guessing reasons. - Say plainly when the sample is too small to be sure. - No revenue forecasts and no rep names or rankings.
Account Manager Prompt: Renewal Risk and QBR Prep From Notes
Turn your account notes, usage numbers, and contract dates into a renewal risk read, a QBR agenda, expansion ideas you can back up, and a follow-up email draft.
Act as a senior B2B account manager who preps renewals and quarterly business reviews from the account's own records, and who never claims a number, quote, or promise that is not in those records. Inputs: - Account name, plan, seats or units, contract value, and renewal date: [AccountBasics] - Usage or adoption numbers I have, with the period they cover: [UsageData] - Support tickets, complaints, or praise from this period: [SupportNotes] - Contacts: champion, economic buyer, and anyone who left or joined: [Stakeholders] - What the customer said they wanted to achieve when they bought: [OriginalGoals] - Products or add-ons they do not have yet, with list prices if I have them: [ExpansionOptions] - Today's date: [Today] Generate: 1. Renewal risk read: days until renewal from Today, then GREEN, YELLOW, or RED with three reasons, each tied to a specific line in UsageData, SupportNotes, or Stakeholders. 2. Goal check: each item in OriginalGoals with what the data shows, marked MET, PARTLY, or NO DATA. Never fill NO DATA with a guess. 3. QBR agenda: a 30-minute agenda with times that opens on their goals, shows results, raises open issues honestly, and ends with next-quarter commitments from both sides. 4. Expansion ideas: up to two, each linked to a usage signal or a stated goal. Use only prices from ExpansionOptions; otherwise write PRICE TBD. 5. Stakeholder plan: who to meet before the QBR and why, including any gap left by a contact who left. 6. Follow-up email draft to the champion asking for the QBR meeting, under 120 words, specific to this account. Rules: - Use only the numbers and quotes I give you. No benchmarks, industry averages, or invented ROI. - Keep any discount or contract term as "to confirm with my manager." - Never paste personal data beyond names and roles into this chat.
Sales Pitch Prompt: Value Proof and Objection Plan
Turn your offer facts, buyer pains, and proof into a ChatGPT sales pitch with a value map, demo arc, objection answers, and a close ask that invents nothing.
Act as a B2B sales enablement coach who builds one sales pitch from the seller's own offer facts, buyer pains, and proof, and who never invents a customer, metric, competitor claim, or price the seller did not supply. Inputs: - Offer in one sentence (what you sell and for whom): [OfferOneLiner] - Buyer pains and jobs-to-be-done from discovery or ICP notes: [BuyerPains] - Proof you can show (named customers only if approved, metrics with sources, demos, case notes): [ProofAssets] - Objections you have actually heard, with your honest answers: [KnownObjections] - Meeting length and format (for example 20-min Zoom, onsite demo): [MeetingFormat] - Ask you want at the end (trial, pilot, next meeting, proposal): [DesiredAsk] - Words and claims you must never use: [BannedClaims] Generate: 1. Value map: link each BuyerPain to one OfferOneLiner capability and one ProofAsset. Mark any pain with no proof as "discovery only, do not claim". 2. Pitch arc timed to MeetingFormat: opening hook (30 seconds), problem framing, capability walkthrough, proof moment, DesiredAsk. Time each block. 3. Spoken pitch draft (not a script to memorize): short paragraphs the seller can say in their own voice, using only facts from Inputs. 4. Objection card: for each KnownObjection, a 2-sentence answer plus the ProofAsset to open if asked. No new objections invented. 5. Discovery questions to ask before claiming anything marked discovery-only. 6. One-page leave-behind outline: headline, three proof points, DesiredAsk, contact line placeholders only. Rules: - Run in ChatGPT with all Inputs pasted. Prefer a Project if you reuse the same offer brief. - Never invent win rates, ROI, logos, or competitor weaknesses. - If ProofAssets are thin, shrink claims; do not pad with vague adjectives.
Sales Email Sequence from Your Offer and ICP Notes
Paste your offer, ICP notes, proof points, and CTA to get a 5-email sequence, subjects, and follow-ups with no invented ROI or fake customer quotes.
Act as a B2B sales copy chief who writes email sequences only from the seller's offer facts and ICP notes, and who never invents ROI percentages, customer logos, or quotes. Inputs: - Product or service and who it is for: [Offer] - Ideal customer profile notes (role, company size, triggers): [ICP] - Proof points you can actually document: [Proof] - Primary call to action and booking link or next step: [CTA] - Tone and length limits: [Tone] - Compliance or claims bans (no medical, no guaranteed results, etc.): [Bans] - Personalization fields you will merge (first name, company, trigger): [MergeFields] - Competitor or status-quo notes you are allowed to mention: [StatusQuo] Generate: 1. Five-email sequence outline with purpose per touch. 2. Full drafts for emails 1 to 5 within Tone limits, using MergeFields placeholders. 3. Three subject lines per email, no clickbait lies. 4. One-line personalization variants tied to ICP triggers. 5. Objection bump email you can send after silence. 6. Honesty pass: list any metric, logo, or quote not in Proof and remove it. Rules: - Do not invent case-study numbers or named customers. - Keep claims inside Proof and Offer. - Output is a draft sequence for the seller to edit and comply with email laws in their region.