How to Sell Software Cost Optimisation Internally Without Killing Morale
- Ibiso David-West
- Apr 10
- 3 min read
Software cost optimisation rarely breaks down at the point of vendor negotiation; more often, it loses momentum internally before any meaningful commercial improvement is realised.
The underlying issue is not typically a lack of opportunity, but rather how the initiative is introduced and interpreted by the wider business. The moment “cost optimisation” is mentioned, it can easily be associated with tool reduction, constrained delivery, or a renewed focus on doing more with less, even when the actual objective is far more measured and commercially focused.
For procurement and finance leaders, this creates a more considered challenge. The task is not simply to identify savings, but to position the initiative in a way that maintains confidence, aligns stakeholders, and avoids triggering unnecessary resistance from teams responsible for execution.
Start With Reinvestment
The way the conversation is introduced will often determine how it is received.
Framing the initiative as a need to reduce software spend can unintentionally signal that value will be removed from the business, which tends to create hesitation before any analysis has even taken place. A more effective approach is to position the work as an opportunity to correct inefficiencies in how existing budget is being allocated, particularly where pricing, contract structures, or usage levels no longer reflect the organisation’s needs.
Try language like this in internal meetings:
We are not trying to break workflows.
We are trying to fix bad pricing, poor terms, and underused capacity.
Any savings we unlock can be recycled into the roadmap, resilience, or strategic hires.
That shift matters because it turns software cost work from a defensive exercise into a performance conversation. CFOs can talk about reinvestment, CIOs can talk about protecting delivery, and procurement can focus on improving deal quality rather than policing every tool choice.
Separate Product From Price
One of the most common sources of internal resistance is the assumption that reviewing software spend will lead to questioning every platform decision the business has made. That is where teams tend to become defensive, as the conversation begins to feel like a broader challenge to their tools, processes, and prior investments.
A more effective approach is to clearly separate product decisions from commercial optimisation, asking these two questions:
1. Do we still need this tool?
2. If yes, are we paying the right price and on the right terms for it?
In many cases, the majority of value sits within the second question. Inefficiencies are often driven by contract timing, packaging, licensing structures, or unused capacity, rather than fundamentally incorrect tool choices. Addressing these areas allows organisations to improve financial outcomes without introducing unnecessary disruption, which makes the initiative significantly easier to support across the business.
Establish Guardrails That Protect Delivery
For any optimisation effort to gain traction, there needs to be clarity around what will not change.
Without clearly defined guardrails, even well-intentioned initiatives can be perceived as introducing operational risk, particularly in environments where software underpins critical workflows. Establishing these boundaries early helps ensure that stakeholders understand the focus remains on commercial improvement rather than functional compromise.
A practical way to manage this is to classify tools into three groups:
Red: business-critical, optimisation focused on price and terms only.
Amber: keep, but repackage, resize, or restructure commercially.
Green: consider rationalisation, replacement, or exit.
This approach provides structure without creating unnecessary disruption, allowing teams to engage in the process with greater confidence that critical systems will remain protected.
How to Frame WYN Internally
When an external partner is introduced poorly, internal teams often perceive it as an audit. When introduced effectively, they are seen as a source of leverage.
That is the angle to use with WYN. The internal message should be: this is a specialist team that knows how software vendors negotiate, helps protect the business from overpaying, and only gets rewarded when savings are delivered.
A CFO can use this board-level narrative:
We are protecting growth by reducing avoidable software overspend.
We are not asking teams to do more with less; we are asking vendors to stop charging more than the value delivered.
We are using specialist support to improve outcomes on large renewals without adding fixed-risk cost.
A CIO can use this functional narrative:
Core workflows stay protected.
The immediate focus is pricing, terms, and unused capacity.
Savings created here can be reinvested into better tools, resilience, or innovation.
That combination lowers resistance because it removes the two biggest fears: loss of control and loss of productivity.
Are you unsure if you're getting the best deal on your current software vendor? Let us help! We offer a complimentary software review for any vendor you’re currently using. Our experts will analyze your current arrangements and tell you if you’re overpaying or if you’re already getting the best price available.
