Your main contact likes the proposal. Someone in operations has questions. Finance has been mentioned, but you haven’t spoken to them. Before sending another follow-up, work out whose answer you actually need.
Sales stakeholder mapping gives you a working record of the people involved in one deal: what each person cares about, what they’ve said, what they’ve agreed to and what remains unknown. A simple table is enough. Use it to choose the next useful conversation, then give that action an owner and a due date.
What is sales stakeholder mapping?
Sales stakeholder mapping means identifying the people involved in a buying decision and recording what you know about their roles, concerns and conversations. For a small agency or consultancy, the map can sit in a shared document or spreadsheet. It doesn’t need to look like an org chart.
The Government Analysis Function’s stakeholder-mapping guidance describes how a map can help create an engagement plan based on audience insight. That guidance concerns government engagement, not a sales framework. The application here is narrower: use what you know about one buyer group to decide whom to speak to next.
A useful map should answer questions such as:
- Who will use or evaluate the service?
- Who can influence, approve or stop the purchase?
- What has each person actually agreed to?
- What do we still need to ask?
Keep the map focused on the decision. You’re building a conversation record, not a directory of everyone at the business.
Start with one deal and identify the people involved
Choose a live proposal. List the buyer contacts you already know, then check for people who may be missing.
For an agency website project, the marketing lead might discuss launch timing while an operations colleague considers who will maintain the site. Someone else may approve spending or review the contract. Treat these as possibilities to investigate, not roles you can assign from job titles alone.
Ask your contact who will use the work, assess whether it meets their needs, approve the purchase and arrange payment. Also ask whether anyone else needs to review the proposal before it can move forward.
You don’t need every name immediately. “Budget approver: not yet identified” is a useful entry because it exposes an unanswered question.
Ask how the decision will be made
A fast reply tells you that someone is responsive. It doesn’t establish that they can approve the purchase.
Ask plainly:
“If the proposal looks right, who else needs to review it, and who gives the final approval?”
Follow with a question about the sequence: “What needs to happen between that review and signing?”
Record the answer with its source. “Maya says the finance lead reviews spending before the managing director signs” is more useful than “Maya is the decision-maker.” If the answer is incomplete, keep the missing detail open rather than filling it in yourself.
Record concerns, conversations and agreements in one table
Copy this format into a shared tool your team already uses. Keep each entry brief enough that a colleague can understand where the conversation stands.
| Person | Role or influence | Concern | Last conversation and date | Confirmed agreement | Open question | Next action | Owner | Due date | |---|---|---|---|---|---|---|---|---| | Name, or person not yet identified | Confirmed role, or marked assumption | What they said matters | Date and relevant point | Explicit commitment, with source | What needs checking | Specific follow-up | Named team member | Calendar date |
The columns do different jobs. The last conversation records what happened. The agreement records a commitment. The open question records what you still don’t know.
For example, “Discussed the proposal” belongs under the last conversation. “Agreed to send consolidated feedback by Friday” belongs under confirmed agreement. Neither means the buyer has approved the project.
If you haven’t spoken to someone, say so. Leave their concern unknown rather than guessing that finance only cares about price or operations only cares about workload.
Separate confirmed details from assumptions
Use wording that makes the evidence visible:
- “Maya said the launch must happen before the trade event” is an attributed statement.
- “Maya agreed to review the revised schedule” is a confirmed commitment.
- “Maya can approve the project” is an assumption unless the approval process has been confirmed.
Agreement to review is not approval to buy. Keep those separate even when the conversation feels positive.
For important details, note who confirmed them and when. If your team believes finance must approve the budget but nobody has verified that, write “Does finance approve the budget?” under open questions. Don’t quietly turn a plausible guess into a fact.
Choose the next conversation from what is still unknown
Look across the map for the unanswered question that most affects your next step.
If the approval process is unknown, ask your main contact to explain it. If a named reviewer hasn’t seen the proposal, request an introduction. If a concern remains unresolved, work out what information or discussion would help the buyer assess it.
When priorities differ, preserve each person’s concern. A marketing lead’s request for an earlier launch doesn’t erase an operations colleague’s need for training. Ask how the buyer team wants to resolve the trade-off:
“We’ve heard that launch timing and ongoing maintenance both matter. Would it help to review the phased-launch option together before we revise the proposal?”
Not everyone needs a separate meeting. A shared discussion may help people compare requirements, while a specific factual question might be answered by email. Let the question determine the format.
If someone is missing, ask your contact how best to involve them. Don’t assume you should bypass the person who has been helping you.
Give the next action an owner and due date
Turn the question into something a teammate can do. “Follow up with Maya” leaves too much room for interpretation. A better action is:
“Alex to ask Maya who reviews the budget and who gives final approval, by 18 November.”
Alex is the seller responsible for taking the action. Maya is the buyer being contacted. Keep that distinction clear.
Use a calendar date for your team’s action. If the buyer hasn’t promised a reply by that date, don’t record it as their deadline. Your commitment may simply be to send the question and then set the next action based on the response.
You don’t need a separate task for every cell in the table. Several unknowns may be answered by one conversation. Record that action once and note which questions it should resolve.
Worked example: an agency proposal with several buyer contacts
This fictional example concerns a website proposal from Elm Studio to Northbank Supply. Alex is the agency’s lead on the deal. All dates and details are illustrative.
Maya, the marketing lead, responds quickly and wants the site ready for a trade event. Ben, in operations, has asked about maintaining it after launch. Maya has mentioned a finance review, but Alex hasn’t confirmed who reviews the budget or who signs.
Below are the map’s entries, shown separately so you can read each person’s context without scrolling across a wide table.
Maya, marketing lead
- Role: coordinates proposal feedback, confirmed by Maya.
- Concern: launch before the trade event.
- Last conversation: 12 November, discussed the launch schedule.
- Confirmed agreement: on 12 November, Maya agreed to review the revised proposal. No review deadline was recorded.
- Open question: who reviews spending and gives final approval?
- Next action: Alex to ask Maya to confirm the approval process by 18 November.
Ben, operations
- Role: will maintain the site, confirmed by Ben.
- Concern: staff need to make routine updates.
- Last conversation: 13 November, asked about training and editing.
- Confirmed agreement: on 13 November, Ben agreed to review a training outline. No review deadline was recorded.
- Open question: would the proposed training cover the team’s needs?
- Next action: Alex to send Ben the outline and ask what is missing by 19 November.
Finance reviewer, name unknown
- Role: review mentioned by Maya; authority unconfirmed.
- Concern: unknown.
- Last conversation: no direct conversation.
- Confirmed agreement: none recorded.
- Open question: who is involved, and what must they review?
- Next action: covered by Alex’s question to Maya, due 18 November. No duplicate task needed.
Maya’s responsiveness hasn’t been recorded as approval authority. Ben’s concern has its own entry rather than being folded into a vague note that “the client likes the proposal.” The finance role remains explicitly unconfirmed.
Put the map’s next actions where Alex will see them
Suppose Elm Studio uses Nudge, an action-first CRM for small teams. Alex can keep the mapping table in a shared document, retain conversation context in comments on the relevant contact or deal records, and create the two next actions with Alex as owner and the dates above. The Today list shows tasks that are overdue, due today and due this week. The document explains the buyer group; the next actions tell Alex what to do about the gaps.
For the 18 November action, Alex asks Maya about approval rather than sending the same proposal again. If Maya identifies a finance reviewer, Alex records that answer with its source and updates the map. The next action then depends on what Maya says: request an introduction, prepare information for the review or arrange a shared conversation.
The same division of work applies without a CRM: keep the buyer context in the map and put the follow-up in the task list your team actually checks. Don’t let an open question sit only in a document nobody opens.
Update the map when a conversation changes the deal
After a relevant conversation, update the concern, agreement or participant that changed. Record the date, close any answered question and set the next action. You don’t need to rewrite every row. Keep detail that helps the next conversation, rather than copying every email into the table.
Take one live deal today. List the people you know, mark the assumptions you’ve been carrying and choose the unanswered question that matters most. Put a teammate’s name and a calendar date beside the action to answer it.
See also seller responsible for taking the action.
See also a colleague can understand where the conversation stands.
