These are the prompts we actually use across our 200+ enterprise deployments — not theoretical examples, but battle-tested formulas refined through thousands of real business interactions with Claude. Each one includes the exact format, a usage note, and the key variable you can swap in.
The Core Prompt Formula
Before the cheat sheet, here's the formula behind all 30 prompts. Every high-performance business prompt contains these four components:
- Role: "You are a [role] with expertise in [domain]"
- Context: The background Claude needs to understand the task
- Task: The precise action you want Claude to perform
- Format: The specific output structure you need
When any of these four elements is missing, output quality drops. The most common failure is omitting the Format — leaving Claude to guess at structure, which produces inconsistent results across users.
Free White Paper
Get 50 More Prompt Templates
Our white paper includes 50 department-specific templates, a prompt testing framework, and governance guidelines for deploying prompts at scale.
Download Free →Universal Business Prompts
Meeting Summary
Executive Meeting Summary
You are an executive assistant who specializes in clear, action-oriented meeting summaries.
Summarize this meeting transcript in the following format:
- DECISIONS MADE: (bullet list of each decision)
- ACTION ITEMS: (person name — task — deadline)
- KEY DISCUSSION POINTS: (3–5 bullets, most important only)
- NEXT MEETING: (date/purpose if mentioned)
Be concise. No filler. If something wasn't discussed, omit the section.
Transcript: {{transcript}}
Email Draft
Professional Email Drafting
You are a senior communications specialist. Draft a professional email with these parameters:
Purpose: {{purpose}}
Recipient: {{recipient_role}}
Tone: {{formal/semi-formal/direct}}
Key message: {{main_point}}
Desired action: {{what_you_want_recipient_to_do}}
Write the email in full. Subject line first. 150–200 words maximum unless the purpose requires more. No filler phrases like "I hope this email finds you well."
Document Summary
Long Document Executive Summary
You are an analyst who specializes in extracting key information for senior executives.
Read this document and produce an executive summary with:
1. PURPOSE (1 sentence: what is this document?)
2. KEY FINDINGS (3–5 bullets, most critical information)
3. RECOMMENDATIONS or DECISIONS REQUIRED (if any)
4. RISKS or CONCERNS mentioned (if any)
5. NEXT STEPS (if defined)
Maximum 300 words total.
Document: {{document}}
Research
Structured Research Summary
You are a business analyst. Research {{topic}} and provide:
1. OVERVIEW: What is it and why does it matter? (100 words)
2. KEY FACTS: 5 specific, verifiable data points
3. MAIN PLAYERS / OPTIONS: Top 3–5 with brief description
4. PROS AND CONS: Balanced assessment
5. RECOMMENDATION: For a {{company_type}} considering {{use_case}}
Cite your reasoning. Flag anything you're uncertain about.
Legal Prompts
Contract Review
Contract Risk Summary
You are a paralegal specializing in commercial contract review. Analyze this contract and produce a risk summary:
RISK LEVEL: [HIGH / MEDIUM / LOW]
HIGH-RISK CLAUSES: (list each with brief explanation of the risk)
UNUSUAL TERMS: (anything non-standard that warrants attorney review)
MISSING PROTECTIONS: (standard clauses absent from this contract)
FAVORABLE TERMS: (terms that benefit our position)
RECOMMENDED ACTIONS: (specific changes to request)
Note: This is preliminary review only. All flagged items should be reviewed by qualified counsel.
Contract: {{contract_text}}
Legal Research
Legal Issue Summary
You are a legal researcher. Provide a plain-language summary of the following legal issue for a non-lawyer business audience:
Issue: {{legal_issue}}
Jurisdiction: {{jurisdiction}}
Context: {{business_context}}
Format:
- PLAIN LANGUAGE EXPLANATION (what this means practically)
- KEY LEGAL CONSIDERATIONS (what matters legally)
- COMMON BUSINESS APPROACHES (how companies typically handle this)
- WHEN TO INVOLVE COUNSEL (specific triggers)
Do not provide legal advice. Flag when professional legal counsel is required.
Free White Paper
Claude for Legal: Complete Department Guide
80+ prompt templates for legal teams covering contract review, research, compliance drafting, NDA automation, and client communications.
Download Free →Finance Prompts
Financial Analysis
Budget Variance Commentary
You are a financial analyst preparing variance commentary for the CFO. Generate professional commentary for this budget variance:
Department: {{department}}
Budget: {{budget_amount}}
Actual: {{actual_amount}}
Variance: {{variance_amount}} ({{variance_pct}}%)
Format:
"[Department] [came in over/under] budget by [amount] ([pct]%) [driven by / due to] [root cause]. [Impact statement or context]. [Forward-looking statement or action]."
Maximum 3 sentences. Use active voice. Include one specific number beyond the variance itself.
Financial Report
Financial Data Interpretation
You are a financial analyst. Analyze these financial metrics and provide:
PERFORMANCE ASSESSMENT: (1–2 sentences: what do these numbers say overall?)
POSITIVE INDICATORS: (2–3 bullets)
CONCERNS: (2–3 bullets, most important first)
COMPARISON TO BENCHMARK: (if benchmarks provided)
RECOMMENDED FOCUS AREAS: (top 2 priorities based on the data)
Data: {{financial_data}}
Benchmark/Context: {{context}}
Marketing Prompts
Content Creation
Email Subject Line Generator
You are a B2B email marketing specialist. Generate 10 subject line options for this email:
Email purpose: {{purpose}}
Target audience: {{audience_role}} at {{company_type}}
Key benefit/hook: {{main_value_prop}}
Tone: {{professional/urgent/curious/direct}}
For each subject line, provide:
- The subject line itself
- A 1-sentence note on the psychological hook it uses
- Predicted open rate tier: [HIGH/MEDIUM/LOW]
Avoid: clickbait, excessive punctuation, spam trigger words.
Content Strategy
Content Brief Generator
You are a content strategist. Create a complete content brief for this piece:
Topic: {{topic}}
Target keyword: {{keyword}}
Audience: {{audience}}
Goal: {{what_should_reader_do_after_reading}}
Funnel stage: {{awareness/consideration/decision}}
Brief should include:
- Recommended headline (3 options)
- Angle/hook
- Outline (H2s and H3s)
- Key points to cover per section
- CTA recommendation
- Internal links to consider
- Word count recommendation
Operations Prompts
Process Documentation
SOP Generator
You are an operations specialist who writes clear standard operating procedures. Create an SOP for:
Process: {{process_name}}
Trigger: {{what_starts_this_process}}
Owner: {{role_responsible}}
Tools used: {{tools}}
End state: {{what_done_looks_like}}
Format as:
1. PURPOSE (1–2 sentences)
2. WHEN TO USE THIS SOP
3. STEP-BY-STEP PROCEDURE (numbered, clear action verbs)
4. DECISION POINTS (if/then logic where relevant)
5. QUALITY CHECK (how to verify it was done correctly)
6. ESCALATION PATH (who to contact if stuck)
Project Management
Project Risk Assessment
You are a project manager. Assess this project for risks and produce a risk register:
Project: {{project_name}}
Scope: {{brief_description}}
Timeline: {{duration}}
Team: {{team_size_and_roles}}
Key dependencies: {{dependencies}}
For each risk identified, provide:
| Risk | Likelihood (H/M/L) | Impact (H/M/L) | Mitigation Strategy | Owner |
Identify at least 8 risks across: timeline, resource, technical, stakeholder, and external categories.
Frequently Asked Questions
What makes a good Claude business prompt?
A good business prompt has four elements: a clear role assignment ('You are a...'), specific context about the task and any constraints, the actual request stated precisely, and a defined output format. Prompts that define all four elements consistently outperform vague requests by 60–80% in our enterprise deployments.
How long should a business prompt be?
The right length depends on task complexity. For simple one-off requests, 2–4 sentences is often enough. For complex, repeatable workflows, system prompts of 200–500 words are common. Claude handles long prompts well — don't artificially shorten if the task genuinely requires more context.
Should I use Claude.ai Projects or API for business prompting?
Claude.ai Projects are ideal for individual and team workflows where you want a persistent system prompt without any coding. The API is best for automated workflows, high-volume processing, and custom integrations. Most enterprise organizations use both: Projects for ad-hoc work, API for production pipelines.
How do I improve a Claude prompt that isn't working?
The most effective debugging approach is to ask Claude directly: 'Here's my prompt and the output I got. What's unclear in my prompt that might have caused this?' Claude can often identify the ambiguity that led to an unexpected output and suggest specific fixes.
Related Articles
Prompt Engineering
50 Business Prompt Templates for Claude
Ready-to-use prompt templates for every major business function.
Prompt Engineering
Few-Shot Prompting for Enterprise
Use examples to teach Claude exactly the output you need.
Prompt Engineering
Enterprise Prompt Engineering Guide
The complete framework for professional-grade Claude prompting.
