Free AI Prompts for Sales & RevOps Teams

You are a top-performing SDR writing a cold email that gets a reply by leading with the prospect's problem, not your product. Write the email to [Name], a [job title] at [company type].

Use ONLY the details I give you below. Do not invent a statistic, a customer name, a case-study result, or a fact about the prospect to make the email land — an unverifiable claim is what gets it deleted. If I leave the opening hook blank, open with the problem instead and do not fabricate a personal detail.

The business problem they likely have: [problem]
My offer (what I help them do): [offer]
My personalized opening hook (one true, researched detail — or leave blank): [hook]

Write the email so that:
- It opens with the hook if I gave one, otherwise with the problem — never with product features or "I'm reaching out because we...".
- The middle names the business problem in concrete terms a [job title] would recognize: not "improve efficiency" but, e.g., "cut the 6 hours a week your team spends reconciling two systems by hand."
- It has exactly one clear, low-friction call to action (a specific question or a 15-minute ask — not "let me know if you're interested").
- It is no more than 5 sentences, plain and human, no jargon and no flattery.

Return just the email, subject line included. Keep the subject under 6 words and specific to the problem, not the product.

NUMBERS RULE — READ THIS FIRST: Every dollar amount, total, weighted value, forecast figure, and gap-to-quota in your output must be one I pasted below, copied verbatim — you may not add, subtract, or otherwise recompute any of them, not even to "check" one. The headline forecast number especially must be a figure I gave you, copied verbatim — never a sum you worked out. (Reading how many days a deal has gone quiet from the dates I give you is fine — the ban is on money math.) If a money figure you need isn't in what I gave you, write "[NOT PROVIDED]" — never close the gap with your own math or an estimate.

You are a senior RevOps analyst writing a weekly forecast narrative for my VP of Sales. Use ONLY the figures and context below — do not invent deals, amounts, or close dates, and do not compute the weighted forecast yourself: I've stated the numbers; your job is to narrate them and make the assumptions explicit.

My pipeline data this quarter:
[PASTE DEAL LIST WITH STAGE, AMOUNT, CLOSE DATE, LAST ACTIVITY]

Context:
- Quota this period: [quota]
- Closed to date: [closed to date]
- Days remaining in the period: [days remaining]
- My CRM's forecast, already computed — restate verbatim, do not recompute: [my CRM forecast]

Write a 3-paragraph narrative (250 words max), then an assumptions block:

1. THE CALL — lead with the number: restate my CRM's forecast above (Commit / Most-likely / Best-case) exactly as I gave it, against quota. State your confidence in one plain sentence. If I left the forecast blank, write "[NOT PROVIDED — forecast not stated]" rather than computing one.
2. WHAT IT HANGS ON — the 3–5 deals this forecast depends on, each with its status in a line, plus any upside deal that could pull in early.
3. RISK & GAP — the deals most likely to slip and why, the size of the gap if any, and what would close it. Name risks honestly; a forecast that hides them costs credibility next quarter.

ASSUMPTIONS — a bulleted list of every assumption the forecast rests on (the weighting applied, which 'maybe' deals you counted as commit, any close date you're trusting). Be specific — not "some deals may slip" but, e.g., "counts [Acme] as Commit although the contract isn't signed — drop it and the forecast misses quota by $30k." Where I gave no figure, write "Not stated" rather than estimating.

Tone: direct, data-backed, no filler. Do not round a 'maybe' up to a 'commit' to make the number look better.

SELF-CHECK before you finish: list every dollar figure in your output, one per line, and after each quote the exact words I pasted that it came from. If any dollar figure is one you worked out rather than copied, remove it from your answer and restate that point with "[NOT PROVIDED]" — your final answer must not contain a computed money figure, not even one you flag. Confirm the headline forecast number is one I pasted, not a total you computed.

You are a disciplined RevOps analyst who keeps a sales pipeline clean. Convert this sales call into a CRM update. Use ONLY what was actually said — never invent a commitment, budget, timeline, decision-maker, or competitor the buyer didn't state; mark anything the call didn't cover as "Not stated." Leave any [Client] or [Counterparty] placeholder exactly as written.

Call transcript/notes:
[PASTE THE CALL TRANSCRIPT OR NOTES HERE]

My CRM's required fields (leave blank to use the default below): [list — e.g., Stage, Next Step, Next Step Date, Amount, Close Date, Decision Maker, Pain, Competitor]
Valid stages (pick exactly one): [paste your stage picklist]

Produce:
1. EXTRACTED FIELDS — fill each required field (or this default if I left it blank: Stage, Next Step + date, Amount, Close Date, Budget, Timeline, Decision-maker, Pain/need, Competitor, Deal-risk signal, one-line summary). Write "Not stated" wherever the call didn't cover it. Capture Pain/need in the buyer's own words: not "needs efficiency" but, e.g., "said 'we're losing two days a week reconciling reports by hand.'"
2. RECOMMENDED STAGE — exactly one stage from my picklist, with a one-line reason grounded in something said on the call.
3. NEXT STEP — a specific action with a named owner and a date — never "follow up" (not "follow up next week" but, e.g., "Send the security questionnaire to Dana by Thu the 20th").
4. CALL SUMMARY — 2–3 sentences for the activity log.
5. FLAGS — one line listing anything to confirm: inferred attributions, an unsure stage call, any field close to a guess.

Keep it paste-ready.