Organize spend around business needs and supply markets, not only accounting codes.
A category is a portfolio of decisions
A category strategy coordinates demand, specifications, suppliers and sourcing waves over time. An individual sourcing event selects an option for a defined requirement. Running several events without a category view can create incompatible standards, conflicting renewal dates and avoidable supplier dependencies.
Start with a scope that has commercial meaning. “Technology” may be too broad to manage. “Collaboration software” can expose overlapping capability, but should still distinguish enterprise platforms from specialist use cases. The category boundary should support a decision, not merely make a chart tidy.
Turn imperfect spend data into useful questions
| Work | Control | Decision it enables |
|---|---|---|
| Normalize suppliers | Keep legal entity and parent mappings; do not erase contracting distinctions. | Where can demand be coordinated? |
| Classify spend | Separate recurring, one-time and pass-through charges. | What is addressable in the next planning period? |
| Map agreements | Attach end dates, notice dates and committed minimums. | Which opportunities are actually actionable? |
| Examine demand | Pair invoices with usage, volumes and business ownership. | Can the requirement be reduced or standardized? |
| Inspect concentration | Look through resellers and shared underlying providers. | Does consolidation increase common-mode risk? |
Flag uncertain classifications and review the suppliers that dominate the decision. Perfect classification of tiny transactions is usually less valuable than resolving one large ambiguous contract. Reconcile the analyzed total with the source system and disclose exclusions.
Select the lever before selecting the event
Demand reduction removes unnecessary consumption. Standardization narrows avoidable variation. Competition tests market options. Consolidation can improve coordination but may increase dependency. Make-versus-buy analysis asks whether an internal capability is genuinely sustainable, including management and continuity costs.
Each lever needs an owner outside sourcing. A software retirement plan requires application owners. Specification changes need technical acceptance. A supplier consolidation requires an operational fallback. Without those owners, the roadmap becomes a list of theoretical savings.
Build a sequenced roadmap
| Wave | Action | Dependency |
|---|---|---|
| Establish | Validate contracts, usage and duplicated capabilities. | Finance and business ownership of the baseline. |
| Simplify | Retire unused demand and agree standards. | Migration funding and exceptions process. |
| Compete | Source the consolidated, viable requirement. | Enough suppliers can meet the revised scope. |
| Govern | Measure adoption, cost and concentration. | Named owners and renewal calendar. |
Sources & context
- CIPS · Strategic sourcing ↗Professional foundation: sourcing connects organizational objectives, market understanding and ongoing review.
- UK Government · The Sourcing Playbook ↗Public-sector sourcing reference. Applicability depends on the organization and procurement regime.
The decision frameworks and illustrative examples are original editorial guidance. Sources support the stated context; they do not endorse this guide.