competitor-research
Competitor Research
Produce a dated, source-tagged competitive brief for one or more named rival companies.
Input
- One or more competitor company names or domains (required).
- Optional brief purpose (e.g. "battlecard for renewal", "board update", "win-loss prep"). If absent, ask once before running so the synthesis stays grounded.
- Optional priority angles (e.g. "pricing pressure", "AI roadmap", "EMEA expansion").
- Optional named hypotheses to confirm or contradict.
Workflow
-
Anchor on purpose. Restate the brief purpose, priority angles, and hypotheses in 1-2 sentences before any tool call so synthesis stays scoped.
-
Resolve each competitor: match a business by name + domain when available. Domain-variant sanity check: if a major-brand input resolves to a tiny headcount with a "Corporate Managing Offices" or "Hotels and motels" classification, the match likely routed to a registered-agent shell entity. Re-try with the alternate domain or with the company-name string. Do not proceed with the wrong identity. Skip any name that does not resolve confidently and flag it under data quality.
-
Enrich each resolved competitor across these dimensions: firmographics (HQ, headcount, revenue, founded), competitive landscape (named competitors), strategic insights (priorities and recent moves), funding and acquisitions (rounds and M&A), workforce trends (headcount trajectory), technographics (current stack), challenges (publicly surfaced risks), company ratings (third-party signals), and LinkedIn posts (recent owned-channel narrative).
-
Fetch business events for the resolved set, scoped to the last 90 days. Keep events that map to: product launches, leadership changes at vice president and above, funding rounds, M&A, office openings or closures, and material hiring shifts. Discard the rest. Event-attribution sanity check: before including any event row in the brief, verify the event title or snippet actually mentions the target company. Industry-wide articles can be cross-attributed to multiple competitors' identities in the ingestion pipeline.
-
Surface the executive team per competitor: size the audience first (count of C-level and VP roles per company), then sample a small slice for preview. Run a count before any larger pull so you can frame the sample honestly.