What is the difference between a decision-maker, influencer, and user?
A decision-maker has authority to approve the purchase or a defined part of it. An influencer shapes the choice through advice, evaluation, or credibility but may not approve it. A user works with the solution day to day. One person can hold several roles, so responsibilities must be checked for each purchase.
Key Takeaways
- Roles describe what someone does in one specific purchase, not what their title suggests.
- Approval can be split. Choosing the solution, releasing the funding, and signing the contract may sit with different people.
- Influencers and users often cannot approve anything, but they shape the evaluation. Keep them involved.
- Record who told you what, when, and whether the responsible person confirmed it.
- A confirmed role is not a confirmed purchase. Budget, need, and timeline still need their own evidence.
How the three roles compare in BANT qualification
BANT stands for Budget, Authority, Need, and Timeline. This blog stays on the Authority part, and on who sits behind it.
| Role | Main contribution | What the role does not establish by itself | Useful verification question |
| Decision-maker | Approves the solution choice, the spend, or both, within a defined scope | That every needed approval is covered. Finance, IT, or procurement may still weigh in | “Once your team picks a supplier, which approvals are still needed?” |
| Influencer | Shapes the decision through evaluation, expertise, or advice | Formal approval rights, or that their preference will win | “How will your recommendation be weighed, and who receives it?” |
| User | Works with the solution daily and knows what must function in practice | Budget control, or a view on cost, security, or contract terms | “What would have to work in your daily workflow for you to support this?” |
These roles overlap. A manager can evaluate a tool, use it daily, and also approve it. In a larger purchase, those jobs may land on three different people. So assess the roles for the purchase you are discussing, not for the person in general. The same contact can be the approver on a small tool purchase and only an influencer on a platform that touches finance and IT.
Assess these roles within the wider BANT qualification framework, because authority alone does not establish budget, need, or timing.
Why a job title does not confirm purchase authority
A VP title suggests seniority. It does not tell you whether that person signs off on this purchase, this budget, or this contract. A director at a small company may control a software budget outright, while a senior executive elsewhere may never see the request.
BANT can oversimplify complex purchases when it turns into a hunt for one decision-maker. Asking “Are you the decision-maker?” invites a quick yes or no, and a quick yes can hide what is still unresolved.
Enthusiasm and product knowledge are not authority either. A contact who knows your category well and argues for the purchase may be an internal champion, meaning someone who advocates for it inside the company. That is useful. It is not the same as approval.
Instead of asking who “the” decision-maker is, separate four responsibilities:
- Solution approval: who agrees this is the right option.
- Funding approval: who confirms the money can be spent.
- Procurement: who handles vendor checks and commercial terms, where that step exists.
- Implementation: who judges whether it can be set up and run.
Not every purchase has all four. One person may cover several. Ask about each instead of assuming.
This matters most when a contact says “I’m the one who decides.” They may well be. But they may mean they decide which option the team prefers, while the budget sits with someone else. Both statements can be sincere. Only one of them gets a contract signed.
Prefer purchase-specific wording. “Who approves this reporting platform, at this scope?” gets a better answer than “Who’s in charge?” The first points to a decision. The second invites an organisational chart.
Questions that reveal each stakeholder’s role
The aim is to learn how the purchase can be approved, not to interrogate your contact. Keep the questions conversational, and treat “I’m not sure” as useful information. It tells you which part of the approval path is still a gap, and a gap you can name is one you can close.
A practical order: start with the user or influencer you already have, then ask them to describe how the decision usually moves. People often explain the process more freely than they claim the authority.
Ask decision-makers about the scope of their approval
Try these:
- “What can you approve on your own?”
- “Who approves or releases the funding for this?”
- “After your team recommends a supplier, what happens next?”
The first question shows the limits of their authority. The second separates choosing a solution from paying for it. The third surfaces steps people forget to mention, such as legal review or a procurement check.
If the answer is “I’d need to check with finance,” that is not a failure. Finance becomes a stakeholder to record. Follow up by asking who should confirm the process, and whether they can be included in the next conversation.
Ask influencers how recommendations are evaluated
Try these:
“How will your team compare the options?”
“Who receives your recommendation?”
“Which technical, procurement, or other reviews remain?”
These reveal the evaluation criteria and the route a recommendation travels. Follow up by asking whether a recommendation usually goes forward as is, or gets reviewed again. If it gets reviewed, find out by whom.
Do not dismiss someone because they lack sign-off. They may be the person who decides whether you reach the shortlist.
If an influencer offers to introduce you to the approver, take the introduction and keep the influencer in the loop. Going around them can cost you the relationship that got you this far.
Ask users what must work in practice
Try these:
- “What has to work in your daily workflow?”
- “What would make you reject a tool like this?”
- “Will you take part in a trial or demo?”
The answers give you acceptance criteria you can bring back to the evaluator. Users usually cannot speak to budget, so do not push them there. Ask who is evaluating fit, and whether your contact can help you reach that person.
Also listen for what users do not say. If they describe a workflow that depends on a system your product has to connect to, that is a technical review waiting to happen. Note it, even if nobody has named IT yet.
Map overlapping roles and remaining approvals
Forrester separates champions from decision-makers, and users and influencers from both. Someone who advocates for you is not automatically someone who can approve of you. This is where many handoffs go wrong. An enthusiastic contact gets labeled “decision-maker” because they are the most responsive person on the thread.
Here is an example. A company is evaluating a reporting platform. The marketing operations manager evaluates workflows and expects to use the platform. A revenue leader approves the functional choice. Finance confirms the spending authorization. IT assesses the integration. Procurement handles commercial terms.
These responsibilities are facts of this example. They are not assumptions to make from job titles.
| Stakeholder | Purchase role(s) | Approval scope | Status | Unresolved question |
| Marketing ops manager | User, influencer | Recommends; no approval | Confirmed | None |
| Revenue leader | Decision-maker | Functional choice | Reported | Does this person also approve spend? |
| Finance | Funding approval | Spending authorization | Reported | Is a separate review needed at this scope? |
| IT | Technical evaluator | Integration review | Inferred | Who owns this review? |
Take the finance row, since it shows the habit worth building. The manager said finance signs off, but finance has not said so.
The next action: ask the manager to introduce a finance contact, or ask the revenue leader what finance needs to see. Until then, spending authority stays “reported,” not “confirmed.”
Notice what the map does not do. It does not label the revenue leader “the” decision-maker and move on. It shows one confirmed role, two that rest on someone else’s word, and one that is only inferred. That is a more honest picture, and a more useful one for whoever picks up the conversation next.
Record authority evidence before the sales handoff
A handoff that says “decision-maker identified” is hard to trust. A short record is easier to check. Suggested fields:
Stakeholder | Purchase role(s) | Approval scope | Evidence source and date | Confirmation status | Unresolved question | Next action and owner
Suggested statuses:
- Inferred: based on a title or observed behavior.
- Reported: described by another contact.
- Confirmed: checked with the responsible stakeholder, or with appropriate approval documentation.
- Unknown: not yet established.
This is a suggested documentation convention, not an industry standard, and it is not drawn from the sources cited here.
Source and date matter more than they look. “Reported by the marketing ops manager on a call” tells the next person how much weight to put on it. “Confirmed in an email from finance” tells them something very different. Without that note, both read as simply “approver identified.”
Most of all, keep the record honest. A confirmed role does not mean the purchase is approved, and an “unknown” is better written down than guessed. Use the BANT qualification checklist to review the remaining criteria before treating the stakeholder map as a complete qualification record.
Choose the next step when authority is incomplete
Missing authority information is not the same as a bad lead. It usually means discovery is unfinished, and the right response depends on what you do know. These are suggested approaches, without numerical thresholds:
- Relevant contact, unclear approvals: continue discovery and agree on a verification step.
- Known approval path, unresolved dependency: record the dependency and its owner.
- User or influencer with useful information: keep them involved and work toward the appropriate approver.
- No active evaluation or agreed next step: make a defined nurture or review decision.
- Evidence of poor fit: treat that separately from missing authority information.
Authority evidence alone does not make an opportunity sales-ready. Budget, need, and timing still count.
The point of these rules is to keep uncertainty visible. An incomplete record should not quietly become “qualified” because the handoff is due, and it should not become “rejected” because one approver has not been named yet. Write down what is known, what is not, and who is going to find out.
To discuss how stakeholder evidence could fit your qualification process, explore Valasys BANT programs.
Frequently Asked Questions (FAQs)
Can someone outside the company influence a BANT-qualified purchase?
Yes. An outside consultant, agency, or advisor can shape requirements or a shortlist. Classify them as influencers, since influence differs from approval. Do not treat them as internal approvers unless the buying organization confirms they hold approval rights for this purchase. Ask your internal contact how the outside advice is used: is it one input, or does it set the criteria? That answer shows how much weight it carries.
When should you recheck a stakeholder’s authority?
Recheck when something material changes: the scope grows or shrinks, funding is reallocated, a new stakeholder joins, a key contact leaves, or the timeline shifts. Also recheck when the record rests on “inferred” or “reported” evidence and the opportunity is nearing handoff. Authority confirmed for an earlier scope may not cover the current one. This is a suggested practice, not a research-backed interval, so set triggers that fit your sales cycle.
Can one person be a decision-maker, influencer, and user at the same time?
Yes. A manager can evaluate a tool, use it daily, and approve it, especially in a smaller purchase. In a larger purchase, those jobs often land on different people. Assess roles for the specific purchase rather than for the person in general. The same contact may be the approver on a small tool and only an influencer on a platform that touches finance and IT.
What should you do if you can’t confirm who approves the purchase?
Treat it as unfinished discovery, not a bad lead. Record what is known and mark each role as inferred, reported, confirmed, or unknown. Then agree on a verification step, such as asking your contact to introduce the finance approver or asking what finance needs to see. Keep users and influencers involved while you work toward the right approver. Do not label the lead qualified or rejected until the gap is resolved.




