emem

Every agency running AI on client work pays a hidden tax each time an agent starts a session with no memory of prior decisions, and that tax compounds across every retainer. Persistent memory layers convert one-off prompts into reusable institutional knowledge, so the same client context serves every tool and every teammate. The strategic question is not whether to add memory, but whether your memory layer exports cleanly enough that switching models does not erase what you learned.

Memory Portability Premium is the strategic value an agency captures when its agent memory layer exports cleanly, measured as the gap between what client context is worth inside a tool and what survives leaving it. Agencies accumulate client-specific architecture, brand rules, and debugging history across long-running retainers, and that accumulated context is the real deliverable asset. When the memory layer is a closed silo, switching tools means rebuilding months of context from scratch, so the premium collapses to zero and the vendor captures the rent. Knownbase stores decisions, debugging discoveries, and constraints as project notes retrievable across sessions and tools, which keeps the archive portable. Cogni runs retrieval through an entity graph with spreading activation and no LLM in the path, so connected facts stay model-agnostic. Bourdon federates one memory across Claude, Codex, Cursor, and Copilot, so a fact learned in one tool is recognized in the others. Before standardizing, test one export: pull a client's memory out and read it without the original tool.

Memory Portability Premium is the practice of valuing an agent memory layer by what survives the exit, not by what it does on day one. Every connector in this category stores something an agency paid to learn: client architecture decisions, brand constraints, debugging discoveries, campaign rulings. If that store exports as clean, structured, attributable records, the knowledge compounds across tools and staff turnover. If it exports as an opaque blob, the agency rents its own institutional memory and repays the learning cost at every switch. The premium is the delta between those two outcomes, and it is measurable in re-prompt hours and re-onboarding days. A concrete test: ask whether a layer like Knownbase or OzBrain can hand back tagged, provenance-linked notes another MCP-compatible agent can read without the original vendor present. Terms risk compounds this. Roughly 60% of 175 AI tools changed monetization-relevant terms in 15 weeks, so a memory vendor's export policy can shift after your client retainer is signed. Price portability before capability.

Recall Latency Tax is the hidden cost of how long an agent takes to surface a fact it already learned. Every re-prompt, re-explanation, and context paste is a tax paid in senior hours, and it compounds across a retainer because the same client architecture gets re-taught every session. The framework separates two retrieval paths: recognition-first federation, where a fact learned by one agent is instantly available to others, versus search-based lookup, where the agent must be told what to look for. Bourdon's recognition-first design pushes recall latency toward zero across Claude, Codex, Cursor, Copilot, and Devin, while Knownbase organizes notes by project and tag so retrieval depends on correct querying. For an agency running five client accounts through three tools each, the difference shows up as fewer re-briefs per deliverable and more margin per retainer hour. Audit recall latency before you audit model quality.

Before standardizing on any agent memory layer, export a full client knowledge set, re-import it into a second tool, and confirm the entity relationships survive the round trip.

Run a full export-and-reimport test on real client memory before standardizing any connector, and reject the layer if the graph, notes, and provenance do not survive the round trip intact.

IF your agency runs three or more AI tools across concurrent client accounts and needs a fact learned in one session to surface in another without manual re-prompting, THEN standardize on a federated memory layer that multiple agents read and write. IF your work is concentrated in one coding tool, one delivery team, and a handful of long-lived projects, THEN a single structured project archive is cheaper and faster to operate.

A delivery pattern that gives a client's AI agents persistent, queryable memory of brand rules, architecture decisions, and past work, so retainer teams stop re-prompting the same context every session. The agency ships a governed memory layer with export paths, not a single-vendor dependency.