/sales-competitors

Sales Competitive Intelligence

You analyze what tools, services, and solutions a prospect currently uses and generate actionable battle cards for selling against each detected competitor. This is NOT a general market analysis — it is focused entirely on helping a salesperson WIN a deal against specific competitors that a specific prospect is currently using or evaluating.

Invocation

/sales competitors <url>

Where `<url>` is the prospect company's website URL. The skill detects what the prospect currently uses and builds sales-focused battle cards for each detected solution.

Step 1: Current Solution Detection

Execute all of the following detection methods in parallel using WebFetch and WebSearch. The goal is to identify every tool, service, platform, and vendor the prospect currently relies on that overlaps with or is adjacent to your offering.

1.1 Website Technology Analysis

Fetch the prospect's website and analyze:

• **HTML source inspection**: Look for script tags, meta tags, and link tags that reference known tools and platforms (e.g., analytics tools, CRM embeds, chat widgets, marketing automation pixels, tag managers, CDN providers)
• **Integration badges and partner logos**: Check the homepage, footer, integrations page, and partners page for logos of tools they use or integrate with
• **"Powered by" footers**: Many SaaS tools place a small badge or link in the footer of pages they power (e.g., help desks, landing pages, e-commerce platforms)
• **Technology stack signals**: Identify the website platform (WordPress, Webflow, Shopify, custom), hosting provider, CDN, email service provider, and other infrastructure choices
• **Login/portal pages**: Check for links to internal tools (e.g., "Login to Dashboard" that redirects to a known SaaS platform)
• **API documentation**: If they have a developer/API page, check what integrations they document — this reveals their stack

Record each detected technology with:

• Tool/platform name
• Evidence source (URL, page element, or signal that revealed it)
• Confidence level: High (explicit mention or badge), Medium (script tag or indirect reference), Low (inference from job posting or industry norm)

1.2 Job Posting Analysis

Search for the prospect's open job postings using WebSearch with queries like:

• "[Company Name] careers"
• "[Company Name] open jobs"
• "[Company Name] hiring"

Analyze job descriptions for:

• **Tool-specific requirements**: "Experience with Salesforce required" or "Proficiency in HubSpot"
• **Technology stack mentions**: Programming languages, frameworks, databases, cloud providers
• **Vendor certifications**: Certifications or training for specific platforms (e.g., "AWS Certified", "Salesforce Admin")
• **Process tool mentions**: Project management (Jira, Asana), communication (Slack, Teams), documentation (Notion, Confluence)

These are HIGH confidence signals — if a company requires experience with a tool in a job posting, they use that tool.

1.3 Case Study and Partnership Search

Search for the prospect appearing as a customer of known competitors:

• WebSearch: "[Company Name] case study [Competitor Name]"
• WebSearch: "[Company Name] customer story"
• WebSearch: "[Company Name] testimonial"

Check if the prospect:

• Appears on a competitor's website as a customer
• Has been quoted in a competitor's case study
• Is listed as a partner or integration partner of a competitor
• Has left reviews on competitor products

1.4 Review Site Search

Search G2, Capterra, and TrustRadius for reviews authored by employees of the prospect company:

• WebSearch: "site:g2.com [Company Name]"
• WebSearch: "site:capterra.com [Company Name]"
• WebSearch: "[Company Name] review [tool category]"

If reviews are found, note:

• Which products they reviewed (these are products they use)
• Satisfaction level (positive, mixed, negative)
• Specific complaints or praise mentioned in the review
• Review date (recent reviews are more relevant)

1.5 Tech Stack Detection Services

If available, check technology detection services:

• WebSearch: "site:builtwith.com [Company Domain]"
• WebSearch: "site:stackshare.io [Company Name]"
• WebSearch: "[Company Domain] technology stack"

These services catalog the technologies used by websites and can reveal tools not visible through direct inspection.

1.6 Social Signal Analysis

Search for company or employee posts mentioning specific tools:

• WebSearch: "[Company Name] [tool category] site:linkedin.com"
• WebSearch: "[Company Name] 'we use' OR 'switched to' OR 'implemented' [tool category]"

Look for:

• Blog posts about their technology choices
• LinkedIn posts from employees about tools they use
• Conference talks where they mention their stack
• Community forum posts asking for help with specific tools

---

Step 2: Categorize Detected Solutions

Organize all detected solutions into categories relevant to the sales conversation:

| Category | Detected Solution | Confidence | Evidence | |----------|------------------|------------|----------| | CRM | [Tool name] | High/Med/Low | [Source] | | Marketing Automation | [Tool name] | High/Med/Low | [Source] | | Analytics | [Tool name] | High/Med/Low | [Source] | | Customer Support | [Tool name] | High/Med/Low | [Source] | | Project Management | [Tool name] | High/Med/Low | [Source] | | Communication | [Tool name] | High/Med/Low | [Source] | | [Other relevant categories] | ... | ... | ... |

Highlight the solutions that directly compete with or overlap with your offering — these are the ones that will get full battle cards.

---

Step 3: Build Battle Cards

For each detected competitor or current solution that overlaps with your offering, build a complete battle card. Each battle card must be detailed enough for a salesperson to use in real-time during a call or meeting.

Battle Card Format

For EACH detected competitor, generate:

## Battle Card: [Competitor Name]

### What the Prospect Uses Them For