The selling happens in conversations. Relationships, discovery calls, renewal reviews, executive briefings — that's where deals move. But the job also happens at your desk, at 6pm, staring at a blank email after a three-call day.
After every customer interaction, there's a documentation tax: update the CRM, write the follow-up email, draft the deal summary for Friday's pipeline review, prep the call brief for next Tuesday's renewal, compose the executive sponsor outreach you've been putting off, and somehow turn that QBR into a coherent write-up the account team can actually use. None of that documentation requires you to be the one crafting it from scratch. You already know the substance. What you need is the prose.
Before we go further — an important clarification for anyone in sales reading this: Claude cannot access your CRM. It cannot pull Salesforce data, listen to Gong recordings, join your calls, query HubSpot, or look up anything about your accounts. It has no visibility into your pipeline, deal history, or customer records. It is strictly a drafting and communication tool. You bring the facts — the call notes, the deal context, the account details — and Claude handles the structure and prose. If you're expecting an AI that connects to your tech stack and writes updates automatically, that's not this. What it is: a tool that turns your raw notes into polished, professional output in under two minutes. For a broader look at how AI supports the full sales function, see Claude AI for Sales.
1. Post-Call Follow-Up Email
The follow-up email is one of the highest-leverage things an AE sends — and most of them are mediocre. Too vague, too long, missing next steps, or so generic the prospect can tell it's a template. A good follow-up recaps what mattered, confirms next steps with specific owners and dates, re-anchors the value conversation, and feels like it came from someone who was actually paying attention.
Paste your call notes. Claude writes the email.
You're helping an account executive write a post-call follow-up email. Here are my notes from the call: [paste bullet notes — what was discussed, decisions made, next steps, names and dates].
Write a polished follow-up email with:
- Subject line
- Short opening that references something specific from the call (not generic)
- Key points discussed (3-4 bullets)
- Confirmed next steps with owners and dates
- Brief re-anchor on the value we discussed
- Warm but professional close
Tone: professional and direct, not overly formal. 250 words max.
The key instruction is "paste your call notes" — not "let Claude reconstruct the call." Claude cannot hear what was said. You bring the specifics (the exact blocker mentioned, the exec's name, the date they want a demo by) and Claude turns those specifics into something that reads as genuinely attentive rather than copy-pasted from a template.
2. Deal Summary / Pipeline Update for VP
Pipeline reviews require a deal-by-deal narrative from every AE on the team. Your VP doesn't want a data dump — they want to know where the deal is, why it's there, what's blocking it, and what the path to close looks like. Three to four tight sentences, in the format that matches how leaders think about pipeline.
You're helping an account executive write a deal summary for a VP pipeline review. Here are the details for this deal: [paste — deal stage, deal size, key contacts, current status, main blockers, proposed close date, next steps].
Write a 3-4 sentence pipeline summary that covers:
1. Where the deal is and why (stage + key context)
2. What the main blocker or risk is right now
3. What's needed to move it forward (action + owner)
4. What the close path looks like
Format: tight prose, no bullet points. Audience is a VP who is reading 12 of these in a row.
The "reading 12 of these in a row" instruction matters. It calibrates Claude's output for density — it won't pad the summary or add context the VP doesn't need. You paste the raw deal notes; Claude produces the polished narrative your VP actually wants to read.
3. Call Prep Document
A well-prepped call is one of the clearest differentiators between an average AE and a great one. Before a renewal, upsell, or complex new business call, the prep work is predictable: know the account's current state, anticipate the objections, prepare your questions, and have your talking points ready. That structured thinking takes 30–45 minutes when you do it from scratch. Claude compresses it significantly.
You're helping an account executive prepare for an important customer call. Here's what I know about this account: [paste — last few touchpoints, current usage or contract status, recent support issues, business context, what I know about the attendees].
The purpose of this call is: [renewal / upsell / new business / executive review].
Build a structured call prep document with:
- Call Objectives (what success looks like)
- Key Questions to Ask
- Likely Objections + Suggested Responses
- Talking Points (value to reinforce, wins to reference)
- Risk Flags (anything that could derail the call)
The "Risk Flags" section is the one most reps skip when prepping manually — and the one that causes the most in-call surprises. Paste in whatever you know about the account (support ticket history, usage dips, competitor activity) and Claude will surface the likely trouble spots in structured form so you can prepare rather than react.
Customer success managers can use the same prompt template for EBR prep — the structure translates directly.
4. Executive Sponsor Outreach
Getting access to the economic buyer is one of the hardest parts of enterprise sales. The champion loves the product. The VP doesn't know it exists. The outreach email that gets a response from a busy executive doesn't lead with your product — it leads with their problem, their metrics, and something specific enough to signal you've done your homework.
You're helping an account executive write an outreach email to an executive sponsor (economic buyer) at an existing or prospective account. Here's the context: [paste — company name, exec's title and name, what I know about their business priorities, what our product does for their team, any relevant business context like growth, layoffs, earnings, news].
This is a [cold / warm] outreach. The goal is to secure a 20-minute conversation.
Write an outreach email that:
- Opens with something specific to their business situation (not our product)
- Frames the business problem we solve in their language
- References the value we've delivered for their team or similar companies
- Makes a single, low-friction ask (20-minute call)
- Stays under 150 words
No buzzwords. No "I hope this finds you well." Professional, not salesy.
The constraint ("no buzzwords," "not salesy") is load-bearing. Without it, Claude defaults to marketing-speak that executives immediately recognize as a template and delete. The specificity of what you paste determines the quality of what comes back — a generic paste produces a generic email. An exec's recent earnings call quote, a public growth initiative, or a specific challenge their industry is facing produces an email that reads as if you actually prepared.
For EAs supporting sales executives who manage executive relationship workflows, Claude AI for Executive Assistants covers the communication coordination layer.
5. Renewal / Expansion Business Case
The hardest renewals aren't the ones where the customer doesn't like the product — they're the ones where the champion loves the product but needs to sell it internally to a CFO or VP who's never seen a demo. Your champion needs a document they can circulate, not just your deck. A one-page internal business case they can put in front of their finance lead with the value already framed in ROI language.
You're helping an account executive build an internal business case for a customer renewal or expansion. Here are the details: [paste — contract value, renewal date, current usage stats, key wins and outcomes, expansion being proposed, cost comparison if relevant, risk of not renewing].
Write a 1-page internal business case the customer champion can share with their CFO or VP, structured as:
- Value Delivered (specific outcomes with numbers where I've provided them)
- ROI Summary (cost vs. measurable benefit)
- Expansion Rationale (what the upgrade unlocks)
- Risk of Not Renewing (what they lose, not what we lose)
- Recommendation
Audience is a finance or operations executive who did not buy the original contract. Use business language, not product language.
"Audience is a finance or operations executive who did not buy the original contract" is the most important instruction in this prompt. It forces Claude to write for someone with zero product context — which is exactly who your champion's CFO is. For finance professionals reviewing these cases on the buyer side, the language this produces is precisely what they need.
6. QBR Narrative / Business Review Write-Up
The QBR call went well. Now you have to write it up — a document that captures what was reviewed, what was decided, and what happens next. This is the deliverable most AEs and CSMs send a week late because it takes two hours to produce from a pile of slides and call notes.
You're helping an account executive write a QBR (Quarterly Business Review) write-up to send to the customer after the meeting. Here are my notes from the QBR: [paste — account metrics reviewed, wins from the quarter, challenges that came up and what was done, next steps agreed, goals for next quarter].
Write a structured QBR document with:
- Account Health Summary (overall state of the relationship)
- Key Wins (quarter highlights with specifics)
- Challenges + What Was Done (honest, not defensive)
- Mutual Action Plan (owners and dates for each next step)
- Next 90 Days (goals and milestones agreed in the meeting)
Tone: professional and collaborative. This goes to the customer's senior leadership team.
"Honest, not defensive" in the Challenges section is a deliberate instruction. Left unguided, AI tools tend to soften challenges into non-statements. Your customer's leadership team sat in the QBR — they know what the issues were. A write-up that acknowledges them clearly and describes what was done builds more trust than one that pretends the quarter was flawless. Claude defaults to balanced language when you give it the instruction.
Business analysts who support post-QBR action tracking and reporting use similar structured output prompts for the data and metrics layer.
Why Claude Over ChatGPT for Sales Work
If you've tried ChatGPT for sales writing and found it serviceable but occasionally unreliable, here's the practical difference for this use case:
100K+ context window. You can paste your full account history — last five emails, all your call notes, the original contract summary, and the current renewal context — in one prompt. Claude reads the whole thing. No chunking, no "summarise first and then paste."
Conservative by default. Claude won't invent numbers, commitments, or deal specifics you didn't provide. For sales documentation, where a fabricated close date or made-up usage stat could damage a real deal, this matters. ChatGPT fills gaps more aggressively; Claude flags when it needs more information. For a detailed comparison, Claude vs ChatGPT for work covers the differences systematically.
Projects per account. Claude's Projects feature lets you create one persistent context per key account. Every call note, follow-up email, and QBR write-up lives in that Project. By the time you're at renewal, Claude has the full relationship history — you don't have to re-paste it every time.
Structured output fidelity. Claude asks for clarification rather than inventing account details when your notes are thin. When you're writing a VP pipeline summary, getting asked "what's the main blocker?" is more useful than getting a plausible-sounding placeholder that doesn't reflect your actual deal.
4 Practical Tips for Account Managers
1. One Project per key account. Every interaction document — call notes, emails, deal summaries, QBR write-ups — goes into the same Claude Project. When renewal season hits, the context is already built.
2. Facts in / prose out. Never ask Claude to guess at deal specifics. Paste the raw data — stage, contact names, numbers, dates, blockers. Claude's output is only as accurate as what you give it. Garbage in, polished garbage out.
3. Specify the reader. "Write this for my VP, 3 sentences max" produces something completely different from "write this for the CFO who doesn't know our product." The audience instruction is the most important line in your prompt.
4. End-of-quarter sprint. The last Friday of every quarter, batch all your deal summaries, renewal briefs, and pipeline narratives in one Claude session. It takes 90 minutes instead of a full day. Your VP gets clean, consistent summaries across the board.
The Complete Claude Playbook
If you want the full prompt library — covering sales, communication, and every business role that writes too much — The Complete Claude Playbook ($27) has the templates organized by workflow, with guidance on how to adapt each prompt for your specific accounts and deal types.
The prompts in this post are a starting point. The Playbook is the full toolkit.