Red-team a strategic proposal to expose fatal flaws

Stress-test an ambitious strategy by surfacing hidden failure modes and unexamined assumptions before committing budget or headcount.

You getFragile Assumptions, catastrophic Failure Scenarios and incentive Mismatches

Prompt

Prompt
Act as an adversarial red-team strategist. Your job is to rigorously critique the proposal provided below to find fatal operational, market, financial, or organizational blind spots.

Rules:
- Identify the top three assumptions that must be true for this plan to succeed, but are unsupported by hard evidence.
- Describe two concrete scenarios where this plan fails catastrophically despite competent execution.
- Highlight any misaligned incentives or friction points between internal teams or external partners.
- Do not soften criticisms with praise or hedge your analysis.

Output format:
1. Fragile Assumptions (table with columns: Assumption, Why It May Fail, How to Test It Now)
2. Catastrophic Failure Scenarios (narrative breakdown of events)
3. Incentive Mismatches
4. Recommended Go/No-Go Gate Criteria

Here is the proposal to red-team:

Example output

Example for: expanding a B2B SaaS tool into self-serve enterprise freemium

1. Fragile Assumptions
AssumptionWhy It May FailHow to Test It Now
Individual contributors will invite teammates without IT approvalEnterprise network policies frequently block unsanctioned browser extensions and data ingestionRun 15 discovery calls specifically with corporate IT and infosec leads
Product-led usage will automatically convert into six-figure enterprise contractsFree users rarely possess procurement authority or discretionary departmental budgetAudit past closed-won enterprise pipeline to trace lead source titles
Support overhead scales linearly with paid tiersMassive free user volumes will overwhelm tier-1 support desks without dedicated self-help infrastructureMeasure current support tickets generated per active non-admin user
2. Catastrophic Failure Scenarios
  • The Support Swamp: Free adoption spikes 400% in month two, dragging senior engineers into triage duty. Feature velocity on core enterprise security commitments stalls, leading to churn among your top five revenue-generating enterprise accounts.
  • The Procurement Wall: Mid-level champions adopt the product widely, but corporate procurement flags missing SOC 2 Type II compliance and vendor risk assessments, permanently banning company domains before sales can negotiate.
3. Incentive Mismatches

Account executives are compensated on large annual contracts and will ignore self-serve users, while product teams will optimize for sign-up volume rather than qualified sales handoffs.

4. Recommended Go/No-Go Gate Criteria

Do not launch the open sign-up flow until you have automated tier-1 onboarding self-service and verified domain-level gating for corporate emails with enterprise security requirements.

Written by AI from this prompt. Your results will vary.

Paste your draft proposal or pitch doc after the prompt in ChatGPT, Claude, or Gemini. Ask the model to role-play a skeptical board member or competitor if you want to push the counterarguments further.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Critical Thinking & Decisions
Critical Thinking & Decisions

Set upfront kill criteria for new initiatives

Establish measurable off-ramps and stop conditions before launching a project. Use this to protect budget and team focus from the sunk cost fallacy.

Critical Thinking & Decisions

Separate luck from skill in past decisions

Break down past wins or losses to see what was sound judgment versus random chance. Use this during retrospectives to avoid rewarding reckless risks or penalizing disciplined bets.