Our production planning department subverts our erp system via excel spreadsheets that they distribute it has all the problems you'd expect.
I looked in horror the first time I gazed upon this thing. The guy who created it hates it and realizes it's a gigantic crutch, but the will to move off of it is a intracompany political land mine.
We're migrating away from a legacy system with a ton of Excel based side processes.
Also Excel's best friend Access keeps showing up in unexpected places. =\
Which is both awesome and a major problem, at the same time.
Excel highly encourages what would be considered insane development practices anywhere else (copy-paste code, single-character variable names, no version control, mixing code and data, mixing front-end code and back-end code, no unit, regression or integration tests, development on live systems). As a result, any nontrivial Excel spreadsheet end up being far more brittle than the same solution coded up by even a well below-average coder. Sure, maybe with extreme discipline these can be avoided, but Summer Intern Derek doesn't have said discipline.
Transferring that knowledge to a software department (and then limitations back) is quite complex and fails more often than not, leaving the business side with a software they don't want to use and can't adapt and quickly go back to Excel ("I understand it! I can adapt it!") and use the official tool only where required with hesitation.
And yes, the Excel tool reaches a messy point, but it's built over years step by step, tied to the process changes.
However, it is much more probable that we would migrate some processes to self developed specialised tools rather than another Google Sheet alternative.