I'm a problem solver who works at the cutting edge, which right now means building software with AI as my collaborator. I co-founded TeamWeaver and I run DHU Labs, a one-person software lab. In under two years I've shipped more than forty working projects. Before that I was a full-time parent for nineteen years, and before that I spent a decade shipping hardware and software where music, computers, and people meet.
The longer story
Music got here first. My dad was a postal carrier whose day started early, and on the long drives with him the radio played synth pop, early reggae, and dancehall. I bought my first record at eleven, learned to DJ on belt-drive turntables and then Technics, and by my teens I was playing parties. What I always wanted to know was where this music came from and how it was made. Chasing that led me through synthesizers into computers, and when the computers of the day were too weak for serious music work I built my own, dual-processor machines running BeOS, partly for the power and partly because BeOS ran Final Scratch, the first system that let you DJ digital files from real turntables. I beta tested early digital vinyl for Stanton, and I believed in Be enough to invest what little money I'd saved and lose all of it. It wouldn't be the last time I was early.
Work started at twelve, stacking stone pallets in the summers at my stepfather's quarry, the one that supplied the stone for Cornell's early buildings. At seventeen I put my board in my car and drove to Mount Hood, met people on my first day who took me in for the summer, and came home sponsored by Never Summer after their industry friends photographed me riding and sent the pictures in. The plan was to go professional. I taught snowboarding at my local resort, got certified, took an instructor job at a new resort in Park City, and an injury from the summer before got worse on the mountain until it sent me home for good. Home meant getting serious about a software degree at the local two-year college, where I learned something more useful than the degree: I love the high-level thinking about what software should be and do, and I have no love for writing it line by line.
My final-semester internship was at Glyph Technologies, a company I already knew because their storage powered the samplers I made music with, and I could hardly believe they were in my town. They put me on a new venture called NetDrives, where I helped build, test, and ship one of the first standalone consumer MP3 players, a box that played MP3 CDs on your home stereo, and part of the job was explaining to people what an MP3 even was. I tested thin-client systems at Neoware through the dot-com years, moved home to Ithaca, and came back to Glyph as an engineer, where we built the GPM-216, a peer-to-peer personal monitor mixer; I helped build the first hundred units and we debuted it at AES in 2005.
When our first kid was born, my wife and I planned to split the parenting, saw quickly that it wasn't possible, and I volunteered. I was the full-time parent for nineteen years: the cooking, the cleaning, the errands, and eventually the homeschooling, which I did until my kids were ready for regular school. It was more work than any job I've had. The whole time, the tinkering never stopped: workstations, music production, and, the moment it started to matter, AI.
Then AI collapsed the distance between thinking of something and building it. The way back was TeamWeaver, the company I co-founded to measure how teams actually collaborate, and the build that proved I could still ship. Since then I've made more than forty working projects: a revenue-intelligence tool that turns a sales team's emailed updates into deal records, a personal medical AI that runs locally so health data never leaves the house, a security scanner, a field-coverage app for enterprise field officers, an audio platform aimed at an AI-native DAW. Most of the forty are private or built for someone else's business, so you can't browse them all; the ones you can try are below, and I'm glad to talk through the rest. Claude does the implementation, and I do what I've always been better at: deciding what's worth building, holding the scope, and judging whether the thing actually works. The kid asking how the music was made turned out to be in training for this. I direct the making now, and the tools finally match the altitude I've always thought at.
What I'm working on
TeamWeaver is the real company here, the one that pulled me back into software. It measures how teams actually collaborate, and its free tool, The Meeting Read, reads any meeting transcript you paste and hands back an honest picture of how that meeting went, right in your browser, without your transcript ever leaving your machine.
DHU Labs is my software lab. Businesses bring me something slow, manual, or confusing, and I tell them honestly whether software would help, including when the answer is no. When it would, I build it while they watch it take shape.
HAP-OS is the project I care most about and the direction everything else points: an operating system for humans and AI working as real pairs, using whatever computing you own, local or cloud. It isn't public yet. It's where I think work is going.
Things you can try
The Meeting Read is free, no signup. AgentProof scores how replaceable a business is by AI agents; AI Readiness scores a company's AI maturity in twenty questions. And DHU Chat is a chat assistant that reasons from a written set of first principles instead of just generating agreeable answers; conversations with it have genuinely changed my mind on hard topics, and in side-by-side tests it consistently beats the same model running plain. All three are live and invite-only, so ask me for access.
Get in touch
If you're building something, deciding whether to build something, or want to know whether I can help with a problem, email me. I answer.