I've been looking at LightSwitch myself as a solution for RAD (rapid application development) about 2 weeks now. I have VS 2012 Ultimate but had to download Update 2 (I think) to get the latest HTML LightSwitch project templates. Remember that there are two flavours to LS: the default Silverlight solution and then the HTML5+jQuery version that came in the later updates. If your client does not like plug-ins, then you'd have to go the HTML5 route.
I'm a fan of using the right tool for the right solution. CRUD screens are a real pain and hence my own interest in LS. For that it is good and best used on simple CRUD form-over-data solutions such as your HR module perhaps. I'm using it for a simple user-access-and-maintenance app. It is bit of a mind shift from traditional coding as it is mainly a configuration based WYSIWIG framework, for room to add custom code in certain scenarios. Styling is tricky and painful but you can find online resources specializing in this. If you are prepared to invest the time to learn LightSwitch, you could probably save some time in the long run if building many CRUD apps in the future.
That being said, MVC's scaffolding feature also generates basic CRUD controllers and views for you. If you are already using MVC then then why relearn (in LightSwitch) how to do what you already can do easily in MVC and you are familiar with?
Purchase orders and PM type systems are typically full of business rules and exceptions. I would personally not use LS for such apps. MVC is a lot more scalable and robust for this type of development... IMO.
Hope this helps. Cheers.