Dispatch 174
Week ↗

Stripe, dashboards, and Colonel

Saturday arrived and I decided to spend it building. Two repos, two commits, and both were heavy lifts. In loopnet-leads I shipped Stripe billing, an admin dashboard, CDV cache, and a UI overhaul. That one c…

Commits
2
Systems
2
Read
2min
Product capture

Ops-Center — user dashboard.

Saturday arrived and I decided to spend it building. Two repos, two commits, and both were heavy lifts.

In loopnet-leads I shipped Stripe billing, an admin dashboard, CDV cache, and a UI overhaul. That one commit touched 47 files with 5,328 lines added and 380 removed. It was the real work of the day. I needed billing in because the product was leaking through the cracks, and admin controls to actually manage it. The CDV cache was a performance fix that had been nagging me for weeks, and the UI overhaul was mostly cleaning up years of accumulated slop. The migrations tell the story: billing credits columns, company enrichment tracking, an admin flag, a Stripe subscription ID field. Each one was a small piece of a bigger puzzle.

The Stripe integration itself was straightforward in theory. Charge people when they run out of credits, show them a usage page, give admins the ability to adjust things manually when someone complains. The billing API, the admin endpoints, the migration for the subscription ID column, all of it came together in that one commit. It felt good to ship something that actually closes a revenue loop instead of just adding features into the void.

In loopnet-leads I shipped Stripe billing, an admin dashboard, CDV cache, and a UI overhaul.

On the ops-center side I pulled a different kind of lever. Colonel AI got a chat bubble, the multi-GPU dashboard got attention, and I cleaned up code that had been needing tidying for a while. That commit was 18,802 lines added, 11,961 removed across 134 files. That is not a small cleanup. The Colonel memory layer got rewritten with both Kuzu and Mem0 clients sitting side by side, the A2A server got updates, the auth dependencies were refactored, and the billing analytics API came in. The .gitignore and CLAUDE.md updates were the quiet kind of work that prevents future headaches.

The multi-GPU dashboard work was mostly about making the monitoring interface actually usable. When you are running multiple GPUs you need to see what is happening without logging into three different consoles. The dashboard should tell you everything at a glance.

Eighteen thousand lines is a lot of churn for a Saturday. Some of it was new features, some of it was removing code that had served its purpose and was just in the way. The ratio leaned toward adding, but the deleted lines were the interesting ones, because they represented decisions I no longer needed to maintain.

Two repos. Two commits. One productive Saturday.

Also in the frame

Real product captures — click any to enlarge.

ops center
listing ops
listing ops