I have read the perldoc on modules, but I don\'t see a recommendation on naming a package so it won\'t collide with builtin or CPAN module/package names.
There is nothing wrong with naming your internal modules after your company; I always do this. 90% of my code ends up on CPAN, so it has "normal" names, but the internal stuff is always starts with ClientName::.