Competitor-in-Deal Detector

Confirm which deals actually have a competitor in them — by checking the account's installed technographic footprint, not the rep's hunch.

RevOps - Competitive

Which deals really have a competitor — from installed footprint, not hunches

12
Deals checked
Hunch vs. reality
3 'competitive' deals are greenfield.
2 hidden competitors the rep missed.
DealInstalledClass
AcmeDatadog (stable)Defend
BetaNew Relic (shrinking)Displace
GammaNoneGreenfield
Why it lands
Reps discount deals they think are competitive. Three of those 'competitive' deals are actually greenfield — no competitor installed — so the discount was margin given away for nothing.

Overview

Cross-reference a pasted pipeline against HG technographic data to detect which deals have a named competitor's product already installed (a real competitive situation) versus which are greenfield — so competitive plays and discounting are targeted at the deals that need them.

Use cases

  • Stop discounting greenfield deals

    A rep assumes a competitor and offers a competitive discount. Technographic shows no competitor is installed — that discount just gave away margin on a deal you were going to win anyway.

  • Catch the hidden competitor

    The rep didn't flag a competitor but one is installed and growing. That's the deal that surprises you at the finish line — found early enough to run a displacement play.

View workflow prompt
# Competitor-in-Deal Detector

## Parameters

- `{{pipeline}}` *(required)* — Pasted deals (deal, domain, amount, rep-suspected competitor). Example: `Acme - acme.com - $80k - suspected: Datadog`
- `{{competitors}}` *(required)* — The competitor products to detect. Example: `Datadog, New Relic, Dynatrace`

## Purpose
For each deal in {{pipeline}}, confirm via HG technographic whether any product in {{competitors}} is actually installed at the account — turning the rep's competitor hunch into a fact and flagging the discrepancies.

## Process
1. **Parse** — read {{pipeline}} with each rep's suspected competitor.
2. **Detect footprint** — `company_technographic` per domain; check for any product in {{competitors}}. `company_install_time_series` where available to see whether the competitor's footprint is growing or shrinking.
3. **Reconcile with the hunch** — flag deals where the rep suspected a competitor but none is installed (greenfield, easier deal) and deals where a competitor is installed that the rep didn't flag (hidden competitive risk).
4. **Intent context** — `company_intent` to see if the account is researching alternatives (a competitor on the way out).
5. **Classify** — Defend (competitor installed + stable), Displace (competitor installed + researching alternatives), Greenfield (no competitor).

## Output Format
Markdown with:
- `# Competitor-in-Deal Detector`
- `## Deal Classification` (table: deal | competitor installed? | trajectory | class)
- `## Discrepancies` (rep hunch vs. installed reality)
- `## Plays` (per class: the competitive motion that fits)
- `## Citations`

## Quality Checklist
- Every 'competitor installed' claim cites `company_technographic`
- Footprint trajectory cites `company_install_time_series` where used
- Discrepancies between rep hunch and data are called out explicitly
- Greenfield deals are not given competitive discounts they don't need