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 three product behaviors and one administrator-access check that is still underway.
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.
For the workflow described in Opitor’s public materials, the rule is narrow and absolute. Drafting is where the help is: it reads the thread, uses relevant context, writes the reply you were going to write, and getting from nothing to a good draft is most of the work. Production model context remains unverified. Then it stops and waits for you.
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.
What production checks show about administrator access
The deployed revision is unknown, and production administrator/non-member checks across all private-message read paths remain pending. This page does not establish a complete administrator access boundary.
The practical consequence, if this boundary is verified, 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.
Whether this boundary constrains company administrators across all production message-read paths remains part of the pending acceptance.
What is known about memory
Anything that works alongside you accumulates a picture of you. The question is not whether it has a memory. It is who holds the pen.
Opitor’s public materials describe a Memory feature, but the current review has not verified its production creation or approval flow, model access, role-based visibility, or backend deletion and retention behavior. Screenshots reviewed for this project showed manually entered records, not proof of an AI-proposed confirmation flow. Do not assume that an item is used only after confirmation, personal-only, or permanently deleted.
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. Public materials describe Opitor as following that shape; production model context remains unverified.
Public materials describe a bounded role: gathering messages, following up todos and deadlines, keeping company goals in view, advising and drafting. The production model context remains unverified. 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. Administrator access to private messages still needs production request comparisons before this boundary can be relied on.
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. The website waitlist is currently the route to request an invitation; after access is granted, the same product works for one person and is enough to check its ordinary behavior yourself. The administrator access boundary still requires production requests from administrator and non-member accounts across private-message read paths.
Watch whether anything goes out that you did not send. Look at what it asked to remember and whether that list matches what you agreed to. Delete something and see whether it comes back. The product behaviors described here are few enough to check in a week of ordinary use. Administrator access still needs separate production acceptance.
Where Opitor fits
Opitor is an AI-native operating system for small companies, where each person gets an AI chief of staff. AI replies are drafts you choose to send and are signed in purple; self-created reminders can be scheduled to send automatically by Opitor. Administrator/non-member checks across private-message read paths remain pending. Product materials describe a Memory feature, but its production creation flow, model access, role-based visibility, deletion and retention behavior remain unverified. Messages, the Todo List and deadlines, and administrator-managed quarterly goals are described in the product materials. Self-serve sign-up is closed; new users can request an invitation through the website waitlist. The product works in a phone browser. See what is an AI chief of staff and the questions and answers page for current verification limits.
Updated 2026-09-25