SaaS Savings are partly from reduced features
The software development process generally follows the "the last 10% of the work takes 50% of the development time" rule. That's where the unique requirements involving customizations and complex data integrations take place. They're hard for developers but greatly simplify work processes for end users.
After the switch to SaaS end users are told "our workflow optimization (to get the overall function to fit into the cloud app) don't allow for that feature in this release."
So the burden of extra work, which was eliminated as a cost of a couple months effort for developers and testers falls onto end users. 2 man months of effort saved at the cost of 5 minutes per week for each of 5,000 people.
If it were only one function set in one app it wouldn't matter, but (at least in our case) the migration of multiple functions to cloud SaaS adds about 2 hours per week to each staff member's workload. Times 5,000 for at least a couple years.
Management claims they've cut IT costs through "Workflow Optimization" and moving to the "the cloud", but staff wind up with less time to work productively and being aggravated by being forced to perform tedious workarounds.
But that's considered progress in a buzzword world.