Memory Is Now Table Stakes for AEO Tools. Profound's Launch Just Proved It.

On May 22, Profound sent their product newsletter. The subject line announced conversation memory for Ask Profound, their AI research assistant. It shipped alongside 15 new capabilities in their redesigned platform, a knowledge graph for their agent layer, and a redesigned filter experience.

None of those other things are the interesting part.

The memory announcement is a category signal. Profound's implementation is thoughtful. It is not breakthrough engineering. It is a market move. The category leader publicly shipping memory means one thing: stateless AEO research tools are now behind. Not in a roadmap sense. In a retention and renewal sense.

What stateless intelligence actually costs

Consider what a typical session with any AEO tool looks like today.

A senior analyst at a mid-size DTC brand opens the assistant. She wants to understand how her brand's citation share in ChatGPT (https://chat.openai.com) responses has shifted since their Q3 repositioning, and whether Perplexity (https://www.perplexity.ai) and Gemini (https://gemini.google.com) are showing different trends. She types the question. She gets an answer. The response is technically correct. Generic where specificity matters. She closes the tab.

Three days later she opens the assistant again. The assistant has no idea who she is. It does not know this analyst cares about citation share specifically, not visibility score. It does not know her brand repositioned in Q3 or what that repositioning was. She has been benchmarking against two specific competitors for six months. The assistant has no record of that. She prefers period-over-period comparison framing. The assistant outputs absolute numbers by default.

She types the context again. Abbreviated this time, because she is busy. The answer reflects that abbreviated context, not the full picture. Still technically correct. Generic in the ways that matter most.

This is not a UX inconvenience. It is a structural quality ceiling on what every AI research assistant in this category can deliver. The product cannot distinguish between a power user who has been building toward a specific strategic goal for two quarters and a first-time user asking a cold question. Every interaction is treated as a first interaction. The analyst re-explains herself. The product re-generates from scratch. The answer is calibrated to the average user, not to her.

Over time, the gap compounds in a specific way: the more invested a user becomes in their strategic analysis, the more their actual context diverges from what the tool knows, and the more they pay the re-explanation tax on every session. The product gets more useful as a category, through new features and improved models, but it never gets more useful specifically for the analyst using it every day, because it forgets her every time.

That is the structural problem Profound just fixed first.

Why this is a category signal, not a product update

Here is the thing about memory in a research product: once the tool knows how you work, the answers it gives are a different category of useful.

Not marginally better. Differently better. The question "how did my visibility change this quarter" gets answered with the context that this user defined visibility to mean citation share across three specific models, that their Q3 repositioning is the relevant reference point, and that Competitor A is the benchmark they care about rather than the default leaderboard. That answer cannot be produced without memory. It can only be approximated with a very long prompt the user has to reconstruct every session.

There is a compounding dynamic on the product side too. When a tool has learned a user's competitors, preferences, analysis patterns, and strategic context over months of use, moving to a different tool means starting over. The accumulated intelligence is not portable. Power users who have built up that context do not move unless something goes significantly wrong. This is retention built into the product architecture, not into the contract.

Profound shipping memory first does not just give them better answers today. It starts compounding a structural advantage that gets harder to close over time. An AEO tool that has six months of accumulated context about a customer's competitive strategy is not the same product it was on day one. The competing tool that offers more features, better pricing, or a slicker dashboard is competing against something that knows the customer's business. Feature comparisons look different in that context.

Every other AEO tool in the market is now competing against a product that gets better the more a user uses it. Their own products reset on every session.

The three layers AEO tools actually need

Memory in the context of an AEO research tool is not one thing. It is three distinct layers, and getting all three right requires different infrastructure and different thinking about what the product is actually doing.

User memory. This is the layer Profound shipped. What does this specific user care about? How do they prefer analysis structured? Which competitors are in their tracked set? What corrections have they made over time? Short-term, this means coherence within a single session, so the assistant does not lose the thread of a multi-turn analysis. Long-term, this means persistence across sessions, so that the conversation on day 47 benefits from everything the user established on days 1 through 46.

