Not a prompt cache
Stateless agents forget last quarter. Memory stores what actually converted: play, account context, DNA cluster, $ outcome, and provenance. The next Scout elevate and Closer motion read that store.
Handoffs write Memory
Scout → Closer → Keeper → Grower is not UI navigation. Each handoff is a lifecycle event. Wins, saves, and expansions write episodes; failed patterns decay so operators are not retraining a chatbot.
Why this is not Gong's graph
Gong's conversation graph is evidence of what was said. Revenue Memory is evidence of what created, protected, or expanded dollars on your fused CRM + product Graph — with agent ownership.
FAQ
What is Revenue Memory?
Learned patterns from attributed outcomes — Pipeline, Protected, At Risk, and Expansion. Shared across all four AI employees so compounding intelligence is the product, not a dashboard.
When does Memory write?
When a governed play completes with an attributed $ outcome — Closer win, Keeper save, Grower expansion. Empty Memory on day one is expected; the loop starts after the first approved result.
Can we export Memory?
Operators inspect episodes with provenance in the product. Warehouse export follows the same tenant and audit rules as the rest of the Graph.