What an AI chief of staff never does

Opitor is an AI-native operating system for small companies, where every person gets their own AI chief of staff. Most writing about a thing like that describes what it can do. This is the other list.

The list matters more than it looks. In a small company the decision to use something like this is not made by a procurement committee over three months. It is made by one person, in an afternoon, on the basis of whether they believe it will behave. What a system refuses to do is the part of that belief you can actually check.

This page covers AI reply drafts, conversation access and the decisions that stay with you.

AI replies stay drafts

AI replies are drafts: you choose whether to send them. A reminder you create for yourself can be scheduled to send automatically by Opitor at its due time; a reminder created by somebody else requires approval. This section describes those paths, not every possible message type.

This is the limit people underrate, because the alternative sounds so convenient. Something that can reply for you saves more time than something that can only suggest a reply. The saving is real. The cost is that you now live in a company where a message from a colleague might not be from that colleague, and there is no way to tell which is which.

That cost falls hardest at exactly this size. In a ten-person company a message from the founder carries weight because it came from the founder, and once people start reading everything with a small question attached — did she write this, or did it write this — you cannot undo it.

In Opitor, AI replies stay drafts you choose to send. Your personal chief of staff helps with messages, todos, deadlines and drafts; you review the wording and decide whether to send the reply.

The second half of the rule points the other way. Everything the chief of staff writes is signed in purple, so when it writes something you can see that it wrote it.

Conversation membership sets access

Administrators cannot read other people’s private messages or groups they have not joined.

The practical consequence is about what people are willing to say. Every company has a set of conversations that are genuinely useful and slightly uncomfortable: this is not working, I think we are wrong about the customer, I am struggling. Those conversations happen somewhere. If they cannot happen in the company’s own tool, they happen in a personal channel that nobody can see, including the people who would benefit from hearing them.

It never replaces the person

A chief of staff in a real company does not do your job. They read along so that they know what is happening, follow up the things that were supposed to happen, prepare the material, and draft. The person still decides, still shows up, still owns the outcome. Opitor keeps AI replies as drafts for the person to send.

The role stays bounded: messages, todos, deadlines and drafts. What a chief of staff should not do is take the meeting, make the call, own the relationship, or decide what the company should do next.

This is not modesty about what the technology could attempt. It is a claim about what is useful. Work in a small company is mostly judgement applied to incomplete information about specific people, and the part that can be handed off is the part around it: the remembering, the chasing, the first version of the text. Handing off that part is a large saving. Handing off the judgement is how a company stops knowing why it does things.

Why the nevers are what make it usable

Taken together, the product limits are part of what makes this usable in a small company.

A company of ten has no security team, no policy review, and nobody whose job is to work out what a tool does with your data. The whole evaluation is one person’s judgement, formed quickly. Under those conditions, capability is not what makes a decision easy. Predictability is.

What it means to be the first person using it

You do not have to move a company to evaluate these claims. Once one person has access, they can use the product on their own before the team decides anything. You can create an account at https://app.opitor.com/signup; the same product works for one person and is enough to check its ordinary behavior yourself. Review the conversation membership rules with teammates before choosing where to share work.

Check that an AI reply remains a draft, compare it with the conversation and choose whether to send it. Review reminders separately: those you create for yourself can be scheduled, while reminders created by someone else require approval. Keep the agreed task and deadline beside the conversation so you can check the next step.

Where Opitor fits

Try one reply draft and one reminder in Opitor. Keep the sending rules distinct: you choose to send an AI reply, while reminders you create for yourself can be scheduled. Use the FAQ to review these rules with your teammates.

Updated 2026-11-10

Create your account