/ Blog
Home Blog Contact Buddy Ads Builder Audit Engine

My business plan had 12 critical gaps. Here's the Claude ...

Claude & Anthropic

Claude finds gaps in business plans by acting as a structured skeptic when you prompt it correctly. Instead of asking "what do you think?", assign it an adversarial role — a Series A investor, a skeptical CFO — and demand a numbered list of every weak assumption, missing metric, and unanswered question. Run four focused sessions covering financials, competitive dynamics, go-to-market specifics, and operational assumptions, and you will surface gaps you genuinely cannot see yourself.

Key takeaways

  • Asking Claude for general feedback produces polished, diplomatic responses; assigning it an adversarial persona with a specific output format produces actionable gap lists.
  • Four focused sessions — adversarial pass, financial stress test, competitive deep-dive, go-to-market pressure test — cover the full range of common business plan failures.
  • The most dangerous gaps are unexamined assumptions that feel so obvious to the writer they never got written down.
  • Claude's output is a checklist, not a verdict; subject-matter experts and at least one human reader must close the gaps it surfaces.
  • The same methodology transfers directly to campaign strategies, content roadmaps, and paid media plans.
Key terms
Adversarial prompting
A technique where you instruct an AI model to adopt a critical, skeptical role in order to surface weaknesses rather than produce polished or balanced feedback.
Unit economics
The revenue and cost figures tied to a single customer or transaction, such as lifetime value (LTV) and customer acquisition cost (CAC), used to determine whether a business model is fundamentally profitable.
Go-to-market (GTM) plan
A step-by-step plan specifying how a business will reach its target customers and generate its first sales, including channels, messaging, and budget.
LTV:CAC ratio
The ratio of a customer's lifetime value to the cost of acquiring them; a key indicator of whether a business can grow profitably.
Prompt engineering
The practice of carefully structuring the instructions you give an AI model to steer its outputs toward a specific format, tone, or level of analysis.

Why do business plans have so many hidden gaps?

Business plan blind spots exist because the writer already knows the logic — their brain fills in what's missing the same way it does when proofreading their own prose. You lived inside the assumptions when you wrote the plan, so you cannot unsee them. A question along these lines surfaced in the r/ClaudeAI community, where a user discovered 12 critical gaps in a plan they considered solid — things like missing unit economics, vague customer acquisition assumptions, no churn modeling, and a competitive analysis that treated market share as though it were simply waiting to be claimed. None of these are unusual; they are the norm.

Key Insight: Most business plan gaps are not about missing information. They are about unexamined assumptions that feel so obvious to the writer that they were never written down at all. Claude's value is in making those invisible assumptions visible.

A seasoned advisor or CFO can surface these gaps, but they cost money, have limited availability, and often soften criticism to protect the relationship. Claude is available at 3am, has no billable hours, and will not worry about your feelings — provided you prompt it correctly.

Why does the way you prompt Claude matter so much?

Prompt framing determines whether Claude acts as a critic or a cheerleader, and the default is cheerleader. Prompt engineering — the practice of structuring inputs to steer model behavior toward a desired output — has a direct impact on the quality of analysis you receive. [1] When you paste a business plan and ask "what do you think?", Claude is going to be polite, find things to praise, and offer gentle suggestions. You will feel good and walk straight into the gaps you just paid nothing to not find.

Common Mistake: Asking Claude "What do you think of my business plan?" produces a balanced, diplomatic response. That is not a stress test — it is a compliment sandwich. You need to explicitly instruct Claude to be adversarial.

The four-part prompt framework

  1. Assign a persona with stakes. "You are a Series A investor who has seen 400 decks this year and passes on 97% of them. Your job is to find every reason to say no."
  2. Specify the output format. "List every gap, assumption, or weak point you find. Number them. Be specific about what is missing and why it matters."
  3. Define what 'good' looks like. "A fundable plan in this space would have X, Y, Z. Compare what I have written against that standard."
  4. Ask for depth on the worst gaps. After the initial list, prompt: "For gaps 3, 7, and 11 — walk me through what a complete, defensible answer to each would look like."

