About me

Since my dad first put a book in my hand early doors I've wanted to tell stories. I'm four years into my first novel and nearing the end of it, which is either evidence of persistence or of how much of my week belongs to other people's narratives.

Professionally it's been the same instinct at higher stakes. Thirteen years inside large organisations, mostly telling people things they hadn't asked to hear. Mergers, divestitures, restructures, brand transitions, a charity merger during a pandemic. The work that reaches my desk usually arrives with a confidentiality protocol attached and a deadline that isn't negotiable.

I started as a content editor writing regulatory bulletins for financial markets, which taught me how to understand a complicated subject well enough to explain it plainly to someone who hasn't got time to be confused. Market structure, custody and asset servicing, financial crime and regtech, private assets, pensions. All of it rewards a meticulous mind; none of it explains itself.

I've built apps, birdhouses, go-karts and computers – although "assembled" is more accurate for the last one. I built my first computer at eleven and blew the motherboard, bending the CPU pins in the process. It was an expensive lesson. I built the second one more carefully.

The technology interest started roughly there and never stopped. I learn coding languages in my spare time, I've flashed and jailbroken more phones than I should admit to, and I once built a smart mirror out of a Raspberry Pi that displayed the calendar, the weather and the traffic. My partner has since relegated it to the home office, which I consider a review rather than a verdict.

It's also what I've built at work: communications functions from scratch, lean teams, an AI-enabled press office, and the narrative architecture that outlasts whoever wrote it. Real-time data infrastructure, distributed ledgers, smart contracts, AI – I've spent years learning to explain them to rooms that needed to act on them.