The best Claude prompts for business give the model three things most people leave out: real context about your company, a defined role, and a concrete output format. Get those right and Claude stops producing generic MBA-speak and starts producing documents you can actually take into a meeting. Below are the business prompts I use every week — for strategy, operations, communication, and decision-making — each ready to copy, paste, and adapt.
TL;DR:
• Every prompt here follows the same skeleton: role + business context + task + output format.
• Replace the [BRACKETED] placeholders with your specifics — vague inputs produce vague strategy.
• Paste real numbers (revenue, headcount, churn) whenever you can; Claude reasons far better with data than with adjectives.
• For recurring work, save your company context once in a Project so you never re-type it.
How to Use Claude Prompts for Business Work
After using Claude extensively for client strategy work, the pattern is clear: the quality of the output tracks the specificity of the input almost linearly. A prompt like “help me with my business strategy” gets you a listicle. The same request with your market, revenue stage, team size, and constraints gets you something worth editing rather than discarding.
Three habits make the prompts below work harder. First, state the role (“act as a fractional COO”) — it anchors vocabulary and priorities. Second, paste real artifacts: a P&L summary, a meeting transcript, last quarter’s OKRs. Claude’s current models handle a 1M-token context window, so a 40-page document is not a problem. Third, define the deliverable: “a one-page memo with a recommendation and three risks” beats “your thoughts.” If you’re new to structuring requests this way, the ultimate Claude prompts library covers the underlying technique in depth, and Anthropic’s own prompt engineering documentation is worth one careful read.
Strategy and Planning Prompts
1. The strategy memo. My most-used business prompt. It forces a recommendation instead of a survey of options.
Act as a strategy consultant preparing a memo for our leadership team.
Company context: [WHAT YOU SELL], [ANNUAL REVENUE], [TEAM SIZE], [MAIN MARKET].
Decision we face: [DESCRIBE THE DECISION, e.g. "expand to the DACH market vs. deepen US mid-market"].
Constraints: [BUDGET, TIMELINE, TEAM CAPACITY].
Write a one-page memo with: (1) a clear recommendation in the first sentence, (2) the three strongest arguments for it, (3) the single strongest argument against it and why it doesn't win, (4) what we'd need to see in 90 days to know we were wrong.2. SWOT that isn’t useless. Standard SWOT prompts produce filler. Forcing evidence fixes that.
Run a SWOT analysis for [COMPANY/PRODUCT] in [MARKET]. Rules: every item must cite a specific fact from the context I've given you (no generic entries like "strong team"). Limit each quadrant to the 3 highest-impact items, ranked. End with the one strategic move the analysis most strongly implies.
Context: [PASTE COMPANY DETAILS, RECENT METRICS, COMPETITOR NOTES]3. Competitive teardown.
Compare [YOUR COMPANY] against [COMPETITOR A] and [COMPETITOR B] on: pricing model, target customer, core differentiator, and biggest weakness. Present as a table, then answer: where are we genuinely differentiated, and where are we pretending to be? Base your analysis only on the materials I paste below.
[PASTE COMPETITOR PRICING PAGES / POSITIONING COPY]4. Quarterly OKR draft.
Draft OKRs for [TEAM] for [QUARTER]. Company objective: [TOP-LEVEL GOAL]. Last quarter's results: [PASTE]. Write 2 objectives, each with 3 measurable key results that a skeptical board member couldn't call vanity metrics. Flag any KR the team can't directly influence.Operations and Process Prompts
5. Process documentation from a brain dump. This one alone justifies a Claude Pro subscription for most operations managers I know — it turns rambling voice-note transcripts into clean SOPs.
Below is an unstructured description of how we currently do [PROCESS]. Turn it into a numbered SOP with: owner per step, tools used, expected time per step, and failure points marked with ⚠. Then list the 3 steps most worth automating and why.
[PASTE BRAIN DUMP OR TRANSCRIPT]6. Bottleneck diagnosis.
Act as an operations consultant. Here is our workflow from [START POINT] to [END POINT], with average time per stage: [PASTE STAGES + TIMES]. Identify the bottleneck, estimate the throughput gain from fixing it, and propose the cheapest intervention first. Assume we cannot hire.7. Vendor comparison matrix.
We're choosing between [VENDOR A], [VENDOR B], and [VENDOR C] for [NEED]. Our requirements, weighted: [LIST REQUIREMENTS WITH IMPORTANCE 1-5]. Build a weighted scoring matrix from the materials below, show the math, and state which vendor wins and under what assumption that flips.
[PASTE VENDOR PROPOSALS / PRICING]8. Meeting-to-action converter.
Here is a meeting transcript. Extract: (1) decisions made, (2) action items as a table with owner and deadline, (3) open questions nobody answered, (4) anything that contradicts a decision from a previous meeting (context below). Keep it under 300 words.
Transcript: [PASTE]
Previous decisions: [PASTE IF ANY]Communication and Stakeholder Prompts
9. The difficult email.
Draft an email to [RECIPIENT + RELATIONSHIP] about [SENSITIVE TOPIC, e.g. a price increase, a missed deadline, ending a contract]. Goals: preserve the relationship, be direct in the first two sentences, offer one concrete next step. Tone: professional, warm, zero corporate euphemisms. Under 150 words. Give me two versions: one firmer, one softer.10. Board/investor update.
Write a monthly investor update from these raw notes: [PASTE METRICS + EVENTS]. Structure: headline metric movement, 3 wins, 2 challenges (stated honestly, with our response), 1 specific ask. Tone: confident but candid. 400 words max.11. Announcement translator. Write once, communicate three ways.
We are announcing [CHANGE, e.g. a reorg, new pricing, a product sunset]. Write three versions: (a) internal all-hands note, (b) customer-facing email, (c) 2-sentence version for the sales team to use verbatim. Each must answer "what changes for me?" in the first three sentences. Facts: [PASTE DETAILS]Analysis and Decision-Making Prompts
12. Pre-mortem. The highest-value 5 minutes before any launch.
We're about to [INITIATIVE]. Run a pre-mortem: it's 12 months later and this failed badly. Write the 5 most plausible failure narratives, each with an early warning sign we could monitor starting this week and one cheap mitigation. Rank by probability × impact.13. Devil’s advocate.
I've decided to [DECISION]. Argue against it as forcefully and specifically as you can — steelman the opposition, don't strawman it. Then tell me which of your counterarguments is strongest and what evidence would settle it. Do not soften your critique with reassurance.14. KPI sanity check.
Here are the KPIs we report monthly: [LIST]. For each, answer: what behavior does this metric incentivize, how could it be gamed, and what counter-metric would catch the gaming? Recommend the 5-metric dashboard you'd actually run this business on.Which Claude Setup Fits Which Business Task
| Business task | Best fit | Why |
|---|---|---|
| Strategy memos, board prep, pre-mortems | Claude Opus 4.8 | Strongest reasoning on multi-constraint decisions |
| Everyday emails, summaries, SOPs | Claude Sonnet 5 | Near-Opus quality at higher speed |
| Recurring work with company context | Projects (Pro plan, $20/mo) | Store context + instructions once, reuse in every chat |
| High-volume automation (report pipelines) | Claude API | Programmatic, scales beyond chat |
If you find yourself pasting the same company context into every chat, that’s the signal to set up a Project with custom instructions — my Claude system prompts guide walks through exactly how. And for a broader look at automating whole workflows rather than single prompts, see Claude for business automation.
Common Mistakes With Business Prompts
- No numbers. “We’re a growing SaaS company” tells Claude nothing. “$1.8M ARR, 11 people, 4.2% monthly churn” changes every recommendation it makes.
- Asking for options when you need a decision. Claude defaults to balanced surveys. If you want a recommendation, demand one explicitly — and demand the counterargument too.
- Treating output as final. Claude drafts; you decide. It doesn’t know your politics, your history with the client, or what the CEO said last week — unless you tell it.
- Pasting confidential data without checking policy. Review your company’s AI usage policy before pasting financials or customer PII into any tool.
- One giant prompt for a multi-step job. Chain instead: analyze first, then decide, then draft the communication. Each step’s output feeds the next.
Next Steps
Steal the three prompts closest to work you did this week, run them with real data, and save the winners into a Project. When you’re ready to extend the same approach to customer-facing work, the 30 Claude prompts for marketing pick up exactly where this library ends — and the full prompts pillar has libraries for every other role.
FAQ
What makes a good Claude prompt for business tasks?
Four elements: a role (act as a CFO), real company context with numbers, a specific task, and a defined output format such as a one-page memo or a table. Prompts missing context produce generic advice; prompts with real metrics produce work you can edit and use.
Which Claude model is best for business strategy work?
Claude Opus 4.8 is the strongest choice for multi-constraint strategy and analysis, while Claude Sonnet 5 handles everyday emails, summaries, and SOPs faster at near-Opus quality. Both are included in the Pro plan at $20/month.
Is it safe to paste company financials into Claude?
Check your company’s AI usage policy first. Many businesses allow it under Team or Enterprise plans, which offer central administration. As a rule, avoid pasting customer PII, and anonymize sensitive figures where the analysis still works without them.
Do I need Claude Pro to use these business prompts?
No — every prompt works on the free plan. Pro at $20/month matters once you hit free-tier usage caps or want Projects, which let you save company context and instructions so you stop re-typing them in every chat.
Can Claude replace a business consultant?
It replaces the first draft of consultant-style work: memos, analyses, SWOTs, and process docs. It cannot replace judgment about your specific market, relationships, and internal politics. Treat it as a sharp analyst who needs your review, not a decision-maker.