AI Prompts for Sales Teams

Account research brief: from raw filings to a first-touch angle

You have 30 target accounts and one hour. Turn one account's public footprint into a brief you can actually open a conversation with.

You are a senior SDR preparing a first-touch campaign for one target account. I will paste raw public material about the account. Produce:

A) ACCOUNT SNAPSHOT — a table with columns: dimension (what they sell, who they sell to, revenue motion, recent trigger events, tech-stack clues), what the material says, and the exact quote or source line it comes from.

B) THREE PAIN HYPOTHESES, ranked — each tied to a trigger event in the material, mapped to my offer, and labeled confirmed / inferred / speculative.

C) ONE OPENER — a 4-sentence first-touch email built on the top hypothesis: one specific observation from the material, no generic flattery, one closing question.

Materials: [PASTE: 10-K EXCERPT / EARNINGS-CALL NOTES / PRESS RELEASES / JOB POSTINGS / SITE COPY]
My offer: [ONE SENTENCE: WHAT YOU SELL AND THE PAIN IT REMOVES]

Rules: Do not invent facts about the account — if a claim is not in the pasted material, label it "assumption" and list it separately. Mark anything I should verify externally (funding, headcount, exec names) before sending. Never include customer-confidential data or personal contact details in the output.

Account dossier: turn a company URL and 10-K into a call-ready brief

You have 40 accounts and an hour. Compress each one into a one-page brief that tells you why to call, who to call, and what to say first.

You are a senior account researcher building a call-ready brief for a rep — a drafting aid, not verified truth. I will paste what I know about a target account.

Produce:

A) SNAPSHOT — one plain sentence on what the company does, its rough size, and the segment I sell into.

B) TRIGGER MAP — a table of buying signals I pasted (funding, leadership change, hiring, earnings language, product launch), each with the plausible pain it implies and a VERIFICATION column preset to "confirm before citing".

C) STAKEHOLDER GUESS — the 2-3 likely roles that own this problem and, for each, the one outcome they're measured on.

D) OPENER — a two-sentence first message tied to the single strongest trigger, specific enough that it could only have been written for this account.

Inputs: [COMPANY + WHAT THEY DO] · [ANY NEWS / TRIGGERS I FOUND] · [WHO I USUALLY SELL TO] · [MY PRODUCT IN ONE LINE]

Rules: Do not invent facts, headcounts, funding, or names not in my paste — mark anything unconfirmed "VERIFY". Keep confidential CRM data and customer lists out of consumer AI tools and follow your employer's AI-use policy. The brief drafts your angle; you confirm every claim before it reaches a buyer.

Discovery debrief: from raw notes to MEDDICC gaps and next step

You just finished a discovery call. Turn messy notes into a gap map and a follow-up email before the context evaporates.

You are an enterprise AE debriefing a discovery call. I will paste my raw call notes or transcript. Produce:

A) MEDDICC SCORECARD — a table with rows: Metrics, Economic buyer, Decision criteria, Decision process, Identified pain, Champion, Competition; columns: what we heard (with the supporting line from my notes), confidence (high/med/low), and the single question that would close the gap.

B) DEAL RISKS — the top 3, each with its evidence line and one mitigation.

C) FOLLOW-UP EMAIL — 5 sentences max: mirror the prospect's own words for the pain, propose one concrete next step with a date.

Notes: [PASTE CALL NOTES OR TRANSCRIPT]
Deal context: [STAGE, DEAL SIZE, COMPETITOR IF KNOWN]

Rules: Do not invent anything the notes do not support — write "not covered" for empty MEDDICC rows instead of guessing. Flag every quote I should verify against the recording before repeating it to my team. Do not include prospect names, emails, or confidential pricing in the output.

Objection war-game: pre-load the five pushbacks before the call

You keep getting surprised by the same objections mid-call. Rehearse them cold so you answer from position, not panic.

You are a sales coach running an objection war-game before a live call — this is prep, not a script to read verbatim.

Produce:

A) OBJECTION LIST — t

Proposal executive summary that mirrors the buyer's business case

The deck is done but page one reads like a brochure. Rewrite the executive summary in the buyer's language before it goes to procurement.

You are a deal-desk writer rewriting a proposal executive summary so it survives being forwarded to people who never met us. I will paste our draft an

Proposal draft: turn discovery notes into a value-framed one-pager

The deal is warm and the proposal is due. Convert your messy notes into a tight one-pager framed on the buyer's outcome, not your feature list.

You are a proposal writer turning raw discovery notes into a clean one-page proposal draft for my review.

Produce:

A) SITUATION — three sentences re

Account expansion map: whitespace, warm paths, and the renewal story

QBR season. Turn usage data and org knowledge into an expansion plan the account team can actually execute.

You are an account strategist preparing a QBR expansion plan. I will paste what we know about the account. Produce:

A) WHITESPACE MAP — a table with

Renewal risk read: a QBR prep that surfaces churn before it's a surprise

Renewal is 90 days out and you're not sure where you stand. Build a QBR that reads the account honestly and catches churn signals early.

You are a customer-success strategist prepping a quarterly business review and an honest renewal-risk read.

Produce:

A) HEALTH TABLE — usage, outcom

Pipeline scrub: commit-call interrogation for every late-stage deal

Forecast call is tomorrow. Pressure-test the commit list so the number you roll up is the number that closes.

You are a RevOps analyst running a pipeline scrub before the forecast call. I will paste the late-stage deal list. Produce:

A) SCRUB TABLE — columns:

Deal inspection: pressure-test your commit before you call it to the boss

You're about to commit a number. Inspect each deal cold so your forecast is defensible, not hopeful.

You are a sales-ops analyst running a skeptical deal inspection before I submit my forecast.

Produce:

A) DEAL TABLE — each deal I paste: stage, amou