> ## Documentation Index
> Fetch the complete documentation index at: https://clearskies.cc/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Stakeholder Map

> Who matters in the deal, where you have relationships, and where you're single-threaded. Built from who actually shows up, not from who a rep remembered to add to CRM.

Every rep will tell you they are multi-threaded. The contact list on the opportunity says three people. The call recordings say one person has attended every meeting and the other two have never spoken. A stakeholder map is built from the record of who actually shows up, who replies, and who has gone quiet, then set against who needs to be involved for the deal to close. The output is usually uncomfortable, which is the point: single-threading is a risk that only looks obvious after the champion leaves.

## Data Sources

| Category         | Required | Recommended |
| :--------------- | :------- | :---------- |
| CRM              | ✓        |             |
| Calls            | ✓        |             |
| Email + Calendar |          | ✓           |
| Messaging        |          | ✓           |

**Starter** (required only): the contacts on record, who attended which calls, and who spoke on them.

**Full** (required + recommended): the same, plus email reply patterns, who is being copied and who is being left off, meeting attendance over time, and any shared Slack channels. Email and calendar matter more here than on most use cases. Attendance and reply behaviour are where single-threading actually shows up.

See the [Context Graph](/docs/unifying-gtm-data/customer-context-graph) for how each source feeds the map.

### Choose your path

| Path                       | Best for                                                                   | Output is delivered                   |
| :------------------------- | :------------------------------------------------------------------------- | :------------------------------------ |
| Build in Claude or ChatGPT | Deal reviews, account planning, and one-off checks before a big meeting    | In the Claude or ChatGPT conversation |
| Build in Clearskies        | Teams who want single-threading flagged across the pipeline without asking | To Slack DMs or channels              |

## Build in Claude or ChatGPT

Ask it about one deal when you need it. Most teams start here, because the first useful version of this is a manager checking a deal they are worried about.

### The Prompt

Open Claude or ChatGPT with the Clearskies MCP connected and paste this (or modify to your needs). Replace the account name with your own.

```text theme={null}
Using the Clearskies Context Graph, map the stakeholders on the Acme deal.

For each person we have touched:
- Their role, and what the record suggests about their influence
- How often they have shown up, and whether that is increasing or falling
- Who on our side has the relationship
- When we last heard from them

Then tell me:
- Who is missing that a deal like this normally needs
- Where we are single-threaded
- Who has gone quiet and when

Base influence on what people actually said and decided on calls, not on
their job title. Where the record does not support a judgement, say so.
```

### Make it yours

* Add `Compare this to the stakeholder set on deals we won last year` to ground "who is missing" in your own outcomes rather than a generic buying committee.
* Add `Draft an introduction request I can send my champion` to turn a coverage gap into a next action.
* Add `Do this for every deal in commit and rank by single-threading risk` to run it across a forecast category.
* Add `Who at Acme have we never contacted but should have` when the account is large enough that the gap is white space rather than risk.

### The Skill (Claude)

The `clearskies:deal-review` skill in the Clearskies plugin for Claude audits a deal's risk signals, and champion engagement and economic buyer status are two of them. It is the fastest way to get the stakeholder read as part of a wider risk picture rather than on its own.

`clearskies:account-brief` covers the wider account view: CRM, calls, email, calendar, and Slack in one place, including the people.

#### Trigger phrases

* "Map the stakeholders on \[account]"
* "Are we single-threaded at \[account]"
* "Who do we know at \[account]"

<Tip>
  Want this packaged for your team? [**Reach out**](mailto:support@clearskies.cc) and we'll help you customize the skill to your workflow.
</Tip>

## Build in Clearskies

For teams who want the gap found before anyone thinks to look. Build the workflow once and single-threading gets flagged across the deals that matter.

### The Workflow

In the Clearskies app, open the workflow builder and describe what you want in plain language:

```text theme={null}
Every Monday at 8am, find the open deals over $50,000 closing this
quarter. For each one, check who we have engaged: who attends calls, who
replies to email, and who has gone quiet. Flag any deal where only one
person on the customer side has engaged in the last 30 days, or where we
have no contact with an economic buyer. Post the flagged deals to the
#pipeline channel.
```

The app configures the schedule, the deals in scope, and the destination.

Scheduled workflows have no meeting context, so the deals come from a record lookup. Start narrow. A flag on every deal is noise, and a flag on the fifteen deals that carry the quarter gets read.

### Deploy to Slack

Once published, only the deals that trip a threshold arrive:

```text theme={null}
Single-threading flag — Acme Corp Renewal + Analytics
Owner: Daniel · $84,000 · Close Jul 31

Engaged, last 30 days
• Sarah Kim (Champion) — on all 4 calls, replies within a day. The only
  person on the customer side who has spoken to us since Apr 28.
• David Park (Director, Sales Ops) — 1 call, joined Acme 3 weeks ago.
  Raised onboarding capacity. No email contact.

Gone quiet
• Mark Chen (VP Sales, recorded as economic buyer) — last touchpoint
  9 days ago. Has not attended a call since Apr 21. The deal grew past
  what he previously approved after the analytics module came in.

Missing
No contact in procurement or security, and both were named on the last
call as steps the deal has to clear.

Why this is flagged
One active relationship carrying a $84,000 renewal plus expansion, with
the recorded economic buyer disengaged while the deal size increased.
```

### Customize the rollout

* Set the thresholds that define a flag for you: days since a second contact engaged, calls with a single attendee, no economic buyer on record
* Choose the deals in scope by stage, amount, close date, or owner
* Route flags to the rep, the manager, or a pipeline channel
* Add roles your deals always need so their absence is flagged, not inferred
* Chain it with [deal status](/docs/use-cases/deal-status) so the coverage read arrives with the rest of the deal picture

## The Plugin

**Ready to make this part of your team's workflow?** We'll set up the Clearskies plugin with you. Clearskies workflows, Claude skills, all tailored to how your team works.

[**Book 15 minutes →**](https://calendly.com/pouyan/new-meeting)

## Next steps

1. [Sign in to Clearskies](https://app.clearskies.cc/)
2. Connect your data sources
3. Get your [Clearskies MCP server](/docs/building-with-clearskies/mcp-server) and try with [Claude](/docs/building-with-clearskies/mcp-clients/claude) or [ChatGPT](/docs/building-with-clearskies/mcp-clients/chatgpt)