Subscribe and every new build lands in your inbox. These go deeper than my LinkedIn posts: the full prompts, the scripts, the numbers, and what broke.
-
Leverage 8/10
the agent framework I use, and how I built our supply planner
How I go from a job I do by hand to an agent that does it: skills first, then stacked into one agent, with a written job description, an autonomy matrix, traces on every run and a second agent auditing the whole thing. Worked through with Batch, our supply planner.
Read the build →
-
Leverage 8/10
the dispatch console: from rules in our heads to an app anyone can open
Dispatch rules at oac went through four stages: remembering them, posters on the wall, a sheet that only ran on my laptop, and now a web app anyone on the team can open. This is the build: the rules engine, the hashed PII matching, and the customs rule that breaks every UK freebie.
Read the build →
-
Leverage 6/10
oac's brain, part 1: the data layer
Every agent I run sits on the same data layer: one Google Sheet workbook as the single source of truth, fed by scheduled Python syncs with health checks. The full wiring: source-by-source workarounds, the rules that keep the numbers honest, what failed first, and a where-to-start map for building your own.
Read the build →
-
Leverage 3/10
Free replacements were quietly wrecking my numbers
A lost parcel means a free replacement. Process it wrong and it corrupts every number downstream: pads orders, tanks AOV, tells your demand model you sold what you gave away. Here's the tagging standard and the skill that does it right.
Read the build →
-
Leverage 4/10
My daily briefing, and how it's changed three times
Every morning an agent writes me a briefing before I'm at my desk: what needs action, what's slipping, what to prep. It started as a glorified summary. Here's how it became something I run my day on.
Read the build →
-
Leverage 4/10
The scenario-planning agent that couldn't live in the grey
I tried to teach Claude the judgement call every planner makes: do I let one flavour dip below minimum for two weeks, given what's landing next month and a retail deal that might close? It couldn't do it. Here's how far I got.
Read the build →
-
Leverage 3/10
Three inboxes, one source of truth: a dispatch tracker for a 4-person team
Dispatch issues, delivery problems and carrier complaints were landing across three different inboxes. Built in a couple of hours: claude scans the inboxes twice a day, classifies, posts a single summary into slack, archives the structured data into a sheet. Built once, compounds daily.
Read the build →
-
Leverage 3/10
SOPs nobody had time to write, written in minutes
In a small team the 'process' is whatever's in one person's head. I use AI to turn how I actually do a task into a clean SOP the team can follow, in minutes, instead of never.
Read the build →
-
Leverage 5/10
An afternoon of invoice reconciliation, down to minutes
Every month the wholesale invoices in Xero have to match the orders in Shopify. By hand it's an afternoon squinting at two exports. This skill finds the files itself and hands back only the mismatches that matter.
Read the build →
-
Leverage 5/10
The month-end stock count, rebuilt from the data
My accountant needs a valued stock count every month: product, packaging, merch, free stock. It used to be CSV exports and manual valuation. Now it's built straight from the databases, with the double-count traps designed out.
Read the build →
-
Leverage 4/10
The pouch is the constraint nobody plans for
Most plans stop at finished product. But you can't run a batch without the pouch, the film, the box, each with its own lead time and minimum. I put packaging in the plan and it immediately found the constraint nobody was watching.
Read the build →
-
Leverage 3/10
Perpetual inventory on a Shopify budget
A small brand can't run an ERP for perpetual inventory, and 'just check Shopify' isn't good enough. Here's how I used a cheap inventory app as the perpetual layer, and the column that quietly breaks everyone who tries it.
Read the build →