Claude for Sales Teams

Build a one-page brief on [company] ([website]).
Cover: what they do, who they sell to, size, recent news from the last 6 months, likely priorities for [persona], and any history we have with them in the CRM.
Then give me three reasons they might need [product] now, each tied to a source. Link every source.

Why it works: It asks for evidence behind every reason, so you can tell real triggers from guesses.

For [company], list the roles that usually take part in buying [product category]: decision maker, budget owner, users, IT and security, procurement.
Check the CRM for contacts we already have at [company] and map them to these roles.
Show the gaps, and suggest which role to reach next and why.

Why it works: It starts from roles, not names, so you do not chase the wrong person.

Search for events at [company] in the last 90 days that could create a need for [product]: funding, leadership changes, hiring for [roles], new markets, product launches, regulation.
Rank them by how strong a reason they give to talk now. One line each, with the link.

Why it works: A dated, sourced trigger beats a generic opener every time.

Here is a list of [number] accounts. Score each one 1 to 5 against our ICP in the project files: industry, size, region, tech stack and any signals you can find.
Return a table: account, score, one-line reason, suggested first step. Put tier 1 accounts first.

Why it works: It scores against your written ICP, so the ranking is consistent across reps.

Prepare me for my meeting with [company] on [date].
Pull the attendees from my calendar, their roles, our last three interactions from email and the CRM, the deal stage and open next steps.
Give me: the goal for this call, five questions to ask, likely objections with a short answer for each, and what a good outcome looks like.

Why it works: It combines three sources you would otherwise open one by one.

I am meeting a [persona] at a [industry] company with about [size] employees.
Write 10 discovery questions, ordered from broad to specific, that uncover pain, impact, current process, decision process and timeline.
Mark the three I must not skip.

Why it works: Ordered questions keep a first call natural instead of an interrogation.

Play a sceptical [persona] at [company]. Raise the objections they are most likely to have about [product], one at a time.
After each of my answers, score it 1 to 5 and show a stronger version using our approved proof points only.

Why it works: Practice with feedback, using only claims you are allowed to make.

Here are my notes from today's call with [name] at [company]: [paste notes or transcript].
Draft a recap email: thank them, summarise what we heard in their words, confirm the agreed next steps with owners and dates, and attach nothing.
Keep it under 150 words. Then list the CRM fields I should update.

Why it works: A short recap in the buyer's words builds trust, and the CRM update is not forgotten.

The deal with [company] has been quiet for [number] weeks. Read our email thread and CRM notes.
Draft three short follow-ups with different angles: a useful insight, a direct question, and a polite close-the-loop.
Each under 80 words. No guilt, no "just checking in".

Why it works: Three angles let the rep pick the one that fits the relationship.

We are single-threaded with [contact] at [company]. Based on the CRM and our emails, suggest two other people to bring in and why.
Draft a short note [contact] could forward internally, and a direct intro email to each new person.

Why it works: It makes it easy for your champion to help you.

List my open deals in [stage or stages] with close dates in the next [30] days.
For each: last activity, the next step on record, and whether that step is overdue.
Flag deals with no next step or no activity in 14 days, and suggest one concrete action for each.

Why it works: Turns Monday pipeline review into a to-do list.

Draft a proposal for [company] using our proposal format in the project files.
Use their goals and pains from the CRM notes and email thread, in their words.
Include: situation, goals, proposed solution, scope, timeline, pricing table using our pricing rules, and next steps.
Mark every assumption in [brackets] for me to confirm.

Why it works: Brackets make every guess visible, so nothing unverified goes to the buyer.

Write a half-page executive summary of this proposal for [buyer's boss, title].
Lead with the business outcome and the cost of doing nothing. Then the plan, the investment and the decision we need.
No jargon. Five sentences maximum in the opening paragraph.

Why it works: Deals often stall above your contact. This gives them something to forward.

Read this proposal as the buyer's procurement lead and as their CFO.
List the ten questions or objections each would raise, rank them by risk to the deal, and suggest how to answer or fix each one in the document.

Why it works: You find the weak spots before the buyer does.

Here is a security questionnaire from [company]: [paste or attach].
Answer each question using only our approved answers in [folder or document].
Where there is no approved answer, write "Needs security team" instead of guessing. Return a table: question, answer, source.

Why it works: Speeds up the slowest part of late-stage deals without inventing answers.