<!-- Markdown rendering of https://salesascode.com/docs/library/relationship-map. The HTML page is canonical. -->

# Relationship Map · Docs · Sales as Code

[← All feature docs](https://salesascode.com/docs/library)

Feature docs · /relationship-map

# Relationship Map

Map an account's stakeholders onto the buying committee and see the white space, the roles with no relationship yet.

Included with [salescron](https://salesascode.com/docs/library/salescron) . A seat without it sees an upsell here instead of the page.

[Open Relationship Map →](https://salesascode.com/relationship-map) [All docs](https://salesascode.com/docs/library)

## Overview

[Relationship Map](https://salesascode.com/relationship-map) answers the question every complex deal turns on: do we know everyone we need to, and where are we exposed. It places each known stakeholder on the buying committee by their title and shows the white space, the committee roles with no relationship yet, each with the next move. This is the salescron equivalent of an account-mapping tool like DemandFarm or Altify.

**What it is for, on the page.** Under the headline, this page says what it produces, what makes it run, and where the output lands. Every Work page reads that line from one registry, so the three answers cannot drift from the page.

## The committee and the white space

The map covers the roles a complex deal needs: economic buyer, executive sponsor, champion, procurement, legal, and security. Each stakeholder's title places them on the committee (a CFO is an executive sponsor, a security engineer covers security, and so on), and the strongest relationship wins a role when more than one contact could fill it. A required role with no engaged contact is white space, shown in red with the next move, never a fabricated relationship.

## Coverage, power, and single-threading

The map scores committee coverage 0 to 100, weighted by relationship strength, so a role covered only by a weak contact counts for less than one held by a strong champion. It flags whether you have real power coverage (a strong economic-buyer or executive relationship) and whether the deal is single-threaded, engaged with at most one person, the classic exposure a competitor exploits.

## Where the stakeholders come from

Paste stakeholders directly, one per line with a title and, optionally, a relationship strength and engagement level, or let the map read the contacts already on the account. Nothing is invented: a committee role you have not met stays white space until you actually earn the relationship.

## How it is shown

The design mockup drew the committee as an org-chart-style graph. Here the same information is rendered as a coverage table, one row per committee role, with who covers it, the relationship strength and engagement, and the white-space next move where no one does, plus four summary tiles (coverage score, required roles covered, engaged stakeholders, white-space gaps). Every value is the deterministic engine's output; no relationship is drawn that you have not actually earned.

---

More for agents: [llms.txt](https://salesascode.com/llms.txt), [full reference](https://salesascode.com/llms-full.txt), [OpenAPI](https://salesascode.com/openapi.json), [sitemap](https://salesascode.com/sitemap.xml).
