Category strategy vs sourcing strategy: why confusing them costs you 20% of your savings

Ask a procurement team what their category strategy is for IT services. They will often describe a sourcing strategy: run an RFP every three years, negotiate pricing, consolidate suppliers, move to the next category. This is not a category strategy. It is a sourcing calendar dressed up as strategy.

The distinction matters because the two disciplines serve fundamentally different purposes. Category strategy — output of the category management lifecycle — is a long-term business plan for a group of related goods or services. It addresses demand, specifications, supply base structure, risk posture, total cost of ownership, internal stakeholder needs, and governance. Sourcing strategy is the tactical plan for executing sourcing events — RFPs, auctions, negotiations — that implement specific elements of the category plan. Future Purchasing and other research organizations consistently find that organizations treating category strategy and sourcing strategy as interchangeable leave 20% or more of potential value unrealized. The cost of the confusion is not theoretical. It shows up in the P&L.

---

The structural confusion: why most teams cannot tell the difference

Research from Jaggaer and The MPower Group identifies multiple structural reasons teams blur the line. First, many organizations rebrand strategic sourcing programs as "category management" without changing the underlying behaviors. The labels change but the work stays the same: source, negotiate, award, repeat. Second, sourcing events are the most visible strategic activity in procurement. RFPs, auctions, and supplier negotiations are concrete and measurable. Category management — demand analysis, stakeholder alignment, risk posture definition, specification optimization — is analytical and governance-oriented. The visible work crowds out the invisible work.

Third, procurement maturity models consistently show that most organizations lack a formal category management framework sitting above sourcing and supplier relationship management. A 2025 analysis by Infosys BPM notes that "organisations often use two of the most common procurement strategies interchangeably. As a result, many fail to leverage the benefits of one distinct strategy over the other." Without the framework, teams default to the only structured process they have: sourcing events.

---

The hierarchy that most teams have backwards

In a properly designed procurement operating model, the hierarchy is clear: enterprise procurement strategy sits at the top, defining how procurement supports business goals. Category management sits beneath it as a standing governance framework for each spend area. Category strategy is the output of that cycle — the business plan for the category. Sourcing strategy is a lower-level execution methodology within category strategy, used when the category plan calls for a market engagement event.

Zetwerk and Future Purchasing both explicitly state: strategic sourcing is a subset of category management, not a peer or synonym. Category management provides the business intelligence and governance to maximize business value. Strategic sourcing executes the procurement aspects effectively. One defines the what and why. The other defines the how and when.

---

Five mechanisms that erode 20% of savings

When teams conflate category strategy with sourcing strategy, value leaks through multiple channels. Each mechanism independently erodes savings. Together they compound.

• Identified savings never materialize. A sourcing event may identify 15% savings through competitive bidding. But without a category governance model that ensures stakeholder compliance, demand management, and process change, those savings appear on a spreadsheet but not on the P&L. The Sourcing Innovation analysis demonstrates this gap directly: "The savings are only realized if the sourcing strategy is followed through over the life-time of the award. Failure to do so will result in lost value."
• Narrow price focus misses upstream levers. Sourcing events optimize around supplier selection and price. Category strategy addresses specification optimization, standardization, demand management, and make-or-buy decisions. These upstream levers — which sourcing strategy never touches — often deliver more sustainable value than a price negotiation against a specification that should have been rewritten.
• Re-tender churn without structural fixes. Teams that treat categories as a series of disconnected sourcing events cycle through RFPs every 2-3 years, chasing the same savings target without fixing the underlying drivers: fragmented specifications, unmanaged demand, poor supplier collaboration. This pattern erodes supplier relationships and increases total cost while appearing to deliver continuous improvement.
• Maverick buying erodes negotiated savings. Without category governance, stakeholders continue buying from non-contracted suppliers or ignoring new pricing agreements. Fractory notes that category management ensures savings are sustained and integrated into long-term strategies, while strategic sourcing alone delivers quick wins that may not stick.
• Risk and resilience benefits go unrealized. Category strategies explicitly address supply risk, resilience, and long-term supply market structure. Sourcing projects focus primarily on cost and basic assurance of supply for that cycle. This leaves categories vulnerable to disruption that later destroys the savings achieved through competitive bidding.

---

The demand management gap: what category strategy addresses that sourcing does not

One of the clearest examples of the gap between category and sourcing strategy is demand management. Sourcing strategy takes demand as a given. The procurement team receives a specification from the business, goes to market, and secures the best price for that specification. The question of whether the specification itself should change — whether the business unit is buying the right thing in the right quantity — is outside the scope of the sourcing event.

Category strategy challenges the specification. The category manager asks: Does the business need this performance standard, or is there a lower-cost alternative? Can we standardize specifications across business units to increase buying leverage? Is the demand forecast accurate, or is maverick buying inflating volumes? Infosys BPM highlights that category management takes a much broader view than strategic sourcing, encompassing "where the category fits into the wider business model and how best to fulfil those requirements from both an internal and external perspective."

---

What good looks like: the standing category governance layer

Organizations that have separated category strategy from sourcing strategy operate with a standing governance layer that functions independently of any sourcing event calendar. Each category has a documented strategy that includes: demand profile and forecast, supply market structure and trends, risk assessment and mitigation plan, total cost of ownership model, stakeholder alignment and governance structure, value lever prioritization (demand, specification, standardization, process, competition), and a sourcing engagement plan that specifies which events will execute which elements of the strategy.

In this model, the sourcing event is a tool, not the strategy. The category manager decides whether to run a competitive RFP, negotiate a sole-source extension, or not go to market at all — based on the category strategy, not the sourcing calendar. The MPower Group notes that "strategic sourcing is one of the lower level strategies utilized in category management," not the organizing principle for procurement work.

---

What this means in practice

The transition from a sourcing-event operating model to a category-strategy operating model requires changes to structure, process, and measurement. Here are the specific actions that produce the shift:

• Assign category ownership as a standing role, not a project. Every spend category needs a category manager who owns the strategy independent of the sourcing calendar. This person's performance is measured on category outcomes — total cost, risk posture, stakeholder satisfaction — not on sourcing-event velocity.
• Require a documented category strategy before any sourcing event. No RFP launches without an approved category strategy that answers: what is the demand profile, what are the value levers, what is the risk posture, and how does this sourcing event serve the strategy? This one rule forces the distinction into daily operations.
• Expand performance metrics beyond savings. If sourcing event savings are the only metric, teams will run more sourcing events and call them strategies. Include demand management savings, specification optimization savings, risk reduction, and stakeholder alignment in category manager scorecards.
• Build the framework before the events. The category management framework — spend segmentation, demand analysis, market analysis, strategy development, implementation, performance management — must be in place as a governance layer. Without it, sourcing events will continue to operate without category context, and the 20% value gap will persist.
• Invest in analytical capability, not just sourcing execution. Category strategy demands spend analytics, market intelligence, total cost modeling, and stakeholder engagement skills. These are different from the negotiation and project management skills that drive sourcing events. Build both capabilities, but recognize they are distinct.

---

FAQ

---