Joe HodgeApplied AI product builder · Founder of Auromind

In a sea of AI design,ownership & tasteare my edge.

I build AI-native software (web apps, local AI and desktop tools), and I prove it works before it ships.

Beneath the surface

Anyone can generate the surface. Here’s what’s underneath.

Four products I built by directing AI agents, and took responsibility for: the decisions, the benchmarks, the tests. Eight of those decisions are circled on the work itself.

01 / 04

Leaf Edge

Trading journal & analytics · web appLive at leafedge.io

  1. Leaf Edge product presentation showing its dashboard, journal and daily review with illustrative demo figures.

    The trade is over. The learning isn’t.

    I trade, so I built the journal I actually wanted to use: broker imports, profit and loss matched down to each execution, and notes that stay attached to the trade they describe.

    Built withNext.js · TypeScript · PostgreSQL · Stripe

    Leaf Edge · product presentation · demo account, illustrative figures

  2. Leaf Edge journal: a notes registry, a chart-review entry linked to trade #198 and an inspector showing the linked NVDA trade built from two fills.

    01The workflow

    The journal lives next to the evidence.

    Notes were scattered across trade details, daily reports and a separate journal. I rebuilt it as one workspace: a registry of entries, an editor, and the linked trade open beside them.

    Leaf Edge journal · interface capture, 14 Sep 2026 · seeded demo data

  3. 02The numbers

    Every number traces back to a fill.

    One trade can be several entries, partial exits and a final contract sold at a different price. The matching engine keys positions by account and contract, so P&L holds up per execution and accounts never bleed into each other.

    “I want to have the options chart first and foremost the view you see”

    My trade-review feedback · May 2026

    Leaf Edge journal · interface capture, 14 Sep 2026 · seeded demo data

02 / 04

MindCap

Local-AI meeting notes · desktop appPast project

  1. MindCap AI & Models settings with the local Gemma 4 E4B 4-bit model selected and an on-device engine panel.

    Fast enough to use. Good enough to trust.

    A meeting-notes app built to run its AI on the laptop: recording, transcription and summaries. The interface was the easy part. The real work was choosing small models and proving they were good enough.

    Built withTauri · Rust · sherpa-onnx · llama.cpp

    MindCap · settings capture · synthetic demo mode

  2. 03April–June 2026 · Model selection

    I made the models compete.

    My rules: run locally, fit a consumer GPU, carry a commercial licence. Around ten speech models and five small language models were benchmarked against that spec, on accuracy, speed and shared GPU memory.

    A 21-minute meeting vs a human transcript · RTX 4070
    Speech modelWords wrongTime taken
    parakeet.cpp · 6-bit23%8 s
    Parakeet TDT v224%48 s
    SenseVoice Small29%25 s
    Cohere Transcribe33%4 min 30 s
    Content word error rate; fillers and speaker labels excluded. The parakeet.cpp run used 40-second voice-packed chunks.

    MindCap · settings capture · synthetic demo mode

  3. MindCap prepared AI notes for a fictional Northstar meeting: executive summary and decisions.

    04June 2026 · In the app

    A benchmark isn’t the product.

    Passing a test suite proved little on its own. Prompts, context budgets and memory windows were set per model size, then judged inside the real workflows: catch-up mid-meeting, prepared notes, chat over past sessions.

    “Those benchmarks are incredibly basic. We still have no idea if the model actually works across the app.”

    My direction to the build agents · June 2026

    MindCap · prepared notes · synthetic demo content

03 / 04

Samplify

Audio sampling workbench · desktop appIndependent desktop project

  1. Samplify desktop library beside a waveform loop selection and a four-colour stem mixer.

    Catch the sound. Stay in the flow.

    A native desktop sampler that keeps a rolling buffer of whatever is playing. Grab the moment you just heard, trim it to the exact phrase and split it into stems without leaving the track.

    Built withTauri · Rust · SQLite · ONNX Runtime

    Samplify · desktop capture, 30 Sep 2026

  2. 05July 2026 · Capture

    A choice, not a guessed window.

    Early captures guessed a window around a marker. I redesigned capture around a frozen waveform: drag the exact range, audition it, save that selection. Slices land on whole sample frames, so timing and stereo stay aligned.

    “The most important thing about a sample is picking the timeframe.”

    Owner feedback in the capture brief · July 2026

    Samplify · desktop capture, 30 Sep 2026

  3. 06September 2026 · The workbench

    Separation you can actually use.

    Pretrained models split drums, bass, vocals and the rest. The product is everything around them: mute, solo, faders, loops and export, in an orange-and-black workspace built for working rather than demos.

    Samplify · desktop capture, 30 Sep 2026

