Authority Mapping: Who Actually Makes the Decision?

What authority mapping actually means

Authority mapping is the discipline of naming every person who shapes a buying decision, then ranking each one by signing power, budget access, and veto risk. The output is a one-page chart that says exactly who signs, who blocks, and who you still need to meet. Reps who run authority mapping on day one of a deal close 2 to 3 times more often than reps who guess (UserGems Multi-Threading Benchmark, 2025).

Direct answer. Authority mapping pinpoints the economic buyer, the champion, the silent blocker, and the day-to-day users inside a B2B deal. Build a draft from public sources before the first call, validate the economic buyer by meeting two, and re-score every contact after each committee meeting. The map closes deals when it ranks people by influence, not by job title.

Most reps already do half of this work. They know the champion. They have heard the economic buyer's name. What they almost never do is write the map down, score the contacts, and update the chart after every meeting. The first two steps win a deal. The third one holds the forecast.

Why authority maps fail before the first call

Authority maps fail for three predictable reasons. The rep builds the map from titles instead of behaviour. The rep mistakes a champion for an economic buyer. The rep stops updating the map after the discovery call. Each failure mode has a cost. The Gartner 2024 B2B Buying Journey study pegged the average committee at 11 people, up from 5.4 in 2014. A map built on titles alone misses the rise.

The deeper problem sits in pipeline reviews. Managers ask "who is the decision maker?" and reps name one person. The forecast inherits that fiction. When the deal slips, the manager learns there were six people in the room, two of whom had veto rights. Authority mapping kills that fiction at week one. For more on why single-threaded deals collapse, see the buying committee playbook and the deeper failure pattern in why multi-threading a deal always fails.

The 7-step authority mapping framework

The Gangly Authority Loop is a 7-step framework that turns a guess about who decides into a scored chart of every named contact. Steps 1 and 2 are pre-call and first-call. Steps 3 through 5 are deep discovery. Steps 6 and 7 hold the map open as the deal moves. Reps running the Authority Loop on every opportunity over $25K ARR reduce slipped-quarter forecast variance from 23% to 7% (Gangly customer benchmark, 2026). For smaller deals, run a compressed version on steps 1, 4, and 7 only.

1. 1

   Pull the org chart before the call

   Build a baseline tree from LinkedIn, the company press page, and the 10-K (if public). Mark headcount under each VP. You start the call with a hypothesis, not a blank slate.

2. 2

   Confirm the trigger and the budget owner on the first call

   The person who feels the pain rarely owns the budget. Ask who funded the last project of this size and who blocked the one before it. Two answers, two roles, both written down.

3. 3

   Map titles to roles, not the other way around

   A VP of RevOps at one company is the economic buyer; at another, the same title is a power user. Map by behaviour and budget, not by job title alone.

4. 4

   Score every contact on access and influence

   Use a 1-5 scale on access (can you reach them this week) and influence (would the signer pause for their veto). Anyone below 3 on both is noise.

5. 5

   Identify the signal silencer

   Every committee has one person who can quietly kill the deal — procurement, legal, security, or a peer VP. Surface them in week one or they surface in week six.

6. 6

   Trade a thread for a thread

   Multi-threading is a transaction. Bring the champion an insight worth forwarding, then ask for the next introduction. Never ask cold.

7. 7

   Re-map after every committee meeting

   The committee changes between calls. New stakeholders enter. Old ones go quiet. Re-draw the map after every meeting where two or more people attend.

The framework is a loop, not a checklist. The rep re-enters step 4 after every committee meeting, re-scores every contact, and shifts thread targets when influence changes. The rep who treats the map as a one-time deliverable will lose to the rep who treats it as a weekly habit.

The four authority roles every deal contains

Every B2B deal contains four authority roles. The names change. The roles do not. Memorise the four, then assign each named contact to one of them. The map gets sharp the moment every contact has a role.

Two warnings. First, the same person can hold two roles — a VP of RevOps is often both economic buyer and power user. Score them on both axes. Second, the silent blocker is usually invisible from public sources. The champion knows the blocker's name. Ask in week one. For tighter qualification language, the MEDDPICC framework maps these roles to a scorable rubric.

Discovery questions that surface the real signer

Discovery surfaces the map. The questions below are designed to pull out roles, budget paths, and silent blockers without making the champion feel cornered. Use all five on call one or two. Save the harder framings for call three.

The five questions on the left surface the map without threatening the champion. Each one starts with a process question, not an authority challenge. The champion answers because the question is about the company, not about their power. The questions on the right read as accusatory. Most reps still ask them and lose the next meeting. For more on call structure, see the sales discovery call playbook and qualifying questions that actually qualify.

