How a ten-person company runs on one system
A ten-person company has no operations team. Nobody’s job is to notice that something promised on Tuesday was never done. There is no weekly review that somebody else prepares. The work of holding the company together is spread across everyone, in the gaps between their actual jobs.
That works until it does not. The failure is rarely dramatic. Something is agreed in a group thread and nobody writes it down. A deadline moves and two people hear about it. A quarterly goal is set in the first week of the quarter and nobody reads it again until the last.
The four things that have to happen every day
Strip a small company down and four things have to be true at the end of each day.
Messages get read. Not every message, but every message that needed a person. Direct messages and group threads both. A question asked on Monday and answered on Thursday cost four days.
Todos get followed up. Somebody has to notice the ones that stopped moving. In a large company that is a manager’s job. In a small one nobody is assigned to it, so it has to be built into where the work lives instead.
Deadlines stay visible. Visible to the people who plan around them, not only to the person who set them. A date that lives in one head is not a deadline, it is a hope.
Quarterly goals stay in view. The few things the quarter is actually about. If they appear only in a planning session at the start and a review at the end, they did not shape the quarter.
Everything else sits on top of those four. When they are healthy, the rest is work. When they are not, the rest is firefighting.
The losses happen at the seams
Most companies that size run those four things in four places: a messaging tool for conversation, a tracker for todos, a spreadsheet for dates, and a document somewhere with the quarterly goals. Each of those is fine on its own. The losses happen between them.
A decision gets made in a thread. Turning it into a todo is a separate act, in a separate tool, done by a person who has to remember to do it. Most of the time they do. The rest of the time the decision exists only in the thread, and the thread scrolls.
A todo gets a date. The date is real inside the tracker, but the person who has to plan around it does not open the tracker on a Tuesday afternoon.
A quarterly goal gets written down. The work that would move it sits in the tracker, described in different words, with nothing joining the two. Nobody is lying when they say the goal is on track. Nobody can show that it is.
The pattern repeats: the information exists, but it exists somewhere the person who needs it is not looking.
The day: what to look at, in what order
A rhythm that works at this size is short and fixed. Three passes, same order every morning.
First, what came in. Read what arrived overnight and decide, message by message, whether it needs you today, needs you this week, or needs nothing. The deciding is the point. A message you have read and not decided about is still open.
Second, what you owe. Your own todos, late ones and today’s at the top. If something is late, either give it a new date or say so in the thread where you promised it. Either is fine. Silence is not.
Third, what you are owed. The things you asked other people for. This is the pass small companies skip, and it only works if the request was written down somewhere that brings it back on its own. Chasing from memory means chasing the loud things and forgetting the quiet ones.
Ten minutes on most days. What keeps it to ten is that all three are in the same place: one pass, not three.
The week: the things without dates
Daily habits handle work that has a date on it. Weekly habits handle the rest, which is where a small company actually drifts.
Pick one day. Friday works, because it closes a week rather than opening one. Look at three things.
What moved, and what did not. Which todos were finished, and which have been open long enough that the date on them is no longer believable. A todo pushed three times is not a todo. It is a decision nobody has made, and the honest move is to make it: do it, hand it off, or drop it.
What was promised and never written down. Read back through the week’s group threads for sentences that begin with “I’ll” and end without a todo. Write them down now, or say out loud that they are not happening.
The quarterly goals. Read them. Not to update a number, just to ask whether the week’s work had anything to do with them. That takes two minutes, and it changes what you plan for Monday more often than you would expect.
What “one system” means here
One system does not mean one more layer above the tools you already have. A layer has to be fed by hand, and the feeding stops exactly when the company gets busy.
It means the four things are parts of the same product. The conversation and the todo it produced are two views of the same work. The deadline belongs to the todo rather than being copied somewhere that has to be kept in step. The quarterly goals sit where the daily work is, not in a document opened twice a quarter.
When that is true, following up is no longer a task somebody has to remember. It is the default behaviour of the place the work already lives.
It is also a fair test to put to any product that says it unifies things: ask where the todo lives. If the answer is that it connects to your existing tracker, it is a layer, and layers fail quietly, under load.
Start with one person
The last piece is the order you adopt it in. A small company cannot afford a migration: ten people changing tools in the same week means a week where nobody knows where anything is, followed by a quiet drift back to the old way.
So start alone. One person, usually whoever has the most threads open, runs their own day in the new place for two weeks. Messages, todos and deadlines, and the goals. Nobody else changes anything.
Two weeks is long enough to find out whether the rhythm holds up in a real week, including a bad one. If it holds, bring in the person you work with most, then the rest. If it does not, you have changed nothing for the other nine people.
Where Opitor fits
Opitor is an AI-native operating system for small companies, where every person gets their own AI chief of staff. Messages (direct and group), the Todo List with its deadlines, and the company’s quarterly goals (OKR, managed by administrators) are parts of the same product, so the follow-up described above is what the system does rather than something a person has to remember. Each person’s chief of staff works across their own messages, todos and deadlines: it drafts, you send, and everything it writes is signed in purple. Opitor is free to start, there are no paid plans yet, and you can start alone and invite your team when you are ready. What an AI chief of staff is covers what it does and what it never does, and the questions and answers page covers what is included.