Before the Next Founder Meeting, Read the Previous One

You last met the founder in June. It is now September. You remember liking the team, a discussion about hiring and a runway figure. You are less certain which hires were already approved, what the figure assumed or what you promised to send afterward.

Opening the latest deck gives you today's account of the company. Reading the previous conversation gives you a starting point for understanding how it got there.

This is where AI meeting notes can help venture investors: recovering the earlier plan so the next conversation can examine what changed.

A changed number needs its original assumptions

Consider an illustrative pair of meetings. On June 4, Lena says her company has twelve months of runway under its current hiring plan. On September 3, she says it has ten months, having postponed two planned hires.

A record containing only "runway: ten months" loses the plan you discussed in June. An automated flag that calls the two figures contradictory is unhelpful, too. Three months have passed, and the hiring plan has changed.

Keep both statements and their dates. Then ask which expenses moved, which assumptions stayed the same and how the current estimate was calculated. The earlier conversation makes that question more precise. It gives Lena a chance to explain the change instead of repeating the company introduction.

The same approach works for a product launch, a key hire or a planned customer expansion. You want the earlier expectation, the later update and the explanation connecting them.

Knowing what was said is one part of knowing the company

A transcript can establish what Lena said in a meeting. It cannot establish the company's cash balance.

That boundary matters because information acquires authority as it is copied. A spoken estimate becomes a meeting summary, then a memo bullet, then a figure someone cites without its date or assumptions. Keeping the source attached lets the next reader see what the figure represents.

In your notes, distinguish the founder's account from material you checked separately and from your own interpretation. If you reviewed a signed customer agreement, record which agreement and when. That document establishes something different from a payment receipt or a customer reference call. A single label such as "verified" loses too much of that detail.

Your reading of the situation deserves its own space as well. "The postponed hires may extend the sales timeline" is a question to investigate. Lena's statement that two hires were postponed belongs alongside it, with the source, so you can tell where the question came from.

Founders face a related problem when they combine investor feedback with customer interviews. We explore that in when three meetings become the wrong roadmap.

Bring back the open thread

Before the September meeting, a short preparation note could look like this:

Last discussion: June 4. Lena described twelve months of runway under the hiring plan discussed that day.

Plan to revisit: Two proposed hires and the timing of the next product release.

My outstanding action: Send the hiring reference I offered.

Question for this meeting: What changed in the hiring plan, and how did it affect spending and delivery?

Afterward, add the dated update and link the relevant passage. Keep the June entry; it is still part of how the plan developed.

There is a relationship benefit here as well as an analytical one. The founder should not have to remind you of every prior discussion or of an introduction you offered. Recovering your own promises is part of preparing properly.

An assistant can search for those threads, but it needs a concrete request. "Summarize everything about this company" invites a broad account. "Find our last discussion of the hiring plan and anything I offered to send afterward" asks for the material you need before the meeting.

Use AI to find the passage you want to question

You can record a founder discussion with the Draki app alone. The bracelet makes capture easier to keep available between meetings, and you can turn it off whenever the conversation calls for it. The current public app sends audio through Draki to OpenAI over Wi-Fi after your permission, and does not automatically separate or recognize speakers.

Connecting an external assistant is optional. Draki uses a custom MCP connection with AI assistants that support remote MCP, subject to their account requirements and settings. With your permission, the assistant can search shared conversation text and context. Once you have confirmed the person, it can retrieve the available history for that person.

For the June and September example, you can ask:

Find my June and September conversations with Lena about hiring and runway. Show the relevant passages with their dates. Identify the assumptions she described and the questions we left open.

Read the passages before writing your agenda. The answer should help you locate the source, particularly if the assistant says an issue was never discussed. It may simply be absent from the recordings available to it.

Our AI memory assistant guide looks at this ability to retrieve earlier conversations. For an investor, a worthwhile test is whether the assistant can bring you back to the last unresolved question with enough detail to ask a better one now.

To use Draki for that continuity between founder meetings, join the waitlist.