Stakeholder Map & Outreach Angles
Stop pinging the same VP three times — get a real buying-committee map with sourced signals.
Your highest-score contact just publicly described the problem you solve
| Stakeholder | Role type | Live signal | Score |
|---|---|---|---|
| Hanna Hennig | Economic Buyer | SDC2025 keynote — AI & digital backbone, May 2025 | 9 |
| Johannes Goerg | Technical Buyer | Adobe Summit keynote — CDP MVP in 9 months, Mar 2025 | 6 |
| 🎯 Your Account | Blocker to pre-empt | New IT Procurement role Oct 2024 — 10%+ savings mandate | 3 |
Overview
Your AEs ping the same VP three times and call it multi-threading. This workflow maps the real buying committee from HG contact_search and FAI data — separating budget owners (CIO/CRO) from operational buyers (Engineering / Data leaders) — ranks each stakeholder by recency × role power, and drafts an outreach angle tied to a specific recent signal. Replaces 'who else should I talk to?' with a sequenced touch plan.
Use cases
Multi-threading kickoffs that actually thread
Your AEs say 'we're multi-threaded' but they're really just pinging the same VP at different times of day. This workflow uses HG contact_search to identify 8 named senior contacts at the account, FAI to flag who actually owns the operational decision, and recent web signals (conference talks, role changes) to score who to engage first. Multi-threading becomes 6 named people with 6 different angles, not one VP three different ways.
Champion-loss recovery the same week it happens
When your champion leaves, the deal stalls until the AE rebuilds the relationship from scratch. This workflow runs the same week — pulls 3 named replacement candidates from HG contact_search filtered to the same function, surfaces tenure and recent signals via web search, and pre-drafts an opening message for each that references the departed champion as the trigger. Recovery becomes a 5-minute task instead of a 5-week relationship rebuild.
View workflow prompt
# Stakeholder Map & Outreach Angles
## Parameters
- `{{domain}}` *(required)* — Target company domain HG Insights uses for lookup. Example: `siemens.com`
- `{{product_context}}` *(optional)* — What you're selling — calibrates which roles map to economic buyer / technical buyer / champion. Example: `data platform for B2B marketing`
## Purpose
You are an AE building a multi-thread outreach plan for {{domain}}. The output names real people from contact-search tools (never invented), tags each as economic buyer / technical buyer / champion / blocker for {{product_context}}, ranks them by who to contact first, and gives the AE a calibrated 2-3 sentence opening for each.
## Process
1. **Role mapping** — given {{product_context}}, identify which titles typically map to each role:
- *Economic buyer* — owns the budget (CFO, CIO, CRO depending on product)
- *Technical buyer* — owns the operational decision (VP Eng, Head of Data, CTO)
- *Champion* — feels the pain directly and would advocate internally
- *Blocker* — gatekeeper whose objection can stall the deal (Procurement, Legal, IT Security)
2. **Stakeholder discovery** — call `contact_search` for {{domain}} filtered to senior IT/eng/finance/ops decision-makers depending on the role mapping. List the top 8 by seniority + role match.
3. **Tenure + signal** — for each, capture title, tenure (when known via web search if HG is sparse), and any recent signal: job change, conference talk, public post, podcast appearance. Use `web_search` for the signal hunt; LinkedIn URLs only.
4. **Ranking** — score each stakeholder on `recency × role_power`:
- *Recency*: signal in last 90 days = 3, last 12 months = 2, older = 1
- *Role power*: economic buyer = 3, technical buyer = 2, champion = 2, blocker = 1
- Sort descending. Top 3 are the immediate outreach plan.
5. **Calibrated outreach angles** — for each top-ranked stakeholder, draft a 2-3 sentence opener that references their specific recent signal AND ties it to {{product_context}}.
## Output Format
Markdown with these sections in order:
- `# 🎯 {{domain}} — Stakeholder Map & Outreach Angles` (header + product context)
- `## Role Mapping` (4-row table: Role | Title patterns | Why for {{product_context}})
- `## Stakeholder Map` (8-row table: Name | Title | Tenure | Recent Signal | LinkedIn | Rank Score)
- `## Top 3 Outreach Angles` (for each: name + opening paragraph + why-it-lands bullet)
- `## Recommended Sequence of Touches` (week-1 / week-2 / week-3 cadence with named touchpoints)
All names traced back to contact-search results. No emails, no phones — LinkedIn URLs only.
## Quality Checklist
- All 8 stakeholders are named (not "VP of …") and traced back to `contact_search`
- Each rank score shows its recency × role-power calculation
- Each outreach angle references a specific dated signal (conference talk, post, hire announcement)
- No fabricated emails or phones — only LinkedIn URLs
- Sequence-of-touches names which stakeholder gets which touchpoint, not generic "send LinkedIn message"