What This Template Is For
A competitor ships a new feature. Your sales team panics. Your CEO forwards a TechCrunch article with "Thoughts?" in the subject line. Your support team starts getting questions from customers. Everyone has an opinion, but nobody has a plan.
Most competitive responses are reactive and emotional. Teams either overreact (rushing to copy the feature) or underreact (dismissing the threat). Both responses are wrong because they skip the analysis step. Before deciding what to do, you need to understand what the competitor actually shipped, how it affects your customers, and whether it changes your strategic position.
This template provides a structured framework for assessing a competitive move, deciding your response, coordinating cross-functional actions, and communicating the decision. It works for any competitive event: feature launches, pricing changes, acquisitions, or market repositioning.
For building ongoing competitive intelligence, the competitive analysis glossary entry covers the fundamentals. The Product Strategy Handbook covers competitive positioning as part of your broader strategy framework. The go-to-market plan template helps you plan your own launches with competitive awareness. For evaluating whether to build a feature in response, the RICE Calculator helps you score it against other priorities.
How to Use This Template
- Fill out the Competitive Event section within 24 hours of learning about the move. Speed matters for internal alignment, even if your external response takes longer.
- Assess the threat objectively. Talk to customers, review the competitor's actual product (not just their marketing), and quantify the impact on your pipeline and retention.
- Choose a response type deliberately. Not every competitive move requires a product response. Sometimes the right answer is better positioning, a sales battlecard update, or no action at all.
- Coordinate actions across teams. A competitive response is not just a product decision. Sales, marketing, customer success, and support all need to know the plan and their role in it.
- Communicate once, clearly. Send one company-wide message with the assessment, the decision, and the action plan. Avoid multiple conflicting narratives circulating through Slack channels.
- Set a review date to reassess. Competitive dynamics shift. The response you choose today may need adjustment in 30-60 days based on market reaction.
The Template
Competitive Event Summary
| Field | Details |
|---|---|
| Competitor | [Company name] |
| Event type | [Feature launch / Pricing change / Acquisition / Partnership / Repositioning] |
| Date announced | [Date] |
| Source | [Link to announcement, press release, or product changelog] |
| Assessed by | [PM name] |
| Assessment date | [Date] |
| Response deadline | [Date: when does the team need a decision?] |
Event summary. [2-3 sentences describing what the competitor did. Stick to facts.]
Threat Assessment
Score each dimension 1-5. A total score of 15+ warrants an active response. Below 10, monitor only.
| Dimension | Score (1-5) | Evidence |
|---|---|---|
| Customer overlap | [How many of your customers also evaluate this competitor?] | [e.g., "35% of our pipeline mentions them in evaluation. High overlap in mid-market SaaS."] |
| Feature parity threat | [Does this close a gap they had or create a new gap for you?] | [e.g., "Closes their analytics gap. They now match our core reporting feature."] |
| Narrative risk | [Does this change how the market perceives the category or your position?] | [e.g., "Their PR positions this as 'AI-native analytics.' Risk of being perceived as legacy."] |
| Customer impact | [Are existing customers asking about it? Could it drive churn?] | [e.g., "3 enterprise accounts mentioned it in QBRs last week."] |
| Strategic alignment | [Does this move into your core territory or a peripheral area?] | [e.g., "Directly into our core. This is a head-on competitive move."] |
| Total | [Sum] |
Threat level. [Critical (20-25) / Significant (15-19) / Moderate (10-14) / Low (5-9)]
What They Actually Shipped
Go beyond the press release. If possible, get hands-on with the product.
| Question | Answer |
|---|---|
| What is the actual functionality? | [Describe what the feature does based on firsthand testing, demo videos, or documentation] |
| What is the quality level? | [Is it polished or MVP? Does it work well or have obvious gaps?] |
| Who is the target user? | [Enterprise / Mid-market / SMB? Technical / Non-technical?] |
| What is the pricing? | [Is this included in existing plans or an upsell?] |
| What are the limitations? | [What does it NOT do? Where are the gaps?] |
| What is the underlying approach? | [Build, buy, or integrate? What tech are they using?] |
Customer Impact Analysis
Talk to customers before deciding on a response. Their perception matters more than your internal assessment.
Customer signals.
| Signal | Source | Urgency |
|---|---|---|
| [e.g., "Two enterprise accounts asked if we have equivalent functionality"] | [e.g., CS team] | [High / Medium / Low] |
| [e.g., "Prospect paused evaluation to look at competitor's new feature"] | [e.g., Sales] | [Urgency] |
| [e.g., "No customer mentions in past week despite analyst coverage"] | [e.g., Support] | [Urgency] |
Net assessment. [Is this a real customer concern or an internal panic? How many customers are actually affected versus how many we think are affected?]
Response Options
Evaluate at least three options before deciding. Include "do nothing" as a valid option.
| Option | Description | Effort | Timeline | Risk |
|---|---|---|---|---|
| A: No product action | Update positioning and sales materials only. No roadmap change. | Low | 1-2 weeks | Risk of appearing unresponsive if customers keep asking. |
| B: Accelerate existing roadmap item | Pull forward a planned feature that addresses the gap. No new scope. | Medium | [Weeks] | Risk of quality issues if rushed. Delays other roadmap items. |
| C: Build a competitive response feature | New work specifically designed to match or exceed the competitor's move. | High | [Weeks/months] | Risk of being reactive instead of strategic. Opportunity cost on other priorities. |
| D: Differentiate away | Double down on areas where you are already stronger. Change the conversation. | Medium | [Weeks] | Risk of not addressing the direct comparison customers are making. |
Recommended Response
| Field | Details |
|---|---|
| Chosen option | [A / B / C / D or a combination] |
| Rationale | [Why this option? What evidence supports it?] |
| Decision maker | [Name and title] |
| Decision date | [Date] |
| Review date | [When will we reassess? 30 / 60 / 90 days] |
Action Plan
Product actions.
| Action | Owner | Deadline | Status |
|---|---|---|---|
| [e.g., Accelerate real-time analytics feature from Q3 to Q2] | [PM name] | [Date] | ☐ |
| [e.g., Ship "good enough" version as beta within 6 weeks] | [Eng lead] | [Date] | ☐ |
Sales and marketing actions.
| Action | Owner | Deadline | Status |
|---|---|---|---|
| [e.g., Update competitive battlecard with feature comparison] | [PMM] | [Date] | ☐ |
| [e.g., Create "Why Us" one-pager addressing the specific feature gap] | [PMM] | [Date] | ☐ |
| [e.g., Brief sales team on talk track and objection handling] | [Sales enablement] | [Date] | ☐ |
| [e.g., Publish blog post on our differentiated approach] | [Content] | [Date] | ☐ |
Customer success actions.
| Action | Owner | Deadline | Status |
|---|---|---|---|
| [e.g., Proactive outreach to top 20 accounts with our roadmap] | [CS lead] | [Date] | ☐ |
| [e.g., Prepare FAQ for inbound customer questions] | [Support lead] | [Date] | ☐ |
Internal Communication
Company-wide message template.
Subject: Competitive update: [Competitor] launched [Feature]
>
What happened: [1-2 sentence summary of the competitive move.]
>
Our assessment: [1-2 sentences on the threat level and customer impact.]
>
Our response: [2-3 sentences on the chosen response and rationale.]
>
What you need to do: [Specific actions by team: Sales do X, CS do Y, Support do Z.]
>
Questions? Reach out to [PM name] in #competitive-intel.
Filled Example: Responding to Competitor's AI Feature Launch
Competitive Event Summary
| Field | Details |
|---|---|
| Competitor | DataPulse |
| Event type | Feature launch |
| Date announced | March 3, 2026 |
| Source | DataPulse blog: "Introducing AI Insights: Automatic Anomaly Detection" |
| Assessed by | Sarah Kim, Senior PM |
| Assessment date | March 5, 2026 |
| Response deadline | March 12, 2026 |
Event summary. DataPulse launched an AI-powered anomaly detection feature that automatically flags significant changes in product metrics and provides natural-language explanations. The feature is included in their Business plan ($299/mo) and above. It covers event-based metrics only, not revenue or custom metrics.
Threat Assessment
| Dimension | Score (1-5) | Evidence |
|---|---|---|
| Customer overlap | 4 | 40% of our pipeline evaluates DataPulse. High overlap in mid-market B2B SaaS. |
| Feature parity threat | 3 | We have anomaly detection in beta. Theirs is now GA. Closes a marketing gap, not a functionality gap. |
| Narrative risk | 4 | "AI-native analytics" positioning is strong. TechCrunch coverage positions them as innovation leader. |
| Customer impact | 2 | Only 1 customer mentioned it. Most of our accounts do not use DataPulse. |
| Strategic alignment | 4 | Directly competitive with our Q2 roadmap. AI analytics is our core differentiator. |
| Total | 17 |
Threat level. Significant (17/25).
Recommended Response
| Field | Details |
|---|---|
| Chosen option | B: Accelerate anomaly detection GA from Q3 to late Q2, combined with differentiated positioning |
| Rationale | Our anomaly detection covers all metric types (events, revenue, custom), not just events. Accelerating by 6 weeks is feasible without cutting scope. Combined with a positioning update, this neutralizes the threat. |
| Decision maker | James Park, VP Product |
| Decision date | March 10, 2026 |
| Review date | April 15, 2026 |