company-intel

## Purpose

Research engine that builds deep, structured understanding of companies, industries, and competitor sets. Produces a stable output format that you can hand off to other skills and agents to generate battlecards, SWOT analyses, positioning statements, PESTEL assessments, market sizing, and workshop content.

This is not a generic encyclopedia lookup. Every section pushes toward commercial understanding, product implications, and actionable intelligence. The output is a research primitive — structured data other skills consume — not a final deliverable.

## Key Concepts

### Four Entry Points

The skill auto-detects entry point from the user's input. If ambiguous, ask one clarifying question: "Is this about a specific company, an industry, or a set of competitors?"

**Single Company** — User names a company (e.g., "Parker Hannifin," "Novo Nordisk"). Produce the full 11-section output for that company.

**Industry/Sector** — User names an industry, sector, or niche (e.g., "clinical data management," "embedded finance," "upstream oil and gas"). Establish broad industry context, narrow into the segment, and connect findings to PM implications. Use the same 11-section structure adapted for sector-level analysis.

**Named Competitor Set** — User names 2-5 companies (e.g., "Compare Emerson, Honeywell, and Parker Hannifin"). Produce individual 11-section outputs for each company, then add a **Section 12: Cross-Company Comparison** that synthesizes across the set.

**Discover Competitors** — User names a company plus the word "competitors" (e.g., "productside.com competitors" or "Parker Hannifin competitors"). The skill:
1. Researches the named company first — enough to understand what it does, who it serves, and what market it plays in (a lightweight pass through Lenses 1-4)
2. Identifies 3-5 likely competitors based on that research, citing why each is a competitor (direct, adjacent, substitute, or emerging disruptor)
3. Presents the list for confirmation: "Based on my research, [Company]'s closest competitors appear to be [A, B, C, D, E]. Want me to run the full competitor set on these, or adjust the list first?"
4. Once confirmed, proceeds with the Named Competitor Set flow — full 11-section output for each company plus Section 12 cross-company comparison

The user can also provide a URL instead of a company name (e.g., "productside.com"). The skill should resolve the URL to the company, research accordingly, and proceed.

---

### Seven Research Lenses

These lenses structure all analysis. Apply every lens to every entry point.

**Lens 1 — Financial Landscape and Business Outcomes**
How the entity makes money. Major revenue streams and cost drivers, margin pressures, growth levers, retention and expansion dynamics, capital intensity, seasonal or cyclical patterns, major risks to performance.

**Lens 2 — Market Offer and Business Model**
How the entity creates and captures value. Target markets, buyers, users, influencers, administrators, and blockers. How segments differ. Multi-sided or multi-stakeholder dynamics.

**Lens 3 — Product Portfolio and Product Outcomes**
Major offers, product families, services, platforms, channels. Bundled solutions, ecosystem plays. Digital versus human-assisted components. Legacy versus emerging offers. Distinction between business line, offer, product, feature set, service layer, and enabling platform.

**Lens 4 — Competitive Dynamics**
Direct competitors, adjacent competitors, substitutes, emerging disruptors. Where differentiation is won or lost.

**Lens 5 — Rising Trends and Strategic Concerns**
Market trends, regulatory forces, technology shifts (especially AI and automation), operational constraints, buyer expectation changes, threats from consolidation or commoditization.

**Lens 6 — How Product Management Works Here**
Product-led vs sales-led vs service-led behavior. Centralized vs federated product structures. Platform vs solution orientation. Roadmap and innovation posture. Compliance or governance overhead. Discovery maturity, data maturity, experimentation maturity, AI maturity. Cross-functional friction. Label inferences clearly.

**Lens 7 — Strategic Signals**
Three signal types — always check all three:
- **Patent activity:** Recent filings and grants via patent databases. Technology domains, R&D clusters, gaps between patent activity and public product narrative.
- **Hiring signals:** Roles open in volume, skills and tools in job descriptions, seniority being hired, language that reveals product culture (discovery, outcomes, AI-native, regulatory, experimentation).
- **Leadership changes:** C-suite and product leadership arrivals or departures in the last 12-18 months. Origin of new leaders (platform companies, consulting, competitors). New CPO, CTO, or CDO roles created, eliminated, or restructured. Board-level changes.

---

### Key Distinctions to Maintain

Always be disciplined about these — collapsing them produces shallow analysis:
- market vs segment
- buyer vs user
- product vs service
- business outcome vs product outcome vs output
- strategy vs tactics
- discovery vs delivery
- platform vs application
- signal vs assumption
- revenue growth vs market share growth vs customer lifetime value improvement vs cost reduction

---

### Tensions Worth Surfacing

Highlight conflicts and tradeoffs wherever they appear:
- growth vs compliance
- scale vs customization
- digital self-service vs high-touch service
- standardization vs domain-specific workflow
- innovation vs legacy burden
- AI ambition vs governance reality
- customer value vs internal efficiency
- short-term revenue vs long-term platform investment

---

### Why This Works

- **Web-grounded:** Uses live search, not training-data recall — output includes citations
- **PM-native:** Every section connects to product management implications, not just business facts
- **Composable:** Stable output format that downstream skills can parse and consume
- **Repeatable:** Same in