01 / 11
Nakama, chief of staff
He takes each request and hands it to the right specialist. Every morning, he says what is waiting for a decision.
NakamaOS in your company
NakamaOS, the software your agents work in
Your agents work in it every day: they sort, prepare, chase and draft in your tools. You approve what goes out, and you see the time saved. Ready in three weeks, hosted in Europe; we then adapt it to your processes.
We work in French. For Portugal, write to us.
We install one company at a time, in the order of the waiting list.
Your team, ready to work
Eleven roles, each with its agent, its view and its job description. You get all of them with Starter; you approve what goes out.
02 / 11
Mira, inbox lead
She keeps the inbox: what is waiting for a reply, what is waiting on others, what can wait.
03 / 11
Noa, marketing lead
She prepares the LinkedIn and X posts, plans the week’s content and suggests ideas drawn from the news.
04 / 11
Theo, sales lead
He looks for prospects, prepares an angle and a first message, and tracks the pipeline and the follow-ups.
05 / 11
Iris, support lead
She sorts the tickets, drafts the replies and spots the question that keeps coming back, to turn it into a help article.
06 / 11
Leo, research lead
He searches the web and reads pages, including those where a session is open, then reports back a sourced summary.
07 / 11
Ada, automations lead
She turns a routine, “every morning, do X”, into a mission: a dashboard that updates itself.
08 / 11
Sage, analytics lead
He keeps the week’s figures: what the agents handled, the engine counters, the e-mail activity.
09 / 11
Otto, knowledge keeper
He keeps the knowledge base: notes, people, organisations, projects, meetings. He finds the right note when asked.
10 / 11
Kai, meetings lead
He prepares every meeting: who is coming, the history, the open points. Afterwards, he draws out the decisions and actions.
11 / 11
Remy, planning lead
He looks at the calendar: the day, the free slots, the week’s load. He suggests blocks of time to protect.
-
Connected to your tools
Gmail, Outlook, calendar, HubSpot, Slack, and over 1,000 direct integrations. With Starter, no limit.
-
The AI of your choice
The model and provider you choose, on an account in your name, with your spending cap. An all-inclusive plan exists on request.
-
Starter
The base team, ready in three weeks, set up so that the agents only do what you allow.
€907/month for 6 months, then €490/month
The software’s screens
Six NakamaOS screens, rebuilt in French with sample data (the software is still in English). For each one: what the agent does, what the software enforces, what you approve.
What the person running the company sees: the morning inbox, support, communication, the night missions, what is waiting for a decision, the product.
-
The Inbox Lead has sorted the night’s e-mails: what is waiting for your reply, what is waiting on others, what is for information, the noise. It flags messages still unanswered after more than five days; on request, it drafts one reply per message, in the house voice, and the follow-up. Approved before sending. NakamaOS
The inbox, sorted every morning
- What the agent does
- Sorting the messages, flagging those still unanswered after more than five days; on request, one reply drafted per message.
- What the software enforces
- A draft is a file, not a send: sending stops on a permission request, approve or refuse. A message covered by a confidential folder rule is classified by a local model, or left aside.
- Approved
- Every send: a quote, a contract, a reply to an incident.
-
The Support Lead sorts the tickets and prepares a reply for each. Before writing, it reads what the memory knows about the customer: past tickets, e-mails, meetings. The recurring question becomes a help article. Approved before it goes out. NakamaOS
Support, ticket by ticket
- What the agent does
- Sorting the tickets, one reply per ticket, the help article drawn from the recurring question.
- What the software enforces
- The screen reads the queue without changing anything. Writing to a ticket goes through the external action tool, which asks for permission. The escalated column mirrors the help desk status.
- Approved
- Every reply; any escalation, any complaint, anything touching a contract.
-
The Marketing Lead has written the week’s LinkedIn and X posts and set the calendar. A post goes out on a click, in its confirmation window, or at the scheduled time. Approved before publishing. NakamaOS
The week’s posts, ready
- What the agent does
- The LinkedIn and X posts, the content calendar, post ideas.
- What the software enforces
- Publishing goes through the approval click and its confirmation window, or through a time scheduled by the person. A post written and not yet approved comes back up on the Today screen before its time.
- Approved
- Every post, before it is published or scheduled.
-
Missions turn “every Monday, prepare the follow-ups” into a scheduled task that starts on its own, at a fixed time or on an event, and keeps its dashboard in a note. Anything irreversible, sending or publishing, still waits for approval. NakamaOS
Missions, at a fixed time or on an event
- What the agent does
- The routines that come round: a dashboard that keeps itself up to date, a follow-up list, a watch.
- What the software enforces
- A mission has a reduced set of tools: it only writes in its own area, starts no other mission, has the browser only if its note allows it, and stops after eight minutes by default. It can obtain no permission. Every run is written to the activity log.
- Approved
- Creating a mission, reading what it reports, pausing it.
-
The Chief of Staff gathers what is waiting for a decision: the replies prepared, the posts from the Marketing Lead, the support escalations, the night’s missions. NakamaOS
What is waiting for your decision
- What the agent does
- The morning summary, handing each request to the right specialist, surfacing what is waiting for approval.
- What the software enforces
- Each pending line opens what it points to: the message, the draft, the post, the mission. A hand-over only happens if the message is classified with enough confidence; otherwise, the conversation stays where it is.
- Approved
- The morning decisions, in order.
-
A sample dashboard, as a mission can keep it: sign-ups, tickets, uptime, pull requests. The data on this screen is sample data. NakamaOS
NakamaCyber, the real case
- What the agent does
- The code, the build-in-public posts, the blog articles, the Stripe payment follow-up, support, e-mails and meetings.
- What the software enforces
- Commits written by an agent carry its mark. Permissions are granted tool by tool and apply to all agents: no agent has rights of its own.
- Approved
- Every reply, every exercise, every post, before it goes out.
The data on these screens is sample data. The layout is the software’s own.
It learns from you, week after week
Around the AI model, NakamaOS holds the tools, the memory, the rules and the approvals. That part is what learns from you, not the model; and what it learns stays with you, in your NakamaOS.
Your preferences
Every correction (“stop doing that”, “always do it this way”) is noted, then applied to the following conversations.
Your memory
Your customers, your projects, your decisions: the memory fills up from your exchanges, and each agent finds the right note in it.
Your routines
What comes back every week becomes a mission, run at the set time, with its dashboard.
Where it runs
Hosted in Europe by default. With Sovereign, on a dedicated server in Europe or on your premises, with local models. Either way, it is the complete NakamaOS, proven every day at Nakama, set up by an application security specialist so that the agents do only what you allow; every month, the update is checked before it reaches you.