
Your company's knowledge is scattered: chats, calls, documents and repos
Why what your company knows is split across chats, calls, documents and repos, what searching costs, and what it takes to bring it together with citations.

A simulated scenario: an agency with 12 clients, promises scattered across emails and calls, and what client separation MemoryFirst offers and what it does not.
Simulated scenario. Estudio Mirador is a fictional eight-person agency with twelve clients: an online shop, two clinics, an agricultural cooperative, a gym chain and seven more. The people, the agency and the numbers are made up and do not represent real customers or results. What we describe about the product, on the other hand, has been checked against our technical architecture, limits included.
It is Tuesday. Norte Clinic asks whether the monthly report will now include call data, as discussed. Carmen, who ran that account until October, is now on two others. Nobody else remembers whether it was "in November" or "when the new dashboard is ready". Someone searches the inbox, someone the client chat, someone the notes of a meeting that was recorded but never transcribed.
In an agency with twelve clients, the most valuable knowledge is the hardest to find: what was promised, to whom, by when, and which exceptions were agreed. And the second problem is worse than the first: if you put all that memory in one place so you can search it, you need to be sure client A's material never shows up in client B's work.

| Item (per quarter, invented assumptions) | Before | After |
|---|---|---|
| "What did we tell the client" searches per week | 25 | 25 |
| Average minutes per search | 12 | 3 |
| Forgotten promises that end in a complaint | 4 | 1 |
| Handover meeting when an account owner changes | 1 hour | 20 minutes |
With those assumptions, 25 weekly searches dropping from 12 to 3 minutes is about 3.75 team-hours a week. Do not trust our figure: it is a starting estimate. What is worth measuring in your agency is how many times a month someone asks "what did we tell...?".
The rule in the scenario is simple: every promise to a client is recorded at the moment it is made, as an event in that client's project. One event per promise, with a type (decision or customer contact), a one-line title, the why in the body and an importance of 3 if money or a deadline is committed.
When Carmen ends a call, her agent (say Claude Code or ChatGPT connected over MCP) records: "Norte Clinic: the report will include call data from January, not earlier." When the deadline changes, a new event is recorded that supersedes the old one; the old one stops feeding answers but stays in the history.
Six weeks later, whoever needs it asks with mf_query ("what did we promise Norte Clinic about call data?") and gets the answer with its citation: the event, the date and who recorded it. And when the account owner changes, the morning brief and the project summary (mf_recall) do half of the handover.

Precision matters here, because this is where agencies put trust at stake. What MemoryFirst does today, according to our architecture documentation:
project only look at that client), but an unrestricted credential sees every project in the workspace.What does NOT exist, and we will not hint otherwise:
One more caution: if your client is in healthcare or law, do not promise outcomes or compliance because of a tool. The database, embeddings and files are in the EU; by default, the question and the retrieved passages go to a US inference provider to write the answer, unless you bring your own key (it covers mf_query and state regeneration, not every process). And there is no self-hosted edition.
The exit matters as much as the start. A workspace owner can export it and request its deletion with a grace period, and there is a verifiable erasure that deletes derived data, checks nothing remains and issues a certificate. Export and account deletion are recent features: check them in the data settings before putting them in a contract.

Free: one project, 30-day retention, one seat. Pro: €12 a month billed annually (€14.40 month to month), unlimited projects and retention, one seat. Team: €39 a month billed annually, five seats and shared memory; each seat beyond five costs €9 a month billed annually (€10.80 month to month). VAT included, figures from our pricing page as of 2026-11-14.
It is for small agencies and consultancies where each account's knowledge lives in heads, emails and chats. It is not a CRM or a client portal: it is not meant for your agency's clients to query the memory directly.
Keep reading with your company's knowledge is scattered, what an AI company brain is and memory you can audit. To compare other options, see the AI memory market in 2026.
Start free with one project and see how it behaves with a single client's data before you scale up.
Start free
Why what your company knows is split across chats, calls, documents and repos, what searching costs, and what it takes to bring it together with citations.

An AI that asserts things it can't prove is a liability, not a feature. Here's how a memory layer with citations, retraction and EU data turns trust into something verifiable.

An honest comparison of Mem0 and MemoryFirst: plans, verified pricing, MCP, graph, data residency and when each one fits. Data checked on 2026-11-14.