What does your product collect
that nobody ever reads back?

Most products have a perfect record and no memory. Millions of rows of what customers asked for, complained about, abandoned and came back for, and the product itself knows none of it.

I build the layer that fixes that. Not a chat box: the brain layer, the product memory underneath whatever you already shipped. Conversations that close into episodes, beliefs that carry confidence and evidence, memories that decay on a schedule so the system stays honest, and a record of what it doesn't know yet so it can tell you.

I've built it twice in production, in two products with opposite shapes, and I write about the parts nobody has written down. If you want the long version first, read how I taught my ten-year-old product to dream.

How this usually starts

With a diagnosis, not a proposal. Before anyone can quote you honestly, one question has to be answered: does the same person come back? If yes, the memory points at your customer. If no, it points at your operator, because they're the one who returns every day. Getting that backwards builds a beautiful system that remembers the wrong human, and I've come close to doing it myself.

So the first conversation is me looking at what your product already stores and telling you what it already knows and isn't using. I don't put a price on this page because the scope genuinely varies: a system with three years of conversation history and one with three months are not the same job, and pretending otherwise would just mean quoting you wrong.

Probably a good fit

• Your product has been live for years and the database is the most valuable thing you own.
• Customers keep asking the same questions and your system answers each one like it is the first time.
• You have an AI feature that works, and you can feel that it is a commodity.
• Something in your product failed quietly for weeks because nothing was technically broken.

Probably not

• You want a chatbot in the corner of your app. That is the least interesting thing you can do with this, and plenty of people will build it for you.
• Your product launched last month. You need customers before you need memory.
• You want someone to pick a vector database for you. That is not the hard part and it is not where the value is.

The one thing I need from you

Not a form. Answer four questions in an email and I'll tell you what I see, whether or not we end up working together. The button below opens your mail client with the questions already in it.