Executive Sponsor Coverage
Sponsor altitude, not just champion movement — and the multi-thread play before the rug pulls.
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
Sponsor altitude is different from champion movement. This workflow audits the named executive sponsors at one customer — are they still in seat, has their function been hit by a restructuring, did the new C-suite hire change the buying committee. Pair with `champion-change-alert-brief` (which catches champion movement) for the full coverage picture.
Use cases
Catch sponsor erosion before the renewal call
The CFO who championed your platform last year is now in a different company. The CIO who replaced him is reviewing every vendor contract. This workflow surfaces both events from `contact_search` + `company_firmographic` and names the 2-3 most likely replacement sponsors — so your CSM multi-threads before the renewal call.
Sponsor altitude vs champion movement
`champion-change-alert-brief` catches when the day-to-day user-side champion changes. This workflow catches when the exec sponsor changes — different altitude, different risk shape. Cross-reference both for the full coverage picture.
View workflow prompt
# Executive Sponsor Coverage
## Parameters
- `{{domain}}` *(required)* — Customer company domain. Example: `acme.com`
- `{{your_product}}` *(required)* — Your product — anchors which functions matter for sponsor coverage. Example: `HG Insights`
- `{{prior_sponsors}}` *(required)* — Comma-separated named exec sponsors from the deal cycle and most recent QBR. Example: `Jane CFO, John VP Eng`
## Purpose
Audit executive sponsor coverage at {{domain}} for {{your_product}}: are {{prior_sponsors}} still in seat, has their function been hit by a restructuring, did the new C-suite hire reshape the buying committee. Higher altitude than `champion-change-alert-brief` (which catches champion movement at the working-level).
## Process
1. **Sponsor presence** — for each name in {{prior_sponsors}}, call `contact_enrich` with parsed firstName + lastName + `companyDomain` = {{domain}} (named-presence check; `contact_search` only filters by title / seniority / location, not by name). For each: still at the company / moved roles internally / left.
2. **Function stability** — `company_fai` for {{your_product}}. Capture the sponsor's function's current `departmentUsageShare` and `departmentSignalStrength` (the tool returns point-in-time only, no trend). A low current share in the sponsor's function + the sponsor still in seat = fragile coverage; the sponsor is exposed when the function is hollow.
3. **Org-level resets** — `company_firmographic` for static context. For strategic events (new C-suite hires in last 6 months, M&A, RIF), route through `web_search` (and `sec_filing_section` for public-company 10-K disclosures). Firmographic is static-only. New CFO in seat → budget re-evaluation likely → existing sponsor's authority may have eroded.
4. **Gap analysis** — for each missing sponsor, who would naturally inherit the relationship? `contact_search` for replacement-tier titles. Name them as multi-thread targets.
5. **Coverage verdict** — Green (all sponsors present + stable function), Yellow (1 missing OR function weakened), Red (≥2 missing OR new CFO).
## Output Format
- `# 🧭 {{domain}} — Sponsor Coverage: <Green|Yellow|Red>`
- `## Sponsor roster` — table: name | role | status (Present / Moved / Left) | evidence source
- `## Function stability` — short paragraph + FAI signal
- `## Multi-thread targets` — 2-3 named replacement-tier candidates if any sponsor is missing
- `## Recommended outreach` — one specific action (e.g., "Schedule a 30-min introduction with the new CFO before Q3 budget close")
## Quality Checklist
- Every sponsor status cites `contact_enrich` (NOT `contact_search` — that doesn't accept name filters)
- Function-stability claims cite `company_fai` current `departmentUsageShare` / `departmentSignalStrength` (point-in-time, no trend)
- No fabricated sponsor names or roles
- Multi-thread candidates only from `contact_search` results at the relevant seniority (no LinkedIn scraping or guessing)
- Verdict matches the named criteria, not vibes
- Cap tool calls at ~8