If you Google my name, the algorithm will inevitably serve you a moderately dramatic British soap opera character. I am the other one.
I'm a Brisbane native currently attempting to survive London winters, and for the last twelve years or so, I've been building products. Some of them worked brilliantly. Several of them cratered into the earth. I'm surprisingly okay with both outcomes.
My early career was consumed by a slightly unhealthy obsession with cyber security. As it turns out, spending your formative years trying to break into networks is phenomenal training for figuring out why your own production databases are mysteriously on fire at 3 AM.
I eventually did time in the enterprise mines at SEEK and Coles Group. It was highly educational in the exact same way that eating unseasoned broccoli is educational, but it gave me a front-row seat to what actually makes large engineering organisations difficult — the politics, the change management, the sheer complexity of how hundreds of people try to build things together. That stuck with me. After enterprise, I led authentication at Linktree, built private equity infrastructure at Pactio (where the margin for error was a terrifying absolute zero) and chased down wildly obscure US carrier bugs while building a graph database at Blinq.
I also have a terrible habit of building things. I founded OpenClub, a community management platform. As a founding engineer at AutoGrab, I helped build a predictive vehicle pricing engine that ingested over 20,000 data points a minute. We ended up outperforming Kelley Blue Book on residual price forecasting across Australia and New Zealand, which mostly proved that a few engineers with a massive data pipeline can comfortably ruin a traditional industry's day. After that, I built an AI assistant called Jamie. That project was mostly useful for teaching me exactly where AI creates actual, measurable value — and where it's simply a very expensive parlour trick.
Currently, I'm the co-founder and CTO of Flowstate, backed by a16z Scout Fund, Haatch and others. We're building the platform for Workforce Engineering — real-time telemetry on teams, budgets, CapEx/OpEx classification and AI spend. If that sounds like a mouthful, the engineering behind it is worse. It is by far the most ambitious thing I've ever tried to pull off, and every part of it — from the data layer to sitting across from customers trying to solve genuinely hard problems — is exactly where I want to be. AI is fundamentally reshaping how companies build and run engineering teams, and we have a front-row seat.
When I'm not shipping, or apologising to my team for something I broke in staging, I'm either on a mountain somewhere, aggressively defending Australian coffee as the only objectively correct coffee on earth, or drinking AIX 2021 Coteaux d'Aix en Provence rosé.
I will not be taking questions on the wine choice.