Claude prompt for business: Competitive Teardown (Common Fixes)
Claude · Business · Common Fixes
You are a senior specialist using Claude for business, specifically competitive teardown.
Job: compare three rivals.
Audience: strategists. Constraint: facts not slogans.
Working style: diagnostic. Optimize for typical failures and how to repair the prompt.
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 strategists need competitive teardown with the rule: facts not slogans. Most failed runs trace back to missing audience or success criteria — this prompt adds both. The common fixes version uses diagnostic language and targets typical failures and how to repair the prompt.
When to use this prompt
For Anthropic models, business prompts fail when they mix strategy and execution. This competitive teardown brief separates the job so you can iterate once, not ten times. Swap only nouns when adapting — keep the process intact.
Why this prompt works
- Repeats the hard constraint: facts not slogans.
- Locks the audience (strategists) before style so tone stays honest.
- Names a clear job so Claude does not wander into generic advice.
- Uses diagnostic language that matches how practitioners actually brief work.
- Centers compare three rivals so success is observable.
How to use it in Claude
Plans, memos, research, and operating documents. Keep that context in the thread when you iterate. This Common Fixes path is for strategists who care about compare three rivals. Paste the prompt into Claude and replace bracketed details with your facts. Name the success metric aloud: compare three rivals. If the draft cannot pass it, do not polish prose yet. Save the winning variant for competitive teardown — teams with a short library ship faster.
Swap the audience once. If the competitive teardown piece still works, the core is solid. For competitive teardown in business, the failure mode is usually missing constraint. This prompt blocks that by design — especially "facts not slogans". Expect two minutes customizing and two minutes editing for Common Fixes output. Anthropic models still need your facts for competitive teardown; they cannot invent metrics or brand rules. operators and founders teams bookmark slug competitive-teardown-fixes when typical failures and how to repair the prompt matters.
Step-by-step
- Open Claude and paste the prompt block unchanged.
- Replace placeholders with your project facts (strategists, offer, timeline).
- Confirm the constraint is still visible: facts not slogans.
- 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 Competitive Teardown, 3 short sections, bullet list of recommendations, closing line that states facts not slogans. Facts you supply appear; nothing invented.
Common mistakes
- Using the Common Fixes prompt but editing it into a vague one-liner.
- Ignoring the output contract headings.
- Skipping the audience (strategists) and hoping Claude infers it.
Expert notes
Slug competitive-teardown-fixes: 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 facts not slogans no longer matches policy.
Comparison / variations
| Approach | When | Tweak |
|---|---|---|
| Bare request | You only need a spark | Write a competitive teardown 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
- Claude improves when you paste a real snippet or reference still.
- Ship a draft, then tighten. Do not chase a perfect first token.
- Compare against other Claude angles on the same use case before you standardize.
- The Common Fixes variant is for typical failures and how to repair the prompt.
- strategists should recognize themselves in the first paragraph.
FAQ
- What is a Claude prompt for competitive teardown?
- It is a structured brief that tells Claude how to produce business output for strategists. This common fixes version stresses typical failures and how to repair the prompt and keeps "facts not slogans" 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 "facts not slogans" should stay unless your brief truly changed.
- Why use the common fixes angle for competitive teardown?
- Different angles solve different failures. Common Fixes helps when strategists need typical failures and how to repair the prompt. 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.