SKILL FILE

Stakeholder Map with AI

Map decision-makers, influencers, and users in your target market so you know who actually signs the cheque, who blocks the deal, and who just uses the product.

Download Skill File ↓

What this skill file teaches Claude

Drop one markdown file into your repo. Claude Code learns how to run this entire workflow.

1

Stakeholder inventory

Every role involved in the buying or usage decision — user, champion, economic buyer, technical buyer, blocker, influencer, coach.

2

Power and interest grid

Classifies each stakeholder by how much authority they hold and how much they care, so you know who to manage closely and who to monitor.

3

Pain and motivation per role

What each stakeholder is trying to solve, what they're trying to avoid, and what they need to hear to say yes. Same product, different pitch per role.

4

Blocker pre-emption

Names the people who can kill the deal (IT, legal, procurement) and builds a pack to disarm them before they slow you down.

5

Entry point recommendation

Tells you whether to land champion-first, user-first, or top-down based on price point, deal type, and where you have warm intros.

6

Per-role messaging brief

Channel and message for each stakeholder, so the user gets a 5-minute demo and the VP gets an ROI calculator.

What you can build with this

Enter a new market segment

You've sold to startups. Now you're targeting mid-market. The map changes completely. Build it before you waste a quarter pitching the wrong person.

Diagnose stalled deals

Three deals in a row got to verbal yes then went silent. The map usually reveals a missing champion or unmet blocker.

Design outbound for a new buyer

You need to reach Directors of Marketing, not just any marketer. The map clarifies what to send, what to lead with, and how to land.

Plan the sales playbook

Per-role messaging, per-stakeholder objection handling, blocker pre-emption pack. The map is the source of truth for the whole playbook.

Get the full skill file

Everything above is 80% of the skill file. Download the complete version with full implementation details, agent prompts, and ready-to-run scripts.

Common questions

No. An org chart shows who reports to whom. A stakeholder map shows who influences a decision, in what direction, with how much power. A senior IT person can have low formal authority and high blocking power (the famous "no one ever got fired for saying no" pattern). The map captures that. The org chart doesn't.
Less detail, but still useful. Even self-serve has a champion (the user who signed up), an economic decision (their boss approves expensing it), and a blocker (IT might block the install). For pure consumer products with personal credit cards, you can skip it. For any B2B SaaS over $50/month, the map is worth 30 minutes.
A persona describes one role in depth. A stakeholder map shows how multiple roles interact around a decision. You can have a champion persona, a buyer persona, and a user persona all in play in the same deal. The map tells you which one to lead with and what each one needs to hear. Run `/persona-builder` for the deepest role, run this for the surrounding cast.
Start with a segment-level map (e.g. "50-person SaaS companies"). Then build account-specific overlays for your top 10 target accounts when you have name-and-title intel. The segment map gives you the playbook. The account map customises it.
Look at your last 4 closed deals — 2 won, 2 lost. For each, list who was actually involved and what each one did or didn't do. If your won deals all had a strong champion and your lost deals were missing one, that's signal. Real deal data corrects the abstract map.
It complements them. MEDDIC tells you what to qualify on. The stakeholder map tells you who to qualify with and in what order. Use both. The map informs the qualification questions, MEDDIC structures the deal review. Neither replaces the other.

Ready to automate?

SoloStack gives you every skill pre-installed — scraping, marketing, sales, CRM, and more. One repo. Every department.

Book a Call →