AIO APEX
Claude Opus 4.8A product manager is heading into a quarterly strategy review tomorrow and needs to brief leadership on why a competitor just won three of their top prospects — and what to do about it. She has 20 minutes to prepare.Startups & Business

Cartographiez la stratégie de n'importe quel concurrent en 15 minutes avec ce briefing d'intelligence structuré

Partager:
Cartographiez la stratégie de n'importe quel concurrent en 15 minutes avec ce briefing d'intelligence structuré

Pourquoi ce prompt est important

Teams without systematic competitive intelligence default to gut feel — which means competing on the wrong dimensions, mispricing, and building features that solve yesterday's battle. A rigorous competitive brief takes experienced consultants days to assemble. This prompt compresses that into 15 minutes, reserving your strategy time for the decisions that actually require human judgment.

À quoi nous l'utilisons

A product manager is heading into a quarterly strategy review tomorrow and needs to brief leadership on why a competitor just won three of their top prospects — and what to do about it. She has 20 minutes to prepare.

Prompt

Act as a senior strategy consultant with 15+ years of experience in competitive intelligence. You specialize in synthesizing publicly available information into clear, actionable competitive briefs for product and business leaders.

Company to analyze: [COMPETITOR NAME]
My company: [YOUR COMPANY NAME]
Our market: [DESCRIBE YOUR MARKET/CATEGORY IN 1-2 SENTENCES]
Our key product: [YOUR MAIN PRODUCT AND VALUE PROPOSITION]
Time horizon: [e.g., next 6 months / next 12 months]

Using publicly available information about [COMPETITOR NAME], produce a structured competitive intelligence brief with the following five sections:

1. POSITIONING ANALYSIS
- Core value proposition and primary customer segment
- Key messaging themes based on their website, marketing materials, and press releases
- Pricing tier and business model

2. PRODUCT & FEATURE MAP
- Their top 5 capabilities or features they emphasize most
- Recent launches or announcements in the last 6-12 months
- Obvious gaps: areas they are clearly NOT competing in

3. STRENGTHS & VULNERABILITIES
- Three specific competitive strengths, each with supporting evidence
- Three specific vulnerabilities or weaknesses, each with clear reasoning
- Where their customers complain most, based on public reviews and community feedback

4. STRATEGIC MOVES TO WATCH
- Two or three likely strategic moves they will make over your stated time horizon, with reasoning
- Any signals from hiring patterns, recent funding, partnerships, or acquisitions that reveal intent

5. OUR RESPONSE PLAYBOOK
- Where we can win against them today, specifically
- Where we should avoid direct competition and why
- One concrete initiative or positioning change that would exploit a gap in their current strategy

Constraints:
- Be specific, not generic. Ground every claim in evidence or clear inference — no vague observations.
- Make a call. Do not hedge with "it remains to be seen" or "time will tell."
- If specific information is unavailable, say so explicitly rather than guessing.
- Keep each section to 3-5 bullets maximum. Dense and useful beats comprehensive and padded.

Résultat

COMPETITOR INTELLIGENCE BRIEF: Notion
Prepared for: AI-native engineering knowledge management platform
Time horizon: Next 6 months

1. Positioning Analysis

  • Core value proposition: "All-in-one workspace" unifying documents, databases, wikis, and project tracking. Primary segment: knowledge workers and small-to-midsize teams looking to consolidate tools.
  • Messaging themes: Flexibility, customization, "company wiki that works." Heavy use of community templates to drive viral growth and reduce time-to-value for new users.
  • Pricing: Free → Plus ($12/user/mo) → Business ($18/user/mo) → Enterprise (negotiated). Low entry price compensates for a steep learning curve; enterprise sales motion added in 2025.

2. Product & Feature Map

  • Top capabilities: Nested page hierarchy, relational databases, public page sharing, Notion AI (generative drafts, Q&A over workspace), and API for custom integrations.
  • Recent launches: Notion AI upgraded with connected data Q&A; Notion Sites (publish workspace pages as a public website); calendar view; deeper Slack integration.
  • Clear gaps: No native code execution, no semantic search across file attachments, weak Git and PR integration, no automated runbook triggering, no version control for database tables.

3. Strengths & Vulnerabilities

Strengths:

  • Brand recognition among knowledge workers is extremely high — organic template sharing drives low-CAC growth that competitors can't replicate easily.
  • Database flexibility lets power users build surprisingly complex internal tools without engineering support.
  • Notion AI is native, not bolted on — reducing friction for teams already in the product who want to add AI workflows.

