HG Insights|Phoenix

Skill: Stakeholder Card Discipline

Stakeholder cards your AE can act on — verified, separated by buyer role, no invented emails.

Overview

Stop invented emails and phone numbers from landing in your AE briefs. Claude renders stakeholder cards with name + title + location + LinkedIn URL only — never fabricates contact details, separates budget owners from operational buyers, and omits any field that wasn't returned by a verified source.

Use cases

  • Outbound that doesn't burn trust on the first email

    If contact_enrich didn't return an email, the brief omits the field — it doesn't guess from a 'first dot last at company' template. The first-touch outreach lands at a real address or doesn't go out, instead of bouncing or reaching the wrong person.

  • Multi-thread plays with budget vs. operational buyers separated

    The stakeholder section splits 'Operational buyers (run the workflow)' from 'Budget owners (sign the renewal)' — your AE walks in knowing who to discover with vs. who to involve at signature time, without having to infer it from titles.

View full skill

Stakeholder Card Discipline

When to use

  • Authoring a workflow that produces stakeholder lists (AE briefs, account plans, outbound prep).
  • Reviewing a stakeholder section that includes contact details — verify against the rules below.

The card shape

A stakeholder card carries:

  • Name (full).
  • Title (current; verified within 90 days).
  • Location (city or region).
  • LinkedIn URL (the canonical /in/... form, not a search-result link).

Optional, only when the source supports them:

  • Department / functional area (from FAI).
  • Tenure (when SEC filings or LinkedIn confirm "in role since [date]").
  • Notable signals (recent press quote, conference talk, etc.) — cite the source.

What never goes on a card

  • Email addresses — contact_search doesn't return them; only contact_enrich does. If the workflow didn't call contact_enrich, omit. Inventing email patterns from a "first dot last at company" template is a fabrication.
  • Phone numbers — same rule. Never invent.
  • Personal social handles (Twitter, Instagram). Professional context only.
  • Speculative attributions ("seems to own the budget") — either the source supports it or omit.

Operational buyer vs. budget owner

Group cards into two sections when both matter:

### Operational buyers (run the workflow)
- Jane Doe — VP Sales Operations, Munich. linkedin.com/in/janedoe
- ...

### Budget owners (sign the renewal)
- Mike Smith — CRO, Munich. linkedin.com/in/mikesmith
- ...

The categorization comes from FAI + title heuristics — see hg-fai for the operational-vs-budget rule.

Common pitfalls

  1. Including a card with only a name and "(VP, IT)". Without title precision and location, the card is unactionable.
  2. Inventing LinkedIn URLs. If contact_search didn't return one, omit; don't construct a URL from "first-last".
  3. Mixing budget owners and operational buyers in one list. Two different conversations.

Reference