competitive-analysis
Skill9 starsChanged 8 months agoMITView on GitHub
Conduct comprehensive competitive analysis for strategic decision-making. Use when entering markets, responding to competitors, or informing strategy.
We split this skill into the rules it gives an agent
21 rules. 0 are common, 21 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 43 edited versions we read keep these.
21
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 51
Not all competitors deserve equal analysis.
- Distinctive: line 82
Use the feature matrix to identify gaps, but compete on value and positioning, not feature lists.
- Distinctive: line 83
Update quarterly — competitor features change constantly.
- Distinctive: line 162
Place each competitor on the 2x2 grid based on those dimensions.
- Distinctive: line 196
Interviewer: Not the salesperson who handled the deal.
- Distinctive: line 215
Loss reasons → Fix or position around: If fixable, add to product roadmap.
- Distinctive: line 216
Competitive patterns → Update battlecards: Use customer language about competitors in sales enablement.
- Distinctive: line 265
Update monthly or immediately after a significant competitor change.
- Distinctive: line 266
Write in sales language, not marketing language.
- Distinctive: line 267
Never disparage competitors.
- Distinctive: line 269
Test battlecards with sales team and iterate based on their feedback.
- Distinctive: line 274
Check competitor social media for announcements.
- Distinctive: line 280
Check review sites (G2, Capterra) for new competitor reviews.
- Distinctive: line 282
Update battlecards if needed.
- Distinctive: line 286
Update feature comparison matrix.
- Distinctive: line 293
Update competitive positioning map.
- Distinctive: line 324
Only use publicly available information and voluntarily shared information.
- Distinctive: line 325
Never misrepresent yourself to gain competitive intelligence.
- Distinctive: line 326
Never ask competitors' employees to share confidential information.
- Distinctive: line 327
Never reverse-engineer proprietary technology in violation of terms of service.
- Distinctive: line 331
Before presenting competitive analysis:
“Common” is measured: kept by at least 6 in 10 of the 43 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Competitive Analysis
When to Activate
- Entering a new market and need to understand the competitive landscape
- A new competitor enters your space or an existing one makes a significant move
- Preparing sales battlecards or competitive positioning
- Informing product roadmap decisions with competitive context
- Conducting a strategic planning exercise (annual planning, board prep)
- Win/loss rate declining and need to understand competitive dynamics
- Evaluating an acquisition target's competitive position
First Questions
- What is the specific competitive question you're trying to answer?
- Who are you competing against today? (Not who you think — who does sales actually face in deals?)
- What market or category are you analyzing?
- What decisions will this analysis inform? (Pricing, positioning, product roadmap, go-to-market)
- How much time do you have for this analysis? (Quick assessment vs. deep dive)
- What internal data do you have? (Win/loss data, sales call recordings, customer feedback)
- Is this a one-time analysis or an ongoing competitive intelligence program?
Competitive Landscape Mapping
Step 1: Identify All Competitors
Direct Competitors: Same product, same customer, same problem.
- These are the alternatives you most frequently encounter in deals.
- Usually 3-7 primary direct competitors.
Indirect Competitors: Different product, same customer, same problem.
- They solve the same problem in a fundamentally different way.
- Example: Zoom (video) vs. in-person meetings vs. phone calls.
Substitute Competitors: Non-consumption or DIY alternatives.
- Spreadsheets, manual processes, hiring someone, building internally.
- Often the biggest competitor, especially for new categories.
Potential Future Competitors: Companies that could enter your space.
- Adjacent players expanding their product scope.
- Platform companies adding features that overlap with your product.
- Well-funded startups in adjacent spaces.
Step 2: Prioritize Competitors
Not all competitors deserve equal analysis. Prioritize based on:
| Factor | Weight |
| Frequency in competitive deals | High |
| Win rate against them | High |
| Market share / growth rate | Medium |
| Strategic threat (future) | Medium |
| Customer overlap | Medium |
Focus deep analysis on your top 3-5 competitors. Monitor the rest.
Feature Comparison Matrix
Building the Matrix
| Feature / Capability | Your Product | Competitor A | Competitor B | Competitor C |
| Core feature 1 | Rating/detail | Rating/detail | Rating/detail | Rating/detail |
| Core feature 2 | ... | ... | ... | ... |
| Integration X | ... | ... | ... | ... |
| Pricing model | ... | ... | ... | ... |
| Support level | ... | ... | ... | ... |
Rating System
- Leading: Best-in-class implementation. Clear advantage.
- Competitive: On par with alternatives. Not a differentiator.
- Lagging: Below competitor quality. A weakness.
- Missing: Feature not available.
Feature Matrix Caution
- Feature parity comparisons favor incumbents. If you compete on features, you lose to whoever has more.
- Use the feature matrix to identify gaps, but compete on value and positioning, not feature lists.
- Update quarterly — competitor features change constantly.
Pricing Analysis
What to Capture
| Element | Your Product | Competitor A | Competitor B |
| Pricing model | Per seat/usage/flat | ... | ... |
| Starting price | ... | ... | ... |
| Mid-market price | ... | ... | ... |
| Enterprise price | ... | ... | ... |
| Free tier / trial | ... | ... | ... |
| Discounting behavior | ... | ... | ... |
| Contract terms | ... | ... | ... |
Pricing Intelligence Sources
- Competitor websites (public pricing pages).
- G2, Capterra, TrustRadius reviews (users sometimes mention pricing).
- Sales team intelligence (what prospects tell you about competitor pricing).
- Customer interviews (what they paid before switching).
- Job postings (sometimes reveal tool stack and budget signals).
Pricing Analysis Insights
- Are you priced above, at, or below competitors? Is that intentional?
- How does your pricing model differ? (Per seat vs. usage vs. flat)
- What is the value-to-price ratio for each competitor?
- Where are competitors using pricing as a competitive weapon (aggressive free tiers, deep discounts)?
Messaging Analysis
How to Analyze Competitor Messaging
Examine these assets for each competitor:
- Website homepage: What problem do they lead with? What language do they use?
- Pricing page: How do they frame their tiers? What features do they gate?
- Product pages: What capabilities do they highlight first?
- Case studies: What outcomes do they showcase? Who are their reference customers?
- Social media: What tone do they take? What content themes dominate?
- Ad copy: What messages are they paying to amplify? (Use Facebook Ad Library, Google Ads Transparency)
- Review sites: What do their customers praise and complain about?
Messaging Comparison Template
| Dimension | Your Messaging | Competitor A | Competitor B |
| Primary headline | ... | ... | ... |
| Key value prop | ... | ... | ... |
| Target audience language | ... | ... | ... |
| Social proof | ... | ... | ... |
| Primary CTA | ... | ... | ... |
| Differentiator claim | ... | ... | ... |
| Tone/voice | ... | ... | ... |
Finding Messaging Gaps
- What valuable capability does nobody talk about? (Opportunity to own a message.)
- What claims do all competitors make? (Table stakes — don't differentiate on these.)
- What language do customers use that no competitor uses? (Customer-centric messaging opportunity.)
SWOT Per Competitor
Template (Do One Per Top Competitor)
COMPETITOR: [Name]
STRENGTHS WEAKNESSES
- [What they do well] - [Where they fall short]
- [Market advantages] - [Product gaps]
- [Resources, brand, scale] - [Organizational issues]
- [Customer love points] - [Common customer complaints]
OPPORTUNITIES (for us) THREATS (to us)
- [Their weaknesses we exploit] - [Their advantages that hurt us]
- [Market gaps they ignore] - [Their likely next moves]
- [Customer segments they - [Resource advantages they have]
underserve] - [Platform/ecosystem advantages]Competitive Positioning Map (2x2)
How to Build
- Choose two dimensions that matter most to your target customers.
- Place each competitor on the 2x2 grid based on those dimensions.
- Identify whitespace — positions no competitor occupies.
Common Axis Pairs
- Ease of use ←→ Power/Complexity (vertical) vs. Individual ←→ Enterprise (horizontal)
- Price ←→ Premium (vertical) vs. Narrow/Specialized ←→ Broad/Platform (horizontal)
- Speed to value ←→ Customization depth vs. SMB ←→ Enterprise
Example
High Ease of Use
│
Canva ● │ ● Figma
│
SMB ──────────────┼─────────────── Enterprise
│
● GIMP │ ● Adobe Creative Suite
│
High ComplexityPositioning Map Insights
- Where is the whitespace? Can you position there credibly?
- Are you clustered with competitors? If so, you need sharper differentiation.
- Is the whitespace empty because there's no demand, or because nobody has claimed it?
Win/Loss Analysis
The Most Valuable Competitive Intelligence Source
Win/loss analysis tells you why customers chose you or a competitor, from the customer's mouth.
How to Run Win/Loss Analysis
- Sample: Interview 10-20 recent won deals and 10-20 recent lost deals.
- Timing: Interview within 30 days of the decision. Memory fades fast.
- Interviewer: Not the salesperson who handled the deal. Use marketing, product, or a third party.
- Questions:
- What alternatives did you evaluate?
- What were your top 3 decision criteria?
- How did we compare on those criteria?
- What nearly made you choose differently?
- What was the deciding factor?
Win/Loss Data Template
| Factor | Won Deals | Lost Deals | Gap |
| Pricing cited as factor | 30% | 65% | -35% |
| Product capability cited | 70% | 40% | +30% |
| Ease of use cited | 60% | 25% | +35% |
| Integration needs unmet | 10% | 45% | -35% |
| Support/service factor | 20% | 50% | -30% |
Turning Win/Loss Into Action
- Win reasons → Strengthen positioning. Double down on what's working in messaging and sales.
- Loss reasons → Fix or position around. If fixable, add to product roadmap. If structural, adjust positioning to avoid those deals.
- Competitive patterns → Update battlecards. Use customer language about competitors in sales enablement.
Battlecard Creation Template
Battlecard Structure (1-2 Pages Per Competitor)
BATTLECARD: [Competitor Name]
Last Updated: [Date]
QUICK OVERVIEW
- What they are: [1-sentence description]
- Target market: [Who they serve]
- Pricing: [Model and range]
- Key differentiator: [Their primary claim]
WHEN WE WIN AGAINST THEM
- [Scenario 1 where we have advantage]
- [Scenario 2]
- [Scenario 3]
WHEN WE LOSE TO THEM
- [Scenario 1 where they have advantage]
- [Scenario 2]
- [Warning signs in the deal]
THEIR STRENGTHS (Acknowledge, Don't Dismiss)
- [Strength 1 — and how to reframe or neutralize]
- [Strength 2]
THEIR WEAKNESSES (What to Probe)
- [Weakness 1 — discovery questions to surface this]
- [Weakness 2]
LANDMINE QUESTIONS (Ask the Prospect)
- "[Question that exposes competitor weakness]"
- "[Question that highlights your strength]"
- "[Question about a requirement they can't meet]"
OBJECTION HANDLING
- "They're cheaper" → [Response]
- "They have [feature] and you don't" → [Response]
- "Everyone uses them" → [Response]
CUSTOMER PROOF POINTS
- [Case study or quote from a customer who switched from this competitor]
- [Metric: "Customers who switch see X% improvement in..."]Battlecard Rules
- Update monthly or immediately after a significant competitor change.
- Write in sales language, not marketing language. Be direct and actionable.
- Never disparage competitors. Acknowledge strengths, reframe, and redirect.
- Include discovery questions that surface the competitor's weaknesses organically.
- Test battlecards with sales team and iterate based on their feedback.
Competitive Monitoring Cadence
Weekly (15 minutes)
- Check competitor social media for announcements.
- Scan industry news for competitor mentions.
- Review any alerts (Google Alerts, social listening tools).
Monthly (1-2 hours)
- Review competitor websites for changes (pricing, messaging, features).
- Check review sites (G2, Capterra) for new competitor reviews.
- Collect competitive intelligence from sales team (deal-level insights).
- Update battlecards if needed.
Quarterly (Half day)
- Full competitive landscape review.
- Update feature comparison matrix.
- Update pricing analysis.
- Conduct win/loss analysis batch.
- Present competitive update to leadership and product team.
Annually (Full day)
- Deep competitive strategy review.
- Update competitive positioning map.
- Reassess competitor priority list.
- Input competitive insights into annual planning and product roadmap.
Competitive Intelligence Sources
Public Sources
- Competitor websites (use Wayback Machine for historical changes)
- Press releases and news coverage
- Review sites (G2, Capterra, TrustRadius, Product Hunt)
- Social media (company and employee accounts)
- Job postings (reveal strategic priorities, tech stack, team growth)
- Patent filings (reveal R&D direction)
- SEC filings (public companies — revenue, strategy, risk factors)
- Conference presentations and webinars
- Podcast appearances by competitor leadership
Customer and Market Sources
- Win/loss interviews
- Prospect feedback during sales process
- Customer advisory board discussions
- Industry analyst reports (Gartner, Forrester, IDC)
- Industry conferences and events
Internal Sources
- Sales team (most direct competitive intelligence)
- Customer success team (why customers considered switching)
- Support team (feature requests that reference competitors)
- Product team (technology and architecture assessments)
Ethical Guidelines
- Only use publicly available information and voluntarily shared information.
- Never misrepresent yourself to gain competitive intelligence.
- Never ask competitors' employees to share confidential information.
- Never reverse-engineer proprietary technology in violation of terms of service.
Quality Gate
Before presenting competitive analysis:
- Have you identified all competitor types (direct, indirect, substitute, potential future)?
- Is the analysis based on current data, not assumptions from 6+ months ago?
- Have you included customer perspective (win/loss data), not just your internal view?
- Are competitor strengths acknowledged honestly (not dismissed or minimized)?
- Does the analysis lead to actionable recommendations (not just information)?
- Have you prioritized — which 3-5 competitors matter most?
- Are battlecards written in sales-ready language?
- Is there a monitoring cadence planned to keep the analysis current?
- Has the analysis been shared with sales, product, and leadership?
Other versions52 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 52
- anthropics/financial-services★ 41ksame name
- anthropics/financial-services-plugins★ 41ksame name
- claude-office-skills/skills★ 433same name
- shawnpang/startup-founder-skills★ 331same name
- mverab/eGEOagents★ 214same name
- Fokkyp/claude-skills★ 211same name
- aakashg/pm-claude-code-setup★ 152same name
- nahid-sparktales/agent-dispatcher★ 59same name
- agencia-conversion/agentic-seo-skills★ 51same name
- launchapp-dev/animus-cli★ 39same name
42 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use onboarding-flow, lead-scoring and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Dragoon0xSkillonboarding-flow
Design first-run experiences that create the aha moment fast. Reduces time-to-value by sequencing actions, progressive disclosure, and contextual guidance. Use when building signup flows, product tours, or empty states.
Also in 3 projects that use this
shawnpangSkilllead-scoring
When a founder needs to qualify inbound leads, define their ICP, build a lead scoring model, set MQL criteria, or route prospects through pipeline stages. Activate when the user mentions lead scoring, ICP, MQL, SQL, lead qualification, inbound leads, or pipeline design.
Also in 3 projects that use this
nicepkgSkilluser-research-synthesis
Synthesize qualitative and quantitative user research into structured insights and opportunity areas. Use when analyzing interview notes, survey responses, support tickets, or behavioral data to identify themes, build personas, or prioritize opportunities.
Also in 4 projects that use this
claude-office-skillsSkillemail-marketing
Email marketing automation - campaign creation, sequence building, A/B testing, deliverability optimization, and analytics
Also in 3 projects that use this
AnthropicSkilluser-research
Plan, conduct, and synthesize user research. Trigger with "user research plan", "interview guide", "usability test", "survey design", "research questions", or when the user needs help with any aspect of understanding their users through research.
Also in 3 projects that use this
Hack23Skillsecure-code-review
Security code review using OWASP Top 10, input validation, and Hack23 ISMS secure development policy for TypeScript/MCP
Also in 3 projects that use this
In this repository73 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ab-testingSkill
- analytics-attributionSkill
- analytics-dashboardsSkill
- cohort-analysisSkill
- marketing-reportingSkill
- brand-architectureSkill
- brand-guidelinesSkill
- brand-positioningSkill
- brand-voiceSkill
- competitive-positioningSkill
- visual-identitySkill
- community-strategySkill
- blog-seo-writingSkill
- content-auditSkill
- content-pillarsSkill
- content-repurposingSkill
- editorial-calendarSkill
- storytelling-frameworksSkill
- thought-leadershipSkill
- ugc-strategySkill
- ad-copySkill
- copywriting-frameworksSkill
- cta-optimizationSkill
- headline-formulasSkill
- landing-page-copySkill
- microcopy-uxSkill
- sales-page-copySkill
- campaign-conceptsSkill
- cro-frameworksSkill
- funnel-designSkill
- landing-page-optimizationSkill
- email-automationSkill
- email-copywritingSkill
- email-deliverabilitySkill
- email-segmentationSkill
- email-sequencesSkill
- growth-loopsSkill
- plg-strategiesSkill
- referral-programsSkill
- viral-mechanicsSkill
- influencer-outreachSkill
- influencer-roiSkill
- martech-stackSkill
- utm-trackingSkill
- ad-creative-testingSkill
- budget-allocationSkill
- google-adsSkill
- linkedin-adsSkill
- meta-adsSkill
- retargetingSkill
- crisis-communicationSkill
- media-pitchingSkill
- go-to-marketSkill
- launch-playbookSkill
- product-positioningSkill
- press-releasesSkill
- customer-interviewsSkill
- market-researchSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

