---
name: stakeholder-map-builder
description: Builds an evidence-backed stakeholder map for an account or opportunity, showing roles, influence, relationship status, concerns, and information gaps. Use for buying-group mapping, account planning, opportunity research, stakeholder discovery, or multi-threading preparation.
license: Apache-2.0
metadata:
  adlass.categories: "sales-crm/account-management, sales-crm/lead-research"
  adlass.industries: ""
  adlass.tags: "stakeholder-map, buying-group, account-planning, influence, sales"
  adlass.adaptation: "mapping"
  adlass.source: "n8n:2582, n8n:4191, original"
  adlass.version: "1"
---

# Stakeholder map builder

## Purpose

Turn scattered account and opportunity evidence into a clear map of the people and roles relevant to a sale. Distinguish known relationships from inferred buying roles and expose coverage gaps.

## Scope

Names, titles, functions, decision roles, influence, known concerns, relationship history, source evidence, and missing stakeholder coverage.

**Excluded:** personal profiling, contact discovery without a permitted source, outreach, and asserting a decision maker without evidence.

## Data basis

- Account, contact, opportunity, and meeting records.
- Public company and role pages when enabled.
- Buying-process framework in scope.

## Result

A stakeholder map and a relationship-gap memo with suggested research questions.

## Quality criteria

- Each person or role has a source citation and confidence.
- Known contacts are separated from inferred roles.
- Influence and decision authority are not conflated.
- Duplicate identities are resolved or flagged.
- Every gap states what evidence would close it.

## Instructions

Use the buying-process vocabulary in scope. Map roles before assigning individuals to them. Treat title-based role assignments as hypotheses. Preserve contradictory evidence and date relationship claims. Do not include personal information unrelated to the business decision.

## Adapt before use
Keep a clear audit trail throughout the run. Use the source wording and field values that support each material conclusion, and retain uncertainty when the evidence does not decide the issue. Separate a missing record from a negative result and a contradictory record from an exception. Prefer a short, prioritised result over unsupported completeness. Check that counts, identifiers, dates, and labels agree across the written result and the structured output. When a rule, source, or mapping is unavailable, name the limitation and explain how it affects interpretation. Do not silently infer ownership, approval, timing, or business intent.

- Define buying roles and influence vocabulary.
- Map account and contact columns.
- Set permitted public sources and confidence rules.