Role-based prompt packs
Copy-paste prompt packs for Sales, Finance, HR, Legal, Support, and Engineering — each built on one repeatable Role · Context · Task · Format · Constraints pattern.
18 min read · Current as of
How to use this pack
Find your department below, copy a prompt, and replace every [BRACKETED] placeholder with your real details. Each prompt is built on the house pattern you'll see throughout this kit — Role + Context + Task + Format + Constraints:
You are a [role]. Here is the context: [paste or attach the material]. Do [task]. Give it to me as [format]. Keep it [length/tone] and avoid [what to leave out].
The more specific your context and constraints, the better the result. Paste the real email, the real numbers, the real policy text — don't make Claude guess. For everyday work use Sonnet 4.6 (the default); switch to Opus 4.8 for the hardest reasoning (complex analysis, tricky drafting) and Haiku 4.5 when you want fast, cheap, high-volume passes. Every prompt here works in claude.ai chat unless noted; the Engineering pack also uses Claude Code and the API.
For a broader, cross-functional set of templates, see the prompt library.
Sales
Where Claude helps most: turning raw call notes, CRM fields, and product facts into personalized outreach, tailored proposals, and fast pre-call research so reps spend time selling, not writing.
| # | Copy-paste prompt |
|---|---|
| 1 | You are an SDR writing cold outreach. Here is the context: prospect [NAME, TITLE, COMPANY], their likely pain point [PAIN], and our product [PRODUCT + ONE-LINE VALUE]. Write a 90-word cold email plus two follow-ups (day 3, day 7). Keep it conversational, one clear CTA, no buzzwords, and avoid claiming results we can't prove. |
| 2 | You are an account executive prepping for a discovery call. Here is the context: [PASTE COMPANY 10-K SNIPPET / WEBSITE BLURB / NEWS]. Give me a one-page brief: their business model, three likely priorities, three discovery questions tied to our solution, and one risk to watch. Format as tight bullets. |
| 3 | You are a sales writer. Here is the context: discovery-call notes [PASTE NOTES] and our pricing tiers [PASTE TIERS]. Draft a follow-up proposal email recapping their goals, mapping each to a capability, and proposing next steps. Keep it under 250 words, confident but not pushy. |
| 4 | You are a deal strategist. Here is the context: this opportunity [STAGE, AMOUNT, STAKEHOLDERS, OBJECTIONS RAISED]. Build a MEDDIC qualification summary and flag the two weakest areas with a question I should ask to close each gap. Format as a table. |
| 5 | You are an objection-handling coach. The prospect said: [PASTE OBJECTION]. Give me three distinct responses — empathize-reframe-evidence — each under 60 words, plus the follow-up question to keep the conversation moving. |
| 6 | You are a sales copywriter. Here is the context: [FEATURE] and the buyer persona [PERSONA]. Rewrite this feature [PASTE FEATURE TEXT] as a benefit-led value statement for that persona, in three lengths: one-liner, two sentences, and a short paragraph. |
| 7 | You are an AE summarizing a call for the CRM. Here is the transcript: [PASTE TRANSCRIPT]. Produce: a 3-sentence summary, next steps with owners, identified pain points, competitors mentioned, and a suggested deal stage. Format as labeled fields ready to paste. |
| 8 | You are a sales researcher. Here is our ICP: [PASTE IDEAL CUSTOMER PROFILE] and this account [PASTE ACCOUNT DETAILS]. Score fit 1–10 against each ICP criterion, justify in one line each, and recommend pursue / nurture / pass. |
| 9 | You are a sales enablement writer. Turn this win story [PASTE DETAILS] into a 150-word customer reference snippet and three reusable talk-track lines, keeping all figures exactly as given and flagging anything that needs customer approval before external use. |
| 10 | You are a negotiation advisor. Here is the context: their ask [PASTE], our floor [PASTE], and non-price levers we have [PASTE]. Suggest three trade options that protect margin, with the framing line for each. |
Suggested Projects setup
- Sales Playbook Project — load the current pitch deck, pricing/discount guardrails, ICP, objection-handling guide, and two best-in-class proposals. Reps then ask for outreach and proposals that stay on-message automatically.
- Account Hub Project (per strategic account) — load discovery notes, org chart, prior emails, and the mutual action plan so every draft is grounded in that account's history.
Data-safety caution: Don't paste a prospect's confidential information or your own non-public pricing into anything outside an approved workspace; treat customer contact data as PII under company policy.
Finance
Where Claude helps most: drafting commentary, structuring analysis, and turning dense spreadsheets and filings into clear narratives — while you keep the numbers and judgment.
| # | Copy-paste prompt |
|---|---|
| 1 | You are an FP&A analyst. Here is the context: this month's actuals vs. budget [PASTE TABLE]. Write the variance commentary: top five drivers, each quantified, with a one-line plausible cause and whether it's timing or structural. Format as bullets under each line item. |
| 2 | You are a finance writer. Here is the context: [PASTE KPI TABLE]. Draft the executive summary section of the monthly business review: three sentences on performance, two on risks, two on the forward outlook. Neutral, board-ready tone. |
| 3 | You are a financial modeler. Describe — step by step — how to build a three-statement model for [BUSINESS TYPE], listing the key assumptions to surface, the drivers that link the statements, and the sanity checks to add. Do not invent numbers; give me the structure. |
| 4 | You are an accounts-payable analyst. Here is the context: this vendor invoice data [PASTE]. Identify duplicates, outliers vs. historical average, and missing PO references. Return a flagged exceptions table with a suggested action for each. |
| 5 | You are a treasury analyst. Here is the context: 13-week cash inflows/outflows [PASTE]. Summarize the liquidity position, the tightest week, and three levers to improve coverage. Keep it to half a page. |
| 6 | You are an investor-relations writer. Here is the approved earnings data [PASTE] and last quarter's script [PASTE]. Draft the CFO talking points for the earnings call, matching prior tone and using only the figures provided. Flag any place a number is missing. |
| 7 | You are a financial-statement reviewer. Here is the context: [PASTE FILING OR REPORT EXCERPT]. Explain it in plain English for a non-finance manager: what it says, why it matters, and the two questions they should ask. |
| 8 | You are a budgeting partner. Here is the context: this department's budget request [PASTE] and last year's actuals [PASTE]. Produce a challenge memo: where the request looks high or low vs. trend, and three questions to put to the budget owner. |
| 9 | You are a finance-process writer. Turn this messy month-end close checklist [PASTE] into a clean, sequenced SOP with owners, dependencies, and a target day for each step. Format as a numbered table. |
| 10 | You are a cost analyst. Here is the context: this spend breakdown [PASTE]. Categorize into fixed vs. variable, highlight the three fastest-growing categories, and suggest one diligence question per category. |
Suggested Projects setup
- Monthly Close & Reporting Project — load the chart of accounts, the reporting template, prior-period commentary, and KPI definitions so commentary is consistent and uses your house terminology.
- Budget Cycle Project — load budget guidelines, the assumptions library, and last year's actuals to support challenge memos and consolidation drafting.
Data-safety caution: Never paste MNPI (material non-public information) — unreleased earnings, forecasts, or deal terms — into any tool outside an approved, access-controlled workspace; respect insider-trading and disclosure rules at all times.
HR
Where Claude helps most: drafting clear, consistent, legally-mindful people communications — job posts, policies, reviews, and sensitive messages — at a quality and speed manual writing can't match.
| # | Copy-paste prompt |
|---|---|
| 1 | You are an HR writer. Here is the context: role [TITLE], team [TEAM], must-have skills [LIST], and our EVP [PASTE]. Write an inclusive job description: summary, responsibilities, requirements, and a short "why join" — and remove any gendered or age-biased language. |
| 2 | You are a recruiting coordinator. Here is the context: this role [TITLE] and its key competencies [LIST]. Draft a structured interview guide: eight behavioral questions mapped to competencies, with what a strong vs. weak answer looks like for each. Format as a table. |
| 3 | You are an HR communications specialist. Here is the context: [POLICY CHANGE] effective [DATE]. Write the all-staff announcement: what's changing, why, what employees need to do, and where to get help. Warm, clear, under 200 words. |
| 4 | You are a performance-review coach. Here is the context: these manager notes on [ROLE, ANONYMIZED] [PASTE NOTES]. Draft balanced review language: strengths, growth areas, and two SMART goals — specific and evidence-based, no vague praise. |
| 5 | You are an L&D designer. Here is the context: skill gap [GAP] for [AUDIENCE]. Outline a half-day workshop: learning objectives, agenda with timings, one activity per objective, and a knowledge check. Format as a table. |
| 6 | You are an HR policy writer. Here is our current [POLICY NAME] [PASTE]. Rewrite it in plain, friendly language at an 8th-grade reading level, keeping all rules intact, and add a short FAQ of five likely questions. |
| 7 | You are an HR business partner. Here is the context: this employee survey free-text feedback [PASTE, ANONYMIZED]. Cluster into themes, rank by frequency, summarize the sentiment of each, and suggest one action per top theme. |
| 8 | You are a compensation communicator. Here is the context: [COMP DECISION SUMMARY]. Draft talking points a manager can use to explain this [PROMOTION / NO-RAISE / ADJUSTMENT] conversation with empathy and clarity, including how to handle a frustrated reaction. |
| 9 | You are an onboarding designer. Here is the context: role [TITLE], team [TEAM], first-week goals [LIST]. Build a 30-day onboarding plan with weekly milestones, key contacts to meet, and check-in prompts. Format as a week-by-week table. |
| 10 | You are an HR writer handling a sensitive note. Here is the context: [SITUATION, ANONYMIZED]. Draft a respectful, neutral message that states the facts, avoids admitting fault or making promises, and points to the right next step. Flag anything I should run past Legal. |
Suggested Projects setup
- People Policies Project — load the employee handbook, the company tone-of-voice guide, and approved templates so every announcement and policy rewrite stays consistent and compliant.
- Hiring Project (per req) — load the job description, scorecard, and interview rubric so question guides and candidate summaries stay aligned to the same competencies.
Data-safety caution: Employee data is PII — anonymize names, IDs, comp figures, and health/leave details before pasting, and keep anything performance- or complaint-related in approved, access-restricted workspaces only.
Legal
Where Claude helps most: accelerating first-pass review, plain-language summaries, and clause drafting — as a force multiplier for lawyers, never a replacement for legal judgment.
| # | Copy-paste prompt |
|---|---|
| 1 | You are a contracts attorney doing a first-pass review. Here is the context: this [AGREEMENT TYPE] [PASTE] and our risk priorities [LIST]. Summarize key terms, flag unusual or off-market clauses, and list the top five negotiation points. Format as a table; note this is a draft for attorney review. |
| 2 | You are a legal writer. Here is the context: [PASTE CLAUSE]. Rewrite it in plain English for a business stakeholder, then explain in two lines what risk it actually allocates and to whom. |
| 3 | You are a contracts attorney. Here is the context: our standard position on [TOPIC, e.g., limitation of liability] [PASTE PLAYBOOK] and the counterparty's clause [PASTE]. Draft a redline-style counter-proposal with a one-line rationale for each change. |
| 4 | You are a legal researcher. Here is the context: [FACT PATTERN] and these provided source materials [PASTE STATUTE / POLICY]. Outline the issues, the relevant rules from the sources given, and the open questions — using only the materials provided and citing nothing you can't see. |
| 5 | You are a compliance writer. Here is the context: [REGULATION SUMMARY] and our current practice [PASTE]. Produce a gap checklist: requirement, current state, gap, and suggested remediation owner. Format as a table for counsel review. |
| 6 | You are a legal-operations analyst. Here is the context: this NDA [PASTE]. Compare it clause-by-clause against our standard template [PASTE] and list every deviation with a flag of low / medium / high concern. |
| 7 | You are a privacy specialist. Here is the context: this data-processing scenario [DESCRIBE]. List the questions a DPIA should answer, the data categories involved, and the controls to consider. Note where outside privacy counsel input is needed. |
| 8 | You are a litigation-support writer. Here is the context: this document set summary [PASTE]. Draft a neutral chronology of events with dates, actors, and source references, marking any gaps or ambiguities. Format as a timeline table. |
| 9 | You are a corporate-governance writer. Here is the context: these meeting notes [PASTE]. Draft formal board-minute language capturing decisions, votes, and action items, in a neutral, precise register. |
| 10 | You are a legal-intake assistant. Here is the context: this business request [PASTE]. Triage it: matter type, urgency, missing information to request, and which legal team should own it. Format as a short intake form. |
Suggested Projects setup
- Contract Playbook Project — load standard templates, the negotiation playbook, fallback positions, and the clause library so reviews and counters reflect approved firm positions.
- Matter Project (per matter) — load the relevant agreements, correspondence, and issue list so summaries and chronologies stay grounded in that matter's record.
Data-safety caution: Protect attorney-client privilege — label privileged work as such, keep privileged material in approved workspaces, and never treat Claude output as legal advice or a substitute for a licensed attorney's review.
Customer Support
Where Claude helps most: drafting accurate, on-brand, empathetic replies and turning ticket history and docs into faster resolutions and better self-service content.
| # | Copy-paste prompt |
|---|---|
| 1 | You are a support agent. Here is the context: customer message [PASTE], their account tier [TIER], and the relevant help-doc [PASTE]. Draft a friendly, accurate reply that solves the issue in clear steps and ends with a check-in. Keep it under 150 words, no jargon. |
| 2 | You are a support writer handling an upset customer. Here is the context: [PASTE MESSAGE]. Draft a de-escalation reply: acknowledge, apologize sincerely without admitting legal fault, explain the fix and timeline, and offer a next step. Warm and calm. |
| 3 | You are a knowledge-base author. Here is the context: this resolved ticket thread [PASTE]. Turn it into a reusable help article: problem, cause, step-by-step solution, and "still stuck?" section. Format with headers and numbered steps. |
| 4 | You are a support analyst. Here is the context: these 20 recent tickets [PASTE, PII REMOVED]. Cluster them into root-cause themes, rank by volume, and suggest one fix or macro per top theme. Format as a table. |
| 5 | You are a macros writer. Here is the context: this common scenario [DESCRIBE]. Write three reply templates — first contact, follow-up, and resolution — with [CUSTOMER NAME] and [DETAIL] placeholders, all on-brand and concise. |
| 6 | You are a triage assistant. Here is the context: incoming ticket [PASTE]. Classify it: category, priority (P1–P4 with reason), sentiment, and the team to route to. Suggest the first diagnostic question to ask. Format as labeled fields. |
| 7 | You are a tone editor. Here is my draft reply [PASTE]. Rewrite it to be warmer and clearer, fix any grammar, keep it under [N] words, and preserve every factual detail and step exactly. |
| 8 | You are a support translator. Here is the context: this reply [PASTE]. Translate it into [LANGUAGE] for a customer, keeping a polite, professional register and any product names unchanged. |
| 9 | You are a QA reviewer. Here is the context: this agent reply [PASTE] and our quality rubric [PASTE]. Score it against each rubric criterion, quote evidence, and give one specific coaching tip. Format as a table. |
| 10 | You are a CSAT analyst. Here is the context: these survey verbatims [PASTE, ANONYMIZED]. Summarize what customers praise and complain about most, with three representative quotes per theme and one recommended action. |
Suggested Projects setup
- Support Knowledge Project — load the product help center, troubleshooting guides, tone-of-voice guide, and approved macros so every drafted reply is accurate and on-brand.
- Escalations Project — load the escalation policy, known-issues log, and refund/credit guidelines so sensitive replies stay within policy.
Data-safety caution: Customer messages contain customer PII — strip names, emails, account numbers, and payment details before pasting into any non-integrated tool, and only handle customer data in approved, access-controlled workspaces.
Engineering
Where Claude helps most: writing, reviewing, explaining, and debugging code in the IDE and terminal with Claude Code, and building Claude into your own products via the Developer Platform / API (Console at platform.claude.com). For full setup, model selection, and integration patterns, see your internal developer enablement guide.
The prompts below split into Claude Code (agentic, runs in your repo/terminal) and API / Console (building applications). For day-to-day chat questions, claude.ai works too.
Claude Code (in your repo)
| # | Copy-paste prompt |
|---|---|
| 1 | Explain how [MODULE / DIRECTORY] works in this codebase: the entry points, the main data flow, and the three files I should read first. Don't change anything yet. |
| 2 | Write tests for [FILE / FUNCTION] covering the happy path, edge cases, and error handling, matching the existing test framework and conventions in this repo. Then run them and fix failures. |
| 3 | I'm getting this error: [PASTE STACK TRACE]. Investigate the cause across the relevant files, explain the root cause, and propose a minimal fix before applying it. |
| 4 | Refactor [FILE] to [GOAL, e.g., extract this logic into a reusable service] without changing behavior. Keep the diff focused, preserve the public API, and run the test suite afterward. |
| 5 | Review the changes on this branch for correctness, security, and readability. List issues by severity with the file and line, and suggest a fix for each. Don't commit. |
| 6 | Add [FEATURE] to [AREA OF CODEBASE]. First outline a short plan and the files you'll touch; wait for my go-ahead before editing. |
API / Developer Platform (Console at platform.claude.com)
| # | Copy-paste prompt |
|---|---|
| 7 | You are a senior backend engineer. Write a [LANGUAGE] function that calls the Claude Messages API using model [claude-sonnet-4-6], with retry/backoff, timeout handling, and streaming. Include error handling and brief comments; don't hardcode the API key. |
| 8 | You are an AI engineer. Design a tool-use (function-calling) schema for this capability: [DESCRIBE TOOL]. Give the JSON tool definition, the system prompt, and the loop that handles tool_use / tool_result. |
| 9 | You are a prompt engineer. Here is my current system prompt [PASTE] and three failing inputs [PASTE]. Diagnose why it misbehaves and rewrite it with clearer role, constraints, and output format. Explain each change. |
| 10 | You are a solutions architect. I need to [USE CASE, e.g., summarize 10k support tickets/day]. Recommend a model from Opus 4.8 / Sonnet 4.6 / Haiku 4.5 with a cost-vs-quality rationale, and sketch the pipeline, including where to add prompt caching and batching. |
Suggested Projects / context setup
- Repo context (Claude Code) — keep a
CLAUDE.mdat the repo root describing architecture, conventions, build/test commands, and "do not touch" areas so Claude Code follows house standards automatically. (See your internal developer enablement guide.) - API Reference Project (claude.ai) — load your API style guide, model-selection cheat sheet, and example service code so engineers can draft and review integration code against your own standards.
Data-safety caution: Don't paste secrets, API keys, customer data, or proprietary source into chat tools that aren't approved for it; use environment variables and your secrets manager, and keep regulated or confidential code in approved environments only.
See the prompt library for cross-functional templates. Verify model IDs and pricing at platform.claude.com before formal use.