About

I build order out of operational messes and, somehow, enjoy doing it.

I’m a revenue operations and healthcare systems leader with a background in building structure where there mostly used to be effort, instinct, and a heroic amount of spreadsheet tolerance.

I do my best work in fast-moving environments where the systems have not quite caught up to the ambition yet.

Portrait of Annie Mays

A lot of my work sits at the intersection of operations, revenue, systems design, and leadership. In practical terms, that means I tend to step into environments where something important is growing, something operational is straining, and somebody needs to figure out what is breaking, what matters most, and what to build next.

I’m especially drawn to messy-growth moments: unclear ownership, fragmented workflows, weak visibility, recurring issues that are being treated like isolated ones, and teams working far too hard to keep underbuilt systems alive.

That kind of environment is not for everyone. I like it.

My career has centered on healthcare operations and revenue cycle, but the throughline has been broader than that. I’ve consistently gravitated toward work that requires clear thinking under pressure, operational pattern recognition, and a willingness to get close enough to the work to understand where the real problem lives.

Over time, that became less about simply managing tasks and more about designing systems, improving decision-making, and helping organizations move from reactive effort to something more stable, visible, and scalable.

In other words: fewer recurring fires, fewer mystery handoffs, fewer “we should probably look into that” problems hanging around for six months.

I’m a calm, direct, systems-minded operator. I care a lot about clarity, trust, good judgment, and building environments where people are not forced to compensate for weak process design with sheer endurance.

I’m not especially interested in looking busy for sport. I care about work that is clear, useful, measurable, and built to hold up when things get complicated.

I also think some of the best leadership happens quietly: asking better questions, seeing patterns early, making decisions without adding theater, and creating enough structure that good people can do strong work without living in constant operational whiplash.

Outside of work, I’m drawn to things that have texture, voice, and point of view. I care a lot about good writing, thoughtful design, and work that feels both intelligent and alive.

Which is probably part of why I like operations as much as I do. At its best, it is not just about efficiency. It is about shaping the conditions that make good work more possible.

Also, and this feels important to disclose, I am permanently a little suspicious of any workflow being held together by vibes alone.

A few things I value

What tends to matter to me most

Clarity

In communication, in ownership, in expectations, in what the work is actually trying to do.

Substance

Smart thinking is useful. Decorative complexity is not.

Calm execution

I trust steadiness a lot more than noise, urgency theater, or chronic chaos posing as ambition.

Good systems

The kind that reduce friction, improve judgment, and keep people from reinventing the same solution every Tuesday.

Bottom line

I like making complex things more workable.

Especially when the work matters, the pace is real, and the current process is one more bad handoff away from becoming a group project with no owner.