Getting user memory right requires solving for explicit corrections specifically. A user who says "remove Brand X from our competitor set" needs that correction to propagate immediately and stay propagated, not just in their next query but in their 50th query. Most memory implementations handle the accumulation of new information reasonably well. The harder problem is updating or superseding existing information cleanly, and the hardest problem is ensuring that a correction made in session 8 does not silently degrade by session 20 because something related was ingested in the interim.

This is the failure mode that breaks trust most directly, because it surfaces during real work, in a client meeting or in a report, not in a QA environment.

Competitive intelligence memory. This is the layer most AEO tools are not thinking about yet.

An AEO analyst does not just have preferences. They work with a structured set of entities: brands, competitors, markets, product lines, query topics, model responses. These entities have relationships. Brand A competes with Brand B in Market C but not in Market D. A competitor gained ground in the healthcare vertical in Q2 but lost citation share in retail. These relationships change over time, and the competitive landscape that was accurate in Q1 may be materially different in Q3.

A competitive intelligence layer means the AI assistant reasons over a persistent entity graph rather than over a flat history of conversations. When a user asks which of their competitors are gaining ground in the segments they care about, the assistant traverses the graph. The answer is more accurate, more specific, and faster. When the competitive landscape shifts and a user says so, the graph updates without requiring a full re-ingest of historical data. Future queries resolve against the corrected state.

Entity resolution is a specific challenge here that is easy to underestimate. Analysts reference the same brand in many ways across many sessions: "our main competitor," "Brand X," "the company that just launched Y," a mis-spelled variant, an informal abbreviation. A memory layer without entity resolution creates a fragmented graph where the same entity appears as multiple disconnected nodes.

Answers that draw on that fragmented graph are wrong in ways that are hard to diagnose and easy to not notice until they cause a problem.

Organisational knowledge graph. This is the layer that converts an AI research assistant from a per-user tool into an organisational intelligence layer, and it is the layer nobody has shipped yet.

One analyst's understanding of how their product lines map to tracked query categories, which verticals matter most to their brand, what their internal naming conventions map to in external brand terms, should not live exclusively in that analyst's conversation history. It should compound into a shared graph that every user and every agent in that organisation can query. When a new analyst joins the team and asks the assistant about their brand's positioning in healthcare, the assistant should already know the positioning history, the Q3 repositioning, the competitor benchmarks the team has established over months of work, and the internal terminology the organisation uses. Not because the new analyst explained any of this, but because the organisational memory accumulated over all previous interactions is available to every subsequent one.

This is the layer that makes the technology compound rather than reset. Every interaction makes the graph more complete. Every analyst who uses the tool adds to the shared intelligence. The product gets more useful for the entire organisation over time, not just for the individual user who happened to be in the session.

Why building this in-house is the wrong bet for most teams

The obvious response to Profound's announcement for any AEO tool is to put memory on the roadmap. The less obvious thing is what getting it right actually costs in time and engineering focus.

A team can ship a version of session memory in a few weeks. Storing conversation history and surfacing it on the next session is not technically difficult. What is difficult is everything that happens to that version at scale, over months of real usage, with real users who change their minds and use inconsistent language and ask questions that reference context from six sessions ago without explicitly restating it.

Entity resolution, as described above, is one failure mode. But the others are equally consequential.

Temporal sensitivity is a failure mode that affects answer quality in ways that accumulate slowly. A piece of competitive information the user shared eight months ago should carry less weight in today's query than the same type of information from last week, particularly in a domain where the landscape changes continuously. A memory system without temporal sensitivity treats all stored information as equally current. The practical effect is that outdated context surfaces alongside current context, and the analyst has no signal about which is which.

Conscious forgetting is the failure mode that affects trust most directly. When a user corrects the system, "that competitor is no longer relevant to us," they expect the correction to hold. If it fails silently, perhaps because a related piece of older information was ingested after the correction and partially overrode it, the analyst notices during a real analysis. That is a trust-breaking failure. Recovery from that kind of failure is slow, and it is the kind of failure that ends up in a competitor's sales conversation.

