> ## Documentation Index
> Fetch the complete documentation index at: https://suprmind.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Red Team Mode: Find the Flaws

# Red Team Mode: Find the Flaws

> **Quick Answer:** AIs attack your idea from six angles - financial, technical, reputational, regulatory, operational, and edge cases. They're deliberately brutal. That's the point.

## What You'll Learn

* How Red Team mode works
* The six attack vectors
* When to use it
* How to present your idea for maximum value
* What to do with the results

## How It Works

1. You present an idea, plan, strategy, or product
2. AIs are assigned different attack vectors
3. Each AI tries to **break** your idea from their assigned angle
4. They don't hold back - this is intentionally adversarial
5. You get a comprehensive view of everything that could go wrong

This isn't balanced analysis. It's a stress test. The AIs are trying to find weaknesses, not validate your idea.

## The Six Attack Vectors

### Financial

*"Will this actually make money?"*

* Unit economics problems
* Revenue model weaknesses
* Market size assumptions
* Customer acquisition cost concerns
* Cash flow and burn rate risks

### Technical

*"Can you actually build and run this?"*

* Architecture weaknesses
* Scalability bottlenecks
* Technical debt risks
* Integration challenges
* Performance concerns

### Reputational

*"How could this damage your brand?"*

* Public perception risks
* How users might misuse the product
* Trust and credibility threats
* Social media exposure scenarios
* Customer backlash triggers

### Regulatory

*"What legal or compliance risks exist?"*

* Data privacy and protection requirements
* Industry-specific regulations
* International compliance differences
* Licensing and IP concerns
* Terms of service vulnerabilities

### Operational

*"What breaks when this meets reality?"*

* Resource and staffing gaps
* Dependency failures
* Process bottlenecks at scale
* Vendor and supply chain risks
* How competitors will respond

### Edge Cases

*"What about the scenarios you haven't considered?"*

* Scale-breaking scenarios
* Unusual user behavior
* Market condition changes
* Cultural and international issues
* Compounding failures across multiple vectors

## When to Use Red Team Mode

| Scenario                              | Why Red Team                            |
| ------------------------------------- | --------------------------------------- |
| Before launching a product            | Find flaws while you can still fix them |
| Before a big investment               | Know what you're risking                |
| Before presenting to leadership       | Prepare for tough questions             |
| When you're too excited about an idea | Force yourself to see the downsides     |
| Before fundraising                    | Anticipate investor objections          |
| After planning a strategy             | Stress-test before committing           |

## Example

**Your message:**

```
Red team this: We're planning to offer unlimited AI conversations
for $29/month. Our competitors charge $49-149/month.
We think aggressive pricing will drive rapid adoption.
```

**Red Team Response (excerpt):**

> **Financial Attack:**
> You're training customers to expect \$29/mo for multi-AI access. When you inevitably raise prices, you'll face massive churn. Companies that undercut on price attract price-sensitive users with the highest churn and lowest expansion revenue. Your margins are too thin to fund the marketing needed to reach premium buyers.
>
> **Technical Attack:**
> "Unlimited" at \$29/mo is a ticking time bomb. A power user doing 200 conversations/month drives significant costs. As adoption grows, so do losses. You'll either need to throttle (breaking the "unlimited" promise) or raise prices (losing the positioning that attracted users).
>
> **Reputational Attack:**
> When you throttle or raise prices, the narrative writes itself: "Company promised unlimited, then pulled the rug." That's a trust-destroying headline on every review site. And the users most likely to be vocal are the power users you'll need to limit first.
>
> **Regulatory Attack:**
> "Unlimited" claims in subscription pricing have drawn scrutiny in multiple jurisdictions. If you throttle after advertising unlimited, you may face consumer protection complaints. Your terms of service need careful legal review.
>
> **Operational Attack:**
> Your competitors will respond. If you're at \$29, they can afford to launch a free tier that matches your feature set for common use cases. They have the margins to subsidize this. You don't.
>
> **Edge Cases:**
> What happens during a viral moment when 10,000 users sign up in a day? Your infrastructure costs spike before revenue recognition. What about enterprise teams buying individual \$29 plans instead of your enterprise tier? You're cannibalizing your own premium pricing.

## How to Present Your Idea

### Give Enough Context

Bad: "Red team my pricing."
Good: "We're a B2B SaaS at \$45K MRR, 200 customers, competing with \[competitors]. Our plan is \[specific plan]. Red team it."

### Be Specific About What You're Testing

Bad: "Red team our startup."
Good: "Red team our decision to expand into Germany before hitting \$1M ARR in the US."

### Include Your Assumptions

"We assume we'll convert 5% of free users to paid. Our CAC is $200. We think the market is $2B. Red team these assumptions."

## What to Do After

Red Team output can feel overwhelming. Here's how to process it:

1. **Sort by severity.** Which flaws could actually kill the project vs. which are manageable risks?
2. **Identify the ones you hadn't considered.** These are the most valuable - they reveal blind spots.
3. **Ask for solutions.** Switch to Sequential mode: "Given the Red Team feedback, how would you fix the top 3 issues?"
4. **Generate a document.** A Decision Record or Executive Brief captures the risks and your mitigation plan.
5. **Revise and re-test.** Fix the critical issues, then Red Team the revised plan.

## Tips

* **Don't take it personally.** The brutality is the feature. You want this feedback now, not after you've invested months.
* **Red Team after Debate, not before.** Debate gives you balanced perspective. Red Team is pure attack. Debate → Red Team → Decision is the optimal flow.
* **The best time to Red Team is when you're most excited.** That's when your blind spots are biggest.
* **Red Team your Red Team.** Ask: "Did the Red Team miss any important attack vectors?"
* **Share results with your team.** Red Team output is excellent for prepping leadership presentations - you'll have answers to every tough question.

## Related Articles

* [How 5 AIs Work Together](/docs/ai-orchestration/how-orchestration-works/)
* [Debate Mode: Test Your Ideas](/docs/ai-orchestration/debate-mode/)
* [Sequential Mode: Deep Analysis](/docs/ai-orchestration/sequential-mode/)
* [Generate a Decision Record](/docs/master-documents/communication-reference/decision-record/)

## Still Need Help?

Reach out to us at [support@suprmind.ai](mailto:support@suprmind.ai) or use the feedback button in the app.