Given that you say it's an intranet app, I'll assume it's web-based. There's essentially two ways Perl can power a web-based app: via CGI; or via some sort of persistent mechanism (FastCGI, mod_perl, Perl-native web servers).

If you're using a persistent mechanism, a single Perl process (and thus a single compilation phase) serves multiple (potentially millions of) requests. So speeding up the compilation phase serves no purpose at all.

If you're not using a persistent mechanism, then a new Perl process is spawned for every request, which has to parse and compile your script, along with all the modules you're using. In this case an opcode cache would give you some extra performance; however switching to a persistent mechanism would give you a far bigger boost.