Two friends, twenty years of
shipping, and one Google Doc

Before Recall

We've been friends for years. Both of us spent 20+ years building products for huge brands, just at different companies. Design, development, shipping things that millions of people actually use. Different paths, same obsession with making things.

When ChatGPT dropped, something clicked for both of us at the same time. We went all in. Claude, ChatGPT, Gemini, Cursor, every tool, every day. We weren't just using AI to code. We were building tools with AI, tools for AI, tools that made AI better. Some we shipped. Some are still sitting on our machines. We couldn't stop building.

But the more we used these tools, the more the same problem kept hitting us.

The problem nobody was solving

You start a new session and your AI has no idea who you are.

What you're working on. What decisions your team already made. What broke last time. So you explain it. Again. Every single time.

It wasn't just the repetition. It was the waste. Every team builds up knowledge as they work. Decisions, patterns, mistakes, context. And all of it just disappeared between sessions.

One day Steve typed into Slack: “Has anyone seen this before?”

Ray had. Three weeks ago. But that fix lived in a Claude session that was long gone. By the time he saw the message, Steve had already spent an hour figuring it out himself.

That kept happening. Not just between us, but across every team we worked with. Someone would solve a problem in an AI coding session, and the knowledge would vanish when the session ended. A week later, another dev would hit the same wall. Burn the same time. Find the same answer.

The fixes existed. They were just trapped in sessions nobody else could see.

And duplicated work was only half of it. We started noticing something worse: devs on the same team making changes that directly conflicted with each other. One dev would refactor an API endpoint while another was building a feature on top of the old version. Neither knew what the other was doing. By the time they figured it out, someone's work had to be thrown away.

It wasn't a communication problem. These were good teams. They just had no way to see what their teammates were doing in real time across AI sessions.

Building Recall with Recall

We took everything we learned from Goldfish (our first memory product for coding sessions), made it secure, and rebuilt it so entire teams could share what they learn automatically. No extra work. No Notion docs nobody reads. No Slack threads nobody searches.

Recall runs silently alongside your AI coding tool. When a session ends, it automatically captures decisions, fixes, and patterns. Next time any teammate hits a similar problem, their AI already knows the answer.

And it's not just for devs. A PM can connect Recall to Claude Desktop and ask “what did the team ship this week?” or “what's blocking the auth migration?” and get real answers from real sessions. No standups required.

One dev solves it. Every dev knows it.

We've been using Recall every day to build Recall itself. That's not a gimmick. It's the whole point. We built the tool we needed, and we use it every single day. Going back to coding without it genuinely feels broken.

What's next

Recall is free. Not a trial. Not a freemium bait-and-switch. Free. We want teams beating on it and telling us what's missing.

We're two friends who've been making products for over two decades, who got obsessed with AI, and who couldn't stop building until the thing we needed existed. Now it does.

Try it. Tell us what sucks. That's how we make it better.