I wouldn't make another move without talking with the Developers and finding out what and why there is a need for so many data changes to prod and let them tell you what the logic behind it is instead of looking for patterns that may or may not exist. If you pose it all in a very helpful manner, it'll also make it easier to work with the Developers in the future because you'll be a member of their club especially if you make it so they don't have to do any manual work to do this every day. Remember, it's probably as big a PITA for them as it is for you. If you're lucky, they will already have some automated process to define the data that needs to be changed so often and you'll easily be able to automate the whole thing from womb-to-tomb.

Once you have it automated, share with them and teach them what and how you did it and why. They'll appreciate the mentoring, as well.

As a bit of a side bar, until they needed more room and had to move, I used to sit right in the middle of the Developers so I could listen for any problems they might have on the database side and I also used to help keep people from proverbial "drive by shootings". I still use the 100% code reviews that I do as a chance to mentor and they seem to appreciate it. When they have a problem, they voluntarily ask my opinion or for my help. They take great pride in writing nasty fast code and also understand that doing it right the first time really doesn't take any extra time at all and saves a huge amount of rework time. It's an amazing group effort between Devs'n'DBAs that I've not seen much of in other companies I've worked for.