I help ambitious teams scale by building the systems beneath the work. Less deck, more system. The work that compounds.
You can't enable AI well if the operations underneath are weak and the data is messy. Most people selling "AI" skip the plumbing. The plumbing is where I start.
The pattern repeats in every role below: enter with no structure, build the operational foundations, then layer documentation, tooling, and AI automation on top.
Most recent first. Keep scrolling to go back in time.
That's the story so far. The next chapter could be yours.
Every tool I work with and what it does for me. Search, switch the grouping, and tap any tool to read how I actually use it.
A loosely organised museum of things I've built, shipped, or co-founded.
Notion agent that turns meeting transcripts into owner-tagged tasks, so actions never die in the notes.
24/7 personal AI infrastructure on a dedicated machine, running a team of specialised agents across business and personal life.
Custom MCP server so Claude can coach against my real training data.
Founded a DTC playtent brand and ran it solo to ~$100K revenue in year one.
Positioning, ICP work, and identity, from naming to unboxing.
Hands-on Meta ads: campaign structure, creative iteration, budget management.
The operating principles behind leading a global delivery team.
Repeatable hiring process for operators who run independently.
Structured reviews and growth paths for a global delivery team.
Defining the metrics that show whether the team is winning.
End-to-end lifecycle tooling at Askable, brief to handover.
Knowledge bases built for Askable and Neuron Mobility, used daily.
Handover process that lifted delivery quality and cut scope creep.
My digital business card. Click the card to flip it over.
CONSULTANT · SYSTEMS & OPS
Builds the systems beneath the work — scaled ops across 8 Australian city launches, led 300+ staff, now shipping automation that runs on autopilot.
Send a short note about what you're working on, what you're looking for, and any timing that matters.
I read every message and reply within a few days.
Three shots. Pull, aim, release. Played basketball growing up, this is the human bit between the consulting copy.
A Notion agent that reads meeting transcripts, pulls out the action items, assigns owners, and pushes them straight into my project management tool.
The system end to end. Click any step, or let it run.
The transcript lands in the meeting note in Notion — exactly where it always did. Nothing new to capture, no new habit to build.
Trigger off where the data already lives. The system starts from the notes I was already taking, so the adoption cost is zero.
The new transcript trips the Notion agent automatically. It runs whether or not I remember it exists — there is no button.
Run on autopilot. A manual kick-off is exactly the activation cost that made the old way fail.
The agent reads the back-and-forth and pulls out every action item — the part I used to do by hand, meeting after meeting.
This is where the time went. The items were always in the notes; they just needed extracting reliably.
Each task gets an owner. Mine drop into a priority bucket that puts work I can action myself at the front of the list.
Added after the first hundred tasks. A raw capture list stops being workable; the bucket keeps it honest.
Tasks land in ClickUp alongside the rest of my work, and the processed meeting note is auto-archived.
Push results to where the work happens. Action items don't get done in note form.
I sit in a lot of meetings each week with different people and stakeholders. Keeping track of what I'm actually meant to action out of each one is the part that quietly eats time. The notes are there in Notion, but the action items live inside them, buried in the back-and-forth.
Before Taskie, tasks would slip. Not all of them, but enough to be a problem. The activation cost of opening every meeting note, pulling out my action items by hand, and dropping them into my project management tool was just high enough that I'd defer it, then forget it.
Tasks were slipping — not all of them, but enough to be a problem. The action items were always in the Notion notes, buried in the back-and-forth, and the manual step of pulling them out was just costly enough that I'd defer it, then forget it.
Three principles before any building, so every wiring decision had a test to pass: trigger off where the data already lives — no new capture surface, no new habit. Push results to where the work happens — tasks land in the project management tool, not back in Notion. Run on autopilot — if it's not automatic, the activation cost doesn't drop.
Sole designer and builder. Built partly to test the new Notion agent functionality and find where it actually fits real work: the agent watches for new transcripts, extracts action items with owners, and pushes them straight into ClickUp.
Switched on against live meetings, not a test set. From day one it ran on every new transcript with no manual kick-off — and no dropped tasks from any meeting that went through it.
After the first hundred tasks the raw list stopped being workable, so I added a priority bucket that puts work I can action myself at the front. Usage is the roadmap — the system keeps showing me where the next fix is.
100+ tasks captured across 50+ meetings since launch. No manual entry of action items, no dropped tasks from the meetings that go through it.