Someone on your team asks: "Why did we go with flat pricing instead of
usage-based?" You half-remember the conversation but you can't recall the
specific argument that tipped it. Git log says pricing: ship v1 at €15/mo,
which tells you nothing. Slack is a wall of noise.
This is where Memo earns its keep.
The workflow
Three steps. Takes under a minute.
- In any Claude session (CLI, Desktop, browser), ask:
"Pull the full reasoning behind our pricing decision from any session that discussed it."
- Memo searches your past sessions semantically — not just keyword, actually understanding "pricing" and "reasoning behind a decision".
- Claude gets back the real transcripts: your typed-out thinking, the back-and-forth with Claude, the specific comparison that killed the usage-based option.
What makes this different
The naive version is "search my notes." The thing is, you probably didn't take notes. You just talked to Claude, worked it out, and shipped. The reasoning lives in those sessions, not in a doc somewhere.
Decision archaeology recovers the reasoning from the work itself — the unfiltered record of how you actually thought through the problem. Not a sanitized retrospective, not a half-remembered Slack thread. The real material.
When it's saved me
Last month I had to defend a choice to replace a core dependency. I knew we'd discussed the alternatives but couldn't remember which specifically. One query later I had the transcript: three alternatives, the exact benchmark that disqualified two of them, the licensing concern that disqualified the third. Took the person asking about 20 seconds to be satisfied; would have taken me an hour to reconstruct from scratch.
The best part is that none of this was saved on purpose. I didn't write a decision doc. I just worked, and Memo kept the record.