Competitive Tech Detection Watch
Competitor landed in your account. Which function, how deep, are they researching it.
Sample output for this workflow will appear here once it is captured.
Run the workflow in Claude, ChatGPT, or HG Insights Playground using the buttons below to see real output.
Overview
A competitor product landing in your customer's account is the loudest churn signal HG can surface. This workflow scans `company_technographic` for net-new products in your category at one customer, scores them by intensity and location footprint, and ties the detection to functional area + intent signals — so you know not just *that* a competitor landed, but in which function and whether the customer is researching it. Complement to `competitive-displacement-targets` which surfaces marketing targets.
Use cases
Not just that a competitor landed — which function
Detecting ZoomInfo in your customer's tech stack is half the signal. Detecting ZoomInfo *with intensity 64 concentrated in their Sales function* is the full signal — that's a real displacement risk, not an ops-team trial. FAI + technographic combined.
Intent rise + tech add = actively shopping
If the customer just added a competitor product AND intent on that product is trending positive, they're actively evaluating alternatives. If the tech add is isolated and intent is flat, it might be a one-off trial. The combined view tells your CSM which conversation to have.
View workflow prompt
# Competitive Tech Detection Watch
## Parameters
- `{{domain}}` *(required)* — Customer company domain. Example: `acme.com`
- `{{your_product}}` *(required)* — Your product — the category the competitor scan filters on. Example: `HG Insights`
- `{{named_competitors}}` *(optional)* — Comma-separated known competitor product names. If empty, the workflow filters by the category of {{your_product}}.. Example: `ZoomInfo, Apollo, Clearbit`
## Purpose
Detect and score net-new competitor tech adds at {{domain}} for {{your_product}}'s category. Tie each detection to functional area + intent so you know which function landed it and whether the customer is actively researching the competitor. Complement to `competitive-displacement-targets` (marketing-side prospect list) — this is the CSM defensive-watch tactic.
## Process
1. **Resolve the category** — `get_product_category` to find the category of {{your_product}}. If {{named_competitors}} is supplied, also call `get_vendor_information` for each to confirm catalog match.
2. **Scan technographic** — `company_technographic` for {{domain}} filtered to that category. Identify net-new entries with `firstVerifiedDate` in the last 12 months. For each: `productLocations` (footprint), `intensity` (depth — point-in-time), `firstVerifiedDate` (recency).
3. **Function-level** — `company_fai` for each detected competitor product. Which functions at {{domain}} are using it? A competitor product showing in your buying-committee function is more dangerous than one in an adjacent function.
4. **Intent on the competitor** — resolve each detected competitor to topic_ids via `list_intent_topics`. Call `company_intent` for {{domain}} with `limit: 200`; post-fetch filter `topics[]` for the competitor topics. Positive `trend` = customer is actively researching them.
5. **Score + verdict** — for each detected competitor, compute a severity: High = (≥3 `productLocations` OR `intensity` ≥50) AND (in your buying-committee function OR positive intent). Medium = one of those. Low = single isolated install with no intent + adjacent-function-only.
## Output Format
- `# ⚠️ {{domain}} — Competitor Adds in {{your_product}}'s category`
- `## Detections` — table: competitor | severity | first detected | productLocations | function | intent trend
- `## Recommended action per detection` — 1 sentence per high-severity row (e.g., "Schedule a head-to-head review with the function lead before Q3 budget close")
## Quality Checklist
- Every detected competitor cites `firstVerifiedDate`
- Function-level claims cite `company_fai`
- Intent claims cite `company_intent` with the specific topic_id
- Severity matches the named criteria (productLocations OR intensity gating)
- No fabricated competitors — only catalog-validated results from `get_vendor_information` or `company_technographic`
- Cap tool calls at ~10