Field Notes · The Stack Series

The operations team in a box

By Will Hess · Founder, Inside Intelligence

This is the capstone of our series on the stack we run Inside Intelligence on. We've walked through each piece — the books, the tickets, the wiki, the vault. Now let's put it together and show you what it actually is: an operations team in a box.

The pieces, and what each one does

Each piece is a real system, self-hosted on our private infrastructure, never exposed to the internet. None of it is a slide. All of it is running.

What ties it together: the agent

The pieces alone are just software. What makes it an operations team is the agent that runs them — the same way Operator would run a client's operations.

The agent watches the system. When something's wrong, it opens a ticket, logs the symptoms, works the fix, and closes the ticket with notes. When it makes a change, it updates the wiki. When a service starts, it pulls secrets from the vault. When a lead comes in, it records it. It's not a chatbot that answers questions — it's an operator that does the work.

The whole point

ChatGPT tells you what to do. Operator does it. The stack is the proof: an agent, on your hardware, running the operations of a business — the books, the tickets, the knowledge, the secrets — without your data ever leaving the building.

Why this is the answer for a duty-of-care office

If you run a law, medical, financial, or licensed-trade office, you don't care about any single tool. You care about this: there's a system that runs your operations, keeps your records, documents your knowledge, and protects your secrets — all on your own hardware, all without your data leaving the building.

That's not a product feature. It's a way of running a business. And it's the same way we run ours.

We're not asking you to trust a promise. We're showing you the receipts — every one of them, in this series.


← Back to Field Notes