Target operating model design for procurement & cost

What a target operating model actually is

Operating model design gets over-complicated fast. In practice a target operating model answers five questions: who does what, where they sit, which systems they use, how the work is governed, and how performance is measured. Every good operating model design document is a clear answer to those five, expressed in a way the business can implement.

Why procurement needs a target operating model

Most cost programmes deliver savings that quietly walk back out inside 18 months. The reason is almost never the sourcing work - it is the absence of an operating model to hold the change. Categories go un-owned, contracts drift, tail spend rebuilds, and the same suppliers reappear on the master vendor list.

• No category ownership - so nobody re-tenders on cadence
• No demand governance - so specification creep re-inflates the base
• No spend visibility - so tail suppliers reappear unchallenged
• No policy discipline - so PO thresholds and preferred suppliers get bypassed

The five design choices in a procurement operating model

1. Structure - centralised, decentralised or hybrid

Centralised gives leverage and discipline; decentralised gives responsiveness. Most UK mid-market businesses land on hybrid - central category management on the top spend lines, business-unit ownership on the rest, with a shared services desk for tail spend.

2. Roles - category managers, buyers, and business partners

Category managers own strategy and sourcing on their categories. Buyers execute transactions. Business partners sit closer to the operating units and translate their demand. Getting this three-way split right is usually more important than any single hiring decision.

3. Systems - the P2P and analytics stack

Systems should follow the operating model, not lead it. A working stack for a UK mid-market business is usually a P2P system with catalogue and PO discipline, a spend-analytics layer for visibility, and a light contract lifecycle tool. Anything heavier tends to under-adopt.

4. Governance - policy, thresholds and cadence

• Approval thresholds by category and by role
• Preferred-supplier policy with off-contract exception process
• Monthly savings review with finance sign-off
• Quarterly category strategy refresh on the top 10 categories

5. Location - onshore, near-shore or offshore

Transactional buying, catalogue management and supplier master data are strong candidates for near-shore or offshore. Strategic sourcing, category management and senior negotiation almost always stay onshore. The mix is worth 20-30% of the run cost of a procurement function.

Procurement RACI matrix - who does what

A procurement operating model only works if the RACI is written down to activity level. Most redesigns fail because RACI stays at "category manager owns the category" - too vague to resolve the real fights between procurement, finance, legal and the business. The matrix below is the level of detail a working operating model needs.

R = Responsible (does the work), A = Accountable (owns the outcome, one per row), S = Support, C = Consulted, I = Informed.

The three RACI fights worth resolving up-front

• Supplier selection - budget holder is Accountable, category manager Responsible. Getting this wrong is why sourcing events get overruled at the last minute.
• Savings validation - Finance is Accountable, procurement Responsible. If procurement marks its own homework the number stops being credible inside two quarters.
• Policy exceptions - CPO Accountable, budget holder Responsible for requesting. Without a named exception owner, the preferred-supplier list dies quietly.

Category-team sizing by addressable spend

The single most-asked question in operating model design is "how big should the team be?". There is no universal ratio, but there is a defensible starting point based on addressable third-party spend, number of categories, and the split between direct and indirect. The table below is the benchmark range we use for UK mid-market and lower mid-market PE portfolio companies.

How to flex the benchmark to your business

• Direct-heavy manufacturers - add 20-30% to category manager count; direct materials need deeper technical and supplier-development time than indirect.
• Services-heavy businesses - shift the mix toward business partners; contract complexity beats supplier count.
• Multi-site or multi-country - add one business partner per major site above three, or the demand-side capture breaks.
• PE portfolio with buy-and-build - flex the team on an FTE per £X spend basis, not headcount, so integrations don't stall on hiring cycles.
• Heavy offshoring of transactional work - buyer/ops FTE can drop by 40-60%, but analytics FTE onshore usually goes up to compensate.

The procurement tech stack

Systems should follow the operating model, but the model still has to specify which layers exist, which vendor tier fits, and what integrates with what. For UK mid-market businesses the stack usually resolves to five layers: source-to-contract, procure-to-pay, contract lifecycle management, spend analytics, and supplier risk and information management. Anything outside these five is optional at mid-market scale.

Sequencing the stack

• Start with P2P and analytics. Nothing else pays back without control of POs and a classified spend cube. This is the ~70% of the value.
• Add S2C and CLM in phase two. Once category ownership is real, eSourcing and CLM start to compound - before that they are shelfware.
• Leave SRM / risk to phase three unless a regulator, customer or supply chain due diligence requirement forces it earlier.

Build, buy or ERP-native

For businesses on modern ERPs (SAP S/4, Oracle Fusion, NetSuite, Microsoft D365), the honest first question is not "which best-of-breed" but "what does the ERP already do adequately?". ERP-native P2P is usually good enough at up to £100m of spend if the process discipline is there. Best-of-breed becomes the right call when multi-entity, multi-currency, or category-specific sourcing complexity exceeds what the ERP handles without heavy customisation.

Integration points that break operating models

• P2P to ERP GL and cost-centre master - if this drifts, the spend cube is fiction
• Supplier master between P2P, CLM and finance - one source of truth or duplicates multiply
• Contract data (price, term, renewal) from CLM to P2P catalogue - or negotiated prices leak
• Savings tracker to finance ledger - or the number stops being trusted

Sequencing a target operating model implementation

Phase 1 - design (weeks 1-8)

• Current-state assessment and pain-point mapping
• Design principles agreed with sponsor and finance
• Target structure, roles and RACI to job-description level

Phase 2 - build (weeks 8-20)

• Roles filled, category ownership assigned
• Systems configured to the new process
• Governance forums stood up with a real cadence

Phase 3 - embed (months 6-12)

• Savings tracked to the P&L, not a spreadsheet
• Category strategy refresh on a rolling cadence
• Operating-model KPIs built into the CFO pack

Where this connects

Operating model design underpins our procurement transformation and procurement consultancy services, and pairs directly with the carve-out cost reduction guide and the new head of procurement first 90 days playbook.