Applied AI & automation
Leverage, not theater.
Multi-agent systems and private + cloud models doing real operational work. If it can’t survive contact with an actual workday, it doesn’t ship. No demos that fall apart the second a human touches them.
A short history of fixing things.
1996
The origin
It started with a Packard Bell and a modem I had to beg for.
A 486 with four megs of RAM, a copy of Windows I, ahem, acquired, and a dial-up connection that felt like a superpower. I taught it — and myself — everything: BBSes, early software liberation, and a Connect Four game I wrote on a graphing calculator because I was bored in class. I've been the kid who takes the thing apart to build a better one ever since.
Packard Bell · 486DX2-66 · 4MB RAM
Late 90s
The efficiency habit
They hired me for data entry. I automated my own job.
A stainless-steel shop put me behind a desk. I watched people re-typing the same numbers off copies of copies, so I built the thing that did it for them — spreadsheets that did the math, an inventory system the whole floor could use, mistakes down to almost none. Then I went out to the shop, learned to weld, and taught the CNC laser to cut what the software drew. Turns out “lazy” and “efficient” are the same person viewed from different angles.
VBA · Access · a union card · a welding hood
Before 21
The creative detour
A crime scene you controlled with buttons and relays.
Somewhere in there I picked up the Adobe suite, early 3D, and a gig wiring the tech for a New York museum — an interactive crime scene run by physical buttons and AV relays that lit up the evidence on cue. Trade-show booths modeled in 3D. My first corporate networks. All self-taught, all before I could legally rent a car.
Macromedia Shockwave · AV relays · command-line AutoCAD
2001
The company
Infinite Media Corp — still running, somehow.
I partnered up, took over the technology, and started the managed-IT side. Classic ASP became PHP became Python became Node — I'm not loyal to a language, I'm loyal to the result. Twenty-plus years later the company's still here and so am I, which in this business counts as a magic trick.
Est. 2001 · web + managed IT
Now
The present tense
I don't “use AI.” I run it like staff.
I orchestrate fleets of AI agents that do real operational work — monitoring, support, catalogs, ops — across cloud models and private ones running on my own hardware, because some data shouldn’t leave the building. I also run technology for Hirschfeld Properties. They put “CTO” on the card, which is generous of them.
Multi-agent orchestration · cloud + private models
The build
The current obsession
The Panel: one screen to run an entire IT shop.
The usual MSP runs on a pile of separate tools stitched together with spreadsheets and hope. The Panel collapses that pile into a single pane of glass — remote management, inventory, tickets, the works — built multi-tenant from the first line of code so it can grow from my shop into a product other shops run their businesses on. Remote management has been live in production since June. The rest is the fun part.
MSP platform · multi-tenant · RMM live since 2026-06-16
Next
What comes next
Never retiring. Just getting pickier.
The plan was never to stop — it’s to only build things worth building. Turn the Panel into something other MSPs run on. Trade notes with the people who actually do this work. Give some of it away as open source. Find the friction, build the machine, repeat until they pry the keyboard out of my hands.
SaaS · open source · the long game