Blog  ›  ROI
ROI Model

ITAM ROI: calculating savings before you buy (build vs buy)

If you have to justify an IT asset management subscription to finance, this is the model. What to count on the savings side, what to count on the cost side, and a worked example for a 200-employee company that proves the ROI in three weeks.

IA
InventorIA Team
Published Apr 27, 2026 · 11 min read

"What's the ROI?" is the most common procurement question, and the most often answered with vibes. The right answer is a model that finance can challenge: clear inputs, defensible assumptions, separate buckets for hard and soft savings, and a sensitivity check.

The five savings buckets

  1. License rightsizing. Hard savings. Cancelled or downgraded SaaS seats from utilisation data.
  2. Auto-renewal prevention. Hard savings. Contracts that would have auto-renewed at higher tiers but didn't because of the 90-day alert.
  3. Shadow IT reclamation. Hard savings. Untracked SaaS that gets sanctioned, migrated, or cancelled.
  4. Hardware lifecycle optimisation. Hard savings. Reassigned devices instead of new purchases; ghost-laptop recovery.
  5. Time saved. Soft savings. IT and finance hours not spent reconciling spreadsheets, prepping audits, or chasing renewals.

Buckets 1–4 are real money. Bucket 5 is real time, which is real money, but finance discounts soft savings — typically by 50%. Build the model honestly with that in mind.

Worked example: 200-employee SaaS-heavy company

A 200-person professional services firm. $1.8M/year IT spend. SaaS-heavy: roughly 60% of IT spend is software, 25% hardware, 15% services. No formal ITAM today; one person spends ~10 hours/week reconciling spend.

Inputs and assumptions

InputValueSource
Annual SaaS spend$1,080,00060% of $1.8M
Annual hardware spend$450,00025% of $1.8M
Industry-typical dormant SaaS rate22%Across mid-market benchmarks
Dormant rate that's safely reclaimable15%Conservative; some seats are intermittent users
Auto-renewal increase rate8%Vendor default at renewal
Hardware ghost-laptop rate4%Mid-market average
Loaded cost per IT/finance hour$60Burdened

The calculation

Bucket 1 — License rightsizing
SaaS spend × reclaimable dormant rate
$1,080,000 × 15% = $162,000/year

Bucket 2 — Auto-renewal prevention
SaaS spend × renewal increase × prevention rate (assume 50% of contracts renegotiated)
$1,080,000 × 8% × 50% = $43,200/year

Bucket 3 — Shadow IT reclamation
Estimated 10% of SaaS in shadow IT, ~30% of that recoverable
$1,080,000 × 10% × 30% = $32,400/year

Bucket 4 — Hardware lifecycle
Hardware spend × ghost-laptop rate × recovery rate
$450,000 × 4% × 80% = $14,400/year

Bucket 5 — Time saved (soft)
10 hr/week × 50 weeks × $60/hr × 70% reduction × 50% discount
10 × 50 × $60 × 70% × 50% = $10,500/year

Total annual savings: ~$262,500

The cost side

ITAM platform subscription (mid-tier) ~$3,108/year ($259/mo)
One-time onboarding effort ~$3,000 (50 hrs × $60)
Ongoing operational effort ~$6,240/year (2 hrs/week × $60)

Year-1 cost: ~$12,348

The numbers

MetricValue
Year-1 net savings$262,500 – $12,348 = $250,152
Year-1 ROI~2,026%
Payback period~17 days
3-year cumulative savings~$760,000

The honest version

Real-world numbers depend heavily on starting state. A company with disciplined IT today might only see 8–12% reclaim. A company that hasn't run a license sweep in three years routinely sees 30%+. The model above sits in the middle.

Build vs buy

"We could build this internally" is the second-most-common procurement objection. The math:

ComponentBuild costBuy cost
Initial platform development2 engineers × 4 months × $12k/mo = $96k$0
SaaS API integrations (15 minimum)1 engineer × 6 weeks/integration = ~$200k for the 15 most-usedIncluded
Identity provider integration1 engineer × 4 weeks = $12kIncluded
Contract parser (LLM)1 engineer × 8 weeks + ongoing inference costIncluded
UI / dashboard1 engineer × 8 weeks = $24kIncluded
Ongoing maintenance~0.5 engineer ongoing = $72k/yearSubscription
Year-1 total~$400k+~$3k

Building wins only if you have unique requirements that no commercial tool meets — and even then, mostly only at >5,000 employees where the integration burden amortises across enough users to make sense.

What finance will challenge

How to make the case

The two-page memo for finance: page 1 is your version of the calculation above with your numbers; page 2 is the cost side, the build-vs-buy line, and the proposed pilot plan (30 days on the free tier, decision point at day 30 with measured savings). Most finance teams approve at that point because the downside is bounded and the upside is measurable.

Run the ROI on your real data — free

InventorIA's free tier covers 10 users; the pilot above can be run in 30 days with no commitment.

Start free →