I'm going to guess from the way you described this that you're dealing with Windows. For that case I've had luck with putting Perl and the required modules on a file server somewhere, and then giving end users a .bat file which uses them. You can start that with the utility pl2bat and then edit it slightly to make it refer to the copy of Perl on the file server.

If done correctly pure Perl programs will work with no local installation at all. And you don't have to create a large executable for every utility.

It has been some years since I did this. At that time I was using ActiveState. What I would do to set things up was install Perl on my machine, copy the Perl directory to the file server, find perlcrt.dll and copy that to Perl's bin subdirectory, then create my .bat files and away I'd go. I could not tell you whether there is still that dll dependency, or whether there might be a new dependency. You will have to experiment to figure out what works.