A NEU hub holds the knowledge and runs the agents. Your team uses it from the Claude they already have. No surprise API bills.
Deployed in hours. Useful to you by week 1. Solve your company's first bottleneck with NEU in month one.
Request accessWhat this hub knows, pocket by pocket.
From 1 November the clinic's monthly budget is 6,000. It replaces the 4,500 agreed in March. Agreed on Monday's call, minute 14, by Lucía for the clinic.
Dental clinic, Northside. Account lead Marta; coordinator on their side Lucía. Budget 6,000 a month from November. Monthly report by the 3rd.
41 minutes, Monday 11:30. Budget from November, the search campaign, the price list, Lucía as coordinator, the Monday report. Five entries proposed from it, all approved.
The Q4 search campaign pauses on the 20th while the budget changes. Agreed on Monday's call, minute 22.
Retired on Monday 11:40, replaced by E-4K2M. Still visible as retired; never offered as current.
The price list sent in March. Retired on Monday's call; the new budget replaces it. Kept for the record.
Coordinator at Northside clinic. Approves creatives on their side. Named on Monday's call, minute 31.
Owner of the agency. Account lead for the clinic. Approver for Clients, Money, People and the shared layer. This card lives in the shared layer and shows in every pocket.
A task for @reporting, proposed from Monday's call. Taken from Marta's session under report-SOP at 14:05; the draft waits for her yes.
Every entry links to what it rests on and what it is about. Click one to see it; open it in Explore for the full card.
Dental clinic, Northside. Account lead Marta; coordinator on their side Lucía. Budget 6,000 a month from November. Monthly report by the 3rd.
41 minutes, Monday 11:30. Budget from November, the search campaign, the price list, Lucía as coordinator, the Monday report. Five entries proposed fr…
Owner of the agency. Account lead for the clinic. Approver for Clients, Money, People and the shared layer. This card lives in the shared layer and sh…
Not drawn in full in this mock.
The price list sent in March. Retired on Monday's call; the new budget replaces it. Kept for the record.
From 1 November the clinic's monthly budget is 6,000. It replaces the 4,500 agreed in March. Agreed on Monday's call, minute 14, by Lucía for the clin…
The Q4 search campaign pauses on the 20th while the budget changes. Agreed on Monday's call, minute 22.
Coordinator at Northside clinic. Approves creatives on their side. Named on Monday's call, minute 31.
A task for @reporting, proposed from Monday's call. Taken from Marta's session under report-SOP at 14:05; the draft waits for her yes.
Retired on Monday 11:40, replaced by E-4K2M. Still visible as retired; never offered as current.
Not drawn in full in this mock.
Each Monday at 07:00 a worker drafts one report per active client from the approved entries since last Monday; the account lead approves; it goes out …
What did we agree with the clinic on budget?
6,000 a month from November E-4K2M, replacing the 4,500 from March E-3H1Q · retired. Agreed on Monday's call MTG-091 and approved by Marta at 11:40. The search campaign pauses on the 20th DEC-140.
Ask reads by meaning across this pocket and the shared entries that relate to it, and answers only from approved entries, each cited. A retired entry is named as retired, never offered as current.
Slack and the documents folder feed the hub directly; the rest reaches it through a person's Claude session, which proposes, and a named person approves.
A grant names a pocket and a verb: read sees it, propose may add and waits for a yes, approve gives the yes. The sheet says in plain words what the person or agent will see. Taking it back is the same screen.
Each Monday at 07:00 a worker drafts one report per active client from the approved entries since last Monday; the account lead approves; it goes out on Slack. The skill report-SOP follows this, step by step.
The same map as in Clients, around this pocket's entries. Drawn once in this mock, for the Clients pocket.
When does the Monday report go out?
Each Monday at 07:00 a worker drafts one report per active client; the account lead approves; it goes out on Slack PRO-004. Today's six drafts are held for Marta.
Ask reads by meaning across this pocket and the shared entries that relate to it, and answers only from approved entries, each cited. A retired entry is named as retired, never offered as current.
Slack and the documents folder feed the hub directly; the rest reaches it through a person's Claude session, which proposes, and a named person approves.
A grant names a pocket and a verb: read sees it, propose may add and waits for a yes, approve gives the yes. The sheet says in plain words what the person or agent will see. Taking it back is the same screen.
The same map as in Clients, around this pocket's entries. Drawn once in this mock, for the Clients pocket.
What does the clinic owe?
Nothing: the September invoices were paid on 8 October. The invoice run moves to the 5th from November, if you approve Nuria's proposal.
Ask reads by meaning across this pocket and the shared entries that relate to it, and answers only from approved entries, each cited. A retired entry is named as retired, never offered as current.
Slack and the documents folder feed the hub directly; the rest reaches it through a person's Claude session, which proposes, and a named person approves.
A grant names a pocket and a verb: read sees it, propose may add and waits for a yes, approve gives the yes. The sheet says in plain words what the person or agent will see. Taking it back is the same screen.
The same map as in Clients, around this pocket's entries. Drawn once in this mock, for the Clients pocket.
Who is on leave next week?
Ana, from 20 to 24 October. Her Clients proposals wait for Marta's yes as usual.
Ask reads by meaning across this pocket and the shared entries that relate to it, and answers only from approved entries, each cited. A retired entry is named as retired, never offered as current.
Slack and the documents folder feed the hub directly; the rest reaches it through a person's Claude session, which proposes, and a named person approves.
A grant names a pocket and a verb: read sees it, propose may add and waits for a yes, approve gives the yes. The sheet says in plain words what the person or agent will see. Taking it back is the same screen.
Decisions that hold in every pocket, and one card about who owns the hub. A pocket's grant brings these along.
Names everyone shares, once each. A client, a person, a document or a meeting is filed in its pocket and listed here, so two pockets never hold two clinics.
Hosted and in your sessions. Everything you operate.
2 Sep 2026Runs on the hub's machine. Nothing to install. Every run is recorded under its routine or its task.
What did the clinic agree on budget?
6,000 a month from November, agreed on Monday's call at minute 14 and approved by Marta at 11:40 (E-4K2M). It replaces the 4,500 from March, which is kept as retired.
And the search campaign?
It pauses from the 20th while the budget changes (DEC-140, the same call, minute 22). Nothing else in the call touches the campaign.
File that the Monday report needs the new number.
Proposed as a task for me, and @budget is checking the budget line meanwhile. Marta gives the yes; the draft waits for her before anything goes out.
approve T-2210 to confirm, or say what to change.task T-2210 · project PJ-0142 · holder @reporting · skill report-SOP reads E-4K2M (budget from November), MTG-091 (Monday's call) draft held for @marta before anything is sent
Three ways in. Your session proposes the type, the id and the links; your click is the word.
Pick from the list. The last block says, in plain words, what they will see.
Nuria will read every entry in Clients (212 today) and the shared entries that relate to it, the owner card included. Her Claude sees the same. She will not see Delivery or People, and she cannot add or approve here. Taking it back is one click on this screen.
Today, your company's knowledge lives in heads, in old threads, in a document nobody reopens. A NEU hub puts it in one place, with the agents that work from it. Accessible from Claude via MCP, or build your own dashboard on its powerful API (coming soon).
Explain the company once, into the hub. From then on, your whole team, every agent and every routine work from the same source of truth.
Three doors. Same question, same entry, same source.
Same entry. Same source. Whoever asks, wherever they ask.
Most tools store what your company knows. The Brain links every fact, decision and person to what it rests on, so when you ask why, you get the chain, not a guess.
Enough to see it is real engineering, not a chatbot guessing. The hard part is not the database, it is keeping a true picture of how your company works.
From documents, chat and calls it proposes the entities and the links between them, not just the text. People, projects, decisions, clients, amounts, dates. A named person approves before any of it counts.
Each of those becomes a node; the links between them are edges. As things change it updates the graph and remembers what was true when, so old facts do not silently rot.
Ask why, and it follows the links: a decision to the facts under it, a fact to the call it came from. Search by meaning finds entries that do not share a word.
Nothing is invented. Each node and edge traces back to where it came from, so when the Brain says something, you can see exactly why it believes it.
In short: a temporal knowledge graph with semantic search running over it, fed from your tools, every entry waiting for a named yes, bounded by your permissions. We keep the rest of the recipe to ourselves.
You give NEU the procedure, written in plain words, or a document your company already has, and NEU turns it into a runnable skill for your worker: it finds the steps, wires each to the right tool, and spots the conditions, the sign-offs, and the rules you set.
A worker takes what you asked, works from the skills and the entries it was given, and the work comes back as a proposal for a named person to approve. You build the workers from your own procedures, and you see every one on one screen: what it is doing now, where it runs, the skills it holds and who approved what.
Hosted and in your sessions. Everything you operate.
2 Sep 2026Runs on the hub's machine. Nothing to install. Every run is recorded under its routine or its task.
A drawing of the Agents tab, with example names. NEU-hosted workers run routines on the hub's machine; a worker in a session is a copy running inside that person's Claude, on their plan.
Routines run on the hub's own machine on a schedule, and agents answer in Slack. Both propose instead of acting, and both leave a record.
What did the clinic agree on budget?
6,000 a month from November.
source: Monday's call · approved by MMarta · E-4K2MMonday 11:30. The call with a clinic client ends and Ana says "file it". Here is what happens next, step by step. Nobody forwards an email. Nobody asks "was that the final number?"
The Brain is sorted into pockets, one per Area of your company, plus a shared layer for what belongs to everyone. Letting a person in is one screen: pick the pockets, pick a verb for each: read, propose, approve. When someone leaves, you take the grants back on the same screen, and they leave with nothing.
Approvals belong to named people. Not to roles nobody remembers setting.
Pick a person to see which drawers open for them.
The parts every company ends up needing, built properly from the start and watched every night.
Already built. Already running. More reliable than a weekend version and ready to grow with you. You pay for the hub, not for the engineer who keeps it alive.
One hub. One clear price. Used from the sessions your team already pays for.
15 € per seat per monthMaintenance included.
3,000 € one-offWorking in the first week.
If the first week shows things to polish, we double the optimization period.
Pay at once or in instalments, agreed on the call.
Our team sets it up with you. One sitting to start, and your hub is up and running in a week.
One sitting with us. Your documents go in. Your tools get connected. By the evening, it answers your first questions about your company, with their source.
Your team is given access. Each person sees their brain pockets.
Your first SOP is a skill. The first worker follows it from their Claude session.
Your first agent runs its first routine on the hub's machine. You approve its first proposal.
Up and running. From here, you say "file it" at the end of a meeting and the company remembers.
Then month one: you name the bottleneck on day one, in writing, with what solved looks like. On day thirty we read it together against the hub's record. If the first week shows things to polish, we double the optimization period.
No. The hub sits behind it. Using it from Claude costs no API tokens; the agents on the hub's machine run on the hub's key, inside the hub's price.
In your hub's own database, hosted by us today, yours to copy any time.
No. It proposes, a named person approves, and it stops at keys and money.
You write the bottleneck and what solved looks like on day one. On day thirty we read it together against the hub's record. If the first week shows things to polish, we double the optimization period.
The API is in the first version. Leave your name and you hear when it opens.
15 € per seat per month, maintenance included. The implementation, if you want it done for you, is 3,000 € one-off. Prices exclude VAT.