Best Claude Prompts for Business, Writing, and Productivity

Claude is not a search engine. The more clearly you define what you want, who it is for, and how you want it formatted, the more useful the output becomes. Vague prompts produce vague results. Specific prompts produce usable work.

This guide gives you tested, copy-and-paste prompts across the tasks where Claude is strongest: writing, research, business analysis, coding, and productivity. Each prompt includes notes on why it works.

New to Claude? Start with What Is Claude AI? before diving into prompts. If you want to understand prompting principles more broadly, read How to Write Better AI Prompts.

How Claude prompts work differently

Claude responds well to prompts that define four things:

• Role or context: What is the situation? Who is asking?
• Task: What exactly do you want produced?
• Format: How should the output be structured?
• Constraints: What should Claude avoid or include?

You do not need all four for simple tasks. But for anything longer than a paragraph, specifying all four consistently produces much better results than just asking a question.

Writing prompts

Blog post from bullet points

Use this when you have research notes and need them turned into readable prose:

I have written the following bullet points on [topic]. Write a 700-word blog section in a direct, informative tone aimed at [audience]. Use subheadings. Do not add facts or claims that are not in my notes. Do not use the words "delve," "tapestry," or "unleash."

[Paste your bullet points]

The instruction to avoid specific buzzwords forces Claude away from its default AI-writing patterns and produces more human-sounding output.

Email — difficult conversation

Write a professional email to [recipient role] explaining that [situation — e.g., a project deadline needs to move by two weeks due to a dependency issue]. Keep it direct and solution-focused. Acknowledge the inconvenience without over-apologizing. Under 150 words.

Newsletter section

Write the opening section of a weekly newsletter for [audience] covering [topic]. Tone: conversational but credible. Length: 120–150 words. Start with a concrete observation or statistic, not a question.

Rewriting for tone

Rewrite the following paragraph. Keep all the information exactly the same. Change the tone from [current tone, e.g., overly formal / passive / hedging] to [target tone, e.g., direct and confident]. Do not change the facts.

[Paste paragraph]

Research and document analysis prompts

Summarize a long document

Summarize the following [document type] in [X] words. Focus on: (1) the main argument or purpose, (2) the three most important findings or recommendations, (3) any key caveats or limitations. Write for an audience of [audience]. Use plain language.

[Paste document]

Extract structured data

Read this document and create a table with the following columns: [Column 1], [Column 2], [Column 3]. Include only entries that relate to [specific topic]. Format as a markdown table.

Compare multiple sources

I am pasting two reports on [topic] below. Identify: (1) where their conclusions agree, (2) where they directly conflict, (3) what each report does not address. Present the findings as a structured list, not paragraphs.

Flag unverified claims

Review the following draft. Flag every factual claim that would require an external source to verify. Do not verify the claims yourself — just list them with the exact sentence they appear in so I can check each one.

Business prompts

SWOT analysis

Using the following context about [company/product/situation], produce a concise SWOT analysis (Strengths, Weaknesses, Opportunities, Threats). Each section should have 3–5 specific, evidence-based bullet points — not generic observations. Context: [paste your context].

Meeting notes to action items

Convert the following meeting notes into a structured action item list. For each action item, identify: the task, the owner (if mentioned), and the deadline (if mentioned). Group by owner. Format as a bulleted list.

[Paste meeting notes]

Executive summary

Write a one-page executive summary of the following report for a senior leadership audience with limited time. Lead with the recommendation, then the key supporting evidence, then the risks. Under 300 words.

Job description

Write a job description for a [role title] at a [company type/size]. The role involves [3–4 main responsibilities]. Required skills: [list]. Tone: professional but human — avoid corporate jargon. Format: summary paragraph, responsibilities list, requirements list, nice-to-haves list.

Coding prompts

Code review

Review the following [language] code. Identify: (1) bugs or logic errors, (2) security issues, (3) performance problems, (4) readability improvements. Be specific. Point to exact lines or functions. Just the code, no explanation of what the code does.

[Paste code]

Write documentation

Write docstrings for every function in the following code. Use [Google/NumPy/reST] docstring format. Include: what the function does, each parameter with type and description, and the return value. Just output the updated code with docstrings added.

Debug from error message

Here is a [language] function and the error message it produces. Identify the root cause of the error, explain it in one sentence, and give me the corrected function. Environment: [e.g., Python 3.11, Node 20].

[Paste code and error]

Productivity prompts

Prioritize a task list

Here is my task list for this week. Re-order it by impact and urgency. Flag anything that can be delegated or dropped. Add a one-sentence note for each task explaining why it is ranked where it is.

[Paste task list]

Prepare for a difficult conversation

I need to have a conversation with [person/role] about [situation]. Help me prepare by: (1) outlining the key points I should cover, (2) anticipating the three most likely objections and suggesting responses, (3) identifying one thing I should avoid saying. Context: [brief background].

Weekly review template

Based on the following notes from my week, produce a structured weekly review. Include: what went well, what did not go as planned, the top three lessons learned, and the three most important priorities for next week. Format as four clearly labeled sections.

Tips that make every Claude prompt better

1. Specify the audience: "Write for a non-technical manager" produces different output than "write for a senior engineer." Always include who will read the output.
2. Give a word or length target: "Under 200 words" or "around 600 words" focuses Claude and prevents both over-explanation and too-brief answers.
3. Say what format you want: Bullet list, numbered steps, markdown table, flowing prose — Claude will match whatever you specify.
4. Tell Claude what to exclude: "Do not include implementation costs" or "avoid technical jargon" shapes the output as much as telling Claude what to include.
5. Iterate in the Artifacts panel: Use Claude's Artifacts feature to refine. "Shorten section 2," "make the tone less formal," and "add a table comparing options" all work well as follow-up prompts on the same output.
6. Paste your content before your question: For document tasks, paste the full text first, then give your instruction. Claude processes the context better when it has the material before the directive.
7. Use an example to define tone: Instead of adjectives ("write formally"), reference a style: "Write in the tone of a Harvard Business Review summary." Claude calibrates to examples better than to vague tone descriptors. One concrete reference is worth three adjectives. This works especially well for rewriting tasks where matching an existing style matters.
8. Chain prompts for complex tasks: For output that needs multiple steps — research, then outline, then draft — break it into separate prompts in sequence. Asking for everything at once often produces a compressed result. Asking step by step produces work you can review and redirect at each stage before committing to the next.

For a deeper dive into prompt strategy across all AI tools, read How to Write Better AI Prompts: A Practical Guide. For Claude-specific research workflows, see How to Use Claude for Research and Document Analysis.

Related: What Is Claude AI? — Claude for Coding — Claude vs ChatGPT