The Sales Prompt Library: Eight Prompts for Every Stage of the Deal

Most sales reps do not have a lead problem. They have a repeating work problem: the same qualification questions, the same call prep, the same three follow up emails, written from scratch every single day.

That repetition is exactly what a language model is good at, provided someone gives it real inputs instead of a vague ask. Below are eight prompts built for that pattern. Each one expects you to paste real deal information, not hypothetical placeholders. Copy them, adapt the tone to your company, and treat the first output as a draft that a human reviews before it reaches a prospect.

This is what the K in the MAKIA framework, Knowledge, looks like in practice: not a workshop about prompting in the abstract, but templates built around the actual repeated tasks of one role.

1. Lead Qualification Snapshot

You are helping me qualify an inbound lead using BANT (budget, authority, need, timeline). Here is what I know about the prospect: [paste notes, form responses, or call transcript]. Tell me what is missing, what questions I should ask next, and whether this looks like a fit for [describe your ideal customer profile in two sentences]. Be direct if the fit looks weak.

When to use it: right after a new inbound lead lands, before you book a call.

What good output looks like: a short list of what BANT information is present versus missing, three specific questions to ask on the discovery call, and an honest read on fit, not just encouragement.

2. Discovery Call Prep

I have a discovery call in [X] minutes with [company name], a [industry] company with about [size] employees. Here is what I know: [paste CRM notes, LinkedIn summary, or website description]. Give me five questions that would uncover their real problem, not just their stated request, and one likely objection I should be ready for.

When to use it: fifteen minutes before a first call, not the night before.

What good output looks like: questions tied to their specific situation, not generic discovery questions you could ask any company.

3. Follow Up Email After a Call

Write a follow up email based on this call summary: [paste notes or transcript]. Confirm what we agreed on, restate their stated problem in their own words, and propose one clear next step with a date. Keep it under 150 words. Tone: direct and useful, not salesy.

When to use it: within an hour of the call, while the context is still accurate.

What good output looks like: an email the prospect could forward internally without editing, because it accurately reflects what was said.

4. Objection Handling Brainstorm

A prospect raised this objection: [paste the objection in their words]. Give me three different ways to respond: one that reframes the concern, one that uses a relevant proof point, and one that asks a clarifying question instead of answering directly. Do not write a script, give me options I can adapt.

When to use it: when you get stuck mid deal on the same objection more than once.

What good output looks like: three genuinely different angles, not three versions of the same rebuttal.

5. One Page Summary for a Prospect

Turn this proposal into a one page summary a busy executive could read in 90 seconds: [paste full proposal]. Lead with the business outcome, not the feature list. Cut anything that is not decision relevant.

When to use it: before a proposal goes to someone senior who was not on the discovery calls.

What good output looks like: a version your prospect's champion can use to sell internally on your behalf.

6. Deal Risk Check

Here is the current state of a deal I am forecasting: [paste stage, last activity date, stakeholders involved, and any recent signals]. Based only on what I have given you, what would make you doubt this deal will close this quarter? Do not reassure me, tell me what is missing or weak.

When to use it: before a forecast call, on any deal you are tempted to call safe.

What good output looks like: a blunt list of gaps, single threaded contacts, stalled momentum, missing next steps, not a summary of what is going well.

7. Renewal or Upsell Conversation Prep

This account is coming up for renewal on [date]. Usage or engagement data: [paste what you have]. Help me prepare for the conversation: what evidence of value should I bring, what expansion opportunity might make sense given their usage pattern, and what would signal risk of churn that I should probe for.

When to use it: four to six weeks before the renewal date, not the week of.

What good output looks like: talking points grounded in their actual usage, not a generic renewal script.

8. CRM Note Cleanup

Turn this raw call transcript into a clean CRM note: [paste transcript]. Structure it as: a two sentence summary, key stakeholders and their roles, stated need, objections raised, and agreed next step with owner and date.

When to use it: right after logging a call, so the CRM stays usable for the whole team.

What good output looks like: a note a colleague could read cold and understand the deal's state without asking you a follow up question.

Try this week

Pick one deal you are currently working. Run prompt 6, the deal risk check, using real information from that deal. Do not soften what it tells you. Bring the answer to your next pipeline review.