Revenue & Cost Program

The remit

I owned project timelines, budgets, and deliverables for client portfolio programs, and I owned the revenue analysis underneath them. Those are usually two jobs. Holding both meant I could not hide behind either — a schedule I defended had to survive a margin conversation I was also responsible for.

The work split three ways: keep the portfolio programs delivering, keep the monthly financial picture accurate, and make the team capable enough that neither depended on me personally.

1. $570K+ in cost savings

The savings came from asset optimization run with cross-functional teams rather than from a procurement squeeze. The approach was unglamorous: establish what was actually owned and actually used, find where inventory and supply chain were carrying cost that produced no service value, rebalance stock configuration against real procurement goals, and hold the change in place with a documented standard rather than a one-time cleanup.

The part that made it stick was insisting on cross-functional ownership. A savings initiative that lives inside one department reverses within two quarters, because the people who feel the friction were not in the room when the decision was made.

2. 98% accuracy, held monthly

Monthly tracking and reconciliation across client portfolios ran at a 98% accuracy rate. That number is a process outcome, not a personal one. I integrated internal databases and record management systems so documentation and data integrity stopped depending on individual diligence, and built the resulting structures as standardized benchmarks the department could apply beyond my own portfolio.

This is the habit I bring to any project: when a metric depends on someone being careful, it will fail the month they are busy. The fix is always structural.

3. A training program with a number attached

I built and ran competitive training for 30+ employees and streamlined onboarding, and the team's efficiency improved 30%. I sourced and secured project resources, set clear goals, and delegated by actual strength rather than by availability.

The measurable part matters. "We ran training" is an activity. "Team efficiency improved 30% after we changed how people are onboarded" is a result, and it is the only version worth reporting to a leadership team.

What preceded it

Before this I spent a year at Chase Bank as an assistant account manager, where I launched process changes worth a 15% efficiency lift and cut budget variances by 10% by leading a financial data evaluation project and presenting recommendations to stakeholders directly. Before that, two years running daily operations and training for a 20-person team — Store of the Month seven times, 75%+ across every tracked KPI.

I list the early roles deliberately. Operations management at the front line is where you learn that a plan which ignores how the work actually gets done is not a plan.