Claude prompt for business: SWOT Analysis (Workflow)
Claude · Business · Workflow
You are a systems thinker using Claude for business, specifically swot analysis.
Job: map strengths and risks.
Audience: strategy teams. Constraint: evidence for every cell.
Working style: operational. Optimize for step order, checkpoints, and handoffs.
Process:
1. Restate the brief in one sentence and list missing facts as questions.
2. Draft the artifact.
3. Stress-test it against the constraint.
4. Return a final version plus 3 numbered improvements.
Output contract: use headings, short paragraphs, and concrete examples. No filler. No invented statistics.
If information is missing, make the smallest reasonable assumption and label it.Use this Claude business template when strategy teams need swot analysis with the rule: evidence for every cell. Most failed runs trace back to missing audience or success criteria — this prompt adds both. The workflow version uses operational language and targets step order, checkpoints, and handoffs.
When to use this prompt
Claude shines at business work when you state the observable outcome: map strengths and risks. The Workflow framing keeps step order, checkpoints, and handoffs visible while you edit. Pair it with a real sample from your portfolio for best results.
Why this prompt works
- Keeps business vocabulary specific instead of buzzwords.
- Locks the audience (strategy teams) before style so tone stays honest.
- Centers map strengths and risks so success is observable.
- Names a clear job so Claude does not wander into generic advice.
- Forces an output contract: headings, examples, and a final version.
How to use it in Claude
For business work, paste claude handles long briefs, policy-aware writing, and stepwise reasoning as a one-line reminder above the prompt. Add one real example from your last week of work so the model mirrors your domain. Name the success metric aloud: map strengths and risks. If the draft cannot pass it, do not polish prose yet. Plans, memos, research, and operating documents. Keep that context in the thread when you iterate. Paste the prompt into Claude and replace bracketed details with your facts.
Start with the ugly first pass for swot analysis. Name what is wrong in five bullets, then rerun in Claude. For swot analysis in business, the failure mode is usually no example. This prompt blocks that by design — especially "evidence for every cell". Expect two minutes customizing and two minutes editing for Workflow output. Anthropic models still need your facts for swot analysis; they cannot invent metrics or brand rules. operators and founders teams bookmark slug swot-analysis-workflow when step order, checkpoints, and handoffs matters.
Step-by-step
- Open Claude and paste the prompt block unchanged.
- Replace placeholders with your project facts (strategy teams, offer, timeline).
- Confirm the constraint is still visible: evidence for every cell.
- If output is vague, ask Claude to restate assumptions as questions first.
- Reply with one fix list, then regenerate the final version only.
Example output
Example output shape: H1 with SWOT Analysis, 3 short sections, bullet list of recommendations, closing line that states evidence for every cell. Facts you supply appear; nothing invented.
Common mistakes
- Using the Workflow prompt but editing it into a vague one-liner.
- Deleting "evidence for every cell" to save space — that is usually the whole point.
- Pasting confidential data instead of redacted placeholders.
Expert notes
Slug swot-analysis-workflow: a operators and founders-oriented business brief. Plans, memos, research, and operating documents. Pair it with one real asset from your portfolio before the second run.
Refresh quarterly: Claude models change. Keep constraints; update examples. Mark the page stale if evidence for every cell no longer matches policy.
Comparison / variations
| Approach | When | Tweak |
|---|---|---|
| Bare request | You only need a spark | Write a swot analysis piece. |
| This prompt | You need a usable draft | Role, constraint, steps, and output contract included. |
| Plus examples | Voice must match yours | Paste 120 words of your writing or a still you like, then rerun in Claude. |
Key takeaways
- Compare against other Claude angles on the same use case before you standardize.
- strategy teams should recognize themselves in the first paragraph.
- If text output drifts, re-anchor with evidence for every cell.
- Business work needs plans, memos, research, and operating documents.
- Claude improves when you paste a real snippet or reference still.
FAQ
- What is a Claude prompt for swot analysis?
- It is a structured brief that tells Claude how to produce business output for strategy teams. This workflow version stresses step order, checkpoints, and handoffs and keeps "evidence for every cell" in the instructions.
- How do I customize this Claude business prompt?
- Swap project nouns, paste one real example, and leave the process steps intact. The constraint "evidence for every cell" should stay unless your brief truly changed.
- Why use the workflow angle for swot analysis?
- Different angles solve different failures. Workflow helps when strategy teams need step order, checkpoints, and handoffs. It is not longer for its own sake — each line has a job.
- Is this Claude prompt updated for 2026?
- Yes. Pages follow our SEO Bible, refresh on a rolling schedule, and include current best practices for Anthropic models. Always verify facts before client delivery.