A new buyer may think the purchasing decision belongs to procurement.
That is understandable. Procurement sends the RFQ, speaks with suppliers, compares offers, negotiates terms, and prepares the recommendation.
But in real procurement work, the buyer is rarely the only person deciding.
- The engineer may define the technical need.
- The user may know what works in daily operations.
- Finance may control the budget.
- Legal may review contract risk.
- IT may approve cybersecurity requirements.
- Quality may assess supplier capability.
- Management may approve the investment.
- Procurement may lead the sourcing process.
So who actually takes the purchasing decision?
The answer is: the purchasing decision is usually shared.
For a buyer in training, this is one of the most important lessons in tactical procurement. A good sourcing result depends not only on finding the right supplier. It also depends on understanding the people inside the organization who influence, approve, use, challenge, or block the decision.
LHTS framework connection
Role: Tactical procurement
Supporting roles: Operative procurement, procurement management, finance, legal, quality, IT, engineering, operations, sustainability
Process: Need definition, stakeholder mapping, sourcing preparation, RFQ, supplier evaluation, award recommendation, implementation, supplier management
Level: Basic
Related course: Sourcing Process 1
Quick answer: who takes the purchasing decision?
In procurement, the purchasing decision is normally influenced by several stakeholders, not only the buyer.
A common way to understand these roles is the buying center model. It includes initiators, users, influencers, deciders, buyers, and gatekeepers. The current LHTS article already uses this model to explain that several people may participate in organizational purchasing decisions.
In simple terms:
The buyer manages the purchasing process, but the decision is shaped by the people who need, use, approve, influence, control, and are affected by the purchase.
The basic problem: the buyer leads the process but does not own all needs
Procurement often owns the sourcing process.
But procurement does not always own the business need.
That distinction is important.
- A buyer may control the RFQ process, but the user knows whether the product works.
- A buyer may negotiate price, but finance owns the budget.
- A buyer may manage suppliers, but operations depends on delivery performance.
- A buyer may prepare the contract, but legal owns legal risk.
- A buyer may compare suppliers, but management may approve the final decision.
This creates a common problem for buyers in training:
The buyer is responsible for creating a good sourcing process, but the buyer must rely on other stakeholders to define what “good” actually means.
If the buyer ignores stakeholders, the sourcing project may fail even if the commercial result looks strong.
- The selected supplier may be rejected by users.
- The specification may be incomplete.
- The contract may miss important risk points.
- The implementation may be slow.
- The supplier may not fit the operation.
- The savings may never be realized.
That is why stakeholder understanding is not a soft topic. It is a core procurement skill.
What is a stakeholder in procurement?
A stakeholder in procurement is any person or group that can affect, approve, use, influence, or be affected by a purchasing decision.
CIPS describes procurement stakeholders as both internal and external. Internal stakeholders are connected to the organization, while external or connected stakeholders include parties with a contractual relationship to the organization, such as suppliers.
For a buyer, this means stakeholders can include:
- Internal users
- Budget owners
- Technical experts
- Finance
- Legal
- Quality
- IT
- Operations
- Sustainability
- Health and safety
- Management
- Suppliers
- Customers affected by the supplier’s performance
The buyer’s task is not to treat all stakeholders the same. The task is to understand who matters, why they matter, and how they should be involved.
The buying center: a simple model for understanding purchasing decisions
The buying center is a useful model (by Kotler) because it shows that different people play different roles in a purchasing decision.
A person does not need to have the title “buyer” to influence procurement. In many sourcing projects, the most important stakeholder may be the user, engineer, budget owner, or senior manager.
1. Initiators: the people who start the need
The initiator is the person or group that first identifies the need.
Examples:
- A production manager sees that a machine must be replaced.
- An engineer identifies a need for a new component.
- A warehouse manager needs a new logistics service.
- An IT manager sees that the current software is no longer sufficient.
- A quality manager identifies a supplier-related problem.
The initiator may not approve the purchase or select the supplier, but they start the process.
Buyer question:
What problem is the initiator trying to solve?
2. Users: the people who will use the product or service
Users are the people who will work with the purchased product, service, system, or supplier in daily operations.
Examples:
- Operators using a machine
- Employees using software
- Maintenance teams using spare parts
- Sales teams depending on packaging quality
- Warehouse staff using logistics services
- Engineers using technical consulting support
Users are important because they understand practical functionality.
- They know what works.
- They know what creates problems.
- They know which details matter in real life.
Buyer question:
What does the user need for this purchase to work in practice?
3. Influencers: the people who shape requirements and opinions
Influencers may not make the final decision, but they affect how the decision is made.
Examples:
- Engineering influences technical requirements.
- IT influences system and cybersecurity requirements.
- Quality influences supplier approval.
- Sustainability influences environmental and social requirements.
- Finance influences cost and budget assumptions.
- Legal influences contract requirements.
- Operations influences delivery and implementation needs.
Influencers often provide expertise.
A buyer should involve them early, because they can either strengthen the sourcing process or challenge it later.
Buyer question:
Whose expertise can change the requirement, supplier shortlist, evaluation criteria, or risk view?
4. Deciders: the people who approve the decision
The decider is the person or group with authority to approve the purchase or supplier selection.
Examples:
- Department manager
- Plant manager
- Project sponsor
- Budget owner
- Investment committee
- CPO
- CEO or executive management for major spend
The decider may not know all technical details, but they have the authority to say yes or no.
Buyer question:
Who has the formal authority to approve this purchase or supplier award?
5. Buyers: the people who manage the procurement process
The buyer leads or supports the purchasing process.
The buyer may:
- Clarify the need
- Challenge the specification
- Identify suppliers
- Send RFQ or RFP
- Manage supplier communication
- Collect offers
- Compare commercial terms
- Coordinate evaluation
- Negotiate
- Prepare award recommendation
- Support contract finalization
- Support implementation
The buyer does not replace stakeholders. The buyer organizes the decision process so stakeholders can make informed choices.
Buyer question:
How do I make sure the process is fair, structured, documented, and aligned with the business need?
6. Gatekeepers: the people who control information, access, or process flow
Gatekeepers control what information reaches the decision process or who gets access to whom.
Examples:
- An assistant managing access to a senior decision-maker
- An IT security function controlling supplier system access
- A legal department controlling contract approval
- A procurement system controlling supplier onboarding
- A technical expert filtering supplier information
- A category manager controlling supplier shortlist access
Gatekeepers are often underestimated. They may not decide the final award, but they can slow down, block, or redirect the process.
Buyer question:
Who controls access, information, approvals, systems, or supplier contact?
Why stakeholder understanding matters in sourcing
Stakeholder management is not only about being polite. It protects sourcing quality.
CIPS explains that early involvement of cross-functional stakeholders helps develop a comprehensive specification and supports change where stakeholder buy-in is required.
That is exactly why buyers must understand stakeholders early.
If stakeholders are involved too late, the buyer may discover problems after the RFQ has already been sent.
- The specification may be wrong.
- The evaluation criteria may be incomplete.
- A supplier may lack a critical requirement.
- A legal issue may appear during contract negotiation.
- A user may reject the solution.
- A manager may not approve the recommendation.
PMI also emphasizes that failing to meet the needs of one influential stakeholder at a critical time can damage a project, and that stakeholders may have different objectives and views that conflict with each other.
In procurement language:
A sourcing project can fail because the supplier is wrong — but it can also fail because the stakeholder map is wrong.
A simple stakeholder map for buyers
A buyer in training can start with five practical questions.
1. Who needs this purchase?
This identifies the initiator and the business owner.
Ask:
Who raised the need?
What problem are they trying to solve?
What happens if we do nothing?
2. Who will use the product or service?
This identifies the users.
Ask:
Who will work with this supplier daily?
What does good performance mean for them?
What problems do they have with the current solution?
3. Who can influence the requirement?
This identifies influencers.
Ask:
Who has technical, financial, legal, quality, IT, sustainability, or operational input?
Who can say that the solution is not acceptable?
Who must review the specification before RFQ?
4. Who approves the decision?
This identifies deciders.
Ask:
Who owns the budget?
Who has authority to approve the supplier award?
Is approval based on spend, risk, category, contract value, or strategic importance?
5. Who can block or delay the process?
This identifies gatekeepers and risk stakeholders.
Ask:
Who controls supplier onboarding?
Who reviews contracts?
Who approves IT access?
Who checks compliance?
Who must approve deviations?
These five questions are often enough to prevent the most common stakeholder mistakes.
Stakeholder relationship: what the buyer should understand
Understanding stakeholders is not only about listing names. The buyer must understand the relationship.
For each important stakeholder, the buyer should understand four things.
1. Interest
What does this stakeholder care about?
Examples:
Price
Quality
Safety
Ease of use
Technical performance
Delivery reliability
Budget control
Contract risk
Implementation time
Sustainability
Supplier innovation
Customer impact
2. Influence
How much power does the stakeholder have over the decision?
Some stakeholders have formal authority. Others have informal influence because of expertise, experience, or seniority.
3. Concern
What could make this stakeholder resist the decision?
Examples:
Fear of supplier change
Previous bad experience
Technical uncertainty
Risk to operations
Too much implementation work
Budget pressure
Loss of control
Concern about quality or compliance
4. Required involvement
How should the buyer involve the stakeholder?
Examples:
Inform only
Consult before RFQ
Invite to supplier meetings
Include in evaluation team
Ask for approval
Include in implementation planning
Include in supplier review
This turns stakeholder management into practical procurement work.
A basic stakeholder matrix for procurement
A useful beginner model is the power-interest matrix.
High power, high interest
These stakeholders must be managed closely.
Examples:
Budget owner
Business owner
CPO
Technical owner
Plant manager
Project sponsor
Buyer action:
Involve early, align regularly, document decisions.
High power, low interest
These stakeholders must be kept satisfied.
Examples:
Senior management, finance leadership, legal leadership, depending on the purchase.
Buyer action:
Provide clear summaries, risks, decisions needed, and escalation points.
Low power, high interest
These stakeholders should be kept engaged.
Examples:
Users, operational teams, service recipients.
Buyer action:
Collect input, test assumptions, involve in evaluation where relevant.
Low power, low interest
These stakeholders should be kept informed when needed.
Examples:
Peripheral functions not directly affected.
Buyer action:
Do not overmanage, but communicate when the decision affects them.
The matrix is simple, but it teaches a key procurement lesson:
Not every stakeholder needs the same level of involvement.
Practical example: buying a new maintenance service
Imagine a buyer is asked to source a new maintenance service for a production site.
At first, the buyer may think:
“I need to send an RFQ and compare prices.”
But the stakeholder map shows a more complex picture.
Initiator
The maintenance manager started the need because the current supplier has poor response time.
Main concern:
The new supplier must reduce downtime.
Users
Technicians and production supervisors use the service.
Main concern:
The supplier must be available quickly and understand the equipment.
Influencers
Quality wants documented work instructions.
HSE wants safety requirements.
Finance wants cost transparency.
Legal wants limitation of liability and termination rights.
Operations wants no disruption during transition.
Main concern:
The solution must work technically, commercially, safely, and contractually.
Decider
The plant manager owns the final decision because downtime affects production output.
Main concern:
The supplier must reduce operational risk, not only reduce cost.
Buyer
The tactical buyer manages the sourcing process.
Main concern:
The RFQ must include the right service scope, KPIs, pricing model, safety requirements, evaluation criteria, and contract terms.
Gatekeepers
Supplier onboarding and HSE approval must be completed before the supplier can enter the site.
Main concern:
No supplier can start work before compliance and safety checks are complete.
Now the buyer understands the real purchasing decision.
It is not only about choosing the cheapest maintenance supplier. It is about selecting a supplier that can reduce downtime, meet safety rules, satisfy users, fit the budget, pass onboarding, and be accepted by the plant manager.
That is stakeholder-based procurement.
How this connects to the tactical buyer role
Stakeholder management is mainly a tactical procurement skill because it is essential in sourcing.
The tactical buyer must:
- Understand the business need
- Identify stakeholders
- Challenge unclear requirements
- Build alignment before RFQ
- Define evaluation criteria with stakeholders
- Make supplier comparison transparent
- Prepare award recommendations
- Manage disagreement
- Support implementation
- Protect procurement process integrity
A tactical buyer who understands stakeholders can prevent late surprises.
A tactical buyer who does not understand stakeholders may run a technically correct RFQ that nobody supports.
How this connects to the operative buyer role
The operative buyer also needs stakeholder understanding, but usually in daily purchasing execution.
Examples:
- A user asks for an urgent purchase.
- Finance blocks an invoice.
- A supplier cannot deliver on time.
- A stakeholder wants to buy outside the approved supplier list.
- A requester uses the wrong specification.
- A manager asks why the PO is delayed.
In these situations, the operative buyer must understand who owns the need, who approves the order, who can clarify the issue, and who must be informed.
Where stakeholder management fits in the sourcing process
Stakeholder management is not one separate step. It appears throughout the sourcing process.
Need definition
Identify who owns the need and who will use the solution.
Key question:
Who can explain what the business actually needs?
Specification
Involve technical, operational, legal, quality, IT, or sustainability stakeholders where relevant.
Key question:
Who must help define the requirement before suppliers are contacted?
Sourcing strategy
Align stakeholders on supplier market, risk, timeline, and decision model.
Key question:
Who must agree on how we will source?
RFQ or RFP
Make sure stakeholder requirements are reflected in the RFQ.
Key question:
Does the RFQ represent the full business need?
Supplier evaluation
Use agreed criteria and involve the right stakeholders.
Key question:
Who should score technical, commercial, operational, legal, quality, or risk factors?
Award recommendation
Explain the recommendation in stakeholder language.
Key question:
Can each key stakeholder understand why this supplier is recommended?
Implementation
Involve users and operational owners before go-live.
Key question:
Who must change behavior, systems, processes, or supplier contact routines?
Supplier management
Keep stakeholders involved in performance follow-up.
Key question:
Who knows whether the supplier is actually delivering value?
Common mistakes buyers make with stakeholders
Mistake 1: Thinking the buyer is the only decision-maker
The buyer manages the process, but the decision is shaped by business needs, authority, technical requirements, budget, risk, and user acceptance.
Mistake 2: Involving stakeholders too late
If stakeholders are involved after the RFQ is sent, they may challenge the specification, supplier list, evaluation criteria, or contract terms too late.
Mistake 3: Listening only to the loudest stakeholder
The loudest person is not always the most important person. A quiet user, legal reviewer, quality engineer, or finance controller may hold information that changes the decision.
Mistake 4: Confusing user preference with business requirement
A user may prefer a certain supplier, brand, or method. The buyer must understand whether this is a real requirement or only habit.
Mistake 5: Ignoring gatekeepers
A sourcing project can be delayed by supplier onboarding, IT approval, contract review, compliance checks, or safety approval. Gatekeepers must be identified early.
Mistake 6: Not documenting alignment
Verbal agreement is weak. The buyer should document key decisions, evaluation criteria, approvals, and stakeholder input.
Mistake 7: Treating stakeholder management as politics
Stakeholder management is not manipulation. It is structured communication, expectation management, and decision alignment.
A simple stakeholder checklist for buyers in training
Before starting a sourcing project, ask:
- Who initiated the need?
- Who will use the product or service?
- Who owns the budget?
- Who approves the supplier decision?
- Who defines the specification?
- Who must review legal, quality, IT, sustainability, or risk topics?
- Who can block implementation?
- Who has previous supplier experience?
- Who must be informed during the process?
- Who must be involved in supplier evaluation?
- Who will manage the supplier after contract signature?
This checklist helps the buyer avoid one of the most common sourcing problems: discovering important stakeholders too late.
Practical buyer rule
A buyer in training can remember this sentence:
Before managing suppliers, learn to manage the internal decision.
If the internal decision is unclear, the supplier process becomes unclear.
If the stakeholders are aligned, the RFQ becomes stronger, the evaluation becomes easier, the award recommendation becomes more credible, and the implementation becomes smoother.
Related course
The natural related LHTS course is Sourcing Process 1.
The course is positioned as a Basic-level course for the tactical buyer role. It introduces the basic steps of a modern sourcing process and explicitly includes stakeholder management as a key skill for conducting successful sourcing events.
This makes it a suitable next step for buyers who want to understand how stakeholder management fits into sourcing preparation, RFQ work, supplier evaluation, and implementation.
FAQ
Who takes the purchasing decision in procurement?
The purchasing decision is usually shared between several stakeholders. Procurement manages the process, but users, initiators, influencers, deciders, budget owners, and gatekeepers may all affect the final decision.
What is a buying center?
A buying center is a model that describes the people involved in an organizational buying decision. Common roles include initiators, users, influencers, deciders, buyers, and gatekeepers.
Why is stakeholder management important for buyers?
Stakeholder management helps buyers understand needs, align expectations, define better specifications, avoid late objections, build decision support, and improve sourcing outcomes.
Is the buyer the decision-maker?
Sometimes the buyer has decision authority, but often the buyer manages the process while a business owner, budget owner, or manager approves the final supplier decision.
What is the difference between a user and a decider?
A user works with the product or service in daily operations. A decider has authority to approve or reject the purchase or supplier selection.
When should stakeholders be involved in sourcing?
Stakeholders should be identified early, preferably during need definition and sourcing preparation. Early involvement improves specification quality and supports buy-in during implementation.
Conclusion
A purchasing decision is rarely made by one person.
For a buyer in training, this is a critical lesson. Procurement may lead the process, but the decision is influenced by people who define the need, use the solution, approve the budget, assess risk, control information, and live with the result.
The buyer’s job is not only to contact suppliers and compare offers.
The buyer’s job is to understand the internal decision system.
- Who started the need?
- Who will use the result?
- Who influences the requirement?
- Who approves the decision?
- Who controls information or access?
- Who must support implementation?
When buyers understand these roles, they can manage sourcing with more confidence, fewer surprises, and stronger business alignment.
