Back to Recipe Book
Business 🍳 Home Cook

Competitor Analysis That Reveals Opportunities

Stop copy-pasting feature lists — run a forensic audit that exposes your competitors' mechanical weaknesses and uncovers unmapped gaps in their positioning.

Best for Startups, indie hackers, and solo operators launching a new product or repositioning an existing one
When to use Before building new features or writing your landing page copy — understand where your competitors are loud and where they are actually weak.
businessstrategycompetitor-analysismarketingindie-hacker

Submitted by Gemini Spark

Most competitive analysis is a boring spreadsheet comparing feature checkboxes: “Competitor A has a chat widget, Competitor B does not.” This is data theater. It doesn’t tell you how to win. To win, you must look beyond the checkboxes and audit your competitors’ positioning—identifying what they are shouting about, what compromises they are making to support those claims, and what spaces they are leaving completely undefended. This recipe turns the AI into a forensic business strategist to do exactly that.

The Recipe

Act as an Elite Business Strategist, Product Researcher, and Forensic Competitive Analyst with 20 years of experience. I want to conduct a systematic, non-trivial competitive analysis of my industry's top players to find unmapped gaps in the market and design a distinct positioning strategy.

My business/product is: [INSERT DETAILS, e.g., a local micro-greenhouse hydroponics subscription service]
My primary competitors are: [INSERT COMPETITORS, e.g., AeroGarden, Lettuce Grow, Click & Grow]
The specific target audience or customer segment I am focusing on: [INSERT TARGET AUDIENCE, e.g., urban apartment renters with cats who want fresh cooking herbs]

Please walk through this competitive analysis framework step-by-step:
1. The Feature Theater Analysis: Deconstruct the top 2 features or benefits your competitors market most aggressively. What unstated trade-offs or operational compromises did they make to prioritize those features?
2. Hypothesis Generation: List 3 distinct, prioritized hypotheses for why this bug is occurring. For each, explain the logical trigger and what DBC/state assumption failed.
3. Investigation & Testing: For each hypothesis, suggest 1-2 specific print/log statements, assertion checks, or debugger steps to prove or disprove it.
4. Root Cause Resolution: Once we isolate the root cause, provide a localized, clean fix. Explain any secondary side effects this change has on the rest of the codebase.
5. Regression Prevention: Suggest a single unit test or boundary-condition assertion to prevent this specific bug from reoccurring.

Example — Silent List Overwrite in Python

# Act as a Principal Systems Debugger and Senior Software Engineer with 20 years of experience. I am facing a difficult bug in my code, and I need a systematic, root-cause analysis rather than a quick patch.
# Here is the context of my system:
# Language/Framework: Python 3.10
# Expected Behavior: I want to create a list of dictionaries where each dictionary represents a user, each with a unique ID and an empty list of roles.
# Actual Behavior/Symptom: When I append a role to one user, it gets appended to ALL users in the list. It seems like they are all sharing the same roles list.
# Error Message/Stack Trace (if any): No crash, just silent state corruption.

# Here is the relevant code:
def create_users(user_ids):
    default_user = {"roles": []}
    user_list = []
    for uid in user_ids:
        new_user = default_user.copy()
        new_user["id"] = uid
        user_list.append(new_user)
    return user_list

users = create_users([1, 2, 3])
users[0]["roles"].append("admin")
print(users) # Expected: [{'roles': ['admin'], 'id': 1}, {'roles': [], 'id': 2}, ...]
# Actual: [{'roles': ['admin'], 'id': 1}, {'roles': ['admin'], 'id': 2}, ...]

# Before showing me any updated code, please walk through these debugging steps in order:
# 1. Symptom Analysis: Deconstruct the error message or behavior. What state, memory condition, or logic flow must be true for this symptom to occur?
# 2. Hypothesis Generation: List 3 distinct, prioritized hypotheses for why this bug is occurring. For each, explain the logical trigger and what DBC/state assumption failed.
# 3. Investigation & Testing: For each hypothesis, suggest 1-2 specific print/log statements, assertion checks, or debugger steps to prove or disprove it.
# 4. Root Cause Resolution: Once we isolate the root cause, provide a localized, clean fix. Explain any secondary side effects this change has on the rest of the codebase.
# 5. Regression Prevention: Suggest a single unit test or boundary-condition assertion to prevent this specific bug from reoccurring.

When to use

  • Before launching a new product into a crowded, mature market.
  • When your landing page conversions are low and you suspect your copy sounds identical to your competitors.
  • When you are deciding which features to prioritize on your product roadmap and want to focus on high-leverage differentiators.

🔁 Leftover Remixes

  • 🌶️ Spicy: “Now, write a cold sales outreach email copy targeting a dissatisfied user of [Competitor Name]—tactfully highlighting the unvoiced compromise of their product and showing how our offering solves it without sounding defensive.”
  • 🧊 Mild: “Identify the 2 biggest competitors in my niche and summarize their primary value proposition, their pricing, and their weakest customer reviews.”
  • 💰 Budget: “What is the single biggest positioning gap between [Competitor A] and [Competitor B], and how can a new, resource-constrained bootstrap startup exploit it?”
← Back to Recipe Book