How I work
The tools make me fast.The method is yours to try.
I keep agents moving on separate jobs, leave the plan in the repo and check what reaches the visitor. I’m giving away the setup, the tools and the checks so you can try the same way of working on your own jobs.
The recorded pace
My work, including the agents working under my name.
These are non-merge commits by me and the Claude Code and Codex agents working under my name, counted across 31 repositories. They record committed work, not just code I typed.
- Non-merge commits in 7 days
- Non-merge commits in 30 days
- Non-merge commits in 90 days
- Product repos started since 20 September
Counted 18 October 2026
The method
Take the part that helps with your own work.
Start with the account setup, try a tool and follow a job from its brief to the live check. Every part is free to read, without an email address.
- 01
Three Claude accounts, one notch
Every account stays signed in. I can see its limits and switch with a key.
- 02
One job per session, room to switch
I keep the files apart with worktrees and leave the state where another session can find it.
- 03
Keep the plan with the work
Decisions, a queue, observable acceptance criteria and a record of what actually shipped.
- 04
Turn repeat work into a skill
I keep the brief, the checks and the stopping point so a repeated job keeps its standard.
- 05
Let one model write and another check
Codex writes from a full brief. Claude checks every claim against the source before publication.
- 06
Give standing work a desk
A written plan, shared records and a database that guards what an agent is allowed to do.
- 07
Ship each piece and check it live
A successful deployment is a starting point. I check the code a visitor can actually reach.
Try a tool
The working tools are public.
Claude Notch keeps my accounts visible. These other public repos cover email journeys, speech, search, editor tools and browser extensions.
Claude Notch
Three Claude accounts, their limits and a key to switch. Free for macOS 26.
See the GitHub repo ↗Hogsend
Code-first email journeys on PostHog and Resend, with self-hosting.
See the GitHub repo ↗psst-free
On-device speech-to-text for macOS using WhisperKit.
See the GitHub repo ↗geo-kit
An AI-search toolkit with a playbook and agent skills.
See the GitHub repo ↗cursor-tools
Tools made with Cursor to make Cursor faster.
See the GitHub repo ↗React + Tailwind extension starter
A Chrome extension starting point with React and Tailwind.
See the GitHub repo ↗
The longer record
The work started before this agent setup.
My work runs from record-label growth to paid-search automation, product delivery and operating businesses. The clients and results give the method its context.
- 2011–2014Beatlock RecordsGrowth and operations for a label and radio show; 500,000+ YouTube views.
- 2014–2016VouchercloudPaid search across 15 international sites; automation saved 240 hours a month and cut team overhead by 40%.
- 2016–2018Reach RoboticsDigital marketing for MekaMon; influencer campaign videos passed 750,000 views.
- 2016–2022; rebuilt 2026Vouchernaut250,000 monthly sessions, no paid spend; 2026 rebuild: fifteen live products by 12 October.
- 2016–nowWithSeismic100+ client engagements; clients include Contra, The Motley Fool and STRV. Contra rating: 5.0.
- 2020–2023; rebuilt 2026Benson25M monthly sessions across 500+ stores; 80+ brands onboarded.
- 2022–2023PatriannaLead growth and product operator; an in-house game studio and five React games shipped.
- 2023–2024PromptheusVoice-to-ChatGPT extension; 30,000+ users in a year.
- 2024–nowDinners With FriendsTechnical founder; 500+ guests across 50 dinners.
- 2026–nowHogsendEmail journeys: SDK, engine, Studio, CLI and MCP tools; EU and US cloud regions and self-hosting.
Keep going
Try the method before making time for a call.
Use what helps with the work you already have. If you want more, follow the weekly build log, check your starting point or bring a real job to a Learn day.
- 01
Follow the work
A chapter a week by email, plus what shipped, what I decided and what went wrong.
Email me the build log - 02
Find your starting point
Take the 2-minute scorecard to find your starting point.
Take the scorecard - 03
Use your own business for a day
£2,500 for a hands-on Learn day. The full fee comes off a Build booked within 30 days.
See the Learn day - 04
Bring a job to a conversation
When you want to work together, bring a job to a free 30-minute call.
Try a chapter a week. See what shipped.
I’ll email one chapter a week, plus what shipped that week, what I decided and what went wrong. No spam; leave in one click.