Last week the strip read 446 fleet hours and I called that the real baseline. This week it came in at 433, against 43 hours of mine, almost exactly even with week one. Call it ten to one, and that’s the shape of the thing: the fleet’s hours swing with what’s in flight, mine hold roughly flat. What the fleet did with its 433 is easy to summarize. Breeze grew the entire money side of a business in a week.
What shipped
Breeze. The big push this week was billing, and not a feature, a spine. Quotes and proposals went from nothing to a full path in seven days: schema, RBAC, and a block editor (Phase 1), then send, a public portal view, and e-sign accept that converts to an order (Phases 2 to 3), then expiry and accept-to-pay through Stripe (Phase 4), then accepted quotes auto-creating draft contracts. Alongside it, the Invoices redesign with a Stripe pay-link and PDF, a Product Catalog with per-org pricing and bundles, and a Contracts redesign with live estimates, auto-renew, and renewal notices. The plumbing under it got the careful version: dedicated billing roles and permission-aware UI, and a move off Stripe Connect to a per-partner Stripe API-key model, which is the kind of decision that’s a pain to reverse, so we made it before there were invoices to break. Ticketing kept moving too (email-to- ticket customer routing in Phase 5, comment and field editing in Phase 6a), the remote-desktop viewer got a redesigned toolbar plus end-user consent and notification before a session starts, and SSO got a domain-verification and admin-gating hardening pass. Four releases went out in the open: v0.80.0 on the 15th through v0.82.1 on the 21st, all on GitHub, each reviewed at the gate.
Hive. The engine spent the week learning to run live agents without me editing a file. Until now a live agent meant config in code; this week it became a row in a table and a panel in the dashboard: a LiveAgentStore with CRUD, a daemon that loads its agents from the database and writes their status back, and a read-only Live Agents panel to watch them. Underneath, a CredentialProvider that resolves each agent’s secrets per run, with a TTL cache and fail-soft behavior, so a live agent gets exactly the credentials it needs when it runs and not before. The point, again: the work that builds the fleet, not just the work the fleet does.
Delegant. Quiet on code, deliberate on direction. One thing landed: the design spec for a Clio MCP, the governed door into a law firm’s practice-management system, plus an offering comparison. It’s a spec, not a shipment, and it’s named here as a spec. It’s also the bridge between the Clio field note that went up this week and a real surface behind it.
Pressless. Steady infrastructure. Project duplication shipped, demo-site bundle restore on deploy so a fresh environment comes up with something real in it, an admin billing-and-subscription view on the user profile, and a fix that stops a design re-import from clobbering a user’s own edits. The boring-and-right column.
LanternOps. This was the week the brand started teaching in public. The Field Notes series went live at /field-notes: two operating-model essays spun out of real solution work, one on running AI search over a firm’s file shares without leaking the folders it shouldn’t see, one on putting AI on a Clio practice. The lead-magnet funnel also got its back half wired: an email platform behind all five site forms, with nurture sequences drafted for the two gated pieces. Teaching first, capture second.
OliveTech. Workflow level, as always. No client names, no client data. The same triage stack keeps running behind the same review gate.
One miss
This one I should have caught at the start. I looked at our own brand with fresh eyes this week and realized it isn’t ours. Not just the website, the whole identity. The midnight palette, the amber signal, the clean grid. It’s the fleet’s default taste, what the model reaches for whenever you ask it to make something look premium. The amber was the tell. I’d told myself it was deliberate, the lantern’s light, chosen on purpose. It wasn’t. It’s the model’s favorite color on a dark page, and I backfilled the lantern story onto it after the fact.
That’s the exact failure I sell against. The value was never what the AI produces. It’s the operator catching what the AI does on autopilot, especially the parts that flatter you by looking intentional. A default that dresses itself up as a decision is the hardest kind to see, because it shows up already wearing your reasoning.
The fix isn’t a repaint this week. It’s to treat the brand like any other thing the fleet hands me: assume the first version is the model’s reflex, not a choice, until I’ve made it one on purpose.
What’s queued
Billing graduates from a path to a practice: invoices that send, get paid, and reconcile, not just render. The live-agent system gets its first agent configured entirely from the dashboard, no code, which is the test of whether the week’s work holds. And the Field Notes earn their keep, a LinkedIn series pointing back at them, so the teaching reaches the people it was written for.
If you’re doing the math on what one person and a fleet can hold, there’s a door.