What I'd question is what you use Ciscoworks currently to achieve. I think if in you're current deployment, if for configuration, logs, troubleshooting, etc you always turn to ciscoworks first and foremost, it's a good option since it's something you're already familiar with, and is actually usefull.
Personally I'm fine without it, we have it deployed in our network, but I've only ever logged in maybe 3 or 4 times, and just find generally doing stuff takes longer then my ad-hoc stuff. We're a fairly big shop, so we have HP Openview for SNMP alarming, fed to our Control Center, Openview Performance Insight for SNMP polling stats and generating statistics. For my equipment, we have all logs sent to a solaris box, and I basically just have a tail that follows the logs on one of my screens all day. We do nightly backups in a script, with a script to grab all current configs, so finding differences in config is easy using unix diff tools. And we do all configuration directly by logging into the box. So for me it's ultimatly a useless tool that I've never had an enticing reason to get into.
On the other hand, some of our backbone team love the thing, but that was mainly because they could deploy a config change such as a new vlan to be trunked to every switch in one go. That was never my responsibility so I could care less.
This brings me back, if it's a tool you use every day, and everyone is already familiar with it, it's a good thing to get. If it's there and you use it once a month, and everything you use it for at that time can easily be done using simple scripts, then don't bother.