Flexera logo
Image: How to calculate SaaS ROI by measuring usage

Back in the day, calculating software return on investment (ROI) was largely an annual exercise in guesswork. Procurement teams would gather estimated hours saved, multiply that by an average employee hourly rate, look at the license count on an invoice and call it a day.

Fast forward to today and the SaaS landscape has fundamentally shifted. The average mid-market company now manages over 100+ SaaS applications, budgets are scrutinized under a microscope and capital efficiency is the primary metric for finance leaders. Vague productivity estimates are no longer enough to justify software renewals.

To prove genuine software value, you have to start at the foundation: Step one is measuring actual usage.

Without precise, automated usage data, any financial model you build for SaaS ROI is built on sand.

1. Redefining “usage” in the modern SaaS landscape

In the early days of cloud software, “usage” simply meant having an account created or logging in once a month. Today, that definition is obsolete. Modern software telemetry allows us to break usage down into three granular, measurable layers:

2. Seat utilization (provisioned vs. active)

The most common SaaS waste is shelfware: licenses bought for a team that go largely untouched.

  • Assigned Seats: How many paid licenses exist
  • Active Users: How many unique individuals actually authenticate into the platform over a 30-, 60- or 90-day rolling window

3. Feature adoption depth

Logging in isn’t enough if users only utilize 5% of a platform’s capability. If an enterprise buys a modern AI-powered CRM but employees only use it as a basic address book, the tool isn’t driving its intended value.

  • Basic Usage: Navigating to pages, reading content, running simple manual inputs
  • High-Value Usage: Triggering automated workflows, using integrated API connections, leveraging advanced reporting or utilizing built-in AI features.

4. Engagement frequency & time-to-value (TTV)

How deeply integrated is the tool into daily workflows?

  • Daily Active Users / Monthly Active Users (DAU/MAU Ratio): Measures habit formation and product stickiness.
  • Time-to-Value (TTV): The duration between initial seat allocation and the user completing their first high-value workflow. Slow adoption drags down your payback period.

Why measuring usage must precede financial modelling

If you try to calculate financial returns before auditing usage, you run into three critical traps:

  1. The Phantom ROI Trap: Calculating ROI based on 100 purchased seats when only 30 people use the platform artificially inflates your perceived return per user, masking massive financial waste.
  2. The “Self-Reported Survey” Fallacy: Studies show that when employees are asked how much time a tool saves them, self-reported estimates tend to be overestimated by 30% to 50%. Behavioral login and activity data ground your ROI in reality.
  3. Misidentifying Training Needs vs. Bad Software: Low usage doesn’t always mean a tool is bad; it often indicates poor onboarding. Identifying low usage early allows leadership to intervene with targeted training before writing off an investment.
  4. The Usage-to-Value Math Model

Once telemetry is gathered, map usage metrics directly into the core ROI formula:

core ROI formula:

An example:

Metric Scenario A (Unvetted Historical Approach) Scenario B (Modern Usage-Audited Approach)
Purchased Seats 100 licenses @ $1,000/yr ($100k TCO) 100 licenses @ $1,000/yr ($100k TCO)
Assumed Usage 100% active usage assumed Telemetry reveals only 45 active users
Claimed Time Saved 2 hrs/week per user ($50/hr rate) 2 hrs/week verified for 45 active users
Calculated Value 100 users × 104 hrs × $50 = $520,000 45 users × 104 hrs × $50 = $234,000
Claimed ROI 420% ROI (Deceptive) 134% ROI (Accurate)

Key Takeaway: Scenario B reveals that while the tool is positive ROI, $55,000 in unused licenses is being wasted which is an immediate optimization opportunity that Scenario A completely missed.

Best practices for auditing usage

To build a repeatable process around Step One, follow this implementation checklist:

  • Automate Data Collection via SMPs: Don’t rely on manual spreadsheets. Integrate a SaaS Management Platform (SMP) or connect directly into single sign-on (SSO) and application audit logs (e.g., Okta, Google Workspace, vendor APIs).
  • Define “Active” Per Category: Customize your definition of activity based on the tool’s function. A communication tool (Slack/Teams) should be audited on daily activity, whereas a quarterly reporting tool may only require monthly or quarterly active signals.
  • Establish Deprovisioning Triggers: Set automated alerts for unused licenses (e.g., zero logins for 30 consecutive days). Automatically trigger a workflow to reclaim or reassign that seat.
  • Segment Usage by Department: Compare adoption across teams. If Marketing has a 90% active usage rate while Sales sits at 20%, discover what Marketing is doing right and replicate those enablement practices.

Evaluating software ROI is not a static yearly task. It’s an ongoing data feedback loop. By establishing accurate, telemetry-backed usage metrics in Step One, you gain the clarity needed to cut unused spend, double down on high-impact tools and protect your software budget.

How do you calculate ROI for SaaS software?

SaaS ROI compares the financial value a tool delivers against its total cost. A basic formula is: ROI = (Value Delivered – Total Cost) ÷ Total Cost × 100. For a more accurate calculation, organizations should base value on actual active users and measurable outcomes rather than the number of licenses purchased.

What SaaS usage metrics should you track to measure ROI?

Key metrics include active users versus provisioned seats, login frequency, feature adoption, engagement frequency and time-to-value. Together, these metrics show whether employees are simply licensed for a tool or are actually using it in ways that generate value.

Why is software usage important when calculating ROI?

Usage determines how much of a software investment is actually delivering value. Calculating ROI based on purchased licenses can significantly overstate returns when many licenses are inactive or underutilized.

How can you identify used or under-utilized SaaS licenses?

Organizations can compare provisioned licenses with authentication and activity data from SaaS applications, SSO platforms and vendor APIs. For example, users with no activity for 30, 60 or 90 days may be candidates for license reclamation or reassignment.

What is SaaS shelfware?

SaaS shelfware refers to software licenses an organization pays for but employees rarely or never use. Identifying shelfware can uncover immediate opportunities to reclaim licenses, reduce SaaS spend and improve overall software ROI.

What is the difference between SaaS adoption and SaaS utilization?

Adoption indicates whether employees have started using a tool, while utilization examines how extensively they use it. An employee might regularly log into an application but never use the advanced features or workflows responsible for delivering most of its business value.

How can a SaaS management platform help improve software ROI?

A SaaS management platform can automate the collection of license and usage data, identify inactive or underused licenses and help organizations establish workflows for reclaiming or reallocating seats. That gives IT, procurement and finance better data for evaluating renewals and optimizing SaaS spend.