A 60% Spend Reduction Is Not a Rate-Card Story

Kicker — Enterprise spend becomes structurally lower only when demand, decision rights, contracts and internal capability change together.

Executive Summary

A rate-card negotiation can produce an immediate saving and still leave the enterprise economically unchanged. The same work remains in scope, the same dependency remains external, and the same approval channels can restore the volume when pressure returns. The invoice is cheaper; the operating model is not.

A structural reduction begins before negotiation. It identifies why demand exists, which work should stop, where suppliers are compensating for absent internal ownership, and which contract mechanisms reward activity rather than outcomes. It then aligns executives around explicit choices and changes the approval system so removed cost cannot quietly return.

In Stefano Rosa Rosso's client-side operating record, external consulting expenditure within a major European banking technology environment moved from approximately €200M to €80M within three months, a 60% reduction while delivery quality was preserved. Across technology categories, the wider governance model delivered approximately 20% structural savings. The lesson is not a universal percentage or a procurement tactic. It is that economics must be governed as part of transformation architecture. Within The S.T.E.P. Execution Architecture™, Economic Discipline & Strategic Sourcing is connected to Strategy, Trust and Performance so savings become an operating consequence rather than a one-time event.

When a CFO announces that external consulting spend has been cut by 60%, the instinct is to assume a negotiation win: better day rates, tougher procurement, a harder line at renewal. Sometimes that is exactly what happened — and it is exactly why the saving rarely survives the next budget cycle.

Rate cuts are reversible the moment leverage shifts back to the supplier. Structural reductions are not, because they remove the reason the spend existed in the first place.

The difference between a cheaper bill and a smaller one

A rate negotiation changes the price of the same work. A structural reduction changes how much work needs to be purchased externally at all. The first appears as a discount. The second appears as fewer statements of work, fewer suppliers and capability that used to sit outside the organisation now sitting inside it.

In a European banking technology environment managing approximately €500M in annual spend, the external profile contained patterns that are more common than many organisations admit: redundant workstreams running in parallel, external teams managing other external teams and an annual consulting bill approaching €200M with deliverables defined too loosely.

The response was not an arbitrary cost mandate. Arbitrary targets create fragility: teams route around them, critical work is protected by exception and the bill returns. The reduction was structural, built on three levers.

Three levers that make a reduction structural

Re-anchor contracts to outcomes, not billable days.

When a supplier is paid for time rather than a defined result, the incentive is to extend engagement rather than close it. The commercial unit must shift from day rate to milestone, deliverable or measurable outcome. This is a harder negotiation than a discount, but it changes the incentive embedded in the contract.

Transfer core competencies to internal owners.

Every engagement that ends without a capability handover guarantees a future engagement to purchase the same expertise again. The saving becomes real only when the organisation no longer needs to buy the capability twice. Internal staffing and training must therefore precede the external exit.

Consolidate supplier tiers deliberately.

Hundreds of relationships are not necessarily evidence of a competitive market. They often show that nobody owns the category. Consolidation creates leverage when backed by volume, continuity and clear category ownership. Without that governance, fragmentation returns under different supplier names.

Applied together, these levers reduced consulting expenditure from approximately €200M to €80M — a structural reduction of 60% — while preserving delivery quality. Cost reduction without capability building is fragility, not discipline.

Remove duplicated demand before consolidating supply.

Supplier consolidation is powerful only after demand has been challenged. Otherwise, a smaller panel simply receives a larger concentration of unchanged work. Map statements of work to enterprise outcomes, identify overlapping deliverables and make one executive accountable for deciding which scope survives. The organisation should negotiate only after it knows what it should still be buying.

Separate identified, contracted and banked value.

A spreadsheet saving is not an EBITDA outcome. Identified value is an opportunity; contracted value is reflected in a commercial commitment; banked value is visible in the run-rate and cannot be recreated through another channel. Boards and CFOs should require all three states because programmes routinely report the first as if it were the third.

The mechanics of restructuring without damaging velocity

Segment work by strategic necessity and dependency risk

Not all external work should be treated equally. Separate regulatory or revenue-critical delivery from discretionary change, commodity capacity and expertise that should be internal. This creates a sequence: protect genuinely critical outcomes, stop low-value activity, redesign dependent capabilities and then negotiate the residual supplier perimeter.

Velocity is damaged when cuts are allocated evenly because high-value work absorbs the same pressure as low-value demand. Structural action is selective. It preserves the capacity attached to explicit strategic outcomes while removing work whose continuation cannot be defended by a Board-level metric.

Use transition gates rather than arbitrary exit dates

External capacity should decline against evidence: a capability owner appointed, knowledge tested, operational exceptions resolved and performance stable. An arbitrary date may create a short-term saving while leaving the organisation unable to operate. A transition gate protects delivery and makes the commercial exit conditional on internal readiness.

Protect management bandwidth

A transformation can lose velocity because leaders spend weeks renegotiating hundreds of local exceptions. Establish enterprise principles, clear materiality thresholds and a small decision forum with the authority to close disputes. The mechanism reduces transaction volume and prevents every supplier or business unit from relitigating the strategy.

Will the saving survive the next budget cycle?

Three questions separate a structural result from a temporary one. Did the volume of externally purchased work shrink, or did it move to another supplier at a lower rate? Is there a named internal owner for every capability that previously sat outside? Did the way future spend gets approved change?

A plan that fails any of these tests may still produce a valid short-term benefit, but it should not be treated as durable. The number on the Board slide and the number that survives next year's budget are only the same when all three hold.

Where this sits inside an execution architecture

This is the Economics discipline inside The S.T.E.P. Execution Architecture™, developed by Stefano Rosa Rosso. It connects demand, supplier contracts and delivery ownership so spend reduction funds transformation rather than merely shrinking a budget.

Economics cannot operate alone. Without Strategy, there is no clarity about work that should stop. Without Trust, there is no mandate to challenge entrenched relationships. Without Performance, there is no proof that capability transferred. A spend reduction governed in isolation is a negotiation dressed as transformation.

Board and C-Suite operating checklist

• Which external work directly supports a non-negotiable strategic outcome?
• Which demand is duplicated, discretionary or created by unclear internal ownership?
• Are contracts linked to outcomes and acceptance evidence rather than elapsed effort?
• Is every saving classified as identified, contracted or banked?
• Can removed demand re-enter through another function, entity or supplier?
• Does every critical external capability have a named internal owner and transition gate?
• Are delivery velocity and service quality monitored alongside cost?
• Has the approval model changed enough to prevent the cost base from rebuilding?

Conclusion: the question before the next renewal cycle

Do not ask only, “How much can we cut?” Ask, “Does this number come from a better rate, or from work that no longer needs to exist?” The first is a negotiation outcome. The second is a governance outcome.

A durable reduction changes four things at once: the strategic boundary around demand, the authority to stop or consolidate work, the economics embedded in supplier contracts, and the capability retained inside the enterprise. That is why a 60% reduction is not a rate-card story. It is evidence of a redesigned operating system.

The S.T.E.P. Execution Architecture™ by Stefano Rosa Rosso makes the interdependence explicit. Strategy determines what will not be funded. Trust gives executives the authority to enforce that boundary. Economics restructures demand and commercial mechanisms. Performance proves that delivery and capability endure. When those conditions hold, cost reduction can fund transformation without damaging velocity—and the saving is far less likely to return with the next budget cycle.

FAQ