Writing

Notes on building systems.

How we think about deploying AI across a business and automating the busywork, then building and running the system in production. You own the code and the data.

Case Study8 min

We replaced Wodify with a gym OS we built and run

Persistence Athletics fired its gym software and asked us to build the replacement. Here is the real story: a custom Stripe billing engine that bills everyone on Sunday, 24 branded email flows, a native iOS app on TestFlight, the EDSO programming engine, and an AI coach assistant. The architecture, the decisions, and the bugs we paid for.

May 30, 2026
Build story7 min

Running a 31-screen retail network across four stores

A POS, a 31-device Fire TV signage fleet, and a menu designer for a four-store cannabis retailer, all wired into one system we build and run remotely over ADB and VPN.

May 24, 2026
Build Story6 min

Two apps, one source of truth: building the DRiV PushPress to GoHighLevel sync

A gym owner had two tools that refused to talk to each other. Instead of forcing a third bigger tool on him, we built a small bridge that runs unattended and hands him back about 40 hours a month. Here is how it works.

May 18, 2026
Point of view7 min

The operating system thesis

Most businesses run on a pile of rented apps and a person who re-types data between them. Here's why we build the one system a business runs on instead, and why AI makes that affordable now.

May 12, 2026
How we work6 min

"You own it, we operate it": what that actually means in production

Most builders ship and vanish, and the software starts rotting on day one. We stay and run it. Here is what that looks like in the live systems: uptime we answer for, features every week, and code you can take whenever you want.

May 6, 2026
How we work6 min

How a tiny team ships agency-scale systems in weeks

An agency floor used to be the price of a real operating system. With Claude Code and Codex, a focused team ships the same thing in weeks. Here is the honest workflow.

April 30, 2026