Available now · contract or full-time · London or remote UK
Operations lead, nine years. Started in finance, moved towards the rest of the business.
I trained as an accountant and spent five years in insurance, investment accounting and risk. What kept pulling me away from the ledger was everyone else’s problem: legal stuck on onboarding, a people team with no hiring pipeline, engineers who needed someone to own the unglamorous parts.
I found I liked that connective work more than the numbers and followed it, through Parity, the Starknet Foundation and now Chainlabs. Payout rails, hiring pipelines, treasury controls, a compliance framework legal signed off on, the bot a 43-person network runs on.
Somewhere along the way I stopped writing specs for other people to build and started building them myself, mostly because waiting was slower. That is how I ended up shipping the payout pipeline and the reconciliation behind it, reviewed by the engineers who know the stack better than I do.
Things I helped build that are still running. Drag the ring or use the arrows; click the front card for the story.
Six layers per build, foundation first. Click a layer to read what it is made of, who built it with me, and what it cost.
A loop, not a ladder. PRINCE2 and AgilePM gave me the vocabulary; nine years of things not going to plan gave me the habit.
Sit with the team that has the problem, not the ticket. Most of the answer is already in the room; my job is to hear it.
Trace what really happens today, end to end, before changing anything. The accountant in me insists.
The problem as stated is rarely the problem. One good question, asked respectfully, saves a month of building the wrong thing.
The smallest version people can use tomorrow, in the tools they already live in. Then own the metric, weekly.
If it has not earned its place in a week, it goes. Keep what works, say plainly what did not, go round again.
Built with other people.
Credited that way.
The best things on this page were built with other people, and I would rather credit the team than pretend otherwise. I ship production code through the same reviewed PR workflow as the rest of the team, and where someone knows a system better than I do, I ask them.
Every role has had the same shape: another team has a process problem, we work out the real question together, and I build the fix with them and hand it back running.
Nine years, financial services into crypto. Why each role ended is stated; none were performance.
Clients, ecosystem counterparties and employers across nine years.
Seven industry-leading firms, in blockchain intelligence, on-chain security monitoring and a top-tier exchange, rely on this vertical's output. I hold the relationships and the delivery cadence with them weekly.
Grant operations for 500+ teams, treasury on Safe multisigs, KYB on Sumsub, and daily work with Ethereum and the ecosystem's core builders.
Where the nine years were spent: Layer-1 and Layer-2 organisations, marine insurance, investment management, media finance and industrial lending.
The everyday stack, and the AI layer on top of it. Hover a group to bring it forward.
Led the Asana migration off Airtable across teams at Parity. Notion and Airtable process work cut onboarding and reporting cycle times by 33% at Starknet. The Chainlabs network of 43 lives in Telegram; Twende's team runs on a Notion Command Center.
Advanced Excel and Sheets from four years of investment accounting and underwriting reporting. Safe multisig on $100M+; Sumsub wired into the AML/KYB framework; KPI dashboards for grants and delivery.
190+ PRs on the production repo through a reviewed workflow; 8,361 contributions in the past year. Not a career engineer. An operator who ships production code with the engineering team and learns in the open.
A working method rather than a tool list. 40 agents in production across two businesses, 22 QC agents on the Chainlabs repo, 18 running Revion's go-to-market. LLM pipelines for contract summaries, QA and reporting; Perplexity and Gemini for research, Cursor and Codex for the build, Claude Code as the operating layer.
The parts that do not fit on a CV but explain a lot.
I have a dog, which settles the shape of most mornings. Training and general wellbeing keep the rest of the day honest, and I am always working on something I am not good at yet. Sport I watch as closely as I play it. Travel taught me that every place runs on a different process and every one of them makes sense once you sit with the people. Music is on most of the time. Family and friends are the point of the whole thing.
Within 48 hours you will have the three questions I would ask first and what I would build in week one. No deck, no pitch, one page. It is how I work, and the fairest way for both of us to find out whether we would work well together. If I am wrong about your problem, you have lost nothing but an email.
Not one prompt. One working session on top of months of groundwork: a single source of truth for every claim, a written brief and operating rules for the AI, an agent library already in production, and the same QA passes I run on any build: requirements check, fact audit against records, copy review, accessibility and performance checks, then deploy verification against the live endpoint. Hover a node.
The same loop as above. I set the brief, audited every claim against my own records, and removed what did not earn its place. Not to show that AI can build a CV, but to show how I run a build.