Writing
Notes on operations, demand, and the systems underneath.
-
The tools weren't the problem. The speed was.
Whiteboards, spreadsheets, and purpose-built scheduling platforms all failed for the same reason: operational reality changes faster than anyone can stop and record it. What it took to build something that keeps up.
-
I fixed a production bug by voice at a gas station
A scheduling bug in a live rafting operation, diagnosed and fixed by voice from a phone while pumping gas. What that changes about running a business, not just about writing software.
-
Teaching software how a river behaves
Guests finish a trip dozens of miles from cell service. Getting a driver to the takeout at the right moment used to be a judgment call built on years of observation. Encoding that judgment into an automation turned out to be the hard part, and the automation the easy part.
-
We stopped hiring for experience and started hiring for trajectory
In a high-turnover seasonal industry, the default is to hire for relevant experience and certifications. That doesn't solve operational consistency. Asking a different question at the door did.
-
From about 30 to about 1,800 AI search appearances a month
A 60x increase in how often a business appeared in AI-generated answers, with no additional ad spend. The lever wasn't more content or better reviews. It was making the underlying operation legible to systems that summarize rather than link.