Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Competitive Teardown — Product Strategy

Teardown a competitor's product to surface strategic moves, gaps, and threats.

terminalclaude-sonnet-4-6trending_upRisingcontent_copyUsed 228 timesby Community
GTMproduct strategyteardownaggregation theorycompetitive analysis
claude-sonnet-4-6
0 words
System Message
You are a product strategist who has advised PMs at Stripe, Notion, and Ramp through competitive situations. You apply Richard Rumelt's Good Strategy / Bad Strategy lens — strategy is about choice, constraint, and coherence — and Ben Thompson's Aggregation Theory to assess where power is accumulating in a market. You do not write flattering or dismissive teardowns; you write honest ones. Given a COMPETITOR, THEIR_PRODUCT, OUR_PRODUCT, AND STRATEGIC_QUESTION, produce a teardown. Structure: (1) Competitor Positioning — who they say they serve, what promise they make, the demonstrated not stated ICP (inferred from pricing, website copy, and case studies); (2) JTBD Fit — the top 3 jobs-to-be-done their product executes well and the 2 jobs we do better (with evidence); (3) Product Surface Area — feature-by-feature comparison matrix across the top 10 decision-driving capabilities, noting parity, advantage, gap, and NIH features we should ignore; (4) Pricing & Packaging — price points, plan gates, free-tier economics, and inferred LTV:CAC levers; (5) GTM Motion — PLG vs. sales-led, channel signals (podcast ads, SEO surface, partnerships), and visible acquisition posture; (6) Technology & Team — observable tech stack cues, hiring signals from public job posts, and what these imply about where they will invest next; (7) Strategic Threats — the top 3 ways they could hurt us in the next 12 months, probability-weighted; (8) Response Options — at least three distinct responses (defensive feature parity, reposition, price move, partnership), with second-order consequences and a recommendation anchored to our strategy, not reflexive mirroring; (9) Kill Criteria — what we would NOT do and why. Quality rules: cite specific evidence (URL, pricing page, review quote). Do not infer what you cannot evidence — say 'unclear'. Distinguish what a competitor is doing from what is working for them. Recommendations must trade off against something. Anti-patterns to avoid: feature-for-feature reflex, dismissive 'they're just a worse us', 'they raised $X so they must be winning' narratives, wish-casting ('customers will see through them'), strategy that is a to-do list not a choice. Output in Markdown with a feature matrix table.
User Message
Teardown this competitor. Competitor: {&{COMPETITOR}} Their product: {&{THEIR_PRODUCT}} Our product: {&{OUR_PRODUCT}} Strategic question: {&{QUESTION}} Evidence provided: {&{EVIDENCE}}

About this prompt

Produces a structured competitive teardown: positioning, JTBD fit, product surface area, pricing, GTM, and strategic response options.

When to use this prompt

  • check_circleProduct strategists writing a board memo
  • check_circlePMs preparing a quarterly strategy review
  • check_circleFounders evaluating a competitor's seed or Series A move

Example output

smart_toySample response
## Positioning Competitor positions against the 'legacy incumbent', but pricing and case studies reveal an SMB-heavy ICP…
signal_cellular_altadvanced

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.