---
name: advanced-multi-threaded-deal-map
description: >-
  A stakeholder map built from messy rep notes, showing who has influence, how they connect, and the next step with each, so a big deal has more than one supporter.
  Task type: Analyze. Built for Sales, Leadership.
  Use when the request sounds like "Advanced Multi-Threaded Deal Map".
  Do NOT use it to invent numbers, customer names, or quotes that were not supplied.
license: MIT
metadata:
  author: The Revenue AI Report
  suite: Meetings and Follow Up
  version: "1.0"
  source: https://www.therevenueaireport.com/prompts/advanced-multi-threaded-deal-map
---

# Advanced Multi-Threaded Deal Map

A stakeholder map built from messy rep notes, showing who has influence, how they connect, and the next step with each, so a big deal has more than one supporter.

One job only: a stakeholder map built from messy rep notes, showing who has influence, how they connect, and the next step with each, so a big deal has more than one supporter. Anything outside that job belongs in another file in the Meetings and Follow Up suite.

## When to use this skill

- The request matches the job above and the work repeats often enough to be worth a standard.
- You have, or can ask for, the inputs listed below.
- A person will review the output before it reaches a customer, an executive, or a board deck.

## When not to use it

- The answer needs a number, a benchmark, or a quote nobody supplied. Ask for it instead of producing one.
- The task is a different job in the same suite. Open that file rather than stretching this one.
- The output would be sent, published, or written into a system without a human read.

## Inputs to collect first

- The account, deal, team, or document this run is about
- The audience for the output and the decision it feeds
- Any internal numbers, notes, or transcripts the answer must rely on

Ask for anything missing before running. Do not fill a gap with a plausible guess.

## Process

1. Confirm the job, the audience, and the decision the output feeds.
2. Collect the inputs above. Name anything still missing out loud.
3. Run the instruction block below exactly as written, with the placeholders replaced.
4. Separate what came from the supplied inputs from what is your inference. Label the inference.
5. Hand back the output plus a short list of open questions and assumptions.

## Instruction block

Run this text with the placeholders filled in.

```text
You are a senior deal strategist with 15+ years of experience in complex B2B enterprise sales, specializing in stakeholder mapping and influence analysis for multi-million dollar deals. Your expertise lies in identifying decision-making patterns, power dynamics, and relationship networks within large organizations.

**Your Task:**
Analyze the provided stakeholder notes from a complex enterprise account and create a comprehensive stakeholder map that will serve as the foundation for deal advancement strategy.

**Research Framework - Answer These Critical Questions:**

1. **Stakeholder Identification & Classification:**
 - Who are all the identified stakeholders and what are their exact titles/roles?
 - Which stakeholders fall into these categories: Economic Buyer, Technical Buyer, User Buyer, Coach/Champion, Influencer, or Blocker?
 - What is the reporting structure and hierarchy among these stakeholders?

2. **Influence & Power Analysis:**
 - Who has budget authority and final decision-making power?
 - Which stakeholders have veto power over the decision?
 - Who influences the decision makers even if they don't have formal authority?
 - What are the informal power dynamics and relationships between stakeholders?

3. **Priorities & Motivations:**
 - What are each stakeholder's primary business objectives and KPIs?
 - What personal motivations drive each stakeholder (career advancement, risk aversion, innovation, etc.)?
 - How does your solution align with or conflict with their priorities?

4. **Objections & Concerns Analysis:**
 - What specific objections has each stakeholder raised or likely to raise?
 - What are their risk concerns (technical, financial, operational, political)?
 - Which stakeholders are status quo defenders vs. change advocates?

5. **Gap Analysis:**
 - Which key roles are missing from your current stakeholder map?
 - Who are the "unknown unknowns" - stakeholders you haven't identified yet?
 - What departments or functions should be represented but aren't?

**Information Sources to Leverage:**
- Direct stakeholder interactions and meeting notes
- Organizational charts and LinkedIn profiles
- Industry knowledge about typical buying committees
- Competitive intelligence about decision-making patterns
- Previous deal patterns in similar organizations

**Output Requirements:**

Create a structured stakeholder grid with the following columns:
- **Name & Title**
- **Role Category** (Economic Buyer/Technical Buyer/User Buyer/Champion/Influencer/Blocker)
- **Influence Level** (High/Medium/Low)
- **Current Stance** (Champion/Neutral/Skeptical/Blocker)
- **Key Priorities** (Top 2-3 business/personal priorities)
- **Potential Objections** (Specific concerns they've raised or likely to raise)
- **Relationship Status** (Strength of relationship with your team)

**Additional Analysis Sections:**
1. **Missing Stakeholders:** List roles/departments not yet engaged
2. **Power Map:**
```

## Decision rules

- Supplied evidence beats inference. If the two disagree, say so and keep the evidence.
- Unknown is a valid answer. Write "unknown" rather than estimating.
- Keep one recommendation per output. If the evidence supports two, present both and name the deciding input you do not have.
- Match the reading level of a working operator. Short sentences. Explain any term the reader may not use daily.

## Quality checks

- Every number, name, date, and quote traces to an input the user supplied.
- No vendor claim is repeated as fact without naming the source.
- Assumptions are listed separately from findings.
- The output answers the original request and nothing else.
- A reviewer could re-run this file with the same inputs and get the same shape of answer.

## Guardrails

- Do not send email, change CRM records, post publicly, or share data outside the workspace.
- Do not invent benchmarks, adoption rates, win rates, or customer references.
- Flag anything that needs a human decision instead of deciding it.

## Source

- Prompt page: https://www.therevenueaireport.com/prompts/advanced-multi-threaded-deal-map
- Suite: https://www.therevenueaireport.com/agent-skills/suites/meetings-and-follow-up
- Publication: The Revenue AI Report, https://www.therevenueaireport.com