Formula
Worked example
A stakeholder map for one account, 4 months before renewal. (Example.)
| Role | Engaged in the last 90 days? |
|---|---|
| Executive sponsor | No |
| Champion | Yes |
| Day-to-day admin | Yes |
| Power users | Yes |
| Finance or procurement | No |
| IT or security | No |
All three engaged threads sit at user level. If the champion left tomorrow, nobody with budget would know the account, so the first move is an exec-to-exec meeting with the executive sponsor.
How CS leaders use it
Ask for a stakeholder map on every account above a set ARR, and review it at the 120-day renewal checkpoint. Check that each account has contact above the champion and that more than one person on your side knows the customer. Each business review or success plan update is a reason to invite someone you haven't met yet. When a champion leaves, the other threads are what carry the renewal. Horizon checks job changes through Apollo and caps an account's health score at 50 for 60 days when a champion or sponsor leaves; see the customer health score.
Common mistakes
- Counting contacts instead of roles. Ten users on one team are still one thread.
- Threads only at user level, with no one who owns the budget.
- One person on your side holding every relationship.
More on this topic: renewals, definitions, guides and tools.
Updated November 3, 2026