Claude prompt for business: SWOT Analysis (Advanced)
Claude · Business · Advanced
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: precise and demanding. Optimize for constraints, evaluation, and edge cases.
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.A strong Claude business swot analysis prompt names the job, audience, and finish line. This page does that for strategy teams. Teams report saving 15–30 minutes per task when prompts include constraints up front. The advanced version uses precise and demanding language and targets constraints, evaluation, and edge cases.
When to use this prompt
Claude shines at business work when you state the observable outcome: map strengths and risks. The Advanced framing keeps constraints, evaluation, and edge cases visible while you edit. Pair it with a real sample from your portfolio for best results.
Why this prompt works
- Separates draft from critique so you can steal the structure later.
- Forces an output contract: headings, examples, and a final version.
- Keeps business vocabulary specific instead of buzzwords.
- Locks the audience (strategy teams) before style so tone stays honest.
- Uses precise and demanding language that matches how practitioners actually brief work.
How to use it in Claude
Save the winning variant for swot analysis — teams with a short library ship faster. When strategy teams review output, they should see constraints, evaluation, and edge cases without hunting for it. Plans, memos, research, and operating documents. Keep that context in the thread when you iterate. Redact client names; keep structure. Slug swot-analysis-advanced is your canonical URL for this brief. Use precise and demanding follow-ups only — mixing tones mid-thread confuses Anthropic models.
Ask for a checklist strategy teams would use. Then grade the draft against map strengths and risks. 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 Advanced 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-advanced when constraints, evaluation, and edge cases 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.
- For business work, paste a rubric and ask for a self-score.
- 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 Advanced 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
This Claude page targets "map strengths and risks" for strategy teams. Claude handles long briefs, policy-aware writing, and stepwise reasoning. The precise and demanding tone keeps constraints, evaluation, and edge cases visible while you edit.
Workflow tip: save three winning outputs for swot analysis and diff them. The shared skeleton becomes your team standard inside Claude.
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
- strategy teams should recognize themselves in the first paragraph.
- Ship a draft, then tighten. Do not chase a perfect first token.
- The Advanced variant is for constraints, evaluation, and edge cases.
- If text output drifts, re-anchor with evidence for every cell.
- State the job (map strengths and risks) in one line before any style talk.
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 advanced version stresses constraints, evaluation, and edge cases 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 advanced angle for swot analysis?
- Different angles solve different failures. Advanced helps when strategy teams need constraints, evaluation, and edge cases. 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.