Article
How to identify a sales champion in an account | JustHandled Labs
justhandledlabs.com
Quoted on this wiki
Every place a page here uses this source, in the order the words come in it.
User: will evaluate, operate, or live with the solution. “Blocker or risk: can slow or stop approval through security, legal, procurement, finance, or inactivity.” Unknown: lacks enough title or engagement evidence for a stronger label.
Do not infer current support from historical friendliness. “Ask an active contact for updated role and committee context.” Remove the person from the active champion plan when the role cannot be revalidated.
No. A senior executive may be the economic buyer or approver while an engaged director, manager, or user acts as the coach or champion. Keep authority, engagement, and demonstrated influence as separate fields. “Start with the account name and a contact list containing name, title, email, and last interaction.” No. Titles can suggest seniority and likely functions, but inferred reporting lines and influence paths must be labeled likely, possible, or unknown until a stakeholder or reliable source confirms them.
5. Give every relevant stakeholder one next action “Unknown Current role and relevance to the purchase. Validate through a known contact before relying on the person.” A map is a decision aid, not an automated outreach list. Review each message, respect consent and applicable law, and do not convert inferred relationships into personal claims.
Microsoft Dynamics treats an opportunity stakeholder as any customer-side person involved in the opportunity, including a champion, end user, economic buyer, influencer, or technical buyer. Start broad enough to preserve those distinctions. “Name and email Contact identity and account-domain match. Current role, influence, consent to outreach, or buying authority.” Keep personal contact data in the smallest necessary working set. A champion exercise does not require copying the CSV into a public document or sending a message to every mapped stakeholder.
1. Inventory the people and the evidence you actually have “Microsoft Dynamics treats an opportunity stakeholder as any customer-side person involved in the opportunity, including a champion, end user, economic buyer, influencer, or technical buyer.” Field What it establishes What it does not establish Name and email Contact identity and account-domain match. Current role, influence, consent to outreach, or buying authority. Title Likely seniority and functional area. Confirmed reporting line or budget ownership. Last interaction Relationship recency. Quality of engagement or internal advocacy. Observed signals Replies, meetings, introductions, approval work, pain, timing, or process context. Anything not present in the CRM record, notes, or supplied context.
Add only explicit influence signals “Budget ownership, stakeholder introductions, buying-process detail, requested follow-up, stated pain, timeline, or approval responsibility can strengthen the hypothesis.” D