HG Insights|Phoenix

Incumbent-Tenure Displacement Sequencer

The incumbent has been installed for years and intent is rising — that's the displacement window. Anchored on the signal HG actually exposes, not the one we wish it did.

Incumbent-Tenure Displacement Sequencer
Sample preview

Sample output for this workflow will appear here once it is captured.

Run the workflow in Claude, ChatGPT, or Phoenix Playground using the buttons below to see real output.

Overview

Surface accounts whose {{incumbent_product}} install has crossed the typical 2-3 year tenure mark — the proxy displacement-window signal per the canonical `company_contracts` source docs (which route product-renewal questions to `company_technographic.firstVerifiedDate`). Compose with intent at `buyers_journey: "Evaluating"` or `"Purchasing"` to surface accounts that are both procurement-cycle-ripe and actively evaluating.

Use cases

  • The proxy that works because HG actually exposes it

    Your BDR runs this with the incumbent product and gets a ranked list of accounts whose install has crossed the typical multi-year tenure mark AND whose intent on the replacement category is active. The hook ties tenure to the active intent signal — not a fabricated renewal date.

  • Honest about what HG MCP exposes

    HG's `company_contracts` is GSI/ICT-outsourcing data — Accenture/IBM/Cognizant deals — not SaaS product renewals. This workflow respects that scope and uses the canonical proxy (`company_technographic.firstVerifiedDate`) instead. No fabricated renewal dates that will drift the moment a procurement team checks them.

View workflow prompt
# Incumbent-Tenure Displacement Sequencer

## Parameters

- `{{domains}}` *(required)* — Comma-separated target-account domains (the territory's named-account list). Example: `acme.com,globex.com,initech.com`
- `{{incumbent_product}}` *(required)* — The incumbent product whose long tenure signals a likely renewal/displacement window. Example: `Salesforce`
- `{{your_product}}` *(required)* — Your product or category — used to resolve intent topics and frame the displacement angle. Example: `HubSpot`
- `{{tenure_min_months}}` *(required)* — Minimum incumbent install tenure in months (default 24 — typical SaaS multi-year cycle. Use 36 for enterprise on-prem.). Example: `24`
- `{{buying_function}}` *(required)* — The function whose contact titles `contact_search` should target (Engineering, Security, Sales Ops, etc.). Example: `Sales Ops`

## Purpose
You are a BDR working a displacement motion against {{incumbent_product}}. **HG MCP does not expose product/SaaS contract renewal dates directly** — the contracts tool in HG MCP is scoped to ICT/GSI outsourcing contracts (Accenture, IBM, Cognizant deals), NOT individual SaaS product renewals. Per the canonical source docs, the proxy for product-renewal proximity is install tenure via `company_technographic.firstVerifiedDate`. Surface accounts whose {{incumbent_product}} install has crossed {{tenure_min_months}} months — they're in or near their renewal/decision cycle — and corroborate with intent at `buyers_journey: "Evaluating"` or `"Purchasing"` on {{your_product}}'s category.

## Process
1. **Resolve product** — `get_vendor_information` once with `vendorName: {{incumbent_product}}` to obtain the `vendorId`. (Alternative: `list_product_categories` if {{incumbent_product}} is best matched at category level.)
2. **Tenure probe per account** — for each domain in {{domains}}, `company_technographic` with the resolved `vendorIds: [<vendorId>]` filter. Compute install tenure as (today − `firstVerifiedDate`) per row. Keep accounts whose tenure exceeds {{tenure_min_months}} months.
3. **Intent corroboration** — `list_intent_topics` once for {{your_product}}'s category. For each surviving account, `company_intent` with `limit: 200`. Post-fetch filter `topics[]`; keep accounts whose `buyers_journey` is `"Evaluating"` or `"Purchasing"`.
4. **Firmographic gate** — `company_firmographic` confirms industry / employee band; drop ICP misses.
5. **Contact pass** — `contact_search` per account for {{buying_function}} senior titles (Director / VP / Head of). `contact_enrich` only for the top 5 accounts (3 credits each — budget per [`hg-credit-awareness`](https://phoenix.hginsights.com/gtm/skills/hg-credit-awareness)).
6. **Rank** — by tenure (longest first — most-likely-in-cycle), then by intent score.

## Output Format
- `# 🎯 Displacement Window: {{incumbent_product}} long-tenure accounts`
- `## Ranked accounts` — table: rank | domain | incumbent tenure (months since `firstVerifiedDate`) | intent buyers_journey | suggested contact | one-line hook
- Hook ties the tenure-cycle implication to the intent signal per [`opening-line-discipline`](https://phoenix.hginsights.com/gtm/skills/opening-line-discipline)
- Each row cites `[company_technographic]` for tenure and `[company_intent]` for `buyers_journey`

## Quality Checklist
- The hook NEVER claims a specific renewal date — the workflow exposes install tenure as a proxy, not the contract itself
- Tenure is computed from `firstVerifiedDate` per row, not approximated
- Intent corroboration is post-fetch filtered (the endpoint is `extra: "forbid"`)
- `contact_enrich` is budget-capped at 5 accounts per run