Use an account mapping template to connect people to a specific buying decision: record their authority, their relationships, what supports each link, and the next contact needed to confirm a gap. A reporting chart is a useful starting point, but cannot represent non-reporting relationships by itself.
Scope the Account Map to One Buying Decision
Lucid’s published account map template makes a small but revealing distinction: it includes reporting relationships and relationships outside that structure. Its construction guide treats buying roles as another layer, then discusses keeping the map current. These are separate design choices. Put them beside an ordinary contact list and a practical question emerges: can you tell how the next buying decision will travel between these people? A list may tell you whom to call. A hierarchy may tell you who manages whom. Neither entry, by itself, tells you whether a colleague can introduce you to the person who approves the purchase. That is the gap this account mapping template is designed to expose. It is a working document for a particular opportunity, with explicit space for an unanswered question.
Define the account, opportunity, and business unit
“Why not map the whole company?” You can keep a company-wide reference, but give this working copy a narrower assignment. Name the customer organization, the business unit involved, and the decision you want to understand. “Approve a pilot for the service team” is a usable scope; “sell into the account” leaves the map without a destination. Include another division or an outside adviser when you have a reason to connect them to that decision. You do not need every employee to begin. Equally, you should not exclude someone simply because they sit beyond the reporting chart. Keep the account boundary visible while allowing relevant relationships to cross it. The immediate deliverable is a route through a buying decision, not a comprehensive description of the organization.
Choose relationship mapping rather than a contact inventory
An account map connects people through named relationships relevant to a purchase. A contact inventory stores people and their details. If you already have an inventory, use it to seed the map; the extra work is describing the links. “Reports to,” “introduces us to,” and “reviews the proposal with” mean different things. Put the verb on the connection so a colleague does not have to infer it from the arrangement of names. The externally published Lucid template is a useful counterexample to the assumption that an account map contains only reporting lines: non-reporting relationships are part of its stated purpose. That establishes a design distinction. It does not establish that a particular relationship exists in your account or that adding one will improve sales results.
Copy the Account Relationship Template
“A relationship field should be enough.” Enough for which question? Knowing that two people work together does not tell you what either may authorize. Knowing the approver’s name does not tell you whether your contact can reach them. And a promising connection gives you little direction if no one knows whether it has been confirmed. The template below therefore puts relationship, decision right, evidence status and next verification next to each other. This is an editorial design for making a map actionable, informed by the published distinction between reporting lines, buying roles and ongoing maintenance. It is not a vendor-certified standard. Copy the blank fields into a shared document and repeat the person and connection entries as needed. A blank marked unknown is a legitimate starting point.
People, decision rights, and relationship links
Begin with the destination of the buying route, then describe the people and the connections separately. Give each person a short identifier so you can refer to the same individual in several links without duplicating their details. For decision rights, write an action and its scope: evaluates the technical proposal, approves this department’s spend, or signs the agreement. Use unknown when you cannot support a more specific entry. A job title remains useful context, but it should not silently become approval authority. For each connection, record a direction. An introduction offered by your contact is a route from that contact to another person; it does not imply that the second person endorses you or has agreed to a meeting. Keep those possibilities separate.
- Account / business unit: [ ] | Buying decision or opportunity: [ ] | Map owner: [ ]
- Person ID: [ ] | Name / team / title: [ ] | Internal or external to account: [ ]
- Decision right for this purchase: [action and scope / unknown] | Relevance to this decision: [ ]
- Connection: [person ID] → [person ID] | Relationship verb: [ ] | Direction confirmed: [yes / no]
- Available access: [direct conversation / offered introduction / possible route / none known]
Evidence status and the next relationship to verify
Now add the fields that stop a possible route from becoming an asserted route. Record what supports the connection, not merely where the person’s name came from. A public profile might support a title while leaving an introduction route entirely unknown. A meeting note may support a working relationship without showing who can approve spending. Label those gaps directly. The status belongs to the specific statement: confirmed, reported by someone else, working assumption, or unknown. Then write a question that could resolve the most important gap, assign someone to ask it, and specify when the answer is needed for the next deal decision. This keeps verification close to the relationship it concerns. It does not require a separate version-control system or a score for every person.
- Connection or decision-right statement being checked: [ ]
- Evidence status: [confirmed / reported / working assumption / unknown]
- Basis: [document, conversation or other record] | What it actually establishes: [ ]
- Open question: [ ] | Person who could answer: [ ]
- Next verification: [specific request] | Our owner: [ ] | Needed before: [deal decision]
Fill the Map from Known Relationships Outward
Start with a connection you can describe, then ask what the next link would let your team do. Each new name should answer a buying-route question rather than merely enlarge the contact inventory. If you cannot explain that connection yet, record the unanswered question before you add another person.
Record indirect access without inventing influence
“Our contact knows the director, so we have executive access.” Do you know that an introduction is available, or only that the two people know each other? Start from the person your team can actually reach and work outward. Ask which colleague participates in the buying decision and how they normally become involved. If an introduction is offered, record the offer and its destination. If you merely suspect a relationship, record a possible route and the question you need answered. Do the same for external consultants, partners or advisers: include them only when their connection to this purchase has a stated basis. Lucid’s guidance distinguishes relationships outside hierarchy and aligned interests. That distinction supports looking beyond reporting lines; it does not license inventing a person’s influence.
Distinguish a verified link from a working assumption
“Updating another document will just create more administration.” It can, if you duplicate every contact field or turn each conversation into a reporting exercise. Keep the map focused on links that affect the next buying decision. Your CRM can remain the contact reference while the map records a route and its unresolved question. For a team already using OKKI Go, keep the account map as a companion working document. Choose tools according to where your team can maintain those distinctions reliably; a plain shared document is enough to use this template. At review, ask yourself whether the recorded relationship still supports the action you propose. Lucid describes map building as continual work, including contacts and notes. The practical extension here is a named next verification, not a requirement to redraw the whole account after every conversation.
Walk Through a Clearly Fictional Account Map
Consider a deliberately fictional account, Alder Components, evaluating a support-ticket pilot for its service unit. These people, relationships and conversation records are invented solely to demonstrate the template. They are not a customer case or evidence of results. The seller can reach Mira, the service systems lead. Mira is willing to assess technical fit and has offered to involve the service director, Daniel. The seller does not yet know who can approve pilot spending. In a contact list, both names could look like useful coverage. In this map, the route has a destination but an unresolved decision right. The missing entry matters because the next request should establish the approval path, rather than assume that a technical conversation also constitutes permission to buy.
- Account / unit: Alder Components / service | Decision: authorize a support-ticket pilot | Our owner: Taylor
- P1: Mira / service systems lead | Decision right: technical evaluation only, as stated in the fictional conversation
- P2: Daniel / service director | Decision right: budget approval unknown
- Connection P1 → P2: offered introduction | Evidence status: confirmed within this fictional scenario | Basis: invented meeting note recording Mira’s offer
- Open question: Who approves this pilot’s spend? | Next verification: Taylor asks Mira to confirm the approver when arranging the introduction
What changes when the technical evaluator has no budget authority
“Should the seller stop talking to Mira?” No. You still have a relevant technical conversation and a possible route onward. The correction is to the request you make, not to Mira’s importance as a person. Ask for the introduction and confirmation of the approval path; do not ask Mira to grant authority she has said she lacks. If Daniel turns out to recommend the purchase but not authorize it, add the next person and explain that relationship. Leave the spending decision unresolved until someone supplies the missing information. The filled map has done something modest and useful: it has identified what the seller needs to learn next. It has not predicted a win, measured influence or proved that the account will follow the route you expect.
Frequently asked questions
How is an account map different from an org chart?
An org chart describes reporting structure. An account map adds connections relevant to a buying decision, including non-reporting relationships and the role each person plays. Use the hierarchy as a starting layer, then record what it leaves unanswered.
What should the template show when influence is unverified?
Mark the specific relationship as a working assumption or unknown, state the basis you do have, and name the question that would confirm it. Do not turn a job title or an acquaintance into asserted approval authority.
Can an external adviser belong in the account map?
Yes, when you have a stated reason to connect that adviser to the scoped buying decision. Record the relationship and what supports it. An external connection should meet the same verification standard as an internal one.
