Stakeholder Mapping for Deals

Map deal stakeholders by role, influence, priorities, objections, and next engagement actions.
Sales - Discovery - Stakeholder Mapping for Deals

Who it's for

Account executives, Sales reps, Sales managers, Founders, Customer success leads

Get Ready

Prepare the Required Inputs listed in the Workflow Prompt. Use as much detail as necessary.

How to use this prompt

1. Copy the Workflow Prompt.
2. Paste it into your AI tool.
3. Replace the "Required Inputs"
4. Run the prompt.

🔒

Unlock the Full Workflow

Get access to this workflow and 1000+ others designed to save hours and get better results with AI.

Workflow Prompt

				
					You are a deal strategy advisor. Your task is to create a stakeholder map for a sales opportunity so the seller can understand who is involved, what each person cares about, and how to engage them.

### Required Input
- Account: [Company name and basic context, e.g. 300-person logistics firm expanding regionally]
- Offer: [What you sell and the core business outcome]
- Known Stakeholders: [Names or roles, e.g. CFO, Operations Director, IT Manager, Procurement]
- Contact Notes: [What each person has said, asked, objected to, or requested]
- Deal Stage: [Discovery, demo, proposal, procurement, renewal, expansion]
- Decision Process Known So Far: [How decisions appear to be made, e.g. CFO approval after operations shortlist]
- Main Risks or Concerns: [Budget, timing, security, adoption, competing vendor, internal priority]

### Input Validation
Review the inputs before creating the stakeholder map. If known stakeholders, offer, deal stage, or contact notes are missing or too limited, ask specific clarification questions. Pause and wait for clarification before generating the final output.

### Instructions
Build a practical stakeholder map that helps the seller take action. Do not assume formal authority based only on job title. Infer influence cautiously from behaviour, access, questions asked, objections raised, and involvement in next steps.

Classify stakeholders by likely role in the buying process, such as economic buyer, decision maker, technical evaluator, user champion, blocker, procurement gatekeeper, legal reviewer, executive sponsor, or unknown. A person may have more than one role if the notes support it.

For each stakeholder, identify likely priorities, personal success measures, concerns, objections, influence level, current sentiment, and what the seller should do next. Separate confirmed information from assumptions.

Look for missing stakeholders who may need to be involved before the deal can progress. Highlight risks where the seller is over-reliant on one contact or lacks access to the economic buyer.

Recommend an engagement strategy that is respectful and realistic. Include what to ask the current champion, how to request introductions, and what value message should be tailored to each stakeholder.

### Output
Provide the stakeholder map in this format:

1. Deal Context Summary
2. Stakeholder Table: Role, Influence, Sentiment, Priorities, Concerns, Evidence
3. Confirmed Buying Roles
4. Likely Missing Stakeholders
5. Champion Strength Assessment
6. Blocker or Risk Assessment
7. Stakeholder-Specific Messaging Angles
8. Introduction Requests to Make
9. Next Engagement Plan
10. Open Questions to Confirm Decision Dynamics
				
			

Optional advanced instructions

				
					Add a relationship risk rating for each stakeholder and explain the highest-risk gap in the deal.
				
			

Example output

1. Deal Context Summary

Account: HarborLink Logistics, a 300-person regional logistics firm expanding into two new distribution markets

Offer: Route optimisation and dispatch visibility software that reduces delivery delays, improves fleet utilisation, and gives operations leaders real-time exception visibility.

Deal Stage: Post-discovery demo

