Everyone on this thread focus on business decisions should something be automated based on perceived monetary value.
However, there is another important aspect in developing internal tools. In a lot of setups, developers rarely have a chance to investigate new technology, new development approach, different architecture, even different programming language on a day to day basis. Work is mostly done using predefined set of technologies.
For tools, the technology requirements are almost always much more relaxed, so the developers themselves gets to choose and try different approaches. While not every tool might end up being success in strictly measured time/money saved sense, in the long run it will help developers stay up to date with the technology, and even apply lessons learned in the real/product development.
As a bonus, employee retention might improve as people won't get bored so soon if they have a chance to try doing something new from time to time.
However, there is another important aspect in developing internal tools. In a lot of setups, developers rarely have a chance to investigate new technology, new development approach, different architecture, even different programming language on a day to day basis. Work is mostly done using predefined set of technologies.
For tools, the technology requirements are almost always much more relaxed, so the developers themselves gets to choose and try different approaches. While not every tool might end up being success in strictly measured time/money saved sense, in the long run it will help developers stay up to date with the technology, and even apply lessons learned in the real/product development.
As a bonus, employee retention might improve as people won't get bored so soon if they have a chance to try doing something new from time to time.