Back to guide/Developer Tools

Competitive Landscape Mapping

Gemini's search grounding provides more current competitive data. Claude's structured analysis produces cleaner categorization. The uncertainty language instruction prevents both models from hallucinating market data.

claude-vs-geminiindustry_or_product_categoryspecific_segmentmy_product
Edit View
Prompt
Map the competitive landscape for {{industry_or_product_category}}.

Focus area: {{specific_segment}}
My company/product: {{my_product}} (or "hypothetical new entrant")

Produce:

1. **Market map**: Group competitors into tiers (Leaders / Challengers / Niche / Emerging). List 3-5 per tier with one-line positioning statements
2. **Feature comparison matrix**: Compare the top 5 competitors across {{num_features}} key features. Use a simple rating (Strong / Adequate / Weak / Missing)
3. **Pricing landscape**: Price ranges by tier, pricing model differences (per-seat, usage-based, flat), and where the market is heading
4. **Differentiation gaps**: What is no one doing well? Where is there room for a new approach?
5. **Moats and switching costs**: What keeps customers locked into each major player?
6. **Trend analysis**: 3 trends that will reshape this market in the next 12-18 months

Base this on publicly available information. Where you're uncertain, say "likely" or "estimated" rather than presenting guesses as facts.

Variables to customize

{{industry_or_product_category}}{{specific_segment}}{{my_product}}{{num_features}}

Why this prompt works

Gemini's search grounding provides more current competitive data. Claude's structured analysis produces cleaner categorization. The uncertainty language instruction prevents both models from hallucinating market data.

Save this prompt to your library

Organize, version, and access your best prompts across ChatGPT, Claude, and Cursor.

Related prompts

Code Review Assistant

Get thorough code reviews with actionable feedback tailored to your language, framework, and standards.

Context-Aware Code Completion

Providing the surrounding code and project context lets the model match existing patterns exactly. The constraint against modifying existing code prevents unwanted side effects.

Inline Code Suggestion

Constraining suggestions to match existing style and scope produces insertions that feel native to the codebase. The 'no explanation' rule mimics real inline completion behavior.

Code Explanation

The audience level parameter adjusts complexity automatically. Requiring a usage example ensures the explanation is practical, not just theoretical.