For agencies & consultancies
Every account lives in one person's head. Then that person moves on.
Each client becomes its own queryable memory - who decided what, what's in scope, what you promised, where it stands right now - built from the team just talking about the work. So when an account changes hands, the knowing doesn't walk out with the person.
Sound familiar
Your real product is context. It lives everywhere except one place.
Ten clients means ten half-organized realities. The brief is in an email thread, the last scope call is in Slack, the reason you said no to that feature is in someone's head, and the current status is wherever the account manager last left it. Each client's world is real - it's just scattered across tools that don't know the client exists.
So the agency's actual deliverable - knowing each account cold - lives in people, not anywhere you can hand off. That's the handover tax: every time an account changes hands, or a new account manager starts, someone spends weeks on archaeology - reading old threads, re-deriving decisions, re-learning what was promised - to rebuild context that was never written down anywhere a machine could follow.
And it leaks. Context bleeds between projects when the same person runs three of them, and it walks out the door when they leave. None of that is sloppiness - it's a missing-map problem. The work is all there; the thread that connects it never had a home.
It draws the map
One account. One map that holds the whole thing.
Connect the client's Slack channel, their Jira project, the shared Notion - or just drop the brief - and Naumu folds it into one map for that account: the brief to the scope it set, the scope to the decision that trimmed it, the decision to the deadline it was traded for, the deadline to the person who owns it. The email, the ticket, and the thread about one client finally sit next to each other, and the account stops living in one person's head.
Watch it work
Ask the account, not the person who is leaving.
Open a client's space and Naumu is a participant, with that whole account as memory. Ask the question a new manager always has to ask around the office - and it answers from what's true, with a receipt: who decided, who promised, and when.
No one had to sit you down and brief you - the account's own memory did. Scripted so you can see the shape - ask your own below and watch it walk the account you're about to inherit.
Start with one account - then bring the rest.
Start with one client in a minute: drop that account's mess - the brief, the thread, the tickets - and watch its map build. No signup, and the space is real from the first dump. Keep it, and each client gets its own space - its own map, its own members, its own billing - so contexts stay separate by design, not by everyone being careful. Named the way your team names them, with no schema to design first.
You're not ripping anything out on day one, either. Keep working where you are - connect the tools the team already lives in, Notion, Jira, Linear, ClickUp, Slack - and Naumu learns each account in the background while everyone keeps working. Drag in a whole project tracker and it's honest about scale: a first pass to correct, not a flawless import, showing what came through and what to double-check. And every member's AI reads and writes that same map - as that member, with that member's permissions.
Each client is a separate space with its own members and its own subscription; unkept trial spaces expire after 30 days. Each connected assistant acts as the person who connected it and sees only what they can; agent writes are logged, attributed, and one tap to undo. How your data is processed: /docs.
Integrations
Connect the tools each account already lives in.
Wire them up once and each client's map keeps filling while the team works - briefs, tickets, and decisions folded into the one place anyone picking up the account can ask.
Who this is for
Stop being the only person who knows the state of every account.
If what you need is to bill hours and tick off tasks, a time tracker and a project tool do that better, and you should keep them. Naumu doesn't invoice or run a timesheet - it holds the why underneath the work: the decision behind the scope, the promise behind the deadline, the reason you said no in April that a client is asking about again in July.
And if a hosted cloud is a hard no for your most sensitive client work, this isn't your tool yet - each account's map lives in its own private space in Naumu's cloud, the trade for letting every teammate and every agent reach it from anywhere. Naumu is for the agency tired of being its own institutional memory, where "what did we actually promise them?" keeps walking out the door with whoever last ran the account.
Why it holds up
Separate by design, not by discipline.
One space per client
A space is its own knowledge graph, with its own members and its own billing. There's no shared pool for context to leak across - the Meridian account and the Klarwerk account are simply different maps, so keeping them apart isn't a habit anyone has to keep.
Every answer has a receipt
Ask an account a question and it answers from what's true, with a source and an author on every line - who decided the scope, who promised the deadline, and when. The reason you said no in April is still there in July, attached to the ticket instead of stranded in a thread.
You decide who sees each account
Permissions are per-member, and every AI assistant inherits them. Inside a space you can mark a node, view, or thread Internal or Invite only; outside it, you can bring a client in as a guest or open a read-only public link - so "shareable" never means "everyone sees everything".
FAQ