What Explosive Growth Taught Recall About Pricing Knowledge Work

Today’s conversation features the founder of Recall, a company that quietly emerged from a pivot by learning what to build and why alongside disciplined, hyper-efficient resource planning.

Recall didn’t start out “hot,” but it’s become one of the more instructive examples of how enterprise companies are actually built in this market. There are practical lessons here for enterprise buyers and operators alike, from pricing and sales motion to how customers can become a true innovation engine rather than just a feedback channel.

As always, let us know what you think and please reach out if you have feedback.

- Dave

Knowledge workers know the problem: despite endless meetings, documents, and discussions, teams repeatedly lose context, re-litigate decisions, and fail to compound what they have already learned.

That is where David Gu [LinkedIn] and Recall come in. Recall is building an organizational memory layer that captures conversations and decisions so teams can retrieve why something happened, not just what happened.

In this conversation, David covers:

• Why modern teams systematically forget their own thinking
• How Recall evolved from note-taking into durable organizational memory
• What buyers actually trust, and do not trust, in AI-generated context
• How Recall fits alongside existing tools instead of replacing them
• Why usage-based pricing maps better to knowledge work than seats

If you care about scaling knowledge work without scaling chaos, this interview breaks down why most teams stall as they grow, how memory quietly becomes a bottleneck, and what it takes to design systems that actually compound learning over time.

Introductions and Origins

Dave Ambrose (00:14)

David, thank you so much for doing this. I am excited to have you here. To start, can you give the audience an overview of Recall, what you are building, and the problem you are trying to solve?

David Gu (00:29)

Yeah, absolutely. Recall is about helping teams remember. If you look at how most organizations work today, an enormous amount of important thinking happens in conversations, meetings, discussions, reviews, but very little of that knowledge actually compounds. People forget why decisions were made, context disappears, and teams end up re-hashing the same things over and over again. We started Recall to capture that context and make it usable over time.

Dave Ambrose (01:12)

What was the original insight that pulled you into this?

David Gu (01:15)

It came from watching teams take notes constantly but never actually use them again. Notes are written, stored somewhere, and then forgotten. The real issue is not capturing information, it is retrieval and relevance. When you need context, you do not remember where it lives or what matters.

From Notes to Organizational Memory

Dave Ambrose (03:02)

So Recall did not start as a fully formed organizational memory product?

David Gu (03:06)