You can suggest features via Twine's issue tracker. I would honestly expect a solution to be better vcs integration and support, not a reinvention of the wheel. Tech-savvy or not, using git or similar through one of the many GUIs or websites should not take more than a crash course, I'd imagine, just for basic forking and pull requests, which will be most, if not all, of what you need.
I would be surprised if Twine tried to roll its own half-baked vcs instead of just making integration easier. @HiEv is right that CLI compilers are way easier to integrate with vcs than Twine 2, and he's also right that 90% of everything your company needs to do, including a lot the vcs stuff, could be done in batch files and on a website like github or bitbucket.
Also, vcs is always worth it imo, probably especially for companies, at least if you're doing stuff with tech and writing code to some extent. If you aren't you might be better served by some sort of mind-mapping or flowchart application.