Pressed for time but wanted to weigh in with this: @mgreiner28, in a situation like this, the smartest thing to do first is take some time to connect the UX processes you're considering with their value to the company. UX is a massive field, and there are any number of smaller disciplines and activities within it. You can't do them all.
So what matters? Stronger user research to ensure you understand what users really need, that you solve the right problems? A focus on Information Architecture because you deal with complex, data- or content-heavy sites and systems? Early lean UX prototyping to simplify complex workflows?
The point: before you start suggesting approaches and activities, consider (1) how specific UX processes or activities benefit the agency's clients, (2) how those same activities benefits the agency and (3) how they benefit each role/dept within your agency.
That last one is important, because you need champions.
Developers need to feel like integrating UX means less work (or rework) for them.
Account Execs or Project Managers need to feel like integrating UX takes pressure off their shoulders to convince clients that the work they do is valuable, that they're serving their needs, or that the results they're after will actually materialize.
Management needs to feel like integrating UX will enable them to deliver results to clients that make them look like heroes, engendering trust and loyalty. Or that a focus on UX will help them get more business (how?).
Again, you can't do it all. Start thinking about what specific things will benefit all involved — and which ones you can actually pull off given current personnel, time/budget constraints and culture.