What I do
My career started on the revenue side of marketing: channel work, demand generation, leading teams and owning budgets, with a fair bit of beating pipeline targets along the way. Over time the work I gravitated toward changed. I found myself less interested in the campaigns and more interested in the systems underneath them.
There's a pattern to it. I notice where teams are quietly losing time and momentum, signals scattered across tools, work being done by hand that shouldn't be, no clear sense of what to tackle first, and I build something that closes the gap. Lately that's meant building AI-native workflows with Cursor, Gumloop, and standard LLMs on my own, without waiting on engineering.
The part of AI adoption I find most interesting is human, not technical: how a team actually folds these tools into real work in a way that feels useful and earns trust. I do my best work where the playbook is still being written, and I care as much about building teams people want to be on as I do about shipping the work.
That shows up most in how I lead. I led ANZ for nine months, built playbooks the team still uses, and I share what I build, so the AI workflows and systems run through the team rather than just me. I'm usually the person people come to when they want to think a problem through. Earlier, at Cisco, I coached a struggling rep back into a trusted contributor, the kind of people leadership the company recognised with an award in 2023. I lead with the numbers too, not just reporting them but turning them into the call we make next.