Maker. Inventor. Entrepreneur.
I build products, software, and strange little machines.█
Most of my time is spent designing consumer products, writing the software to make them, automating the workflows that produce them, and then moving on to the next thing before anyone notices. I work across hardware, software, manufacturing, and whatever weird idea showed up this week.
// what I build
Energy supplements, functional beverages, experimental food products. I handle everything from formulation to packaging to DTC distribution — then build the tooling to make it repeatable.
Internal manufacturing systems, SaaS products, automation pipelines, developer utilities. If there's a workflow that's annoying to do manually, I've probably already automated it — or built a product around fixing it.
Microcontrollers, embedded systems, retrofitted lab equipment, workshop contraptions. Some of it ships. Some of it just ends up on a shelf looking interesting. All of it teaches me something.
Experimental apps, odd tools, creative engineering experiments. These usually start as "what if..." and end up teaching me the most. Not everything needs a business model to be worth building.
// selected projects
Real things, not hypothetical ones.
Designed the formulation, sourced manufacturing, built the DTC brand, wrote the fulfillment backend, designed the marketing site, and handled the entire supply chain. End to end — one person.
Built internal software to track production runs, QA checkpoints, ingredient lots, and output inventory for a physical products operation. Replaced a pile of spreadsheets with something that actually works.
Route optimization, driver dispatch, and delivery confirmation tooling for a local delivery operation. Built fast, iterated in production, survived real-world conditions.
Retrofitted lab equipment and built custom firmware to automate a small-batch packaging workflow. Microcontrollers, sensors, and a healthy disregard for "just do it manually."
Various small SaaS tools and developer utilities — some launched, some never left localhost, all interesting. The failed ones usually taught more than the successful ones.
// how I think about building
Reading about a problem is fine. Building a broken first version is better. The feedback loop of making real things is the fastest path to understanding anything.
Perfect is the enemy of interesting. Get something real in front of real conditions as fast as possible. You'll learn more in week one of shipping than in months of planning.
If I've done something manually twice, I'm already thinking about how to automate it the third time. Systems compound. Manual work just accumulates.
Every domain I've worked in was once unfamiliar. Electronics, formulation chemistry, supply chains, firmware — none of it was something I "already knew." Curiosity and persistence close the gap.
// now
Right now I'm building tools, experimenting with products, and trying to make interesting things faster than I did yesterday. The specifics change week to week — that's kind of the point.
~/projects
// contact
If you're building something interesting, have a weird idea, or want to collaborate on something that doesn't fit neatly into a job description — reach out.