Quick Competitive Intel

Summarize competitor moves and their implications

daily-essentialsbeginnerCompetitive StrategySWOTStrategic Response300-500 words

Customize Your Prompt

Fill in the variables to generate your personalized prompt

Competitor Name

Announcement/News

Our Current Position

Additional Context (Optional)

Ask the assistant to search for current data

Preview

See how your prompt will look with the current variables

[Competitor Name] just announced: [Announcement/News]. We currently position ourselves as [Our Current Position].

Role: Competitive Intelligence Analyst with deep market knowledge.

Instructions:
1. Analyze strategic intent behind this move
2. Assess direct impact on our offerings
3. Identify gaps this exploits in our roadmap
4. Recommend immediate and long-term responses
5. Consider market signaling implications

Specifics:
## Threat Assessment
**Threat Level:** [Critical/High/Medium/Low]
**Timeline Impact:** [Immediate/3-month/6-month]

## Strategic Analysis
**Their Play:** [Possible intent, with supporting evidence and alternatives]
**Market Signal:** [What this tells us about market direction]
**Customer Impact:** [How this affects our customers]

## Our Response Options
**Immediate (This Week):**
- Communication: [Customer/sales messaging]
- Product: [Quick wins to neutralize]

**Short-term (Next Quarter):**
- Roadmap adjustments: [Features to prioritize]
- Positioning: [Message updates needed]

**Strategic (6+ Months):**
- Platform investments: [Foundational capabilities]
- Market expansion: [New segments to target]

Purpose: Inform product strategy and competitive response.

## Web research, when available
- Search for facts relevant to this task, such as current prices, product capabilities, market data, or applicable requirements.
- Prefer primary sources. Cite the source title, direct URL, and publication or data date near each factual claim.
- Match source recency to the claim. Check current prices and capabilities; retain older research when it remains relevant and label its date.
- Explain material differences in definitions, samples, and time periods before comparing benchmarks. Report conflicting evidence and access limits.
- Keep sourced findings separate from assumptions and recommendations. Public research cannot establish private company metrics, customer quotes, or internal commitments.
- If browsing is unavailable or a fact cannot be verified, say so. Do not invent sources or imply a search was completed.

## Evidence and accuracy
- Use supplied facts and verified sources. Do not invent metrics, quotes, people, company details, commitments, or personal experience.
- Mark assumptions [ASSUMPTION], estimates [ESTIMATE: method], and unresolved questions [UNCERTAIN: reason]. Leave unavailable values unfilled rather than guessing.
- Explain confidence as high, medium, or low using the evidence available. These labels are judgments, not calibrated probabilities. Give numerical probabilities only when a stated method supports them.
- Treat preset weights, scores, timelines, and targets in this template as starting examples. Adapt them to the task and explain changes; they are not universal benchmarks or approved commitments.
- Define score scales and directions before calculating totals. Keep units, denominators, and time periods consistent. Do not average away a critical blocker.
- Use only exact supplied or verified quotes with attribution. Label requested fictional examples as illustrative. Distinguish observed behavior from inferred motives or causes.
- Use only the sections and rows the task needs. Write plainly, preserve necessary technical terms, and avoid unsupported benefits or forced specificity.
- Identify missing information needed for a decision. Recommendations remain proposals until reviewed by the responsible team.

What Makes a Good Quick Intel Read

• Clear intent: what they’re signaling vs. what they shipped.
• Threat level with who/when: segments affected and timeline.
• Options by horizon: immediate, next quarter, and strategic plays.
• Positioning response: how we talk to customers and sales this week.
• One owner per action—avoid “somebody should.”

Common Quick Intel Mistakes

• Overreacting to PR without checking distribution, price, or usability.
• Declaring "we must build this" before testing demand with customers.
• Ignoring switching costs and inertia—“do nothing” wins more than you think.
• No owner or timeframe—great ideas quietly expire.
• Copying messaging and drifting off your wedge; you lose your edge fast.

Questions PMs Actually Ask (Quick Competitive Intel)

Competitor just launched X. Do we need to copy it?

Check what shipped, who can use it, and whether customers need it. Customer conversations and usage evidence can help decide whether the roadmap should change.

How do I set the right threat level?

Score by overlap with your ICP, distribution strength, real pricing, and switching costs. A slick demo with weak channels is a "monitor", not a fire drill.

What should we do this week vs. next quarter?

This week: update sales/CS talk tracks, ship a quick win if there’s an obvious hole. Next quarter: prioritize one strategic bet that reinforces your moat—data, distribution, ecosystem.