This approach reliably produces the "oh no" moments you want to have privately, not in front of an investor. If you want to see how others are systematizing these kinds of prompts, the workflow of converting repeatable prompts into Claude skills applies here too.

What are the most common gaps Claude will find?

Across structured prompting sessions, the same categories of weakness appear repeatedly regardless of industry or stage.

Gap Category What Is Usually Missing Why It Is Dangerous
Unit Economics LTV:CAC ratio, payback period Profitable revenue does not equal a profitable business
Customer Acquisition Specific channel assumptions & CPAs "We'll grow via social media" is not a plan
Churn & Retention Monthly churn rate, cohort modeling A leaky bucket kills growth projections
Competitive Moat Why you win when a well-funded player copies you Feature advantages disappear within 18 months
Go-to-Market Specifics First 90 days, first 10 customers Launch plans need ground-level detail
Revenue Model Risks Dependency on a single channel or customer One lost account can be an existential crisis
Regulatory & Legal Industry-specific compliance requirements Discovered late, these become show-stoppers
Team Gaps Missing functional expertise Investors bet on teams, not just ideas
Market Size Math TAM/SAM/SOM methodology Top-down estimates without bottoms-up validation
Financial Model Assumptions Headcount timing, COGS at scale Models break when assumptions do not hold
Customer Validation Actual evidence of willingness to pay Surveys are not purchase intent
Exit or Sustainability Path Long-term outcome for investors or owners No clear answer raises obvious red flags

Claude will not find all twelve in a single pass. Across three or four structured sessions — each focused on a different lens — it is possible to work through the entire list. Claude is a large language model capable of sustained, structured analysis across a long conversation [2], but fresh focused sessions outperform one exhausted mega-thread.

How should you structure the four review sessions?

Practitioners who use Claude for planning tend to converge on a multi-session workflow rather than one giant prompt, and that structure is worth following deliberately.

Best Practice: Run each session as a separate Claude conversation. The context window is large, but focused prompts produce sharper, more targeted analysis than a single thread trying to hold every dimension at once.

Session 1 — The adversarial pass

Paste the full plan and use the investor persona prompt. Ask for a numbered list of every gap, weakness, and unanswered question. Do not defend yourself — just capture the output. If you get fewer than eight items, your prompt was not adversarial enough.

Session 2 — The financial stress test

Focus exclusively on numbers. Ask Claude to surface every assumption embedded in your financial model, including the ones not labeled as assumptions. Then run scenarios: "What happens to Year 3 revenue if customer acquisition cost is 40% higher than projected and churn is 2x your estimate?" A plan that cannot survive a bad quarter is a wish, not a plan.

Session 3 — The competitive deep-dive

Describe your top three competitors in detail. Ask Claude to argue the case for why a customer would choose each competitor over you. Then ask: "What would Competitor A need to do to completely neutralize our advantage, and how long would that realistically take?" This is uncomfortable. That is the point.

Session 4 — The go-to-market pressure test

Take your GTM section and ask Claude to rewrite it with ground-level specificity. Not "we'll partner with influencers" but actual channel mechanics, targeting parameters, and unit economics. If Claude cannot fill in those specifics using your plan's logic, your plan does not have that logic yet. For more on using AI to build out a business from scratch, the discussion around starting a business with AI covers complementary ground.

Does this methodology work for marketing and advertising plans too?

Yes — the same structured skepticism transfers directly to campaign strategies, channel plans, and content roadmaps, and the gaps are often just as significant. I have used Claude to stress-test Google Ads strategies using the same framework: provide the campaign structure, target CPA, audience assumptions, and projected ROAS, then ask it to play a skeptical media buyer who has seen these numbers fail before.

The output consistently flags issues like:

This is the same pattern that drives Buddy, the AI Google Ads agent I have been building on Claude — give the model structured context, assign a critical perspective, and surface what is broken before money is spent finding it the hard way. If you are curious how that kind of AI agent gets built, the write-up on building AI marketing agents with Claude Code goes into the mechanics.

Key Insight: The gap-finding methodology that works for business plans works equally well for campaign strategies, content calendars, product launch plans, and hiring roadmaps. It is a transferable thinking framework, not a one-time exercise.

What can Claude not do in this process?

Being honest about limitations is part of using this tool responsibly. Claude does not have access to your specific market's real-time data, does not know your customer base, and cannot replace a domain expert who has spent twenty years inside your industry. [3] It will tell you what is missing, but it does not feel the consequence of being wrong.

Common Mistake: Using Claude's lack of objection as confirmation that a gap has been filled. Claude will often accept a reasonable-sounding answer even when it does not fully close the logical gap. Ask explicitly: "Is this answer actually sufficient, or am I papering over the problem?"

What to do next

  1. Pull the document now, unpolished. Paste the messier version of your plan into a fresh Claude conversation — that version is closer to what you actually believe, and that is what needs stress-testing.
  2. Run the adversarial pass first. Use the investor persona prompt and demand a numbered list of every gap and weak assumption. Do not soften the brief.
  3. Work through the list deepest gaps first. For each item, ask Claude to show you what a complete, defensible answer would include, then use that as a writing prompt to actually close the gap.
  4. Run the financial stress test in a separate session. Surface every assumption in your numbers, then model a bear case where your two biggest variables are 40–50% worse than projected. If the business fails in that scenario, you need a contingency plan or a different model.
  5. Do a final-pass summary. After revisions, ask Claude to name the three most critical remaining risks. Those three items become the first thing you address proactively with any stakeholder who reads the plan.

Frequently asked questions

How long should each Claude session take when reviewing a business plan?

Each session typically runs 20–40 minutes of active back-and-forth, depending on how deep you go on each gap. Do not rush the financial stress test — working through multiple scenarios for your two or three biggest variables is where the most valuable realizations tend to happen. Four sessions across a few days is more productive than four sessions in one sitting.

Should I share confidential business details with Claude?

Review Anthropic's current privacy and data usage policies before sharing sensitive information. [4] If confidentiality is a concern, you can anonymize specific figures, customer names, or proprietary technology descriptions while keeping the structural logic intact — Claude can still find most structural gaps without knowing exact revenue numbers or client identities.

Can I use Claude to review a business plan if I am not a sophisticated business analyst?

Yes — the structured persona prompts do the heavy lifting. You do not need to know what unit economics are before you start; Claude will identify that they are missing and explain what a complete answer would include. The gap list itself becomes your education in what a fundable plan requires.

Is this different from building a business plan inside ChatGPT?

The adversarial prompting methodology works in any capable large language model. The practical differences come down to response style and context handling. If you have experimented with building a business plan in ChatGPT, the same gap-finding framework applies — the key variable is your prompt quality, not which model you use.

How do I know when the plan is actually ready, not just Claude-approved?

Claude-approved is not the bar. The plan is ready when you have closed each gap with real data or a clear decision, a domain expert has reviewed the sections where they have specific expertise, and at least one human who does not want to spare your feelings has read the full document with the adversarial brief. Claude surfaces the questions; humans validate the answers.

What Claude plan or subscription do I need for this kind of extended analysis?

Extended multi-session business plan analysis works best on a paid plan, where you have higher usage limits and access to the most capable models. [5] The free tier can handle shorter documents, but you are likely to hit rate limits mid-session on a full business plan, which disrupts the analytical flow.

References

  1. Wikipedia. “Prompt engineering.” Accessed Oct 29, 2026.
  2. Wikipedia. “Large language model.” Accessed Oct 29, 2026.
  3. Anthropic. “Intro to Claude.” Accessed Oct 29, 2026.
  4. Anthropic. “Claude Help Center.” Accessed Oct 29, 2026.
  5. Anthropic. “Plans & pricing.” Accessed Oct 29, 2026.
  6. Original community discussion: r/ClaudeAI thread on Reddit.

Related Reading

AI Disclosure: This article was generated with AI assistance based on a community discussion on Reddit r/ClaudeAI. Expert analysis and practitioner perspective by John Williams, Founder, AHMEEGO · Google Ads Practitioner with $350M+ in managed Google Ads spend. AI was used to draft and structure the content; all strategic recommendations reflect real campaign experience.