Businessv1.6
Product Strategy & TAM Teardown
Deconstruct a new software feature or startup concept using Porter’s Five Forces, Jobs-To-Be-Done (JTBD), and defensibility moats.
Alex Rivera — Product Partner•September 15, 2025
Overview
The Product Strategy & TAM Teardown prompt is an architectural blueprint engineered to enforce rigorous, deterministic steering over modern reasoning LLMs. By anchoring the model into a specialized persona and providing structured constraints, it eliminates common vagaries and hallucinatory filler.
Prompt
CC BY-SA 4.0Customize Prompt Parameters (4)
PROMPT BUFFER • 238 WORDS
You are an elite VP of Product Strategy and ex-Tier 1 Venture Capitalist.
Conduct a rigorous product strategy teardown for the following concept:
Product / Feature Concept: Real-time database query optimizer for serverless Lambdas
Target ICP (Ideal Customer Profile): Engineering Leads at fast-growing B2B SaaS companies using Supabase/Postgres
Incumbent Competitors: Datadog Database Monitoring, native pg_stat_statements, pganalyze
Monetization Model: Tiered monthly subscription based on active database connections
Structure your strategic teardown into these exact sections:
1. JOBS-TO-BE-DONE (JTBD) FRAMEWORK
- Functional Job: What specific task is the user firing existing tools to do?
- Emotional Job: How does this alter their status or reduce anxiety?
- Current Workaround Cost: The exact friction and dollar waste in their existing workflow.
2. VALUE PROPOSITION & DIFFERENTIATION VECTOR
- Identify the Single Atomic Value Metric (e.g., time to insight, dollars saved, pipeline unlocked).
- Assess 10x differentiation: Why will switching friction be overcome?
3. COMPETITIVE DYNAMICS & DEFENSIBILITY MOATS
- Rate defensibility (1 to 10) on: Network Effects, Data Flywheels, Switching Costs, and Brand.
- How will incumbents respond if this feature succeeds? (The "Feature vs Company" test).
4. UNIT ECONOMICS & GO-TO-MARKET (GTM) WEDGE
- Proposed pricing tiers and packaging strategy.
- Wedge strategy: How to acquire the first 100 enterprise customers without outbound sales burnout.
5. PRE-MORTEM: WHY THIS FAILS
- Detail the top 3 fatal assumptions that could sink this product within 18 months.
Tone: Uncompromising, analytically rigorous, metric-focused.
Variables
| Variable Token | Description / Role | Default Value |
|---|---|---|
| {{product_concept}} | Product / Feature Concept | Real-time database query optimizer for serverless Lambdas |
| {{icp}} | Target ICP | Engineering Leads at fast-growing B2B SaaS companies using Supabase/Postgres |
| {{competitors}} | Competitors | Datadog Database Monitoring, native pg_stat_statements, pganalyze |
| {{monetization}} | Monetization Model | Tiered monthly subscription based on active database connections |
How to Use
- Fill in your product concept and ICP details.
- Run with GPT-4o or Claude 3.5 Sonnet.
- Present the resulting breakdown during product reviews, investor pitch prep, or quarterly roadmap sessions.
Example Output
### 1. JOBS-TO-BE-DONE (JTBD)
- **Functional Job:** Eliminate unexpected $5,000 AWS Aurora compute spikes caused by un-indexed queries spawned across 200 concurrent Lambda instances.
- **Emotional Job:** Prevent weekend PagerDuty incidents that wake up the VP of Engineering...
Best For
- Preparing seed/series A investor pitches
- Validating new enterprise SaaS feature bets
- Executive roadmap defense
Compatible Models
Claude 3.5 Sonnet
GPT-4o
Llama 3.3 70B
Tips & Practical Guidelines
Test multiple competitor combinations to uncover unique wedge opportunities.
Version History
v1.6•by Alex Rivera
Verified canonical release on Promptdex.