Having been in a similar situation, I found the problem was me ... in a way. I was too productive. People, especially testers, do not believe the speed by which bug-resistant code can be developed in Perl, especially by a maestro. Remember - these people find bugs for a living!. They know how fast software takes to be developed and how many iterations it has to go through to be relatively decent. I mean, they know more than you do! Duh ...

At least, they think they do. They don't really understand the paradigm shifts that are enabled with Perl. And, you're extremely gung-ho about what you're doing (which is good). Unfortunately, you're probably coming across as a cowboy who's just going to make their life a living hell.

The solution I used was this:

1. Back off. They know about the tools. You pushing will not help increase acceptance.
2. Find one user and make them your friend. Get to know them personally. I mean, literally, go out for beers or to smoke breaks together.
3. Find out what that one user complains about the most. (Also at this time, discuss with your friend your frustrations. Maybe they have insight for you.)
4. Ask them if you can make a tool to help out and be with your friend to hold their hand.
5. Write the tool. This tool has to be 110% bug-free. I cannot emphasize this enough. This is probably your only chance to make a good impression.
6. Work with your friend and get them to use it. Make it part of their daily life. Be willing to make the stupid features. DO NOT TELL THEM WHAT IT TAKES, OTHER THAN "Yeah, I can do that."
7. At this point, you have started the change. Lather, rinse, repeat.

And, good luck. I truly do feel your pain.

------
We are the carpenters and bricklayers of the Information Age.

Don't go borrowing trouble. For programmers, this means Worry only about what you need to implement.

Please remember that I'm crufty and crochety. All opinions are purely mine and all code is untested, unless otherwise specified.