How to use this assessment: How to use this assessment: Work through each item and mark it complete once confirmed. Items flagged High Risk represent the most common sources of material overspend. A score of 15 or more indicates a well-governed position.
Section 1: Budget Baseline and Spend Inventory
The foundation of any annual software budget plan is a complete, current inventory of all software commitments — licences, SaaS subscriptions, cloud services, and support contracts — with renewal dates and true-up exposure mapped across the next 12 to 24 months. Without this baseline, budget estimates diverge from reality and renewal deadlines slip past negotiation windows.
1. You have a complete, audited inventory of every software licence, SaaS subscription, and cloud commitment expiring in the next 12 months.
An audited inventory is the single most critical control in budget planning. Without it, organisations routinely discover mid-year renewals they missed, auto-renewals they did not anticipate, or true-up bills that exceed forecasts by 20 to 35 percent. Best practice is to conduct an inventory at least twice annually — Q4 for the following year and Q2 for mid-year renewals. Use automated discovery tools to capture all SaaS subscriptions including shadow IT. Tag each item with renewal date, list price, current discount, and true-up exposure. Reconcile against actual invoices from the past 12 months to ensure completeness.
● High Risk
2. You have documented the renewal dates, contract terms, and price increase caps for all mission-critical enterprise agreements such as Microsoft, Oracle, SAP, and Salesforce.
Enterprise agreements represent 60 to 75 percent of total software spend for large organisations, yet many teams lack centralised documentation of renewal timelines and term limits. Missing a renewal date by even 30 days can forfeit negotiating leverage and lock you into automatic price increases of 3 to 8 percent annually. Create a master contract register indexed by vendor, contract ID, renewal date, licence count, and list price. Flag any renewal within 120 days. For each EA, extract and document annual price escalation limits, volume discount thresholds, and any renegotiation windows such as mid-term true-ups.
● High Risk
3. You have identified and quantified all software currently not deployed or actively used — commonly called shelfware.
Shelfware — paid-for but unused licences — typically accounts for 25 to 35 percent of enterprise software spend and is one of the easiest levers to pull during budget planning. Large enterprises waste an average of $80M annually on unused licences. To identify shelfware, cross-reference your licence inventory against actual usage data including login records, seat assignments, and audit logs. Flag all licences with zero usage in the past 90 days. Quantify the annual cost. For shelfware with planned future use, set a reclamation deadline; otherwise remove it from the budget and reallocate the capital.
● High Risk
4. You have calculated the financial impact of true-up reconciliation for the past three years and hold a rolling 24-month forecast.
True-ups — the annual reconciliation of actual usage against licensed quantities — represent a significant and often overlooked budget line item. Microsoft true-ups alone can trigger 10 to 20 percent uplift charges if not actively managed. Collect three years of historical true-up invoices and calculate the average annual increase in both seat count and total cost. Use this data to forecast next year's true-up exposure based on current headcount trends and usage patterns. If true-ups are growing faster than headcount, investigate whether licences are over-deployed or whether usage is creeping up due to new departments or roles.
● High Risk
5. You maintain a documented process for monthly or quarterly software spend reconciliation against budget, with formal variance reporting to finance and procurement leadership.
Unplanned software spend surprises are a leading cause of budget overruns and late-year capital reallocations. Organisations that implement monthly spend reconciliation typically catch budget variances two to three months earlier than those using only year-end reconciliation. Establish a recurring process to compare actual invoiced spend against forecast, broken down by vendor, product line, and cost centre. Flag any variance greater than 10 percent with root cause analysis. Share variance reports monthly with finance and procurement leadership. This discipline also surfaces auto-renewed licences, price increases, and new charges that vendors sometimes bury in invoices.
● Medium Risk
Section 2: Renewal Timing and Negotiation Readiness
Negotiating power peaks 90 to 120 days before a software renewal or true-up event. Organisations that miss these windows often accept vendor-proposed price increases and terms without pushback. Strategic renewal timing means identifying all upcoming expirations, preparing usage and cost justifications early, and initiating vendor conversations from a position of informed strength rather than reactive urgency.
6. You have established a mandatory 90-day alert and escalation process for all software renewals, with cross-functional review before any commitment is made.
The 90-day window is critical. Studies show that organisations initiating renewal conversations 90 or more days in advance secure discounts 15 to 25 percent better than those waiting until 30 days before expiry. A 90-day alert process allows time for usage analysis, internal stakeholder consultation, competitive benchmarking, and contract redlining before you respond to the vendor's renewal quote. Assign accountability to a central software asset management team or procurement lead. For high-value contracts above $100K annually, require formal approval from both IT and finance before signing any renewal.
● High Risk
7. You have compiled quantified usage data including seat utilisation, monthly active users, and consumption trends for your top 10 software vendors as a negotiation foundation.
Vendors typically propose renewal quantities based on historical entitlements or industry averages, not actual usage. Armed with real usage data, you can justify reductions in seat count, negotiate volume-based discounts, or push for lower per-unit pricing. For each of your top 10 vendors, extract the last 12 months of usage metrics: active users, login frequency, feature usage patterns, and any unused modules or licences. Present this data to the vendor 60 to 90 days before renewal with a statement confirming your current utilisation rate. This shifts the negotiation burden to the vendor to justify why you need the additional capacity.
● High Risk
8. You have identified and documented backup options or competitive alternatives for at least 60 percent of your top software vendors by annual spend.
Vendors negotiate harder when they know you have alternatives. Even if switching costs are high, the mere existence of a credible alternative can unlock 10 to 20 percent discounts or improved contract terms. For your top vendors, document at least one viable alternative: a competing product, an open-source solution, or an internal build option. You do not need to be serious about switching, but the vendor should sense that you have evaluated the market. When the renewal conversation begins, reference your analysis and explain what would justify staying with the current vendor.
● Medium Risk
9. You have negotiated or are actively negotiating annual price escalation caps into your major enterprise agreements, such as CPI-linked or a fixed maximum percentage.
Price escalation clauses often slip past review during renewal negotiations, locking organisations into 4 to 6 percent annual increases over multi-year contracts. Best practice is to cap escalations at CPI — typically 2 to 3 percent in mature markets — or a fixed percentage of 3 percent maximum. If you have a contract without an escalation cap, request an amendment during the next renewal or mid-term review window. If the vendor refuses, treat that as a red flag and accelerate your evaluation of alternatives. Even a 1 percent improvement in escalation terms can save $50K to $150K over a three-year agreement for mid-market enterprises.
● Medium Risk
10. You have assigned executive sponsorship and budget ownership to specific individuals for each renewal cohort, with formal handoff and communication protocols.
Renewals fail when responsibility is unclear. Assign a single renewal owner for each major vendor — typically from procurement or IT operations — with a backup. This individual is responsible for tracking the renewal date, collecting usage data, initiating vendor conversations, and finalising terms. Document this assignment in writing and communicate it to the vendor's account team. This clarity prevents miscommunication, missed deadlines, and last-minute scrambles that weaken your negotiating position. For critical vendors, consider quarterly check-ins starting 12 months before renewal to build rapport and gather feedback early.
● Medium Risk
Section 3: Cost Optimisation and Rightsizing
Cost optimisation is not a one-time event but an ongoing cycle of rightsizing, consolidation, and alignment between purchased capacity and actual usage. Annual budget planning must incorporate tactics to eliminate redundancy, consolidate vendors, and enforce usage governance to sustain savings year over year.
11. You have conducted a formal vendor consolidation analysis for your SaaS portfolio and have a documented roadmap to reduce the number of active vendors by at least 20 percent within 18 months.
Vendor sprawl directly inflates software spend and governance overhead. The typical enterprise manages 200 to 400 SaaS vendors, but 60 to 70 percent of spend is concentrated in the top 10 to 15. Consolidation — choosing a single vendor for a category instead of managing three — typically yields 15 to 25 percent savings, improves security, and simplifies renewals. Start with a category analysis: identify how many email, CRM, project management, analytics, and collaboration vendors you have. For each category, rank vendors by total cost of ownership including integration, training, and support. Select a consolidation target and assign a project owner to execute the migration. Build the savings into next year's budget.
● High Risk
12. You have implemented or are piloting a software licence reclamation or redeployment programme that reuses or reallocates unused or underutilised licences across departments.
Many organisations licence software by department or business unit in silos, creating duplication and waste. A reclamation programme — where IT tracks licences and reallocates them to departments with active demand — can recover 10 to 20 percent of annual spend without reducing functionality. Examples include reallocating unused Adobe Creative Cloud seats from a department that has downsized to a team with active demand. Implement a light-touch process: quarterly audits to identify idle licences, a simple request form for internal reallocation, and a clawback policy that allows IT to reclaim licences from departments that have exceeded their headcount.
● High Risk
13. You have evaluated and implemented an enterprise-wide discount or preferred-vendor programme for your top five software vendors, such as volume agreements or campus licensing.
Volume licensing programmes can deliver 20 to 35 percent discounts compared to list pricing, but they require upfront commitment and administration. Evaluate whether your top five vendors offer structured programmes aligned to your organisation's size, growth rate, and usage. If a programme exists, calculate the total cost of ownership — including the multi-year commitment and any minimum purchase guarantees — versus your current spend. For organisations with stable to growing headcount, these programmes often deliver cumulative savings of $200K to $500K annually. Assign a procurement lead to manage the programme and ensure your organisation stays aligned with minimum commitments.
● Medium Risk
14. You track and actively manage cloud service commitments such as reserved instances and savings plans to prevent overcommitment and ensure alignment with actual consumption.
Cloud cost controls are a subset of software budget planning. Many enterprises purchase Azure or AWS commitment discounts without forecasting actual consumption, leading to overcommitment and sunk costs. Establish a quarterly review of cloud commitments: compare committed capacity against actual usage over the past quarter. If utilisation is below 60 percent, adjust future commitments downward. For rapidly scaling environments, favour flexible, shorter-term commitments to avoid overcommitment. Use cloud cost analytics tools to model scenarios before purchasing new commitments.
● Medium Risk
15. You have a formal process to sunset or discontinue software within 90 days of identifying it as redundant, with clear communication to users and documented cost avoidance.
Identifying waste is one thing; acting on it is another. Organisations often discover unused licences but fail to formally discontinue them, allowing the cost to persist in the next renewal cycle. Establish a sunset protocol: once you identify shelfware or redundant licences, schedule a discontinuation date 30 to 60 days out, communicate the decision to affected departments, and reallocate users to replacement tools if necessary. Document the cost avoidance and track it against budget targets. This discipline prevents the sunk-cost fallacy and demonstrates the value of continuous optimisation to finance and business leadership.
● Medium Risk
Section 4: Governance, Compliance, and FinOps
Annual software budgeting is not solely an IT function; it requires cross-functional governance involving IT, finance, procurement, and business unit leaders. FinOps discipline — building financial accountability into technology decisions — ensures that software spending is aligned with business strategy, compliant with licensing terms, and auditable.
16. You have established a formal software asset management or software governance committee with representation from IT, procurement, finance, and legal, meeting at least quarterly.
Software spending accountability dissolves when no single team owns it. A formal SAM committee — with a charter, agenda, and decision authority — ensures that budget planning, vendor negotiations, renewals, and compliance are managed systematically. The committee should include IT operations leads to define requirements and usage, procurement to negotiate and manage contracts, finance to track spend and variance, and legal to flag compliance and licence audit risks. Schedule quarterly meetings to review upcoming renewals, discuss spend variance, approve consolidation initiatives, and address compliance findings. This structure also creates a single point of escalation for business units requesting new software.
● High Risk
17. You have implemented a mandatory software approval gate that requires finance and procurement sign-off before any new software purchase or renewal commitment above a defined threshold such as $25K annually.
Uncontrolled software purchases are a leading driver of budget overruns. A software approval gate ensures that all material commitments are screened for cost, compliance, and business alignment before they happen. Define a threshold for any new software or any renewal above $25K annually. For approvals below the threshold, IT can act autonomously but must log the purchase in a central registry. For approvals above the threshold, require a brief business case including vendor name, product, annual cost, business justification, and alignment to existing tools. This practice typically reduces discretionary software spend by 8 to 15 percent annually.
● High Risk
18. You have conducted a software licensing compliance audit in the past 24 months and have documented a remediation plan for any identified gaps including unauthorised use, deployment of unlicensed modules, or breach of use rights.
Licensing compliance is both a legal and financial risk. Vendors audit enterprise customers one to two times per decade on average, often triggered by a large renewal or acquisition. If an audit finds you deployed products beyond your licence terms, you can face true-up bills of 1.5 to 3 times the original licence cost plus legal fees. Conduct an internal compliance audit every 24 months: compare your deployed software from an IT asset inventory or network scan against your licence entitlements. Document any gaps and either acquire additional licences, reduce deployment, or modify your use to comply with licence terms. A documented remediation plan demonstrates good faith and can significantly reduce audit penalties.
● High Risk
19. You have established financial accountability and chargeback mechanisms for software spend, allocating costs to departments or business units based on actual consumption or seat assignment.
When software costs are buried in a central IT budget, business units have no incentive to optimise usage or limit headcount. Chargeback — allocating software costs back to the department or cost centre that uses them — creates transparency and accountability. For example, instead of IT absorbing all Salesforce costs, charge departments for the number of Salesforce licences assigned to them. This practice typically reduces software spend by 5 to 12 percent as departments become cost-conscious and challenge unnecessary licences. Start with your top three to five vendors and implement a simple chargeback model based on seat count or consumption.
● Medium Risk
20. You have defined and documented software spending and optimisation targets for the next 12 months and built these targets into departmental and executive scorecards.
What gets measured gets managed. Organisations without formal spending targets often see software spend drift upward 5 to 8 percent annually with little pushback. Define explicit targets aligned to your business strategy: reduce software spend per FTE by 8 percent, reallocate $500K from shelfware to high-priority tools, or achieve 85 percent utilisation rates across all major vendors by year-end. Cascade these targets into departmental scorecards and tie them to executive compensation or bonus metrics. This alignment ensures that software optimisation is not a one-time project but a sustained cultural and financial priority.
● Lower Risk
Ready to optimise your AI contract and cost position?
Download our AI Platform Contract Negotiation Guide — covering all major vendors, pricing structures, and negotiation tactics.Next Steps
Score your confirmed items against the benchmarks above. If you are in the High Exposure or Partial Governance bands, prioritise the items flagged High Risk — these represent the most common sources of material overspend and are addressable within a single procurement or FinOps cycle.
Redress Compliance works exclusively on the buyer side, with no vendor affiliations. Our GenAI advisory practice has benchmarked AI costs, negotiated enterprise AI contracts, and built governance frameworks across 500+ enterprise engagements. Contact us for a confidential review of your AI cost and contract position.