How thirteen things stay runnable by one person

I build the thing that removes me from the repetitive part.

Thirteen ventures is not thirteen businesses I juggle. It is one instinct applied thirteen times: find the work I keep redoing, collapse it into one system, then let that system serve everything downstream.

Touch a shared system to see what it feeds
Layer 1The operator
GX
Grux
A Mac agent that orchestrates Claude swarms, meters its own cost, guards its own URLs, and runs the rest of the portfolio so I do not have to hold it all in my head.
Swift and SwiftUIAgent swarmsCost meteringHallucination tests
drives
Layer 2Shared systems, built once, reused everywhere
serves
Layer 3Thirteen ventures, ten live right now
AI Anyone
AI characters
The Binaural
iOS audio
BoardSnap
iOS vision
Motor City Organics
DTC body care
Thudletter
3D print gifts
PocketCurio
3D print keepsakes
djbnb
DJ marketplace
MUTDemon
Madden AI
Arc Raiders AI
Quest tracker
Grux
The operator
Holdable
In build
AI NPC Engine
In build

The build record.

Ten live right now, two in build. Every one went from the first line of code to real users without a team. The AI products run on frontier model APIs, agentic workflows, and evals in production, not in a demo.

Tools & Games1 live

Focused products with devoted users, audio, marketplaces, game companions.

The Vaultstill online

Shipped, still running, not where today's hours go.

Brands I built and still keep on the internet. I am not adding features to these. They stay up because they work.

Deep V is the exception, shut down and no longer online. Listed anyway, because the work happened.

LIVEΒ· auto-updated from my machine

Shipping cadence.

Every square is a day I put code into one of these products, auto-scanned from my machine twice a day.

Loading…
How I work

What I am like on a team of one, and on a team.

I bring order to ambiguity.

No playbook, no team, no clean brief. I build the structure as I go, and I would rather ship one thing that serves ten customers than ten things that serve one each.

I close the loop myself.

End to end ownership from the first conversation to the thing running in production. Nothing sits waiting on a handoff that never comes.

I am cheap to correct.

When I am wrong I say so early, out loud, and move. Nearly three years of my own working sessions are on the record for anyone who wants to check that.

Prototype to production

The demo is the easy part.

Anyone can get a model to do something impressive once. The work is everything after: the evals, the cost per call, the latency budget, the failure mode nobody planned for, the thing that has to keep working on a Tuesday when nobody is watching. I have walked that whole distance on my own products. It is why I can tell a customer the truth about what comes next.

Many
ventures live
Real
users reached
Daily
ships to prod
1
founder
ship.sh
$ git commit -m "ship it"
[main] feat: new venture live
$ ship --prod
βœ“ build passed
βœ“ prod live in 42s
$ β–‹
Detroit Β· inbox open

My inbox is open.

Building something and want to compare notes, partner up, or just connect? This is the fastest way to reach me. Same address if you are only looking through the portfolio and something caught your eye. I read and answer everything myself.

Email me β†’jack@dotcomjack.com