agentleFS
stephenroganstephenrogan/csm-skills/skills/stakeholder-map-builder/SKILL.md

stakeholder-map-builder

Skill0 starsChanged 8 months agoMITView on GitHub

Builds a structured map of customer stakeholders with roles, influence levels, engagement status, and relationship strategy per contact. Identifies coverage gaps and single-thread risk. Use when asked to map stakeholders, build an org chart, assess relationship coverage, identify single-thread risk, plan stakeholder engagement, or when a CSM needs to understand who matters at an account and where the relationship gaps are. Also triggers for questions about stakeholder mapping, contact assessment, org chart analysis, relationship coverage, multi-threading assessment, or who to engage at a customer account.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every gap in the map is a bet.

    line 104

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Stakeholder Map Builder

Builds a structured view of who matters at a customer account, how strong your relationship is with each person, and where the gaps are. The most common preventable churn pattern is single-threaded accounts where the champion leaves. This skill makes that risk visible before it materialises.

How to Use

Provide for each known contact:

  • Name, title, function
  • Their relationship to the product (champion, user, economic buyer, decision-maker, blocker)
  • Your relationship strength (strong, adequate, weak, none)
  • Last engagement (when you last spoke and through what channel)
  • Their sentiment (advocate, supportive, neutral, sceptical, detractor)
  • Any notes (political context, personal preferences, upcoming changes)

Also provide:

  • Account ARR and segment
  • Renewal date
  • Any known gaps (people you know exist but have not engaged)

Stakeholder Classification

TypeDefinitionWhy They MatterPriority
ChampionActively advocates for the product. Goes to bat for you internallyIf they leave, the relationship is at immediate risk. Your most important contactCritical -- always engaged
Economic BuyerControls or directly influences the budget decisionIf not engaged, the renewal is decided by someone you have never spoken toCritical -- engage before renewal
Decision MakerHas final authority on the renewal or expansion decisionMay be the same as Economic Buyer or may be different (CEO, board, procurement)High -- at least one touchpoint before any commercial conversation
Technical LeadOwns the implementation and day-to-day technical relationshipIf frustrated with the product, technical issues escalate and adoption stallsMedium -- engage on product-related topics
End User ChampionUses the product daily and advocates to their peersTheir enthusiasm drives organic adoption. Their frustration spreads just as fastMedium -- recognise and support
Executive SponsorSenior leader who provides strategic air cover for the investmentIf unaware of value being delivered, the budget is vulnerable in prioritisation discussionsHigh -- quarterly engagement minimum
InfluencerDoes not decide but shapes opinionsAn unmanaged negative influencer can poison the relationship without the CSM knowingVaries -- identify and monitor
DetractorActively opposed to the product or the relationshipMust be identified and addressed, not ignored. Detractors who are unmanaged become the voice the buyer hearsHigh -- engage deliberately

The Map

## Stakeholder Map: [Account Name]
**Date:** [date] | **ARR:** EUR [amount] | **Renewal:** [date]

### Active Contacts
| Name | Title | Type | Relationship | Last Touch | Sentiment | Notes |
|------|-------|------|-------------|-----------|-----------|-------|
| Tom Chen | VP Engineering | Champion | Strong | Mar 1 (call) | Advocate | Primary relationship. Drives internal adoption |
| Sarah Kim | CFO | Economic Buyer | Weak | Dec 15 (QBR) | Neutral | Met once. Has not engaged since. Critical gap |
| Lisa Park | Eng Manager | Technical Lead | Adequate | Mar 5 (email) | Supportive | Responsive. Handles day-to-day |

### Known But Not Engaged
| Name/Role | Type | Why Not Engaged | Priority |
|-----------|------|----------------|----------|
| CTO (name unknown) | Executive Sponsor | Never identified or introduced | High -- need executive coverage |
| Operations Manager | Potential user | Product is used in Engineering only. Operations could benefit | Medium -- expansion opportunity |

### Coverage Assessment
| Coverage Dimension | Status | Risk |
|-------------------|--------|------|
| Champion | ✓ Active (Tom) | Low -- but single-threaded to one champion |
| Economic Buyer | ⚠ Gap (Sarah not engaged) | High -- renewal decision at risk |
| Executive Sponsor | ✗ Missing | Medium -- no strategic air cover |
| Breadth (departments) | ⚠ Narrow (Engineering only) | Medium -- a reorg in Engineering could sever the entire relationship |
| Depth (levels) | ⚠ Thin (VP + Manager, no C-level) | Medium -- no board-level awareness of value |

### Single-Thread Risk
[Assessment: is this account dependent on one person? If yes, what is the mitigation plan?]

### Multi-Threading Plan
| Target Contact | Path to Engagement | First Action | Timeline |
|---------------|-------------------|-------------|---------|
| Sarah Kim (CFO) | Through Tom (champion introduction) | Ask Tom to facilitate a brief ROI discussion | This month |
| CTO | Through Tom or Sarah | Identify name and role first. Then propose executive alignment meeting | This quarter |

Risk Scoring

FactorScoreRationale
Only 1 active contactHigh riskAny disruption to that person strands the relationship
No economic buyer engagedHigh riskRenewal will be decided without your input
No executive sponsorMedium riskInvestment lacks strategic protection
All contacts in one departmentMedium riskDepartmental reorg could sever the entire relationship
Active detractor exists with no engagement strategyMedium riskUnmanaged detractors become louder over time
3+ active contacts across levels and functionsLow riskRelationship is broad and resilient

Quality Gates

  • Is every contact classified by type (not just by title)? A VP can be a champion, an economic buyer, or a detractor. The title tells you their level. The type tells you their role in the relationship
  • Is the economic buyer identified? If you do not know who controls the budget, the most critical gap is finding out
  • Is the single-thread risk assessed honestly? If losing one person would put the account at risk, that risk needs to be documented and addressed
  • Does the multi-threading plan have specific actions with timelines? "Engage more people" is not a plan. "Ask Tom to introduce me to Sarah at the next QBR on April 15" is

Principles

  • The stakeholder map is a living document, not a one-time exercise. Contacts change roles, leave, and shift sentiment. Review the map quarterly and update it after any significant change
  • Your champion is not your only relationship. They are your most important relationship and the bridge to every other relationship at the account. Use the champion to build breadth, not as a substitute for it
  • The economic buyer is always the highest-priority gap. You can survive without an executive sponsor. You can manage without broad departmental coverage. You cannot renew without the person who controls the budget
  • Every gap in the map is a bet. You are betting that the person you have not engaged will not become the decisive voice in the next renewal, escalation, or competitive evaluation. Sometimes that bet pays off. Often it does not

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.