Procurement & S2P · Strategy and investment
Procurement Transformation Strategy: How to Set Priorities and Build the Business Case
Decide what needs to change, why it matters and which improvements deserve investment.
At a glance
Make the choices explicit
- Start with the business problemConnect each priority to evidence and an outcome.
- Compare the investment optionsInclude costs, uncertainty and the cost of doing nothing.
- Name who owns the benefitAgree the sponsor, measures and decision required.
On this page
A procurement transformation strategy sets out the business outcomes to pursue, the problems that prevent them and the changes worth funding. It should let a sponsor understand the choices, challenge the assumptions and decide what to support.
A list of projects is not enough. “Implement a new platform” says little about whether the business needs faster purchasing, stronger contract controls, lower external spend or more reliable supplier information. Define the problem before choosing the solution.
This guide focuses on priorities and the business case. Once those choices are agreed, use the procurement transformation roadmap to plan delivery. Detailed team structures and operating-model design are separate decisions.
01 · Start with the outcome
Connect procurement priorities to business objectives
Ask finance, operations, legal and the business sponsor which outcomes procurement needs to support. A growing business may need purchasing decisions to keep pace with demand while retaining control over commitments. Another may need to reduce avoidable external spend or protect continuity with critical suppliers.
Turn each ambition into a decision statement: “We need eligible routine purchases to reach the right approver without unnecessary executive escalation, while exceptions remain visible.” That is specific enough to investigate without assuming that new software is the answer.
- Outcome: what should improve, for whom and over what review period?
- Constraint: which controls, service needs or existing commitments must be respected?
- Trade-off: where could improving speed weaken control, or additional checks create more work?
- Success measure: what evidence would persuade the sponsor that the change worked?
Agree which objectives take precedence when they conflict. A faster approval time is not a success if users achieve it by bypassing required checks.
02 · Establish the starting point
Build a baseline people can challenge
Combine transaction evidence with process walkthroughs and stakeholder examples. Record the period, population, source and limitations so a strong complaint is not mistaken for a representative result.- Approval friction: sample requests by value, risk and business area. Separate time waiting for an approver from time spent correcting incomplete requests.
- Contract control: identify which agreements required legal review, whether that review occurred before signature and where evidence is missing.
- Supplier control: distinguish active suppliers from dormant or duplicate records, and check completeness against the requirements for each supplier group.
- Cost and effort: trace repeated chasing, rework, off-contract buying and avoidable exceptions to their causes.
Use the procurement capability assessment to investigate the skills, process and system gaps behind the baseline before committing to a solution.
03 · Choose what deserves investment
Compare priorities using the same criteria
Use a short set of criteria agreed with the sponsor: contribution to business objectives, control or service exposure, scale of the problem, confidence in the evidence, expected benefit, total cost and the capacity needed. Score consistently if that helps discussion, but keep the reasoning beside the score.
Handle mandatory obligations and unacceptable exposures explicitly. A required control should not lose funding simply because its cash return is harder to calculate. Ask the relevant owner to explain the requirement and the minimum proportionate response.
For discretionary improvements, compare the current approach, a targeted process or configuration change, and a broader investment where justified. For example, excessive approval escalation might be addressed by clearer authority rules and changes to an existing workflow. A new platform needs evidence that the current environment cannot meet the agreed requirement at an acceptable cost.
Record the choice: fund, investigate further, defer or stop. For a deferred item, retain the reason and the condition that would reopen the decision. Priority expresses importance and investment intent; the delivery roadmap determines sequence.
A dashboard may make missing supplier checks visible, but it cannot complete the checks itself. Evaluate dependent changes together so the business case does not claim a benefit that another unfunded activity must deliver.
04 · Define the commitment
Make scope and exclusions concrete
Describe the business areas, entities, supplier groups, transaction types and process boundaries included in the proposal. State the expected change in business behaviour as well as any system deliverable.
An illustrative scope might cover approval rules and supplier onboarding evidence for new indirect purchases in one business unit, using the current platform. It could exclude direct materials, a global supplier clean-up, ERP replacement and organisation-wide restructuring.
Record what the proposal assumes about data quality, policy decisions, access, internal availability and existing technology. If legal has not agreed review triggers or finance has not agreed spending authority, those are unresolved dependencies that affect the investment decision.
Name who can approve changes to scope and how additional requests will be assessed. This keeps a specific control improvement from quietly becoming a much larger programme.
05 · Make the economics visible
Build a business case with traceable assumptions
Present the options over the same period and on the same basis. Include the cost and consequence of continuing with the current approach, then show what additional investment changes. Ask finance to agree the treatment of costs and benefits before the figures are used for approval.
Include the full cost of the change
- One-off work: analysis, process design, policy work, data cleansing, configuration, integration and testing.
- People and adoption: internal specialist time, operational cover, training, communications and supplier engagement.
- Ongoing costs: licences, support, administration, control monitoring and reporting.
- Uncertainty: contingency linked to specific risks, with assumptions about volumes, effort, rates and available capacity.
Separate the types of benefit
Cash-releasing savings require an actual reduction in spend or budget. Capacity released means people can use their time differently; it becomes a cash saving only if a corresponding cost is removed. Cost avoidance, working-capital effects and reduced control exposure should remain visible as separate categories.
For each benefit, record the baseline, calculation, expected adoption, owner, evidence source and review period. Check for double counting: time saved by simpler approvals should not also be claimed in full as a separate automation benefit.
Illustrative calculation, not a client result. Suppose 600 eligible requests a month each require 12 minutes of avoidable chasing. Removing that effort would release 120 hours a month. At 50% adoption of the improved process, the planning estimate is 60 hours a month. At an assumed loaded cost of £35 an hour, that represents £2,100 a month of capacity value, not an automatic budget saving.
If one-off work costs £18,000 and ongoing support costs £500 a month, first-year cost is £24,000. Annualised capacity value at the assumed adoption level is £25,200 before allowing for ramp-up. At 30% adoption it falls to £15,120. The decision therefore depends on adoption, implementation timing and how the released capacity will be used; these figures alone do not establish cash payback.
Show a credible range and the assumptions that most affect the result. Describe risk reduction through control coverage and exception evidence where a monetary estimate would be speculative. Do not turn an unquantified risk into a precise savings claim.
06 · Assign accountability for value
Name the sponsor and the benefit owners
The sponsor owns the investment decision, resolves competing priorities and secures the time needed from the business. Confirm what they are being asked to approve: an investigation, a defined improvement or a larger commitment with stated conditions.
Benefit owners are accountable for the operational changes and evidence behind the expected value. They may differ from the project manager. A procurement lead might own reduced approval rework, a legal owner might validate contract-review coverage, and a finance owner might confirm whether a saving reaches the budget.
Give each benefit an agreed measure, baseline, target, review date and validation method. For legal-review coverage, specify the contracts in scope, the evidence required before signature and how approved exceptions or missing records are treated. For approval speed, keep transaction mix and the start and end points consistent.
The procurement reporting guide develops KPI definitions and source requirements in more detail. Use only the measures needed to test this investment case.
Ask owners to confirm their commitment before approval. If no one can explain how a proposed benefit will be realised and evidenced, it is not yet ready to be included as a firm commitment. The article on why procurement transformation stalls explores the wider consequences of weak sponsorship and overstretched teams.
A related procurement client story
Translate governance problems into practical priorities
Denova’s case study describes a fast-growing technology company where purchase approvals went to the CFO regardless of value, contracts had been signed without legal review and supplier onboarding documentation was incomplete or missing.
An embedded Procurement Manager supported policy work, a proposed tiered approval framework, a vendor compliance programme and closer legal alignment.
Read how an embedded Procurement Manager helped a growing technology company build its procurement foundation.
07 · Copy and adapt
Illustrative strategy-on-a-page template
Select and copy the template into your planning document. Keep the summary to one page where practical, with supporting calculations and evidence attached. Replace the prompts with your own facts; an unknown needs an owner and a validation date.
PROCUREMENT TRANSFORMATION STRATEGY — DECISION SUMMARY
Business area / entities: ___
Version, date and review period: ___
Business objective: ___
Why change now; consequence of doing nothing: ___
Baseline problems and evidence: ___
Population, period, source and known limitations: ___
Priorities and rationale: 1. ___ 2. ___ 3. ___
In scope — processes, supplier groups and outcomes: ___
Out of scope / deferred choices and reasons: ___
Options considered and preferred option: ___
Investment requested and appraisal period: ___
One-off costs — analysis, design, data, systems, testing: ___
Internal time, operational cover and adoption costs: ___
Recurring costs and risk-based contingency: ___
Volume, effort, rate, timing and adoption assumptions: ___
Sponsor and decision authority: ___
Benefit owners and their commitments: ___
Benefits — cash savings / capacity / avoidance / control: ___
Measures and validation: baseline → target; definition, evidence source, owner and review date: ___
How finance / risk / business owners will validate value: ___
Downside scenario and double-counting checks: ___
Dependencies and unresolved questions: ___
Owner and date for validating each assumption: ___
Decision requested — amount, scope, conditions and approver: ___
Next review or condition for reconsidering investment: ___
What a completed priority might look like
Illustrative example: “Improve control over new indirect supplier commitments in Business Unit A. A review of 100 recent requests found 18 with no recorded onboarding evidence; validate whether evidence exists elsewhere before treating them as non-compliant. Prioritise required evidence, clear review triggers and exception ownership in the existing workflow. Exclude global supplier remediation and platform replacement.
Request a capped £12,000 for analysis, data validation and configuration estimates, plus agreed internal procurement, legal and finance time. The CFO sponsors the decision; the procurement lead owns evidence completeness and legal validates review requirements. Confirm the baseline and proposed targets before requesting implementation funding.”
This is a fictional decision example, not the Denova client’s plan, fee or result. Its value is the explicit scope and funding condition.
08 · Before the approval meeting
Check that the decision is ready to make
- Can the sponsor see the business problem and why it matters now?
- Are the baseline and its limitations supported by identifiable evidence?
- Have the current approach and proportionate alternatives been compared?
- Are priorities, scope and exclusions explicit?
- Do costs include internal effort, adoption and ongoing ownership?
- Are benefits separated by type, with assumptions and downside scenarios?
- Have the sponsor and benefit owners accepted their responsibilities?
- Is the requested amount, decision authority and any funding condition clear?
A useful outcome may be approval, a narrower scope or a request for more evidence. Record the decision and its conditions. The agreed priorities can then become the inputs to a delivery roadmap.
Plan the next step
Trackbacks/Pingbacks