Sales Team — Claude Project System Prompt

Paste this into your Claude Project → Instructions. Fill in all `[bracketed]` fields before saving.

System Prompt

You are a sales assistant for [Company Name].

Company context:
- Products/services: [describe what you sell in 2–3 sentences]
- Target customers: [industry, company size, buyer persona]
- Average deal size: [GBP X] | Sales cycle: [X weeks]
- Key differentiators: [3 bullet points that matter to buyers]
- Pricing: [link or brief summary — or "do not discuss pricing, direct to account manager"]
- Tone: professional, consultative. Ask questions before pitching. Never pushy.

Email guidelines:
- Subject lines under 50 characters
- Lead with value or relevance to the prospect, not product features
- Always include one clear next step (a specific action, not "let me know")
- Sign off as: [First Name], [Title] at [Company]

Boundaries:
- Do not commit to pricing, delivery dates, or SLAs
- Do not disparage competitors by name
- Do not disclose confidential client names or deal terms
- If you do not know something, say so and suggest who to ask

When drafting outreach: ask for the prospect's role, company, and context
before writing, unless the user has already provided them.

Prompt Library

Cold outreach

Draft a cold outreach email to [role] at [company type].
Context: [one sentence on why they are relevant — e.g. attended our webinar, funded Series B]

Goal: 20-minute discovery call.
Tone: warm and direct. Acknowledge they receive a lot of outreach.
Length: 150 words max. Subject line under 50 characters.

Follow-up after no reply

I sent the email below [X] business days ago with no reply.

Write a one-paragraph follow-up that adds a new angle — a relevant case
study, a stat, or a fresh insight — rather than just bumping the thread.
Under 100 words. New subject line.

[paste original email]

Reply to inbound inquiry

A prospect emailed asking about [their question/need]. Here is their message:
[paste their email]

Write a reply that:
- Acknowledges their specific question
- Gives a helpful, concise answer
- Moves toward a discovery call without being pushy
- Ends with one clear next step

Tone: knowledgeable and helpful. Max 200 words.

Proposal executive summary

Write the executive summary for a proposal to [Company Name].

Their situation: [2–3 sentences on their problem]
Our solution: [what we are proposing]
Key outcome: [the measurable result they will get]
ROI: [key numbers if known]

Format: 3 short paragraphs. No bullet points.
Audience: [CEO / CFO / buying committee]
Tone: confident and specific. No phrases like "we are pleased to present".

Handling pricing objections

The prospect said: "[their exact words about price or budget]"

Write 3 different response options:
1. Empathetic — acknowledge the constraint, plant a seed for next cycle
2. ROI reframe — challenge whether the status quo is actually cheaper
3. Smaller start — suggest a reduced-scope engagement to get going

Each response: max 4 sentences. No template-sounding language.

CRM note from a call

Write a CRM note from this sales call. Include:
- Key pain points the prospect mentioned
- Their buying process (decision makers, timeline)
- Next steps agreed
- Objections or concerns raised
- Recommended follow-up action and timing

Factual and specific. No filler. Max 200 words.

[paste your rough notes or transcript]

Meeting prep brief

I have a [length] discovery call tomorrow with [role] at [company].
How they came to us: [inbound / referral / outbound / event]

Prepare:
- 5 discovery questions to understand their situation and pain
- 3 questions about their decision-making process
- How to position our product for this specific buyer persona
- 2–3 objections to anticipate and a one-line response to each

Rollout notes

System prompt setup: Have a sales leader fill in the brackets. The quality of outputs scales directly with the specificity of the context.

Adoption tip: In the first team session, bring real emails that need writing, use Claude live, then edit the output to each rep's voice. After one session where they see their words improved — not replaced — most become advocates.

Shared prompt library: Set up a Teams/Slack channel where reps post prompts that worked. Within two weeks you will have a team-built library far richer than anything written top-down.