Twenty years running businesses. Then I learned to build the software they run on.
Most people who build software have never had to run the thing it's for. I did that first — two decades on the operations side, where the rush is the test and a broken system costs you the night. Then I went and learned to build the systems myself, end to end.
It started with the physical: kitchens, floors, hardware, the stuff that has to work when it's busy. That teaches you what software forgets — that a tool nobody has time to fight with is the only tool that survives a Friday night.
From there it went deep and technical: a real-time trading platform that put nine figures of notional volume through three perpetuals exchanges, an exchange SDK written from scratch, automation that ran production without babysitting, and a team-lead seat on the launch of agent-to-agent commerce at a two-billion-dollar protocol. Different industries, same lesson every time — the software is never the point. The business the software serves is the point.
So I don't sell you a website, or a piece of software, or a screen on the wall. I look at how your business actually runs and build the connected system underneath it — then I'm the person you call when something breaks.
- Real-time financial systems
- Numbers that update the instant they change — so a dashboard tells you the truth right now, not last month.
- Custom trading terminals
- Fast tools built for people under pressure. Your staff shouldn't wait on software mid-rush either.
- SDK-level integrations
- I connect systems at the deepest layer they allow — your POS, your scheduling, your site, talking to each other.
- Production automation
- Work that runs itself once it's set up — fewer manual steps, fewer things to forget, fewer late nights.
- Autonomous agent systems
- Software that finds work, does it, and gets paid without a person watching — the same discipline behind automation that runs a back office.
Range isn't a scattered résumé — it's the reason the pieces fit together. One person who has run the floor and written the code sees the whole system, not just their corner of it.