Multi-session continuity is the hardest to test and the easiest to ship around. An implicit preference expressed across five conversations needs to be surfaced correctly in the sixth. No single session established the preference explicitly, so there is no explicit record to retrieve. The system has to synthesize it from distributed signals. Most memory implementations fail here, and the gap does not show up in any benchmark that evaluates single-session recall. It shows up in production, months later, when the system gives an answer that contradicts something the user thought they had established.

Getting these four failure modes under control on production data takes time. The teams who have done this work are the ones who have been in production long enough to see all four patterns emerge and iterate against them. In practice that is 9 to 12 months of real iteration, not 9 to 12 months of building.

Most AEO companies are SEO infrastructure businesses. They are excellent at crawling, parsing, indexing, and visualising data about how AI models respond to queries. Memory infrastructure is a different engineering discipline with different failure modes and a different iteration cycle. That distinction matters for how fast they can move and how much of their roadmap they are willing to redirect. A team that integrates a purpose-built memory layer compresses 9 to 12 months to weeks. That compression is the entire argument for not building from scratch.

What memory-native looks like in practice

The same analyst opens the assistant. She does not type context.

The assistant already has her competitive set, her preferred framing, the Q3 repositioning as a reference point, and the fact that she tracks citation share across ChatGPT, Perplexity, and Gemini specifically. She asks how her visibility shifted this quarter. The answer is structured the way she structured her last three analyses, because that preference is stored and retrieved. It benchmarks against her specific competitors, not the default leaderboard, because her competitive set is in the graph. It flags that one of her tracked competitors gained citation share in healthcare specifically, because the organisational graph has the vertical breakdown her team has built up over months of use.

She types a correction mid-conversation: "We stopped tracking Brand X last month, they pivoted out of our space." The graph updates. Brand X is removed from the competitive set. Every future query from every analyst on her team resolves without Brand X in the benchmark, because the organisational layer carries the correction forward.

Notice what is different here. She is not managing the product. She is doing analysis. The product is not a query interface she has to prime on every session; it is a research partner that accumulates context and gets more useful the more she uses it. The compound effect is not visible in a demo. It is visible at the 90-day mark, when the analyst realises she has stopped writing long preambles before her queries, and that the answers she gets are calibrated to her strategy in ways she can no longer imagine working without.

This is the product Profound is building toward with this week's announcement. This is what every other AEO tool in the market now needs to build toward as well.

The window

The AEO tools category has a specific competitive dynamic right now. Most of the serious players are well-funded, well-distributed, and serving overlapping customer sets. Differentiation between them is thinner than any of them would publicly say, which is why Profound's memory announcement carries more competitive weight than a typical feature launch.

Memory is not a feature that can be directly copied and shipped in a sprint. It is a product characteristic that compounds over time, and the compounding starts the moment the first user interacts with a memory-enabled product. A tool with six months of accumulated memory about a customer's competitive strategy is materially different from a tool that shipped memory last week. The gap between those two products is not visible in a feature comparison document. It is visible in a renewal conversation.

Two quarters is roughly the window before early-adopter advantage starts converting into retention advantage. The teams that ship memory in that window will have users who are invested in the tool in ways that go beyond pricing or feature comparisons. The teams that ship it later will be shipping into a market where some of their customers have already built that investment with a competitor.

At Maximem, we built Synap (https://www.maximem.ai/synap) specifically for this transition: an agentic memory layer for AI products that handles entity resolution, multi-session continuity, temporal sensitivity, and the organisational graph layer without requiring the host engineering team to solve those problems from scratch. Several AEO teams are already in integration conversations with us.

The work of getting the hard parts right on production data is done. What integration offers is compression: from 9 to 12 months of in-house iteration to weeks.

Every AEO tool is now one renewal cycle away from explaining why their assistant does not remember anything.