Most SAM programs do not fail because the idea is wrong. They fail because they never get funded, or they get funded as an IT housekeeping project with no clear financial outcome. A strong business case changes that. It turns "we should know what software we have" into "we can reduce run-rate spend by a measurable amount, protect ourselves against audit costs, and pay for the program within the first year."
This guide shows how to build that case so a CFO can approve it in one meeting.
Start with the cost of doing nothing
Finance teams approve spending when the alternative is more expensive. So the first section of your case should describe what the current approach costs, using evidence the reader already trusts.
Industry data gives you the frame:
Then translate it into your organization's numbers. Three figures usually make the point:
- Total annual software spend. Combine software, SaaS and maintenance lines from the general ledger. Most organizations underestimate this, because SaaS bought on cards and expensed by teams is spread across many cost centers.
- Renewals in the next 12 months. List each agreement, its value and its notice deadline. Any agreement that renews automatically without review is committed spend you are not managing.
- Known waste. Even a quick check of your largest vendors, comparing licenses paid for with licenses used in the last 90 days, will usually find seats nobody uses.
Build a conservative savings model
Your savings estimate is the heart of the case. It has to be credible, so build it bottom-up from your largest vendors rather than applying a single industry percentage to the whole budget.
For each of your top 10 vendors, estimate four levers:
- Reclaim: licenses assigned to people who no longer use them.
- Right-size: users on a higher plan or edition than their work requires.
- Consolidate: overlapping products that do the same job.
- Renegotiate: better price or terms at renewal, supported by usage evidence.
Separate two kinds of savings in the model:
- Run-rate savings reduce spend every year after the change, for example fewer licenses at renewal.
- One-time savings avoid a single cost, for example a true-up you no longer need to pay or an audit settlement you avoided.
Run-rate savings are worth more and should carry the case. One-time savings are a bonus.
Show the payback
The cost side of the case is usually small next to the savings: a SAM platform, some consulting time to build the baseline, and a share of internal effort for governance. Present costs and savings on the same timeline, month by month, because savings arrive as renewals come round, not all at once.
Three numbers belong on the summary page:
- Payback period: the month in which cumulative savings exceed cumulative cost.
- First-year net benefit: savings minus cost in the first 12 months.
- Three-year net benefit: the figure that shows SAM is a program, not a one-off.
Put a value on risk
Audit exposure and unmanaged renewals are harder to quantify, but leaving them out understates the case. Use ranges rather than single figures:
- Audit exposure. For each publisher likely to audit you, estimate the gap between what is deployed and what you are entitled to, at list price. Flexera's 2025 survey found that half of organizations had been audited by Microsoft in the previous three years, and 45% had spent more than $1 million on audits in that period.
- Auto-renewal exposure. Add up the value of agreements that will renew automatically in the next 12 months without a named owner reviewing them.
You do not need to claim you will avoid all of it. Showing that the organization currently has no way to know its position is often enough.
Address the objections before they are raised
Finance and IT leaders tend to ask the same questions. Answer them in the case:
| Objection | How to answer it |
|---|---|
| "We already track licenses in a spreadsheet." | Show the gaps: renewals found late, usage data missing, no notice dates. |
| "Our vendors give us good prices." | Price is one lever; volume and edition are usually larger. |
| "This will disrupt users." | Start with clearly inactive accounts and communicate before reclaiming. |
| "We do not have the people." | A partner can build the baseline and run the first cycle; ongoing effort is a few hours a week. |
| "Savings will not show up in the budget." | Agree with finance how savings are recorded before the program starts. |
Structure the one-page summary
Executives read the first page. Put everything that matters there:
The one-page summary
"When does it pay back, and how will we know the savings are real?" Answer both on page one.
How MI One and our SAM service help
Frequently asked questions
How big should the savings estimate be?
Large enough to matter and small enough to be credible. A conservative range built from your own vendors is better than a headline industry percentage.
Who should sponsor the business case?
Ideally a joint sponsor from IT and finance. SAM decisions affect both budgets and user experience, so shared ownership speeds up approval and execution.
How do we prove the savings afterwards?
Agree in advance how savings are measured, for example the difference between the previous contract value and the renewed value, and track them per vendor.
Sources
- Gartner, "Gartner Says Organizations Can Cut Software Costs by 30 Percent Using Three Best Practices," July 19, 2016. https://www.gartner.com/en/newsroom/press-releases/2016-07-19-gartner-says-organizations-can-cut-software-costs-by-30-percent-using-three-best-practices
- Flexera, 2025 State of ITAM Report press release, June 18, 2025. https://www.flexera.com/about-us/press-center/it-teams-losing-visibility-according-to-flexera-2025-state-of-itam-report
- Zylo, "2025 SaaS Management Index," January 16, 2025. https://zylo.com/news/2025-saas-management-index