As the decision maker (also a software engineer) I will work hard to avoid SaaS because it's a sensible move. And that is especially true if other engineers believe as you do that it's difficult to make a good product.
By comparison, the same app, installed locally, doesn't suffer from any of the above problems. There is no contract, no latency, and I don't have any risk if the company is sold. I will likely just have to find another solution provider, in the last case, but at least I'm not locked into additional years of servitude supporting a poor product for my users.
Many very large enterprise software providers (Sage, Oracle, IBM) and small OSS shops (Grafana, Zabbix, ProxMox) offer run local versions of ERPs or entire applications with no usage restrictions. The licensing pays for support and updates, not usage. In this model, the software provider has incentive to provide good support, and quality updates. They care to maintain the product because their care is what they are selling.
So, it won't absolutely be the case at this scale. Business as usual is the opposite of that at this scale. I should have to prove beyond doubt that there is no alternative when I agree to sign for SaaS. I'm agreeing to take on a lot of risk when I do that.
>Why would there be no contract with a local app?
Because that's what I want to buy, and for good reason (see above). And someone has figured that out and sold it to me.
I mean, you try making such software and let me know how that goes for you. This type of vague criticism sounds a lot like the typical engineer retort of "I can build it myself in a weekend," discounting the real complexity involved.