I tried to get people to code review before merge and nobody cares. Nobody cares about clean code either. Everyone is worried about getting something working somehow even if it's bug-ridden and slow.
I would say get into the process than the code. this way you can justify your actions better to PMs and managers. People don't like their code to be watched, but they will eventually fix their coding-standard issues each time a red light comes up after they check-in. (styleCop is the tool for .NET community).
The product is about the people. You have to demonstrate caring for the people before you can get them to share your views on what makes a better product.
Always remember that everyone disagrees on the details. As the old adage goes: Quot capita tot sensus.