--- name: competitive-brief description: Create a competitive analysis brief for one or more competitors or a feature area. Use when informing product strategy or feature prioritization, building sales battle cards, prepping board or investor materials, or deciding where to differentiate vs. achieve parity. argument-hint: "" --- # Competitive Brief > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). Create a competitive analysis brief for one or more competitors or a feature area. ## Usage ``` /competitive-brief $ARGUMENTS ``` ## Workflow ### 1. Scope the Analysis Ask the user: - **Competitor(s)**: Which specific competitor(s) to analyze? Or a feature area to compare across competitors? - **Focus**: Full product comparison, specific feature area, pricing/packaging, go-to-market, or positioning? - **Context**: What decision will this inform? (product strategy, sales enablement, investor/board materials, feature prioritization) ### 2. Research **Via web search**: - Product pages and feature lists - Pricing pages and packaging - Recent product launches, blog posts, and changelogs - Press coverage and analyst reports - Customer reviews and ratings (G2, Capterra, TrustRadius) - Job postings (signal of strategic direction) - Social media and community discussions If **~~knowledge base** is connected: - Search for existing competitive analysis documents - Find win/loss reports or sales battle cards - Pull prior competitive research If **~~chat** is connected: - Search for competitive mentions in sales or product channels - Find recent deal feedback involving competitors ### 3. Generate the Brief #### Competitor Overview For each competitor: - Company summary: founding, size, funding/revenue if public, target market - Product positioning: how they describe themselves, who they target - Recent momentum: launches, funding, partnerships, customer wins #### Feature Comparison Compare capabilities across key areas relevant to the analysis. See **Feature Comparison Matrices** below for rating scales and matrix templates. #### Positioning Analysis Analyze how each competitor positions themselves — target customer, category claim, key differentiator, and value proposition. See **Positioning Analysis Frameworks** below for the positioning statement template and message architecture levels. #### Strengths and Weaknesses For each competitor: - **Strengths**: Where they genuinely excel. What customers praise. - **Weaknesses**: Where they fall short. What customers complain about. - Be honest and evidence-based — do not dismiss competitors or inflate their weaknesses. #### Opportunities Based on the analysis: - Where are there gaps in competitor offerings we could exploit? - What are customers asking for that no one provides well? - Where are competitors making bets we disagree with? - What market shifts could advantage our approach? #### Threats - Where are competitors investing heavily? - What competitive moves could disrupt our position? - Where are we most vulnerable? - What would a "nightmare scenario" competitive move look like? #### Strategic Implications Tie the analysis back to product strategy: - What should we build, accelerate, or deprioritize based on this analysis? - Where should we differentiate vs. achieve parity? - How should we adjust positioning or messaging? - What should we monitor going forward? ### 4. Follow Up After generating the brief: - Ask if the user wants to dive deeper on any section - Offer to create a one-page summary for executives - Offer to create sales battle cards for competitive deals - Offer to draft a "how to win against [competitor]" guide - Offer to set up a monitoring plan for competitive moves ## Competitive Landscape Mapping ### Identifying the Competitive Set Define competitors at multiple levels: **Direct competitors**: Products that solve the same problem for the same users in the same way. - These are the products your customers actively evaluate against you - They appear in your deals, in customer comparisons, in review site matchups **Indirect competitors**: Products that solve the same problem but differently. - Different approach to the same user need (e.g., spreadsheets vs dedicated project management tool) - Include "non-consumption" — sometimes the competitor is doing nothing or using a manual process **Adjacent competitors**: Products that do not compete today but could. - Companies with similar technology, customer base, or distribution that could expand into your space - Larger platforms that could add your functionality as a feature - Startups attacking a niche that could grow into your core market **Substitute solutions**: Entirely different ways users solve the underlying need. - Hiring a person instead of buying software - Using a general-purpose tool (Excel, email) instead of a specialized one - Outsourcing the process entirely ### Landscape Map Position competitors on meaningful dimensions: **Common axes**: - Breadth vs depth (suite vs point solution) - SMB vs enterprise (market segment focus) - Self-serve vs sales-led (go-to-market approach) - Simple vs powerful (product complexity) - Horizontal vs vertical (general purpose vs industry-specific) Choose axes that reveal strategic positioning differences relevant to your market. The right axes make competitive dynamics visible. ### Monitoring the Landscape Track competitive movements over time: - Product launches and feature releases (changelogs, blog posts, press releases) - Pricing and packaging changes - Funding rounds and acquisitions - Key hires and job postings (signal strategic direction) - Customer wins and losses (especially your wins/losses) - Analyst and review coverage - Partnership announcements ## Feature Comparison Matrices ### Building a Feature Comparison 1. **Define capability areas**: Group features into functional categories that matter to buyers (not your internal architecture). Use the categories buyers use when evaluating. 2. **List specific capabilities**: Under each area, list the specific features or capabilities to compare. 3. **Rate each competitor**: Use a consistent rating scale. ### Rating Scale Options **Simple (recommended for most cases)**: - Strong: Market-leading capability. Deep functionality, well-executed. - Adequate: Functional capability. Gets the job done but not differentiated. - Weak: Exists but limited. Significant gaps or poor execution. - Absent: Does not have this capability. **Detailed (for deep-dive comparisons)**: - 5: Best-in-class. Defines the standard others aspire to. - 4: Strong. Fully-featured and well-executed. - 3: Adequate. Meets basic needs without differentiation. - 2: Limited. Exists but with significant gaps. - 1: Minimal. Barely functional or in early beta. - 0: Absent. Not available. ### Comparison Matrix Template ``` | Capability Area | Our Product | Competitor A | Competitor B | |----------------|-------------|-------------|-------------| | [Area 1] | | | | | [Feature 1] | Strong | Adequate | Absent | | [Feature 2] | Adequate | Strong | Weak | | [Area 2] | | | | | [Feature 3] | Strong | Strong | Adequate | ``` ### Tips for Feature Comparison - Rate based on real product experience, customer feedback, and reviews — not just marketing claims - Features exist on a spectrum. "Has feature X" is less useful than "How well does it do X?" - Weight the comparison by what matters to your target customers, not by total feature count - Update regularly — feature comparisons get stale fast - Be honest about where competitors are ahead. A comparison that always shows you winning is not credible. - Include the "why it matters" for each capability area. Not all features matter equally to buyers. ## Positioning Analysis Frameworks ### Positioning Statement Analysis For each competitor, extract their positioning: **Template**: For [target customer] who [need/problem], [Product] is a [category] that [key benefit]. Unlike [competitor/alternative], [Product] [key differentiator]. **Sources for positioning**: - Homepage headline and subheadline - Product description on app stores or review sites - Sales pitch decks (sometimes leaked or shared by prospects) - Analyst briefing materials - Earnings call language (for public companies) ### Message Architecture Analysis How does each competitor communicate value? **Level 1 — Category**: What category do they claim? (CRM, project management, collaboration platform) **Level 2 — Differentiator**: What makes them different within that category? (AI-powered, all-in-one, developer-first) **Level 3 — Value Proposition**: What outcome do they promise? (Close deals faster, ship products faster, never miss a deadline) **Level 4 — Proof Points**: What evidence do they provide? (Customer logos, metrics, awards, case studies) ### Positioning Gaps and Opportunities Look for: - **Unclaimed positions**: Value propositions no competitor owns that matter to buyers - **Crowded positions**: Claims every competitor makes that have lost meaning - **Emerging positions**: New value propositions driven by market changes (AI, remote work, compliance) - **Vulnerable positions**: Claims competitors make that they cannot fully deliver on ## Win/Loss Analysis Methodology ### Conducting Win/Loss Analysis Win/loss analysis reveals why you actually win and lose deals. It is the most actionable competitive intelligence. **Data sources**: - CRM notes from sales team (available immediately, but biased) - Customer interviews shortly after decision (most valuable, least biased) - Churned customer surveys or exit interviews - Prospect surveys (for lost deals) ### Win/Loss Interview Questions For wins: - What problem were you trying to solve? - What alternatives did you evaluate? (Reveals competitive set) - Why did you choose us over alternatives? - What almost made you choose someone else? - What would we need to lose for you to reconsider? For losses: - What problem were you trying to solve? - What did you end up choosing? Why? - Where did our product fall short? - What could we have done differently? - Would you reconsider us in the future? Under what conditions? ### Analyzing Win/Loss Data - Track win/loss reasons over time. Are patterns changing? - Segment by deal type: enterprise vs SMB, new vs expansion, industry vertical - Identify the top 3-5 reasons for wins and losses - Distinguish between product reasons (features, quality) and non-product reasons (pricing, brand, relationship, timing) - Calculate competitive win rates by competitor: what % of deals involving each competitor do you win? ### Common Win/Loss Patterns - **Feature gap**: Competitor has a specific capability you lack that is a dealbreaker - **Integration advantage**: Competitor integrates with tools the buyer already uses - **Pricing structure**: Not always cheaper — sometimes different pricing model (per-seat vs usage-based) fits better - **Incumbent advantage**: Buyer sticks with what they have because switching cost is too high - **Sales execution**: Better demo, faster response, more relevant case studies - **Brand/trust**: Buyer chooses the safer or more well-known option ## Market Trend Identification ### Sources for Trend Identification - **Industry analyst reports**: Gartner, Forrester, IDC for market sizing and trends - **Venture capital**: What are VCs funding? Investment themes signal where smart money sees opportunity. - **Conference themes**: What are industry events focusing on? What topics draw the biggest audiences? - **Technology shifts**: New platforms, APIs, or capabilities that enable new product categories - **Regulatory changes**: New regulations that create requirements or opportunities - **Customer behavior changes**: How are user expectations evolving? (e.g., mobile-first, AI-assisted, privacy-conscious) - **Talent movement**: Where are top people going? What skills are in demand? ### Trend Analysis Framework For each trend identified: 1. **What is changing?**: Describe the trend clearly and specifically 2. **Why now?**: What is driving this change? (Technology, regulation, behavior, economics) 3. **Who is affected?**: Which customer segments or market categories? 4. **What is the timeline?**: Is this happening now, in 1-2 years, or 3-5 years? 5. **What is the implication for us?**: How should this influence our product strategy? 6. **What are competitors doing?**: How are competitors responding to this trend? ### Separating Signal from Noise - **Signals**: Trends backed by behavioral data, growing investment, regulatory action, or customer demand - **Noise**: Trends backed only by media hype, conference buzz, or competitor announcements without customer traction - Test trends against your own customer data: are YOUR customers asking for this or experiencing this change? - Be wary of "trend of the year" hype cycles. Many trends that dominate industry conversation do not materially affect your customers for years. ### Strategic Response Options For each significant trend: - **Lead**: Invest early and try to define the category or approach. High risk, high reward. - **Fast follow**: Wait for early signals of customer demand, then move quickly. Lower risk but harder to differentiate. - **Monitor**: Track the trend but do not invest yet. Set triggers for when to act. - **Ignore**: Explicitly decide this trend is not relevant to your strategy. Document why. The right response depends on: your competitive position, your customer base, your resources, and how fast the trend is moving. ## Output Format Use tables for feature comparisons. Use clear headers for each section. Keep the strategic implications section concise and actionable — this is where the value is for the reader. ## Tips - Be honest about competitor strengths. Dismissing competitors makes the analysis useless. - Focus on what matters to customers, not what matters to product teams. Customers do not care about architecture elegance. - Pricing is hard to compare fairly. Note the caveats (different packaging, usage-based vs seat-based, enterprise custom pricing). - Job postings are underrated competitive intelligence. A competitor hiring ML engineers signals a strategic direction. - Customer reviews are gold. They reveal what real users love and hate, unfiltered by marketing. - The most valuable part of competitive analysis is the "so what" — the strategic implications. Do not skip this. - Competitive analysis has a shelf life. Note the date and flag areas that change quickly. --- Attribution added by YourAIKit. It is not part of the upstream file. - Source: https://github.com/anthropics/knowledge-work-plugins/tree/main/product-management/skills/competitive-brief - Credit: Anthropic, Knowledge Work Plugins (product-management) - Upstream copy: anthropics/knowledge-work-plugins at commit 33d3dea41a341b341d4f5da2e8801ae0c89be2b8, product-management/skills/competitive-brief/SKILL.md - Copyright: held by the upstream authors credited above - License: Apache-2.0. Full text: https://youraikit.com/licenses/anthropics-knowledge-work-plugins-product-management/LICENSE - The full upstream license text (LICENSE) follows. License (LICENSE): ```text Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. ```