You're going to be building things that many people will use for a long time in the future. Even that small script that converts a customer email to PDF, copies

You're going to be building things that many people will use for a long time in the future. Even that small script that converts a customer email to PDF, copies it to the shared folder, and prints it on the copy room printer could become a critical system. Find these small one-off projects and solve them before they slow down the business. I've made many small utilities that overtime got replaced by larger systems but without them, maybe the company wouldn't have grown large enough to afford the large system. Think of yourself as a foundation-builder than a typical developer at an established company. Once you setup a git-flow or email distribution lists, you'll own these systems for a while and will be the expert on managing/fixing/growing them. Plan well but not too much. Get it out in production (inside the premises) immediately. If you're working on external customer-facing stuff, start writing policies on how things should happen, if such policies don't already exist.