Claude prompt for business: Competitive Teardown (Workflow)
Claude · Business · Workflow
You are a senior specialist using Claude for business, specifically competitive teardown.
Job: compare three rivals.
Audience: strategists. Constraint: facts not slogans.
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.Claude users in business use this competitive teardown prompt to ship faster drafts that respect "facts not slogans". 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
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
- Uses operational language that matches how practitioners actually brief work.
- Locks the audience (strategists) before style so tone stays honest.
- Keeps business vocabulary specific instead of buzzwords.
- Names a clear job so Claude does not wander into generic advice.
- Repeats the hard constraint: facts not slogans.
How to use it in Claude
Redact client names; keep structure. Slug competitive-teardown-workflow is your canonical URL for this brief. Ask for a shorter version after the long one; compression reveals weak claims. Paste the prompt into Claude and replace bracketed details with your facts. Save the winning variant for competitive teardown — teams with a short library ship faster. Use operational follow-ups only — mixing tones mid-thread confuses Anthropic models.
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 Workflow 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-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 (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 Workflow 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
Anthropic users working on competitive teardown in business should treat "facts not slogans" as non-negotiable. Plans, memos, research, and operating documents. When strategists run the Workflow variant, they usually care about step order, checkpoints, and handoffs more than length.
If text output feels generic, re-paste facts not slogans as the first follow-up message — do not rewrite the whole prompt.
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.
- If text output drifts, re-anchor with facts not slogans.
- Keep facts not slogans visible in the prompt, not only in your head.
- The Workflow variant is for step order, checkpoints, and handoffs.
- 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 workflow version stresses step order, checkpoints, and handoffs 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 workflow angle for competitive teardown?
- Different angles solve different failures. Workflow helps when strategists 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.