The counter-point here is that 10 years passes and processes have changed and needs have evolved and everyone's still stuck using that old internal app that was built by people who are no longer at the company and no one wants to update it because it's toil and there's no budget, and so processes are cumbersome and artificially complicated because everything has to go through that app.

Case in point at my company there's an internally-built ITSM app that requires a user to select "Approved" no less than 8 times across 4 screens to approve an internal request.

My point here is that there will always be edge cases that disprove the rule, so yes you're right, but are you right most of the time? I doubt it.

In my 30 years working in this field (and 10 of those years were spent helping companies deal with poor internally built apps), the majority of internally-built applications at companies that aren't modern software companies (i.e. most companies) age very poorly, have poor internal support and little to no technical health budget, have terrible user experiences, and are generally disliked by most employees who have to use them.

Particularly in these times when everyone can compare the tools they work with to the stuff on their phones or laptops that they use every day. It's an unfair comparison but it's still there. The expectations for interfaces and software usability have increased faster than most companies can manage for their internal products.