How I work

How I organise work with agents.

I use agents for research, development and recurring business tasks. These seven chapters describe the setup: how I write briefs, keep decisions with the code, divide the work and check a release. The examples come from recent projects and the tools I use to deliver them.

Read the chaptersFollow the work by email ↓

Repository activity

A dated snapshot of the repositories.

These are non-merge commits by me and the Claude Code and Codex agents working under my name, counted across 31 repositories. These are activity counts, not measures of quality, productivity or commercial impact.

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

Seven chapters

The working process, explained.

The chapters cover tools, planning, implementation, review and release. Each is free to read without an email address, with examples and files you can use in your own setup.

  1. 01

    Three Claude accounts, one notch

    Every account stays signed in. I can see its limits and switch with a key.

  2. 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.

  3. 03

    Keep the plan with the work

    Decisions, a queue, observable acceptance criteria and a record of what actually shipped.

  4. 04

    Turn repeat work into a skill

    I keep the brief, the checks and the stopping point so a repeated job keeps its standard.

  5. 05

    Let one model write and another check

    Codex writes from a full brief. Claude checks every claim against the source before publication.

  6. 06

    Give standing work a desk

    A written plan, shared records and a database that guards what an agent is allowed to do.

  7. 07

    Ship each piece and check it live

    A successful deployment is a starting point. I check the code a visitor can actually reach.

Public tools

Software and setup files.

These repositories contain tools I use for account management, email journeys, search and browser extensions. The library includes the supporting instructions and setup files.

Browse the full library →

Previous work

The experience behind the projects.

My background includes record-label operations, paid-search automation, product development and running software businesses. The figures below refer to the periods listed.

  1. 2011–2014Beatlock RecordsGrowth and operations for a label and radio show; 500,000+ YouTube views.
  2. 2014–2016VouchercloudPaid search across 15 international sites; automation saved 240 hours a month and cut team overhead by 40%.
  3. 2016–2018Reach RoboticsDigital marketing for MekaMon; influencer campaign videos passed 750,000 views.
  4. 2016–2022; rebuilt 2026Vouchernaut250,000 monthly sessions, no paid spend; 2026 rebuild: fifteen live products by 12 October.
  5. 2016–nowWithSeismic100+ client engagements; clients include Contra, The Motley Fool and STRV. Contra rating: 5.0.
  6. 2020–2023; rebuilt 2026BensonOriginal platform: 25M monthly sessions across 500+ stores; 80+ brands onboarded. Rebuilt in 2026.
  7. 2022–2023PatriannaLead growth and product operator; an in-house game studio and five React games shipped.
  8. 2023–2024PromptheusVoice-to-ChatGPT extension; 30,000+ users in a year.
  9. 2024–nowDinners With FriendsTechnical founder; 500+ guests across 50 dinners.
  10. 2026–nowHogsendEmail journeys: SDK, engine, Studio, CLI and MCP tools; EU and US cloud regions and self-hosting.

Further reading and help

Tools, notes and working sessions.

Browse the setup files, receive the chapters by email or discuss how the approach could apply to your team.

  1. 01

    Run it on your own project

    Choose tools, skills and setup files from the library, then copy an installation prompt for your selection.

    Open the library
  2. 02

    Follow the work

    Seven chapters, one a week, then the build log: delivery decisions, agent workflows and work shipped.

    Email me the build log
  3. 03

    Find your starting point

    Answer ten questions about your current agent workflows and get suggestions for what to investigate.

    Take the scorecard
  4. 04

    Establish a shared team workflow

    £2,500 fixed to build and test a team workflow, including preparation, a working day and documentation. The full fee comes off a delivery sprint booked within 30 days.

    Explore team adoption
  5. 05

    Discuss the business priority

    A free 30-minute call about what you need done and where I can help.