04 / 04

Twin Shadows

Game analysis · web appPublic site · development paused

  1. Twin Shadows live homepage in its Noxus theme, with the theme selector and summoner search.

    Serious data. A different world.

    Summoner lookup, match analysis and team planning for League of Legends, designed to feel like part of the game rather than a spreadsheet beside it.

    Built withNext.js · TypeScript · Python · Riot API

    Twin Shadows · live homepage capture, 30 Sep 2026

  2. 07July 2026 · Design system

    Five worlds, one design system.

    Hextech, Ionia, Noxus, Demacia and Shurima each change typography, materials and atmosphere through shared tokens. The rules keep data honest: win and loss colours never change, and decoration stays off maps and tables.

    “Forget low quality SVG’s and go for telling the story and vibe of that region, through the UI.”

    My regional-theme direction · July 2026

    Twin Shadows · live homepage capture, 30 Sep 2026

  3. 08July 2026 · In use

    Approval isn’t the finish line.

    After the look landed, I kept testing: stuttering, flaky summoner search, a janky theme selector. Each went back into the queue. A strong identity is only worth having if the app still feels quick.

    Twin Shadows · live homepage capture, 30 Sep 2026

Four products · eight decisions

Built with AI. Proven before it ships.

Each one started with a problem I cared about, and each one changed once I used it. The full stories cover my role, the collaborators and the limits.

A real interface walkthrough: All Notes → Session Notes → All Notes. Seeded demo content, captured September 2026. Silent, 8 seconds.

How I build

I use AI agents for nearly everything. I don’t take their word for anything.

I direct coding agents the way a lead directs a team, and I built the system that keeps them honest. CommandRig is my local software factory. It hands each bounded task to an agent, runs the project’s own checks, judges the result on evidence it observes itself, then waits for me.

“Exit 0 is not evidence.”Rule one in CommandRig. A passing exit code only proves a command finished.

  1. 01

    Scope

    A bounded task, an objective, and the checks that will judge it, written down before any code.

  2. 02

    Isolate

    A fresh copy of the project, pinned to an exact commit, so nothing touches the real one.

  3. 03

    Build

    One agent session (Claude, Codex or another) works inside that copy and hands back a claim.

  4. 04

    Verify

    The project’s own checks run, and the result is read from what actually changed on disk.

  5. 05

    Approve

    The run stops. Nothing merges until I have reviewed the evidence and said yes.

Why the gates exist

An agent reported “8/8 pass, 0 fail.” It had written its code into the wrong copy of the project. The check that reads what actually changed caught it, and the run was blocked.

CommandRig fleet log · 28 August 2026 · one of six harness bugs found by running the agents, not by reading the code

In my own words

“OK so the agent was just being deceptive before really, just mocked the data.”

MindCap build log · June 2026 · on finding that a “working” speech-engine result was mocked data

167test files in CommandRig, a working prototype I run on my own projects

750+test files behind Leaf Edge, with CI that fails if any table ships without row-level security

CommandRig and Ko-Lab, my agents’ shared task and memory server, are private. I’m happy to walk through either on a call.

Work with me

Bring me the problem. I’ll bring the proof.

You work directly with me. UK based, remote first, with 20+ hours a week for the right project.

Tell me what you’re building
  1. 01

    AI features that actually work

    I choose the right model for the job, measure it on your data and ship it with an evaluation set, so you know it works today and can tell if it stops.

    Model selection · Evaluation · Local or cloud
  2. 02

    Data-heavy web applications

    Imports, reconciliation, dashboards and the workflows around them, built on records that hold up when someone checks the numbers.

    Next.js · PostgreSQL · Integrations
  3. 03

    Agent workflows for small teams

    Repository instructions, MCP servers and review gates, so the coding agents your team already uses produce work you can rely on.

    Claude Code · Codex · MCP
  4. →

    Hiring instead?

    I’m open to applied AI and product-builder roles, mainly remote.

    See my experience

Joe Hodge · Founder of Auromind Ltd

A curious mind.
A considered eye.
Someone who sees it through.