Engineering leader · Product builder · Dallas, TX
I ran a fulfillment platform moving ~25,000 shipments a day. Now I build products, running the engineering as a managed system of agents.
Fifteen years in fulfillment technology, from the finance side of 3PL warehouses to directing the OMS/WMS platform at Cart.com, where the engineering org doubled its throughput on flat headcount. Still hands-on: a builder who stays in the code.
What I'm building
01 · Early preview · v1.0.5 for Apple silicon Macs
Every Claude Code session, one calm board.
A Mac app that runs many Claude Code sessions in terminals it owns, across one account or several, and puts whichever one is waiting on you at the top.
02 · Internal preview · not taking orders
Paste your website. See your team's polo.
Reads a company's website (its logo, brand colors and line of work) and draws three original all-over-print polo patterns on a photoreal shirt.
Track record
Cart.com · 2021–2026
Director, Technical Product Operations
331 → 680 tickets per quarter
Doubled peer-reviewed engineering throughput on flat headcount by rolling out AI-assisted engineering org-wide, after proving it on my own tickets first.
Read the case studySnowfall Technologies · 2017–2021
Development / Product Manager
0 → 14 clients in 24 months
Took a new 3PL fulfillment platform from zero clients to a proven operation, then through its acquisition by Cart.com.
Read the case studyHow I work
A written contract with numbered acceptance checks, and a retry budget: two failed verifications and the loop stops and comes to me.
A separate, read-only verifier checks the work against the contract before it counts as done.
Graphs, contracts and worklogs in the repo, so any session can pick the work up cold.
The frontier model plans and reasons; execution and verification go to cheaper models unless quality depends on it.
Reversible internal work just proceeds. Anything that leaves the building, such as messages, money or production data, waits for approval.
