How Buyers Can Build Support for Sourcing Changes

A buyer completes a market test and identifies significant savings. The analysis is solid. The recommended supplier meets the documented requirements. 

Then the stakeholders refuse to change suppliers. 

This happens too frequently. The buyer starts by evaluating the supply market and approaches stakeholders after finding an opportunity. By then, stakeholders may feel that procurement has ignored their needs or already made the decision. 

The problem is rarely the savings analysis. The buyer failed to build stakeholder alignment before proposing the change. 

How can procurement influence stakeholders during a sourcing project? 

Procurement can influence stakeholders by understanding their interests, involving them early, and connecting the recommendation to the business outcomes they value. You will have more influence when stakeholders see that their needs shaped the sourcing strategy. 

This requires more than a presentation at the end of a sourcing project. Stakeholder engagement should begin before you develop the RFQ or invite suppliers to quote. 

Here are five steps that will help. 

1. Identify everyone affected by the category 

Most categories have more stakeholders than buyers initially expect. Direct material categories will usually involve engineering, operations, quality, logistics, and more.  Indirect categories can be particularly complicated – consider temporary labor, for example.  Groups that are likely involved include human resources, legal, finance, plant management, production supervisors, and the employees managing temporary workers.  

Start by asking: 

• Who uses the suppliers in this category? 
• Which functions interact directly with the suppliers? 
• Whose objectives are affected by supplier performance? 
• Who approves the decision? 
• Who could prevent implementation? 
• Who has influence even if they lack formal authority? 

Do not limit the list to department leaders. End users often understand service requirements that never appear in a contract or statement of work. 

2. Understand interests before discussing solutions 

The principles in Getting to Yes apply directly to stakeholder discussions. Separate people from the problem and focus on interests rather than positions. 

A stakeholder’s position might be, “We cannot change suppliers.” 

The interests behind that position could include: 

• Avoiding production interruptions 
• Retaining an undocumented supplier service 
• Reducing workload for plant employees 
• Protecting an existing relationship 
• Avoiding responsibility if the implementation fails 

You cannot address these concerns until you understand them. 

Conduct individual stakeholder interviews before developing your sourcing strategy. Ask open-ended questions such as: 

• What services do you rely on from the current suppliers? 
• What problems do the suppliers help you solve? 
• What frustrates you about their current performance? 
• What capabilities would a new supplier need? 
• What improvements would create the most value? 
• What risks concern you most? 

Probe for examples and supporting facts. Then summarize what you heard and ask, “Did I miss anything?” 

That final question confirms your understanding and frequently uncovers information the stakeholder did not mention initially. 

3. Find the interests you share 

Stakeholder interviews will uncover shared, unique, and conflicting interests. 

Shared interests provide the foundation for alignment. Purchasing, engineering, finance, and operations may disagree about the solution but still agree on higher-level objectives such as maintaining production, supporting the business plan, reducing risk, and earning an acceptable return. 

Consider a situation in which engineering wants additional technical support from a supplier, but finance did not include that service in the budget. 

Arguing about the budget will reinforce the conflict. A better starting point is: 

“We want engineering to meet its business plan while providing an acceptable return on investment for the company.” 

Once both groups agree on that objective, they can evaluate options instead of defending positions. These might include limiting the scope of support, negotiating a different commercial model, or quantifying the business benefits to justify additional funding. 

4. Tailor the business case to each stakeholder 

A single savings presentation will not influence every stakeholder. 

Translate the sourcing recommendation into the outcomes each audience values: 

• Finance: savings, cash flow, budget impact, and return on investment 
• Operations: continuity, response time, and implementation risk 
• Engineering: technical capability, innovation, and supplier support 
• Legal: contractual protection, compliance, and liability 
• End users: service quality, ease of use, and workload 

Prepare for likely objections before the discussion. Decide what evidence will address each concern and what commitment you need from the stakeholder. 

For example, a plant manager may not oppose the projected savings. Rather, they may believe the disruption associated with switching suppliers outweighs the benefit. Your business case should therefore include the implementation plan, service comparison, contingency measures, and results from a controlled pilot. 

Lead with the stakeholder’s interests. Do not make them translate procurement metrics into operational value. 

5. Show stakeholders how their input affected the strategy 

Stakeholder interviews create expectations. If you collect input and never explain what happened to it, the interviews can reduce trust instead of building it. 

Before issuing the RFQ, play back what you learned: 

• Summarize the most important stakeholder requirements. 
• Share how those requirements are being expressed in the statement of work and KPIs. 
• Ask stakeholders to confirm that you captured the critical requirements. 

This closes the feedback loop and gives stakeholders meaningful ownership of the sourcing strategy. 

Build support before you need approval 

Stakeholder influence is not a final presentation skill. It is the result of how you manage the entire sourcing process. 

Stakeholders often know things the buyer does not. They understand undocumented supplier services, operational dependencies, recurring problems, internal constraints, and implementation risks that may never appear in the spend data, contract, or statement of work. 

Engaging stakeholders early improves the sourcing requirements and reduces the risk of recommending a supplier that looks good on paper but cannot support the business. 

Changing sources also requires more than selecting a supplier that meets the technical requirements. It is a change-management effort. People may need to adopt new processes, systems, responsibilities, and working relationships. 

Buyers must build support, address concerns, explain the reasons for the change, and involve stakeholders in implementation. A technically sound sourcing decision can still fail if the people affected are not prepared to make it work. 

When stakeholders help develop the requirements and evaluate the options, procurement is no longer asking them to accept someone else’s decision. Procurement is helping them implement a decision they helped create. 

---

Interested in more blogs, on-demand webinars, and more resources on Indirect Purchasing?