PlaybookPrompts

Produce a structured competitor teardown

Business Strategy competitivestrategy

Most competitor analyses are feature lists. This prompt produces a teardown that surfaces positioning, gaps, and tactical signal you can act on.

Prompt
Produce a structured teardown of this competitor.

Competitor: {{COMPETITOR_NAME}}
What you can observe (public homepage, pricing, recent posts, hiring, customer logos):
{{OBSERVATIONS}}

Structure:
1. POSITIONING — the 1-sentence promise they're making, and to whom.
2. ICP HYPOTHESIS — who they actually serve (which may differ from positioning).
3. PRICING & PACKAGING — the levers they pull, where they leave money on the table.
4. MOAT vs. EXPOSURE — what's defensible, what's vulnerable.
5. RECENT MOVES — what their last 3 product/marketing/hiring signals tell us about strategy.
6. OUR PLAY — 3 specific things WE should do given this teardown.

No guessing without flagging. Mark uncertain claims with [hypothesis].
Variables to fill in
  • {{COMPETITOR_NAME}}
  • {{OBSERVATIONS}}

How to use this prompt

  1. Copy the prompt above (Copy button on the top-right).
  2. Replace each {{VAR}} with your own value. Variables: {{COMPETITOR_NAME}}{{OBSERVATIONS}}.
  3. Paste it into one of the recommended tools below.
  4. Iterate: tighten constraints in the prompt if the output is generic.

Why this prompt is structured this way

The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.

Heads up: some of the links on this page are affiliate links — meaning we may earn a commission if you sign up after clicking, at no extra cost to you. We only recommend tools we'd put on our own stack. You can see our full affiliate disclosure here.

Pair this prompt with a tool

The PlaybookPrompts weekly

One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.

Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.