well there's the craftsman argument and then there's the broken windows argument.
the craftsman one if obvious: if you're in a devops/IT role and your job is to manage salesforce, then you should have some input in it as it'll affect you efficiency (aka the profitability of your company). A salesman shouldn't be buying tools for the carpenter without the carpenter's input.
the windoww argument is a bit more superficial but still a factor to consider. I may not be working on mainaining saleforce, but I will need to interface with it for logstics purposes. if it's so inefficient that it becomes a chore to track hours or update documentation or etc. it's going to leave a bunch of broken windows. You can still operate with a broken window, but that part of the building will be a place to avoid. You may even try to work around the CRM wherever possible. Which seems to lose the point of a CRM