How to validate the economic buyer without burning the champion

The hardest move in authority mapping is reaching the economic buyer without making the champion feel skipped. Three rules hold. First, never go around the champion silently. Second, never go around them quickly. Third, always trade an insight for the introduction.

1. 1

   Tell the champion you need to meet the economic buyer, and why

   "For a deal this size, my company expects me to validate the business case with the budget owner before we move further. That is how I keep your timeline safe." Honest, deal-protective, and frames the request as a benefit to the champion.

2. 2

   Bring an insight the economic buyer will care about

   A benchmark, a competitor move, a regulatory shift. The champion forwards insight, not requests. Make the introduction worth forwarding.

3. 3

   Offer to draft the introduction email

   Most champions never write the email because they do not know what to say. Give them a 60-word draft they can forward in one click. Win-rates on champion intros climb when the rep writes the email.

Some deals never produce a champion introduction. In that case, run a parallel thread — a peer of the economic buyer who you reached through a different vector (an event, a referral, a signal-triggered email). Multi-threading is not a back-channel; it is insurance.

The authority map template (copy this on day one)

The authority map fits on one page. Five columns: Name, Title, Role (one of the four from section 4), Access score (1-5), Influence score (1-5). One row per named contact. Add a notes column for the trigger you have on each person — the last conversation, the open thread, the next step.

Two scoring rules. Access measures whether you can reach the contact this week through the channels you have today (champion intro, LinkedIn warm path, event meeting). Influence measures whether the signer would pause if this contact pushed back. Anyone scoring 1 on both axes is not on the map. They are on the org chart.

Update the map after every meeting. The simplest update protocol: open the map inside two hours of the call, add new contacts mentioned by name, re-score anyone who shifted role, and write one sentence on what changed. Reps who update inside two hours catch role shifts the manager would otherwise miss for a week.

Mistakes that flatten the map and stall the deal

Most authority maps fail in the same five ways. None of the failures show up in a CRM field; all of them show up in the slipped deal. Audit the map against this list once a week.

1. 1

   Mistaking the champion for the economic buyer

   The champion takes the meeting. The economic buyer signs the contract. Conflating the two flattens the map into one row and the deal into one thread.

2. 2

   Skipping the silent blocker

   Procurement, legal, and security surface eventually. The cost of surfacing them in week 8 is a quarter; the cost in week one is a phone call.

3. 3

   Mapping titles, not behaviour

   A VP of RevOps at a 200-rep company is an economic buyer; at a 20-rep company, the same title is a power user. Re-score by behaviour, not by job board title.

4. 4

   Static maps that never get re-scored

   The Forrester 2025 B2B Buyer Study pegs median committee composition shift at 90 days. Maps that never refresh become fiction inside one quarter.

5. 5

   Asking "are you the decision maker?"

   Most contacts will say yes. None of them are. Ask process questions instead: who funded the last project, who blocked the last vendor, what does approval flow look like.

A sixth failure mode shows up only in enterprise: the rep meets the economic buyer once, declares the map complete, and stops re-meeting them. Economic buyers shift attention. A quarterly check-in keeps the thread warm. Without it, the rep enters renewal cold. For longer-cycle deals, the AE multi-threading guide covers cadence in detail.

Verdict. Authority mapping wins deals because it converts a guess into a chart. The chart is only as good as the last update. Reps who run the seven-step loop weekly forecast inside 5% of close. Reps who build the map once and walk away forecast inside 25% on a good quarter.

How Gangly fits the authority mapping workflow

Gangly stitches the authority map into the rep's daily workflow instead of a static slide. Signals from job-change feeds, intent data, and call transcripts flow into the same map. The rep opens one view to see who joined the committee, who changed role, and who needs an introduction this week.

• Signal Detection: surfaces job changes, funding events, and product launches that shift committee composition so the rep re-scores the map before the next call.
• Call Prep Engine: pulls the authority map into the pre-call briefing so the rep walks in knowing every named contact, their role, and the open thread.
• Post-Call Notes: auto-updates the map after each call by extracting new names, role shifts, and silent blockers from the transcript.
• CRM Hygiene: keeps the contact records, roles, and access scores synced to Salesforce or HubSpot so the forecast inherits the map.

The product brief: a rep should never maintain the authority map as a separate slide. The map should live where the rest of the deal lives — inside the CRM, fed by signals, refreshed by every call. See the connected sales workflow for the full sequence or book a demo to see the live authority map view.

Frequently asked questions

The questions below come from rep interviews, Reddit threads in r/sales, and the People Also Ask block on the keyword. Each answer is short on purpose. The full framework lives in section 3.