Emailing xls files around is functional, sure, but the software developer in me dies a little bit every time I do_final(1).xls
I don't know that a hypothetical no-code tool does any better at any of those, but Excel, powerful as it is, has some real issues.
https://support.microsoft.com/en-us/office/view-previous-ver...
Compared to git log -p, to see the changes in all the places there are instead of hoping I click on the right cell and catch all the changes.
Most of the data inside is just XML and with a good (stable) XML autoformatter you can even see some nice diffs between versions of an XLSX file.
A long time ago for interesting reasons of my own (including the fact that I was using darcs at the time and diff/patch-size especially of binary files was directly a performance issue) I wrote a tool called musdex to automate that workflow as (in git terms) pre-commit/post-checkout/post-merge hooks. I offer no warranties for anyone wild enough to use a tool like that in production Excel workflows, but it's a "fun" thing to try.
I have one public example of this on my GitHub that comes to mind, but it's a particularly weird one because it uses a musdex plugin to extract/combine an already non-binary format. (In this case it was an Inform 7 story.ni file that I just preferred to source control as lots of smaller, column-wrapped "chapter" files rather than one long "book" file of run-on paragraphs. GitHub's cool modern code browser hasn't been taught how to do jump to section for Inform 7 story.ni files, so it is nice being able to browse it as a file tree instead. Similar it's nice to see commit diffs broken down by chapter. I can't install my own Inform 7 plugin to GitHub's website, but I can certainly reshape my repo with a tool like musdex.)
We need to think about a tool that can do those with the same ease as Excel (Or Access). If we can't do that, it's because we need to make these tools better.