How to Build a Winning Business Case for a New SAM Tool
You know you have a problem. Your software costs are climbing, you have no real visibility into your license compliance, and your team is drowning in spreadsheets trying to manage it all. You know a modern Software Asset Management (SAM) tool is the answer, but to get the funding you need to convince your CFO and other senior stakeholders. You need a compelling, data-driven business case.
A winning business case is not a request for new technology; it is a proposal that states a business problem, quantifies its financial impact, and presents a credible plan for a return on investment (ROI). This guide walks through the steps of building one, from the problem statement to the objections you should answer before anyone raises them, and the document you hand over at the end.
Step 1: Define the Problem in Business Terms
Frame the problem in terms a business leader, not just an IT manager, can understand. Avoid technical jargon and focus on the financial and operational impact of your current approach to SAM. Build the problem statement around a few themes. The figures below are an example for a company spending €10 million a year on enterprise software; replace every one with your own.
Financial Waste
“We spend approximately €10 million a year on enterprise software. We cannot measure how much of it goes on unused or underused licenses; if it is 30%, that is €3 million a year. Without a SAM tool we have no way to find that waste or remove it.”
Compliance Risk
“Our manual processes give us no reliable way to know we are compliant with our major vendor agreements, such as Oracle and Microsoft. A single unbudgeted audit finding from one of them could mean a true-up of millions of euros, a significant and unmanaged financial risk.”
Operational Inefficiency
“Our IT team spends an estimated 500 hours a year collecting and reconciling software inventory data for compliance and renewals by hand. That is low-value work that keeps them from the projects that drive the business.”
Security Exposure
“We cannot list the end-of-life and unpatched software running in our estate, so we cannot retire it before it becomes an incident.”
Step 2: Quantify the Cost of Inaction
Once the problem is defined, quantify the cost of doing nothing. This is the step that creates urgency: continuing with the status quo is not a neutral choice, it is a decision to accept a level of financial loss and risk.
| Cost of inaction | Annual financial impact |
|---|---|
| Wasted software spend | €3,000,000 (30% of €10M) |
| Potential audit risk | €2,000,000 (estimated potential finding) |
| Manual labour | €25,000 (500 hours × €50/hour) |
| Total annual cost of inaction | €5,025,000 |
This simple table turns abstract waste and risk into a concrete figure that gets a CFO’s attention. Keep the arithmetic visible: a number the reader can recompute is a number they trust.
Step 3: Propose the Solution and Its Benefits
Now introduce the proposed solution. Focus on the outcomes the tool will deliver, not its features, and tie each benefit to a problem you have already defined:
Cost Reduction
“The SAM tool will identify unused software, redundant applications and opportunities to right-size our SaaS and cloud subscriptions. We project a 15% reduction in annual software spend in the first year.”
Risk Mitigation
“The platform will give us an accurate, continuous license position for our major vendors, so we find and close compliance gaps before an auditor does and enter any audit with our own evidence.”
Increased Efficiency
“By automating data collection and analysis, the platform frees our IT team for strategic projects.”
Name the tool you recommend and why it fits: how it integrates with the systems you already run, whether it scales with the estate, the vendor’s support and reputation, and its total cost of ownership. The SAM tool buyer’s guide covers the criteria and the questions to ask vendors.
Step 4: Present a Credible Financial Analysis (ROI)
This is the heart of the business case: a clear calculation of the projected costs and benefits. Count every cost, including the ones that are not on the vendor’s quote, and keep cash savings apart from avoided risk. A CFO will discount a risk figure; let them see the ROI holds without it.
Projected Costs (Year 1)
- SAM platform subscription: €100,000
- Implementation, integration with existing systems and training: €20,000
- Total Year 1 cost: €120,000
From year 2 the subscription and ongoing support and maintenance recur; set them out too, so nobody finds them in next year’s budget.
Projected Savings (Year 1)
- Software spend reduction (15% of €10M): €1,500,000
- Productivity savings: €25,000
- Total Year 1 savings: €1,525,000
Return on Investment (ROI)
- Net benefit (savings minus costs): €1,525,000 – €120,000 = €1,405,000
- ROI: (net benefit ÷ costs) × 100 = (€1,405,000 ÷ €120,000) × 100 ≈ 1,171%
Risk Avoided (not counted in the ROI)
The €2,000,000 potential audit finding from Step 2. Show it as exposure the tool lets you measure and reduce, not as a saving: if the platform closes most of the gap before an audit, the case only gets stronger.
Even on cash savings alone, the investment pays for itself within the first year. That is what makes the decision look not just prudent but necessary.
Step 5: Recommend a Phased Approach (Pilot Project)
To make the proposal easier to approve, recommend a phased approach. Instead of an enterprise-wide investment upfront, propose a small, focused pilot. It shows fiscal discipline and proves the tool’s value for a fraction of the cost.
Example Pilot Proposal
“We recommend a 90-day pilot focused on optimizing our Microsoft 365 subscriptions. The pilot will cost €15,000. Based on our initial analysis, we expect to identify at least €200,000 in annualized savings during the pilot, an immediate return that proves the platform for a wider rollout.”
Pick the pilot where the data is easiest to reach and the savings are easiest to verify. Incremental SAM tool implementation covers how to stage the rest.
Step 6: Answer the Objections Before They Are Raised
Every business case meets the same three objections. Answer them in the document, with evidence, rather than in the meeting:
- “It costs too much.” Point to the cost of inaction and to the pilot: the first spend is small and its result is measured before anything larger is committed.
- “It will disrupt how we work.” Show that the tool reads the inventory and processes already in place rather than replacing them, and name who does what during the rollout.
- “Our people will need training.” Put the training in the cost line, state how long it takes, and have the people who will use the tool try it during evaluation.
Back the answers with evidence: case studies from comparable organizations (a public-sector example is West Northamptonshire Council’s Microsoft licence consolidation), references from the vendor’s customers, and once it has run, your own pilot’s numbers.
Step 7: Put It in One Document
Hand over a clear, concise document that a reader who missed the meeting can approve on its own. Use these sections:
- Executive summary: the problem, the proposed solution and the expected return, in half a page.
- Problem statement: the themes from Step 1, in business terms.
- Cost of inaction: the table from Step 2.
- Proposed solution: the tool you recommend and why it fits your systems and vendors.
- Costs, benefits and ROI: the analysis from Step 4, risk kept separate.
- Plan: the pilot, its success measure and the decision point after it.
- Objections and answers: from Step 6.
From Cost Center to Value Driver
A well-built business case changes how the organization sees SAM: from a niche, technical, IT-only concern to a business priority. Frame the problem in financial terms, quantify the cost of inaction, present a credible plan for the return, and you secure the investment to take control of your software estate and make your SAM program a driver of business value.
Need numbers for your business case?
The strongest figures are your own. Load your inventory on the LICENSEWARE Free plan, or run a one-off pay-as-you-go analysis, to see your license position and unused software before you ask for a budget. To size a subscription or a pilot around the vendors that matter most to you, talk to sales.
Questions
What should a SAM tool business case include?
An executive summary, the problem in business terms, the cost of doing nothing, the tool you recommend and why, the costs (subscription, implementation and integration, training, ongoing support), the benefits and ROI, a phased plan starting with a pilot, and answers to the likely objections.
How do you calculate the ROI of a SAM tool?
Subtract the total first-year cost from the first-year savings, divide by the cost and multiply by 100. Savings are the software spend you can cut (unused licenses, over-provisioned editions, redundant applications) plus the staff time you no longer spend reconciling by hand. Costs include the subscription, implementation, integration and training.
Should audit risk count in the ROI?
Show it, but beside the ROI rather than inside it. An avoided audit finding is real money, but it is a probability, and a CFO will discount it. If the ROI holds on cash savings alone, the risk figure only strengthens the case.
How long should a SAM pilot run?
Long enough to produce a savings figure someone outside the project can verify, and no longer. A pilot scoped to one vendor or one subscription family, such as Microsoft 365, can usually show its result within a quarter; set the success measure and the decision date before it starts.
