NAKAMA

Use cases

What your agents do, role by role.

Six roles covered by the base team from installation, then six we build to measure after the audit. For each case: what the agents do, and what stays with you.

E-mail prepared by the agent yours to approve Sales prepared by the agent yours to approve Support prepared by the agent yours to approve Communication prepared by the agent yours to approve Monitoring prepared by the agent yours to approve Meetings prepared by the agent yours to approve

From installation, with the base team

Six everyday roles, covered from day one. For each: what the agent does, what stays with you, and a typical exchange.

Mira

Inbox Lead · with Nakama (Chief of Staff)

E-mail and follow-ups

  • Sort the inbox every morning
  • Spot what is still unanswered
  • Prepare replies and follow-ups

Stays with youEvery send: it waits for your approval.

  1. Mira

    Inbox sorted: 3 messages are waiting for your reply. The quote sent on Monday has been unanswered for 6 days: the follow-up is ready.

  2. You

    Approved, send it. And suggest a call on Thursday.

  3. Mira

    Follow-up sent, with the call suggestion. I will let you know as soon as they reply.approved

Written example, fictitious data. Nothing goes out without your approval.

Theo

Sales Lead · with Mira (Inbox Lead)

Prospecting and sales

  • Qualify inbound requests
  • Prepare a profile and a first message per prospect
  • Follow up and offer meeting slots

Stays with youThe relationship and the negotiation.

  1. Theo

    Inbound request this morning: company profile prepared, first message drafted. Two follow-ups are due this week.

  2. You

    The message is good. Add our two references in the sector.

  3. Theo

    Message sent with the two references. Both follow-ups are ready for tomorrow.approved

Written example, fictitious data. Nothing goes out without your approval.

Noa

Marketing Lead · with Otto (Knowledge Keeper)

Communication

  • Read your notes and decisions of the week
  • Draw one text per channel from them
  • Fit the format to LinkedIn or X

Stays with youEvery post, before it goes out.

  1. Noa

    This week: three LinkedIn posts and two X posts, drawn from your meeting notes. Scheduled for Thursday at 9 am.

  2. You

    The second post is too long. Split it in two.

  3. Noa

    Split in two; the second half goes out on Friday. All five posts are scheduled.approved

Written example, fictitious data. Nothing goes out without your approval.

Iris

Support Lead · with Otto (Knowledge Keeper)

Customer support

  • Sort requests
  • Draft the reply with the customer’s history
  • Turn the recurring question into a help article

Stays with youSensitive cases and commercial gestures.

  1. Iris

    12 requests sorted. The reply to the billing question is ready, with the customer’s history. One question came up three times: draft help article.

  2. You

    Send the reply. For the article, add a screenshot.

  3. Iris

    Reply sent. The article is waiting for your review, with the screenshot.approved

Written example, fictitious data. Nothing goes out without your approval.

Leo

Research Lead · with Ada (Automations Lead)

Competitive and regulatory watch

  • Follow your sources every day
  • Compare and spot what changes
  • Flag what matters

Stays with youWhat you do with it.

  1. Leo

    Morning watch: two changes at your competitors, one regulation published yesterday. One-page summary, with sources.

  2. You

    Detail the regulation: who is concerned, and when.

  3. Leo

    Fact sheet added: scope, deadline, the three new obligations, with sources.

Written example, fictitious data. Nothing goes out without your approval.

Kai

Meetings Lead · with Remy (Planning Lead)

Meetings and planning

  • Prepare every meeting
  • Draw out the decisions and the actions
  • Keep the schedule up to date

Stays with youThe trade-offs.

  1. Kai

    2 pm meeting: brief ready, three open points. Yesterday’s minutes: four decisions, two actions to follow up.

  2. You

    Minutes approved. Send them to the participants.

  3. Kai

    Minutes sent to the four participants. Both actions are in the schedule.approved

Written example, fictitious data. Nothing goes out without your approval.

Custom, after the audit

What we build when your processes call for it. These agents join the base team.

  • Responding to tenders

    Leo, research lead · Otto, knowledge keeper

    Read the tender file, extract the requirements and technical constraints, prepare the outline of the bid and the list of documents.

    Stays with youThe price, the strategy, the signature.

    See the sectorFR
  • Purchasing and suppliers

    Mira, inbox lead · Sage, analytics lead

    Compare quotes, chase suppliers, prepare purchase orders.

    Stays with youChoosing the supplier and placing the order.

  • Finance and accounting

    Sage, analytics lead · Nakama, chief of staff

    Match and classify transactions, flag anomalies, prepare the monthly reporting.

    Stays with youApproved entries and the decisions.

  • HR and admin

    Remy, planning lead · Mira, inbox lead

    Prepare onboarding, answer routine requests (leave, certificates), sort applications against your criteria.

    Stays with youEvery decision about a person.

  • NIS2 and DORA compliance

    Otto, knowledge keeper · Mira, inbox lead

    Keep the evidence register, chase owners, follow supplier questionnaires.

    Stays with youApproving each requirement.

    See the sectorFR
  • Security operations (SOC)

    Iris, support lead · Leo, research lead · Kai, meetings lead

    Triage alerts, discard known false positives, enrich the rest, draft the incident report.

    Stays with youClosing a critical alert, and every decision.

    See the sectorFR

Not sure where to start?

Tell us what you need: the written answer is free. It says whether an audit makes sense, €4,900, deducted from the project if you sign.