The Operator Engagement

The work of keeping an agentic system aligned with how your business actually operates. Monthly, ongoing, ends when you say so.

The Engagement is what happens after the Build. Pricing starts at $1,000/month and is scoped to the system you have and the attention it needs.

Why this phase exists

Agentic systems are not products. They're operating layers — small specialist teams that perform real work in real time, against standards that have to keep matching how your business actually runs.

Operating layers drift. The business evolves. New cases appear that the agents haven't seen. The standards you set in the Build start to be wrong six months later for reasons that are obvious in retrospect and invisible in the moment. The knowledge base needs the kind of disciplined updating that no operator does well in their spare time. Without someone watching this, the system slowly stops being the system you paid for.

The Engagement is the work of watching. Not babysitting — watching. The methodology has a name for it: the Reconciliation Pass. It's the discipline that keeps the knowledge base and the agents' actual behavior in alignment as the business changes. It's the work that makes the difference between an agentic system that compounds in value over a year and one that quietly decays into something nobody trusts.

What the Engagement includes

One Reconciliation Pass per month, scheduled. The discipline at the center of the methodology — the work that keeps the knowledge base honest, the agents' outputs aligned with current standards, and the system improving instead of drifting.

One monthly review call. A working session with you or your designated operator. What's working, what's surfacing, what needs to change. This is where you tell us what you've noticed and we tell you what the system is doing under the hood.

A defined response window for the things that come up between scheduled work. Two hours per month of unscheduled time, 24-hour response on a normal week. Edge cases get integrated as they appear, not after they pile up.

Annual review of scope and price. The Engagement isn't fixed. Once a year we look honestly at what the system actually needs and adjust — sometimes up, sometimes down — against real usage.

What's not included

Major architecture changes. Adding a second bottleneck domain, building net-new agents, migrating the system to different infrastructure — these are separate engagements with their own scope and pricing. The Engagement maintains and evolves what the Build delivered; it doesn't quietly absorb the next Build.

This distinction matters. Retainer relationships in this category usually rot for one of two reasons: the scope creeps until the operator can't deliver against it, or the operator gets defensive about what's "included" and the client stops asking for what they actually need. Naming what's outside the Engagement up front protects both sides from that drift.

What changes over a year

The system that runs your operation in Month 12 is not the same system that ran it in Month 1. The agents are sharper because the knowledge base is denser. The edge cases that surprised everyone in the first quarter are now handled routinely. The standards have been adjusted in the places where they needed adjusting and held in the places where they didn't.

You also change. By Month 12 you've operated an agentic system for a year. You understand what these things are, what they need, and what to ask for. The Engagement is partly the operator keeping the system aligned, and partly the operator helping you become someone who can think about agentic systems clearly — because eventually you may want to keep doing this yourself, or hire someone to do it inside your business, and the only way to get there is to spend time near the work.

Pricing and commitment

Engagements start at $1,000/month and are scoped to the system you have and the attention it actually needs. Final pricing is set after the Build, when there's a real system to scope against.

The Engagement is month-to-month. No annual contract, no cancellation penalty, no automatic escalation. You can end it whenever the work no longer serves you, and the system stays yours either way — the Build is what you own, and the Engagement is what you choose to keep paying for around it.