Earlier quoted context omitted.
Not the OP, but also selling B2B software. You can hold a user accountable that they'll actually use the software purchased. The company is spending a lot of money on it, finds value in it, and wants to ensure it's being used and implemented correctly. B2B software with figures like the OP means you're building a professional relationship with a customer (as opposed to a transactional one), and can push back when the…
Also, users are sometimes simply ordered, by their bosses or IT, not to press buttons in ways that are known to break the software. This is sometimes considered cheaper than fixing bugs, or at the very least, mitigates the problem until the next scheduled deployment window. It’s a very different world.
And I'm saying this a developer, where we would (and have) gladly sometimes fixed the bug during the 1h call with the customer, but until it was being rolled out... weeks, maybe months.