Vulnerabilities:

  • Engineering teams consistently report slow load times on large pages and unreliable offline sync (dominant complaint on G2 and Reddit threads, Q1–Q2 2026).
  • No version history for database records — a hard blocker for teams treating their wiki as a system of record.
  • "Built for everyone" positioning is structurally limiting: engineers feel Notion is designed for marketing and operations teams, not for them. Notion cannot fix this without alienating their core base.

4. Strategic Moves to Watch

  • Doubling down on Notion AI's Q&A feature to position the product as "company brain" — reducing search friction and increasing daily active use. Expect major AI feature announcements at their annual event.
  • Aggressive enterprise sales expansion: 15+ Account Executive job postings observed in Q2 2026, targeting deals above $50K ARR. Expect more enterprise-grade compliance and admin features.
  • Likely GitHub or Linear integration deepening based on API team headcount growth — an attempt to close the developer experience gap without restructuring the core product.

5. Our Response Playbook

  • Win today: Target engineering teams who tried Notion for runbooks, ADRs, and incident docs and abandoned it. Their frustration is structural — Notion's "generalist" architecture cannot serve engineers natively without a full product redesign.
  • Avoid: Competing on general document creation or visual page building. Notion owns that territory and has a brand moat.
  • Exploit: Run messaging around "your runbooks stay current automatically" — the specific pain Notion's static pages cannot solve. Offer a free Notion migration tool to reduce switching friction for engineering teams already invested in the Notion ecosystem.

L'analyse concurrentielle fait partie de ces tâches que tout le monde sait devoir faire rigoureusement et que presque personne ne fait. Le résultat habituel est soit un tableur de comparaison de fonctionnalités (qui rate complètement la stratégie), soit une diapositive vague sur les "acteurs clés du secteur" (qui ne donne rien d'actionnable à la direction).

Ce prompt produit un véritable briefing de renseignement concurrentiel dans le format que les consultants en stratégie utilisent réellement : analyse de positionnement, cartographie des lacunes produit, forces et vulnérabilités avec preuves, signaux stratégiques prospectifs, et un plan de réponse concret. Le résultat est conçu pour les décisions, pas pour le classement.

Ce qui rend ce prompt efficace

Le prompt impose de la spécificité à chaque étape. Chaque section exige des preuves ou la reconnaissance explicite que les preuves ne sont pas disponibles — ce qui élimine le remplissage générique qui rend la plupart des analyses générées par IA inutiles. La section "Mouvements stratégiques à surveiller" utilise les signaux d'embauche, les schémas de financement et l'activité de partenariat comme proxies d'intention, ce qui est exactement la façon de travailler des analystes de renseignement professionnels.

La structure en cinq sections reflète la manière dont les consultants en stratégie expérimentés cadrent le travail concurrentiel : comprendre le monde du concurrent avant de décider comment y répondre. La section Plan de réponse est la dernière par conception — les réponses stratégiques n'ont de sens qu'une fois que vous comprenez à quoi vous répondez réellement.

Quand l'utiliser

Ce prompt est le plus utile avant la planification trimestrielle, avant d'entrer dans un nouveau segment de marché, lorsqu'un concurrent lance un produit nouveau significatif, ou lorsque vous vous préparez à une conversation avec un investisseur qui inclura inévitablement "comment voyez-vous la concurrence ?".

Il fonctionne mieux avec Claude Opus 4.8 ou GPT-5, qui ont un contexte et une profondeur de raisonnement suffisants pour synthétiser les multiples dimensions demandées par ce prompt. Pour des analyses concurrentielles rapides, Claude Sonnet 4.6 est un substitut raisonnable.

Comment le personnaliser

Remplacez les cinq champs entre crochets en haut. Plus votre description du marché et votre proposition de valeur sont spécifiques, plus le plan de réponse sera ciblé. Si vous souhaitez que l'analyse se concentre sur une dimension spécifique — par exemple, uniquement le pricing et la stratégie go-to-market — ajoutez une contrainte en bas du prompt spécifiant ce qu'il faut souligner.

Pour un suivi concurrentiel récurrent, exécutez ce prompt chaque mois pour chacun des 3 principaux concurrents et comparez les résultats d'un trimestre à l'autre. Les changements dans leur messaging et leurs priorités produit révèlent souvent des pivots stratégiques 3 à 6 mois avant les annonces publiques.

ai-promptsproduct-strategyBusiness Strategycompetitive-analysismarket-research
Partager: