About · how I work
Operating cadence first, AI inside it.
Lede
I run implementation in regulated fintech. AI configured inside the operating cadence, not bolted on top. The interesting work sits between what AI compresses and what compliance keeps manual.
How I work
My work follows a small pipeline: scope, architect, configure, run, compound. The goal is that each implementation leaves the operating backbone in better shape than it found it. Regulated-ops judgment first, AI fluency inside the cadence, segmented rollouts over big-bang releases.
/scope /architect /configure /run /compound
Where I am
Greater Indianapolis, Indiana. Remote by choice: the work travels, and this is home.
Always open
- Claude, for the first-draft conversations my notebook used to hold.
- Claude Code, for the work no spreadsheet can compress.
- Smartsheet, the operations backbone, five workspaces deep.
- Firecrawl MCP, schema-first instead of manual sweep.
- Descript, for the video version of the writing.