2. Stakeholder Table: Role, Influence, Sentiment, Priorities, Concerns, Evidence

  • Maya Chen, Operations Director: User champion and operational decision maker. Influence: High. Sentiment: Positive but cautious. Priorities: reduce late deliveries, improve dispatch visibility, standardise processes. Concern: dispatcher adoption. Evidence: requested demo focused on live dispatch board and exception alerts.
  • Daniel Ortiz, CFO: Likely economic buyer. Influence: High. Sentiment: Unknown to neutral. Priorities: ROI, overtime reduction, margin protection. Concern: subscription cost and implementation risk. Evidence: CFO approval required after shortlist.
  • Priya Nair, IT Manager: Technical evaluator and possible blocker. Influence: Medium to high. Sentiment: Neutral. Priorities: TMS integration, security, implementation workload. Evidence: asked for integration documentation and security questionnaire.
  • Elise Morgan, Procurement Lead: Procurement gatekeeper. Influence: Medium. Sentiment: Unknown. Priorities: contract terms, vendor compliance, pricing structure.
  • Tom Reyes, Dispatch Supervisor: User influencer and adoption risk indicator. Influence: Medium. Sentiment: Mixed. Priorities: ease of use and fewer manual calls. Concern: alerts slowing dispatchers down.

3. Confirmed Buying Roles

  • User champion: Maya Chen, Operations Director
  • Likely economic buyer: Daniel Ortiz, CFO
  • Technical evaluator: Priya Nair, IT Manager
  • Procurement gatekeeper: Elise Morgan, Procurement Lead
  • User influencer: Tom Reyes, Dispatch Supervisor

4. Likely Missing Stakeholders

  • Regional branch manager from the site using the competing vendor
  • Customer service leader who handles delivery complaints
  • Executive sponsor if expansion risk is visible at CEO or COO level
  • Legal reviewer if contract terms require review

5. Champion Strength Assessment

Maya appears to be a credible champion because she owns the operational problem, requested a specific demo, and understands the internal approval path. Champion strength is moderate to strong, but not yet proven.

6. Blocker or Risk Assessment

  • IT could slow the deal if integration requirements are complex or undocumented.
  • Dispatch supervisors could block adoption if they view alerts as noise.
  • CFO could reject the project if ROI is not quantified.
  • Competing vendor presence creates comparison risk.
  • Seller is currently over-reliant on the Operations Director.

7. Stakeholder-Specific Messaging Angles

  • Operations Director: Standardise dispatch execution and reduce late-delivery escalations.
  • CFO: Protect margin during expansion by reducing overtime and inefficient routing.
  • IT Manager: Low-risk integration path and secure data handling.
  • Procurement Lead: Transparent pricing and contract clarity.
  • Dispatch Supervisor: Faster exception resolution and fewer manual status calls.

8. Introduction Requests to Make

  • Ask Maya to include Daniel for a short ROI alignment discussion before proposal.
  • Ask Maya to include Priya in a technical review before integration assumptions are made.
  • Ask Maya whether Tom should pressure-test dispatcher workflow during the demo.
  • Ask Maya whether a regional stakeholder using the competing tool should be included.

9. Next Engagement Plan

  • Run a tailored demo for Maya, Tom, and Priya using two realistic dispatch exception scenarios.
  • Confirm operational success metrics and adoption requirements.
  • Schedule a CFO-focused call to review the business case and budget path.
  • Provide IT with integration and security documents before proposal.
  • Delay full pricing proposal until CFO and IT criteria are clearer.

10. Open Questions to Confirm Decision Dynamics

  • Who owns the final yes or no after operations shortlists vendors?
  • What budget has been set aside?
  • What criteria will be used to compare vendors?
  • How much influence does the branch using the competing vendor have?
  • What adoption concerns have caused past tools to fail?
  • What implementation date is required to support regional expansion?

When to reuse this workflow

You may also like...

🔒

Unlock the Full Workflow

Get access to this workflow and 1000+ others designed to save hours and get better results with AI.

No guesswork. Just proven systems.

  • Copy & paste ready prompts
  • Step-by-step instructions
  • Works with ChatGPT instantly

BANT-Based Discovery Call Qualification Script

Qualify leads using the BANT framework to determine fit, urgency, and readiness for sales progression.

Proof Points and Case Study Insertion

Strategically insert proof points and case studies into presentations to increase credibility.

Demo Customisation Framework

Customise demos based on prospect context to increase engagement and close rates.

Unlock the full library.

Get access to all workflows, across every sector, with structured systems built for better results.

Get Free Access