About
I've always been more interested in how things actually work.
Not the theory of a business — the shift change, the invoice, the line at the door, the spreadsheet nobody wants to open. Most of what I build started as a problem I had to solve on a Friday night.
Where it started
I started around food and people. Long days, small margins, and the constant question of where the money went.
That environment teaches you to pay attention to detail, because detail is the entire difference between a good month and a bad one.
Restaurants
Working in and around restaurants showed me that most operational problems are not complicated — they're just unmeasured.
Costs, portions, scheduling, prep, guest experience: each one is a habit before it is a number. I write about how those habits show up in the P&L.
Events
Events compress everything. A month of planning turns into six hours where nothing can be rescheduled.
Running them taught me about logistics, promotion, ticketing and the fact that guest experience is mostly about waiting time.
Building software
I build products for the businesses I know. That means fewer fields, faster screens and tools that work on a phone in a loud room.
Some of it is software people pay for. A lot of it is free tools that solve one specific problem well.
What I'm working on now
Tools for restaurant costing and performance, event and ticketing software, books, and writing about what I learn while building.
If any of that is useful to you, the newsletter is the best place to follow along.
Stay in the loop.
Practical insights on restaurants, events, software, and the things I'm building.