LanternOpsThe Operator's LogManaged AI Teams
LanternOps Book a diagnosis →
§0 The Operator's Log

One operator. Five ventures. A fleet that does the work.

I run a services firm and four software ventures with managed AI teams, all of it orchestrated by an engine I built. This is the weekly record of what the fleet ships, what it costs, and what I had to fix. Real numbers, real artifacts, misses included.

— Todd Hebebrand

15.3×
Leverage
430
Fleet hours
28
Operator hours
102
Shipped

Latest entry · 2026-W28. How these are counted →

The operation 6 ventures · 1 engine
  • OliveTech The managed-services firm. Running other people's systems since 2007; the discipline everything else inherits.
  • LanternOps Managed AI teams for professional firms. The shop you're standing in.
  • Breeze Open-source, AI-native RMM for MSPs and IT teams.
  • Pressless Describe your website, AI builds it. WordPress migration is the wedge.
  • Delegant Identity and governance for AI agents in Microsoft 365.
  • Hive The engine, not a product. Persistent agent colonies that run the rest: fleet-monitor, alert-router, email-triage, code-reviewer.

One entry a week, every week. Nothing else.

RSS
  1. Entry 006 Week five: the ceiling moved The week ending July 12. The fleet worked 430 hours against 28 of mine, the widest gap yet, and the reason is a security review that ran itself. Breeze closed a twelve-finding OAuth audit, hardened the agent trust boundary, and started speaking four new languages.

    15.3×·102 shipped·2026-W28

    Jul 13, 2026 →
  2. Entry 005 Week four: one policy, every org The week ending July 5. Breeze stopped treating an MSP as a pile of separate customers and let one policy own the whole book of business. The money side grew deposits and scheduled reports, and Hive turned the lights on in its own house.

    9.8×·141 shipped·2026-W27

    Jul 6, 2026 →
  3. Entry 004 Week three: hardening the house The week ending June 28. After building the money side, Breeze spent the week locking the doors: a security and authorization sweep, vulnerability management, EDR, and a framework upgrade under the whole thing. And the brand I called out last week as the model's default finally became a choice.

    9.6×·201 shipped·2026-W26

    Jun 29, 2026 →
  4. Entry 003 Week two: Breeze learns to get paid The week ending June 21. Breeze grew the whole money side of a business in seven days, quotes, invoices, contracts, and a catalog, while the engine taught itself to run live agents from a dashboard and LanternOps started teaching in public.

    10.1×·189 shipped·2026-W25

    Jun 22, 2026 →
  5. Entry 002 Week one: the engine keeps the books The first full week the fleet counted itself, June 8 to 14. A heavy one: Breeze shipped v0.70.0 with native ticketing, privileged access, and an in-Excel client assistant, while the engine grew two new triage colonies of its own.

    10.5×·108 shipped·2026-W24

    Jun 15, 2026 →
  6. Entry 001 What the fleet already built The record starts here. Before week one of the log: a brand built in two days, an open-source RMM with 1,300+ commits, three more products in flight, and the engine that runs it all. Reconstructed numbers, honestly marked.

    3.7×·82 shipped·2026-W24reconstructed

    Jun 9, 2026 →

A few firms a year get this done to their operation. Here's the door →