Sales
Research accounts, personalize outreach at scale, prep for every call, and keep your pipeline notes clean — all from the Claude Desktop chat, no terminal and no CRM gymnastics.
Full worked systems, not one-off prompts — each walks the whole workflow end to end. Pick one and follow it.
Build the value narrative every rep sells from
Turn scattered product facts, win stories, and ROI numbers into one value narrative — the problem you kill, the proof behind it, and the cost of doing nothing — that every brief, opener, objection card, and renewal inherits.
Define your ICP and a qualification rubric Claude can score against
Turn your won and lost deals into a sharp ideal-customer profile and a plain-language qualification rubric — then have Claude score new leads and deals against it, so the team chases fit, not noise.
The objection battle-cards
Turn your hardest recurring objections — price, a named competitor, "not now" — into honest, non-defensive responses that reframe around value, as a doc the whole team reuses.
The pre-call account brief
Turn folders of notes, an email thread, and a CRM export into a tight pre-call brief — where you stand, what they care about, open promises, the top risks, and your opening line.
The personalized outreach engine
Feed a CSV of leads and your value prop; get one specific, researched opening line and a short follow-up sequence per row — grounded in each account's real context, not mail-merge flattery.
The discovery-call system
Build a tailored discovery plan before the call and a clean capture after it: the questions that surface the real problem and budget, a listening guide, and a structured summary that scores the deal and feeds your CRM.
The post-call follow-up system
Turn any call recording or transcript into momentum: the real objections, what they committed to, the open questions, and a ready-to-send recap with a clear next step.
The tailored proposal and pricing draft
Turn discovery notes and your pricing into a proposal that mirrors the buyer's own words: their problem, the value tied to proof, a clear scope and price, and pre-handled objections — drafted in minutes, not an afternoon.
The weekly pipeline review
Clean a messy deals export, standardize stages, flag every deal gone quiet for 30 days, total the pipeline by stage, and get a skeptical read on which deals are real.
The renewal play, end to end
Run a renewal or expansion as a planned play, not a scramble: research the account, map the risks, line up the value story, pre-handle objections, draft the outreach, and build a step-by-step runbook for the call.
The strategic account plan, end to end
Run a key account as a planned campaign, not a stack of one-off deals: map the stakeholders and whitespace, build the multi-thread value story, plan the expansion sequence, and assemble a quarter-by-quarter account plan with named owners and gates.
Sales with Claude, in depth
The playbooks above are single jobs. These are the long reads behind them — how the work fits together across a quarter, what good looks like, and the judgement calls the prompts assume you have already made. Read in any order.
- Account-in-a-Box — the Sales capstone The Sales capstone — integrate all five modules into one coherent sales system for a single brand, proven end to end by taking one account from cold to won-and-growing, Checked against a master rubric that covers the artefacts and the judgement behind them. Bring your own account and it doubles as deployable work.
- Running the Deal: discovery that surfaces the truth, and proposals that close Module 3 of the Sales deep dives — go past the recipe to run discovery that surfaces the real problem and budget, capture a call into structured signal that scores the deal, and write a proposal that mirrors the buyer and ties price to proof — then prove it against a real rubric. Builds on the foundation and the outreach engine.
- Sales Foundation: master the value narrative every deal inherits Module 1 of the Sales deep dives — go past the recipe to master the three documents every call, email, proposal, and rep inherits: the value narrative, the ICP-and-qualification rubric, and the objection battle-cards. Build them for your own product and prove it against a real rubric. Free to sample.
- Sales Measurement: where the quarter's won and lost rewrites the value narrative Module 5 of the Sales deep dives — the pipeline review that makes the foundation smarter: measure against the number not the activity dashboard, read honestly which deals are real, and close the loop by turning a quarter's won and lost into a versioned edit to your value narrative, ICP, and battle-cards. Graded against a rubric, both languages.
- The big play: orchestrate a renewal or strategic account, end to end Module 4 of the Sales deep dives — run a flagship renewal or strategic account end to end: a runbook with an owner and a date on every line, named deal-desk, legal, and Arabic approval gates, a stakeholder-and-whitespace map and per-thread value story built before the call, and a bilingual offer that lands native and simultaneous. Graded against a real rubric, not a vibe.
- The outreach engine: turn your foundation into pipeline that fills itself Module 2 of the Sales deep dives — turn the value narrative, ICP, and battle-cards you built in M1 into a repeatable prospecting system: qualify, research the account into a brief, personalize from real context, sequence the follow-up, log it. Build it for your own product and check it against a real rubric.
- The Sales Foundation toolkit: the files your team installs The take-home pack for Module 1 — a ready sales CLAUDE.md, fill-in templates for value-narrative.md, the ICP-and-qualification rubric, and battlecards.md, plus the saved prompts that build them. Turn the foundation you wrote into files your whole team sells from.
The non-negotiables before any of this ships. Read the operating guide for the full data, brand, legal, and rollout playbook.
- Verify before you commit. Claude states a renewal date, a usage figure, or a past promise with total confidence and can be wrong — confirm any fact, number, or date against the source before you say it on a call or put it in a forecast. The brief is a starting point, not gospel.
- Keep customer data where it belongs. Call notes, transcripts, leads, contracts, and pipeline exports are sensitive — keep them in a workspace your company has approved, drop only what a task needs into the Desktop file pane, and approve each read in the 'Ask permissions' prompt. Use
[prospect]-style placeholders if you ever share a prompt. - Give Claude your real source of truth. Feed it your
value-prop.md,qualify.md, andbattlecards.mdso "our value," "a good deal," and "how we handle that" point at real documents — built once in the Stage 1 playbooks, inherited by every deal. - One approval gate on every commercial move. Pricing, discounts, contract terms, and the expansion ask are never a rep's to commit solo — route anything beyond what's already approved past deal-desk or your manager before it reaches the buyer. Claude drafts the quote and the recap; the authority to agree terms stays with whoever owns it.
- Adapt for Arabic, don't translate. Bilingual outreach gets its own value narrative and localized proof, not a machine-translated copy of the English — a translated cold email reads translated, and in this region that's the difference between credible and ignored.
- Claude drafts; humans own the deal. The research, the recap, and the runbook are drafts you adapt — trust your read of the room over the bullet points, and a person owns the relationship, the call, and the number.
Questions people ask
- Is it safe to put customer data into Claude?
- Keep a customer's private details — contacts, contract terms, anything regulated — in a workspace your company has approved, and let Claude read the local copy through the Desktop file pane, approving each read in the 'Ask permissions' prompt. Working from your own call notes and exports that way is fine; just verify before you act.
- Does this replace my reps or my CRM?
- No. It speeds up the prep and the admin — research, recaps, tidying notes — so your reps spend more time selling. You still own the relationship and the deal; Claude just clears the busywork around it.
- Do I need to be technical to use it for sales?
- No. You open the Claude Desktop app, drag in your real files — call notes, an email thread, a leads CSV — and ask in plain language. No terminal, no queries, no setup.
- What's a realistic first task?
- Prepping for a call: point Claude at your notes from the last few touches and ask for where the relationship stands, the top risks, and the best opening question. It's a five-minute win in the Desktop chat that you'll feel on the very next call.