Quick version: Standard AI is trained to agree with you. This prompt breaks that habit by forcing AI into adversarial mode so it finds your weaknesses before the market does.
The Problem Nobody Talks About
Standard AI wants to be helpful. Feed it your business plan and it will highlight the strengths, paper over the gaps, and send you off feeling ready.
That readiness might be the most dangerous thing it does.
Think about what happens in practice. You paste in your plan. The AI comes back with something like “this is a compelling opportunity with strong market timing.” It flags a couple of minor risks. You leave the conversation feeling validated. Then you spend $30,000 on inventory for a product nobody actually needs.
The problem is structural, not a quirk. AI models are trained on feedback that rewards helpfulness and positivity. When you ask “is my plan good?”, the framing itself pulls the response toward yes. The model is not lying. It is doing exactly what it was optimized to do. That is the trap.
The fix is not a better tool. It is a different role. You stop asking AI to evaluate your plan and start asking it to kill it.
How the Red-Team Approach Works
You assign AI the role of a well-funded competitor. You give it a specific goal: destroy your business in 18 months using a realistic budget. You ask it to name your two biggest vulnerabilities and exactly how it would exploit them.
What comes back is not encouragement. It is a stress test.
The framing matters more than most people realize. When you ask “what are the weaknesses in my plan?”, the AI answers as an advisor. It softens the language, hedges the risks, balances every negative with a caveat. When you ask “how would you destroy this business if you were a competitor?”, it answers as an adversary. That shift in role changes the quality of the output completely. You get specific tactics instead of vague concerns. You get timelines instead of disclaimers.
A good red-team response will name things like: your pricing is vulnerable to a competitor who launches at 30% lower and runs at a loss for 12 months, your customer acquisition depends on one channel that could change its algorithm overnight, your supply chain runs through a single vendor who could cut you off or go directly to your customers. Those are not abstract risks. They are attack vectors.
One Fix That Makes It Actually Useful
The original prompt sets the competitor’s budget at $100M. Problem: nearly any startup can be killed with $100M. That is not a useful finding.
Scale it down to what a realistic competitor in your space could actually deploy. Something like $2M to $5M. Now the weaknesses you find are ones you can genuinely address.
Here is why this matters. If you ask a $100M competitor to come after you, the response will focus on things like “they could outspend you on ads” or “they could hire your entire team away.” True, but so what? You cannot defend against unlimited capital. What you can defend against is a scrappy, well-funded startup that targets your weakest customers first, undercuts you on price in one segment, or builds a feature you have been quietly ignoring for two years.
Matching the budget to your actual competitive landscape forces the AI to get specific. A $3M competitor cannot buy their way in. They have to be clever. That is exactly the kind of threat you need to prepare for, because that is exactly what shows up in the real world.
🎯 Use Cases
- Pre-launch: run this before committing to ads, hires, or inventory. It is cheaper to find the hole in your plan now than after you have spent $50K proving it exists.
- Investor prep: surface the hard questions before the VC room does. Investors are paid to find weaknesses. You want to find them first and walk in with the answers already prepared.
- Pivot decisions: check if your Plan B carries the same vulnerabilities as Plan A. A lot of pivots just move the same core weakness into a new market without fixing anything.
- Competitive strategy: understand what you would do if the positions were flipped. The tactics that could hurt you are usually the same ones you could use against others.
Prompt of the Day
Here is my business plan: [Insert Plan]. Act as a direct competitor with a realistic [$3M] annual budget. Outline a 3-step strategy to make my business obsolete within 18 months. Identify my 2 biggest vulnerabilities and explain exactly how you would exploit each one.
When you run this, pay attention to specificity. Vague answers like “they could build a better product” are not useful. Push back with: “be more specific about the exact feature gap and how you would communicate it to my customers.” The more concrete the attack, the more actionable your defense.
Finding the Kill Switch Early
This is not pessimism. It is discipline.
The businesses that survive long enough to matter are the ones that found their weak points before anyone else could. Not because they were lucky. Because they went looking.
When the red-team prompt surfaces something uncomfortable, that is the signal to act. Shore up the vulnerability, build the moat, fix the dependency before it becomes a crisis. Then run the prompt again after your next big decision. New hires, new markets, new pricing models all create new attack surfaces. The exercise is not a one-time thing. It is a habit.
Most founders spend more time pitching their strengths than understanding their weaknesses. The ones who last flip that ratio. Run this prompt. Fix what it surfaces. Then run it again after every major change.
That is the actual job.
Frequently Asked Questions
Q: Isn’t a $100M competitor budget unrealistic?
Good catch. The $100M is an extreme stress-test to uncover worst-case vulnerabilities, but most real competitors won’t have that firepower. For more realistic scenarios, use the actual funding your competitors have raised, or cap it at what market dynamics would realistically allow. This shifts the exercise from theoretical kills to edge cases they could actually exploit.
Q: How do I scope the competitor budget to my industry?
Look at what your real competitors have spent on major competitive moves, acquisitions, feature launches, marketing blitzes. Use that as your baseline, then ask what would happen if they raised an additional round or two. Some founders found success using 2-3x their own runway as the cap: scary enough to force hard thinking, but not pure fiction.
Q: What’s the difference between theoretical and realistic vulnerabilities?
Theoretical: “They could hire 500 engineers and rebuild our product in six months.” Realistic: “They have the budget to launch a focused feature that captures our primary use case before we hit Series B.” The second actually tells you what to defend against and how to pivot before it becomes a problem.
The ‘Red-Team’ Strategy for Business Plans.
by u/Significant-Strike40 in PromptEngineering