competitor-matrix
Conduct competitive analysis with feature comparison matrices, positioning teardowns, win/loss evaluation, and market trend assessment. Activate when researching competitors, building a feature comparison table, evaluating competitive positioning, preparing a competitive brief, analyzing win/loss patterns, mapping the competitive landscape, or assessing market threats and opportunities.
What this skill does
## Mapping the Competitive Landscape ### Defining the Competitor Set Categorize competitors into four tiers based on proximity and threat level: **Tier 1 -- Direct rivals**: Products targeting the same users with the same approach to the same problem. - These appear in head-to-head evaluations, review site comparisons, and sales deal cycles - Customers actively weigh your product against these alternatives **Tier 2 -- Alternative approaches**: Products addressing the same underlying need through a different mechanism. - A fundamentally different methodology for the same user problem (e.g., a spreadsheet used in place of dedicated project management software) - Include the option of doing nothing at all -- inaction or manual workarounds are often the strongest competitor **Tier 3 -- Potential entrants**: Organizations not competing today but positioned to move into your space. - Companies with overlapping technology stacks, customer relationships, or distribution channels - Large platforms that could absorb your functionality as a built-in feature - Focused startups serving a niche that could expand toward your core market **Tier 4 -- Substitute solutions**: Entirely different approaches to the underlying need. - Hiring personnel instead of purchasing software - Relying on general-purpose tools (spreadsheets, email, shared documents) instead of purpose-built products - Outsourcing the entire process to a service provider ### Constructing a Landscape Map Plot competitors along dimensions that reveal strategic positioning: **Useful axis pairs**: - Breadth versus depth (platform suite vs. focused point solution) - Downmarket versus upmarket (SMB-oriented vs. enterprise-focused) - Self-service versus sales-assisted (go-to-market model) - Simplicity versus power (ease of adoption vs. configurability) - Horizontal versus vertical (general-purpose vs. industry-tailored) Select axis pairs that expose the positioning differences most relevant to your market. Well-chosen dimensions make competitive dynamics immediately visible. ### Ongoing Competitive Monitoring Systematically track competitor activity over time: - Product updates: changelog entries, blog announcements, press coverage of new capabilities - Pricing and packaging adjustments - Capital events: funding rounds, acquisitions, IPO filings - Talent signals: senior hires and open roles that indicate strategic direction - Deal outcomes: accounts won and lost, particularly those involving head-to-head competition - Third-party coverage: analyst reports, review site rankings, media commentary - Ecosystem moves: partnership announcements and integration launches ## Building Feature Comparison Matrices ### Construction Process 1. **Establish capability domains**: Organize features into functional groupings that reflect buyer evaluation criteria, not your internal product architecture. Mirror the language and categories that buyers use. 2. **Enumerate specific capabilities**: Within each domain, list the discrete features or functions to compare. 3. **Apply consistent ratings**: Score every competitor using a uniform scale. ### Rating Scales **Four-level scale (recommended for most contexts)**: - Strong: Industry-leading execution. Deep, differentiated functionality. - Adequate: Competent implementation. Meets requirements without standing out. - Weak: Present but limited. Meaningful gaps or rough execution. - Absent: Capability does not exist. **Six-level scale (for granular deep-dive assessments)**: - 5: Best-in-class. Sets the benchmark others pursue. - 4: Robust. Comprehensive and well-implemented. - 3: Sufficient. Covers core needs without differentiation. - 2: Partial. Exists but with notable limitations. - 1: Rudimentary. Barely functional or in early preview. - 0: Not available. ### Matrix Format ``` | Capability Domain | Our Product | Rival A | Rival B | |--------------------|-------------|-----------|-----------| | [Domain 1] | | | | | [Capability 1a] | Strong | Adequate | Absent | | [Capability 1b] | Adequate | Strong | Weak | | [Domain 2] | | | | | [Capability 2a] | Strong | Strong | Adequate | ``` ### Comparison Best Practices - Base ratings on direct product evaluation, customer testimony, and independent reviews -- not vendor marketing material - Recognize that capability exists on a spectrum. "Offers feature X" is less informative than "how effectively does it execute feature X?" - Weight the matrix toward capabilities your target buyers prioritize, not toward raw feature volume - Refresh comparisons regularly -- competitive feature sets evolve rapidly - Acknowledge areas where competitors genuinely lead. A matrix that invariably favors your product lacks credibility. - Annotate each capability domain with a "buyer relevance" note explaining why it matters in purchase decisions ## Positioning Teardown ### Extracting Competitor Positioning For each rival, distill their market positioning: **Positioning template**: For [intended audience] who [face this challenge], [Product] is a [market category] that [delivers this core benefit]. In contrast to [alternative], [Product] [achieves this differentiation]. **Where to find positioning signals**: - Website hero section: headline and supporting copy - Product descriptions on marketplace listings and review platforms - Sales materials (occasionally surfaced by prospects or in public-facing decks) - Analyst briefing content - Public company earnings call language and investor presentations ### Messaging Layer Analysis Deconstruct how each competitor communicates value across four levels: **Layer 1 -- Category claim**: Which market category do they occupy? (CRM, collaboration suite, developer platform) **Layer 2 -- Differentiator**: What distinguishes them within that category? (AI-native, unified workspace, API-first) **Layer 3 -- Promised outcome**: What result do they pledge to deliver? (Close revenue faster, ship products in half the time, eliminate missed deadlines) **Layer 4 -- Evidence**: What proof do they marshal? (Customer logos, published metrics, industry recognition, case studies) ### Identifying Positioning Gaps Scan for strategic openings: - **Unoccupied territory**: Value propositions that no competitor claims but that buyers would find compelling - **Saturated claims**: Messages repeated by every player in the space, rendering them meaningless as differentiators - **Emerging narratives**: New value propositions catalyzed by market shifts (AI augmentation, distributed work, data sovereignty) - **Overpromised positions**: Claims competitors make that their products cannot fully substantiate ## Win/Loss Analysis ### Methodology Win/loss analysis reveals the actual reasons deals are won and lost -- the most directly actionable form of competitive intelligence. **Information sources**: - CRM deal notes from the sales organization (readily available but subject to attribution bias) - Structured interviews with buyers shortly after their decision (highest signal, lowest bias) - Exit surveys from departing customers - Post-decision outreach to prospects who chose a competitor ### Interview Framework Questions for won deals: - What problem prompted your evaluation process? - Which alternatives did you consider? (reveals the true competitive set) - What tipped the decision in our favor? - What nearly caused you to choose differently? - What would need to change for you to reconsider your choice? Questions for lost deals: - What problem were you trying to address? - Which solution did you select, and what drove that decision? - Where did our offering fall short of your requirements? - What could we have done differently during the evaluation? - Under what circumstances would you consider us in a future evaluation? ### Synthesizing Win/Loss Patterns - Track reasons for wins and losse
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.