My advice would be to talk to the BMC guys on the ground performing the POC. They will likely have the best understanding of your use cases and how BladeLogic fits into these.
From my experience I've found that companies using Puppet generally have one "puppet guy" as he's the only one who knows Ruby. You can do a lot with BladeLogic Server Automation (BSA) with no scripting knowledge (compliance rules for example ).
When it does comes to scripting you can just use bash or windows cmd to achieve most of your tasks. The network shell language is nearly identitical to bash so finding people who can write it is easy.
To give you some idea, here are some tasks you can do with no scripting:
- Restart a windows service
- Change a registry value
- Add a vDisk to a VMware Virtual Machine
- Reconfigure a virtual machine's number of vCPUs.
- Change a single matched line in a single configuration file on every server in your fleet.
Regarding content, puppet has community submitted content so it is of questionable quality and will need to be adapted to suit your implementation. BSA has compliance content available for the major regulations (PCI, SOX, DISA etc...).
Also if your idea is to move towards a Cloud Lifecycle Management product suite then BladeLogic is a must as it is part of the suite!