afrexai-competitive-intel
Complete competitive intelligence system — market mapping, product teardowns, pricing intel, win/loss analysis, battlecards, and strategic monitoring. Goes far beyond SEO to cover the full business landscape.
What this skill does
# Competitive Intelligence Engine
A complete system for understanding, tracking, and outmaneuvering competitors. Covers market mapping, product analysis, pricing intelligence, sales battlecards, win/loss analysis, and ongoing monitoring.
## When to Use
- Entering a new market or launching a product
- Losing deals to competitors and need to understand why
- Quarterly strategy reviews
- Pricing decisions (new product or adjustment)
- Sales team needs competitive talking points
- M&A due diligence on a target or acquirer
- Investor pitch prep (show you understand the landscape)
- Content strategy informed by competitor gaps
---
## Phase 1: Market Mapping
### 1.1 Competitor Identification
Classify every competitor into one of four tiers:
| Tier | Definition | Example | Monitoring Frequency |
|------|-----------|---------|---------------------|
| **Direct** | Same product, same buyer | Your closest rivals | Weekly |
| **Adjacent** | Different product, overlapping buyer | Platform expanding into your space | Bi-weekly |
| **Indirect** | Different solution to same problem | Spreadsheets replacing your SaaS | Monthly |
| **Emerging** | Early-stage, same vision | YC startups in your category | Monthly |
### Discovery Methods
Search these sources systematically:
1. **Google**: "[your category] software/tool/service" — note top 10 organic + ads
2. **G2/Capterra/TrustRadius**: Your category page — note top 10 by reviews
3. **Product Hunt**: Search your keywords — sort by votes
4. **Crunchbase**: Search your category — filter funded companies
5. **LinkedIn**: "[competitor name]" company pages — note employee count trends
6. **Reddit/HN**: "alternative to [leader]" or "[category] recommendations"
7. **Customer interviews**: "Who else did you evaluate?"
8. **Lost deal notes**: Who did you lose to and why?
### Market Map YAML
```yaml
market_map:
category: "[Your Category]"
date: "YYYY-MM-DD"
total_addressable_market: "$XB"
competitors:
- name: "Competitor A"
tier: "direct"
website: "https://..."
founded: 2019
funding: "$50M Series B"
estimated_revenue: "$10-20M ARR"
employee_count: 150
employee_trend: "growing" # growing | stable | shrinking
hq: "San Francisco, CA"
key_customers: ["Customer 1", "Customer 2"]
primary_market: "mid-market" # smb | mid-market | enterprise
positioning: "All-in-one platform for X"
strengths: ["Feature A", "Strong brand"]
weaknesses: ["Expensive", "Slow support"]
threat_level: "high" # low | medium | high | critical
notes: ""
```
---
## Phase 2: Product Teardown
### 2.1 Feature Matrix
For each direct competitor, build a feature comparison:
```yaml
feature_matrix:
last_updated: "YYYY-MM-DD"
categories:
- name: "Core Features"
features:
- name: "Feature X"
us: "full" # none | partial | full | superior
competitor_a: "full"
competitor_b: "partial"
weight: 5 # 1-5 importance to buyer
notes: "We have deeper customization"
- name: "Feature Y"
us: "none"
competitor_a: "full"
competitor_b: "full"
weight: 3
notes: "On our roadmap for Q3"
- name: "Integrations"
features:
- name: "Salesforce"
us: "full"
competitor_a: "partial"
weight: 4
```
### 2.2 Product Teardown Template
For each major competitor, conduct a structured teardown:
```markdown
## [Competitor Name] Product Teardown
**Date:** YYYY-MM-DD
**Analyst:** [name]
### First Impressions (0-5 min)
- Homepage messaging: What problem do they lead with?
- Sign-up friction: How many steps? What info required?
- Time to value: How fast can you DO something?
- Design quality: Modern, dated, cluttered, clean?
### Onboarding (5-30 min)
- Guided tour? Checklist? Video? Nothing?
- Sample data provided? Sandbox mode?
- How quickly did you feel competent?
- What confused you?
### Core Workflow
- Complete their primary use case end-to-end
- Note: steps required, clicks per task, speed, error handling
- Screenshot key screens
### Differentiators
- What can they do that we can't? (be honest)
- What's their "magic moment"?
- What do their happiest customers praise? (check G2 reviews)
### Weaknesses
- Where did you get stuck?
- What felt missing or half-baked?
- What do their angriest customers complain about? (check G2 1-2 star reviews)
### Pricing vs Value
- What plan would a typical customer need?
- Price per user/month at that tier?
- Any hidden costs (implementation, support, integrations)?
- Free trial? Freemium? Money-back guarantee?
### Technical Assessment
- Stack: (check Wappalyzer, BuiltWith, job postings)
- API: Public? REST/GraphQL? Rate limits? Docs quality?
- Mobile: Native app? Responsive web? PWA?
- Performance: Page load speed, UI responsiveness
- Uptime: Status page? Historical incidents?
```
### 2.3 UX Scoring Rubric
Score each competitor's product (0-10 per dimension):
| Dimension | What to Evaluate | Weight |
|-----------|-----------------|--------|
| **Ease of Setup** | Time to first value, onboarding friction | 15% |
| **Core UX** | Primary workflow efficiency, intuitiveness | 25% |
| **Feature Depth** | Covers edge cases, power user needs | 20% |
| **Reliability** | Uptime, bugs encountered, error handling | 15% |
| **Integrations** | Ecosystem breadth, API quality | 10% |
| **Support** | Response time, quality, self-serve resources | 10% |
| **Mobile** | Native quality, feature parity | 5% |
**Total = weighted sum. Compare across competitors.**
---
## Phase 3: Pricing Intelligence
### 3.1 Pricing Comparison Table
```yaml
pricing_intel:
date: "YYYY-MM-DD"
competitors:
- name: "Us"
model: "per-seat" # per-seat | usage | flat | hybrid | freemium
entry_price: "$29/user/mo"
mid_price: "$79/user/mo"
enterprise_price: "Custom"
free_tier: true
free_limits: "5 users, 1000 records"
annual_discount: "20%"
contract_required: false
implementation_fee: "$0"
hidden_costs: []
- name: "Competitor A"
model: "per-seat"
entry_price: "$49/user/mo"
mid_price: "$99/user/mo"
enterprise_price: "Custom ($150+/user)"
free_tier: false
annual_discount: "15%"
contract_required: true # annual minimum
implementation_fee: "$5,000"
hidden_costs: ["API access on enterprise only", "SSO $50/user extra"]
```
### 3.2 Price Positioning Analysis
Answer these questions:
1. **Where do we sit?** Map all competitors on a 2x2: Price (low→high) vs Feature depth (basic→advanced)
2. **Who's cheapest?** At 10 users? 50 users? 200 users? (pricing often crosses over at scale)
3. **Total Cost of Ownership**: Include implementation, training, migration, hidden fees
4. **Value ratio**: Features-per-dollar compared to each competitor
5. **Pricing trend**: Are competitors raising prices? (check Wayback Machine on /pricing)
6. **Discount behavior**: Do they discount aggressively in deals? (ask sales team, check G2 reviews mentioning price)
### 3.3 Pricing Strategy Recommendations
Based on analysis, recommend one of:
| Strategy | When to Use | Risk |
|----------|------------|------|
| **Premium** | Clearly superior product + brand | Losing price-sensitive deals |
| **Parity** | Similar product, compete on other axes | Race to bottom |
| **Penetration** | New entrant, need market share fast | Perception of low quality |
| **Value** | Better product at lower price | Margin pressure if costs rise |
| **Niche** | Specialized for segment competitors ignore | Small TAM |
---
## Phase 4: Sales Battlecards
### 4.1 Battlecard Template
Create one per direct competitor:
```markdown
# 🏆 Battlecard: Us vs [Competitor]
**Last Updated:** YYYY-MM-DD | **Confidence:** High/Medium/Low
## Quick Stats
| Metric | Us | Them |
|--------|-----|------|
| Founded | | |
| FuRelated in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".