The first contact can help map the account even when they cannot own the problem. Use the conversation to locate the problem, understand who handles it, and earn a route to that person. A person without authority can still help you understand what happens next when you build rapport with them.1 Your job is to find the problem and identify who on the team is best equipped to solve it.2 A name without that route is another untested assumption.
| Stage | What you are trying to learn | Example question |
|---|---|---|
| Diagnose | The problem being discussed and whether the current contact is responsible for solving it | "Is this person responsible for solving the business pain our solution solves?"3 |
| Classify | Whether this person owns the problem, feels workflow pain, or can route you to the owner4 | Who handles this problem when it appears? |
| Map | Who is missing, who can block the work, and who will present the business case internally5 | "Who's missing? Who can block this? Who will present the business case internally?" |
| Request | Whether the route to the economic buyer runs through a champion6 | Who should I speak with to move this forward? |
| Validate | Whether the named person is the right route and can carry the problem | Is this yours to own? |
Diagnose the problem
Describe the problem clearly enough for someone else to recognise where it sits. Keep the conversation on the failing work, who feels the effect, and what happens when nobody fixes it.
Use the diagnostic question in the table to test your understanding. If you cannot answer it, keep asking about the work before requesting a referral. Listen for the team that handles the issue, the point where the work changes hands, and the person expected to resolve it.
Move on when the contact can describe the problem in operational terms and you know which part needs a new owner or route. A vague complaint gives you no reliable basis for choosing the next person.
Classify the contact
The current contact may help in different ways. Decide what role they play before asking for access. A useful route gives you ownership, someone who feels the workflow pain, or a credible way into the person who owns the work.
Ask: "Who sees this problem most often?" "Who decides what happens when it appears?" and "Who would know whether this should be fixed?" Pay attention to how confidently the contact describes the workflow. Someone who can explain the path may help even when they cannot approve a change.
If the contact cannot place the problem, ask which team or process it belongs to and use the answer to refine the map. If they name a person, ask what that person will care about before you make contact. You then have a reason for the referral and a way to open the next conversation.
Map stakeholders
Keep the map small enough to use during the call. You need to know who owns the problem, who can slow the decision, and who can carry the case inside the company.
Use the three questions in the table when the contact gives you a partial answer. They expose gaps in your map and show whether the current contact understands how the decision travels. Ask each question separately if the contact answers at a high level, then write down the name or role they point to.
When the map shows a champion who will carry the issue internally, use that route to reach the economic buyer.6 Ask the champion what the economic buyer needs to see, who else will review the issue, and what could stop the work. Keep those questions tied to the problem you already diagnosed.
Request the referral
Make the request easy to act on. Explain the problem in the contact's words, say why you think another person handles it, and ask how to reach that person.
When direct contact with the economic buyer is needed, ask: "What is the best way for me to communicate with you if I need to contact your directly?"7 Keep the wording close to the situation. The contact should understand why you need the next conversation and what you want to discuss.
Ask for the next action before the call ends. That might be an introduction, permission to mention the current contact, or a recommended way to approach the person. If the contact offers only a department or a general inbox, ask who inside that group can explain the problem and what context to include.
Keep the request focused on placing the problem with the person who can deal with it. Thank the contact for the direction, then use the context they gave you in the next conversation.
Validate the handoff
Use a referral as a route to test. Ownership, relevance, and willingness to continue the conversation still need confirmation.
When the new person responds, restate the problem in one sentence and ask what part of it they handle. Listen for a correction, a boundary, or another handoff. If they confirm ownership, ask what needs to happen next. If they redirect you, return to the map and update the route before continuing.
Keep the original contact informed when the referral changes direction. That preserves the context behind the introduction and makes it easier to ask for another route when the first one was wrong.
What not to do
Use these as stop signs when a contact offers a name or sends you elsewhere.
- Count a reply as a referral only when it directs you to a different, correct person.8
- Before relying on an unknown stakeholder, validate their current role and relevance to the purchase through a known contact.9
- Direct the contact to a specific person when you can, so the matter does not reach a dead end.10
- Someone else should own the customer problem, and the salesperson should hold that person accountable.11
- Give a misroute a way back and capture the reason. A cross-functional team has collaborated on forms for returning misrouted referrals and capturing feedback.12
On your next conversation, write down the problem before asking for a name. Leave with a named next step and test whether it reaches the person who can carry the work.