Skip to content

SheetThe record

OrderAs the CV has it

Sourcesrc/data/experiences.ts, the file the CV reads

Count6 roles, read from the list

The record · 6 roles

The work, by when it happened.

The same work as the home page, in the order a CV gives it: every role, its dates, and where it's written up. The titles are the ones each employer gave, which is why two of them still say designer.

  1. Sept 2025 to Apr 2026Contract

    Full Stack Developer

    BPO Collections Ltd

    Payment infrastructure on an FCA-regulated estate. Fiserv end to end, 80% more mobile payments from launch, and a legacy ASP.NET stack hauled onto Next.js while it kept taking money.

    The case study: BPO Collections Ltd

  2. Feb 2024 to now

    Co-⁠founder & Design Systems Engineer

    inclusive.io

    117 components, built on my own, twice. Then the gates that could take the claim back off me.

    The case study: inclusive.io

  3. Oct 2017 to now

    Founder & Full‑Stack Developer

    DesignBuddy UK

    My own studio since 2017. 50+ clients. The brand and the build, both.

  4. Dec 2022 to Jan 2024

    Head of Web

    Paul McFadden Wealth

    Ran the web department for the group and its partner businesses, accountable for eight figures of web revenue. Hired three of the team and co-managed seven, across video, design and social.

  5. Aug to Dec 2022

    Senior Web Designer

    TMD Media

    Agency pace. Conversion sites, three or four at a time, to the date on the sheet.

  6. Oct 2016 to Sept 2022

    Graphic Designer

    NOVAVAPES

    Six years owning one brand while the company grew up around it.

  7. 2005 to 2016

    Before any of this

    Building for the web from fourteen, then a few years of freelance and whatever else paid, then retraining as a graphic designer. Fifteen years across development and design, and it's the code that came first.

    How I got here

  8. Alongside

    Quoin

    It puts a web page on a baseline grid.

    The live tool: Quoin

SheetHow I'd run your team

RuleEvery principle links to its proof

Sourcesrc/data/principles.ts

Count7, read from the list

How I'd run your team

Seven things you can check before you hire me.

What I'd bring to a department, written down only where it has already been done somewhere on this site you can go and look at.

  • A standard is a gate, not a statement

    A statement costs an afternoon and a gate costs you the argument, in public, the day it goes red, which is exactly why it works. I held my own AAA claim to one and it took the claim straight off me. Anything an agent writes is held to the same gates as any other contributor, and nothing merges unread.

    The gate that took my own claim off me

  • You get the number without asking twice

    There are 43 things on this site that are still wrong, and the count sits on the home page on purpose. If you're hiring at this level, the useful question isn't whether somebody has open defects, it's whether they can tell you the number without being asked twice.

    Still wrong, counted

  • Own the number, not a share of it

    Owning a revenue number is different from contributing to one. As Head of Web the funnel breaking was my problem at nine on a Sunday, and every argument about page speed, form length and one more tracking script landed on my desk. Most technical decisions turn out to be staffing decisions in a costume.

    Head of Web, Paul McFadden Wealth

  • Hold both halves

    Almost every expensive problem I get called into lives in the gap between design and engineering. Design says it's an engineering problem, engineering says it's a design one, and it sits there for a year with nobody's name against it. I can hold both halves, which is the only reason I can see it at all.

    Four screens to one, and 80% more mobile payments

  • Finish what other people left

    Roughly half a dozen developers had a go at the SagePay to Fiserv migration and not one of them took it as far as testing. I finished it on my own, against a PCI-DSS estate that never stopped taking live money, with zero failed cutovers.

    The payments case study

  • Release like it's going to press

    Six years in print is six years of releases you can't take back: one shot, it goes on a press, and a wrong bleed arrives as a room full of boxes. I carried that into a payment migration where a bad release isn't an ugly page, it's somebody already in arrears who can't get the payment through.

    Six years at NOVAVAPES

  • Bring people on, and write it down

    I recruited an apprentice and brought them from junior to running the social channel outright, and as Head of Web I hired three of the team and co-managed seven across video, design and social. inclusive.io has 47 supporting documents and a 14-document handover pack, for a project with nobody to hand it over to, which is either thorough or daft depending on the morning you ask me.

    The handover, in the inclusive.io case study

Tell me what's breaking