Insights2 min read
An AI operator is not an assistant
An assistant drafts; a human sends. An operator owns the outcome and escalates when it must. The difference decides whether AI removes work or adds a review step.
Cliff des Ligneris
Most AI products in business software are assistants. You ask, they draft, you check, you send. The pitch is speed. The reality is a new review step on top of the old job. The job did not go away. It got a helper that needs supervision.
Even is built on a different idea. It is an operator. It owns the booking system of a movement studio (yoga, pilates, martial arts, dance, fitness). It does not suggest a reschedule; it reschedules, within the rules the owner set, and it tells the owner afterwards. When something falls outside those rules, it stops and asks. That is the whole distinction: an assistant waits for permission every time. An operator holds standing permission for a defined scope and escalates at the edge.
Three things follow from this, and they are harder than they sound.
Scope has to be explicit. An operator needs a written boundary: what it may do alone, what needs a human, what it must never do. Writing this down is uncomfortable, because it forces the owner to admit which decisions were never rules in the first place. That discomfort is the work. Without it you do not have an operator; you have an assistant with a long leash.
Behaviour has to be tested, not hoped for. We run Even’s decisions against evals: concrete situations with the answer we expect. A change that moves an eval the wrong way does not ship. Assistants get away without this because a human reads every output. Operators do not get that cover.
Escalation is a feature, not a failure. The measure of a good operator is not that it never asks. It is that it asks about the right things, with the context attached, and never twice about the same thing once the owner has answered.
Why does the distinction matter for a COO? Because assistants produce a productivity story and operators produce a headcount story. One saves minutes across many people. The other removes a job from someone’s week. They need different pilots, different metrics and different conversations with the team.
If a vendor says operator and demos an assistant, ask who clicks send.