| name | stakeholder-map |
| description | Map evidenced stakeholders; never infer ties from titles. |
| metadata | {"short-description":"Map stakeholders, influence, and coverage gaps"} |
Stakeholder Map
Outcome
An evidence-backed relationship map that reveals support, risk, and missing access.
CRM-neutral operating contract
- Discover available CRM, communication, calendar, knowledge, and file capabilities before choosing a retrieval plan. If no live CRM is available, use user-supplied exports when that still satisfies the request; never imply a live write is possible.
- Map records by meaning, not vendor labels: organization, person, lead, opportunity, activity, product, service record, user or team, and knowledge item. Inspect schemas and custom fields, preserve native IDs, stages, currencies, timezones, and fiscal periods.
- Keep observed facts, derived conclusions, and missing information distinct. Anchor consequential claims to record IDs, fields, timestamps, or named sources, and state access or freshness limits.
- Start read-only. Before creating, updating, assigning, sending, or scheduling, show the exact proposed action and obtain confirmation unless the current request already authorized that exact mutation.
- Obey connected-system permissions, resolve ambiguous records or people instead of guessing, check for duplicates before creation, and report partial failures without repeated retries.
Workflow
- Resolve the user, target records, requested scope, reporting window, timezone, and business objective. Ask only for missing details that materially change the result.
- Retrieve the minimum authorized evidence needed from the following inputs: Contacts, roles, titles, opportunity-contact relationships, meetings, emails, notes, introductions, decisions, and reporting lines when verified.
- Normalize relevant entities and fields while retaining native record identifiers and source timestamps.
- Apply the analysis rules below. When evidence conflicts, show the conflict rather than averaging it away.
- Deliver the required output in a compact form suited to the scope. Put urgent or decision-relevant items first.
Analysis rules
- Separate formal role, buying role, influence, stance, and relationship strength; these are not interchangeable.
- Support every non-obvious classification with interaction or record evidence and a freshness date.
- Mark unknown, ambiguous, and conflicting relationships explicitly.
- Identify coverage gaps such as no economic decision-maker, no champion evidence, single-threading, or missing user representation.
Required output
- Stakeholder table
- Verified relationship map in prose
- Supporters, blockers, and unknowns
- Coverage gaps
- Recommended engagement moves
Actions and boundaries
Propose contact-role updates as field-level changes; confirm before writing.
