Granola: what the fund learns between updates.

A partner opens Acme and sees conversations placed next to updates, datapoints, tasks, and reports. One entry could read: "August 28, Founder check-in. Revenue is slightly behind plan; an enterprise pilot moved into next quarter; the founder requested two VP Sales introductions. 3 decisions, 2 commitments, 1 proposed metric observation." Each entry shows the date and type, owner and attendees, the Granola folder, a concise summary, key changes since the prior interaction, decisions, asks, and commitments, a link back to the Granola note, and whether PostMoney used the summary, transcript, private notes, or a combination.

The company record becomes more current without anyone treating a call as a formal reporting event. The research ranks it first: it is the basic portfolio memory everything else depends on.

The most operationally useful information in a meeting is often not a KPI. It is an agreement or obligation. PostMoney could identify four distinct objects from each conversation:

Approved items become PostMoney tasks with the meeting as their source, and a later conversation closes the loop: the introduction happened, the candidate declined, or the company no longer needs the help. The research calls this the feature most likely to prove immediate value.

A new note lands in a lightweight review inbox already matched to the likely portfolio company. PostMoney could propose the match from attendee email domains, known founder and executive emails, the calendar title, the Granola folder name, company names in the summary or transcript, and previous confirmed matches for the same attendees.

Uncertain matches wait in the inbox instead of being forced into the company record. PostMoney already treats unresolved ingestion and company reconciliation as a concept, so this fits. Funds should not have to reorganize Granola to use it, though a folder hierarchy makes matching easier.

Before a founder call, a partner gets a brief with the current KPI snapshot and trajectory, the most recent formal update, changes since the last conversation, prior company asks and fund commitments, open tasks and overdue follow-ups, unresolved questions, missing requested metrics, relevant health signals, and suggested questions based on changes in the record.

Granola already writes a brief from the calendar, past conversations, and optionally email. Recreating that would be redundant. Granola knows the calendar; PostMoney knows the portfolio. The research ranks this third because it closes the loop and provides frequent individual value.

Meeting history plus the structured record could show when the story changes: "The founder said the financing would close in July; the August meeting now points to the fourth quarter." "Pipeline was described as $3.2 million in the board meeting but $2.4 million in the written update." "Hiring was the top priority in the prior meeting; the latest call introduced a hiring freeze." "The company reported twelve months of runway, while the internal partner meeting discussed an urgent bridge." "Three conversations mention delayed payments, but the formal update does not discuss collections."

These are not necessarily errors. They may reflect different definitions, timeframes, sources, or precision, so PostMoney frames them as changes, tensions, or questions requiring review, never as accusations. The research calls this the strategic differentiator.

Open question: what would make users trust a change or contradiction detected from spoken conversation?

Founders state numbers in meetings: "ARR is about $4.2 million now." "We have ten months of runway." PostMoney could capture these as proposed observations that distinguish actual versus forecast, exact versus approximate, current value versus reporting-period value, and company statement versus internal fund estimate.

Spoken metrics may be approximate, forward-looking, misheard, missing a time period, or stated by someone other than the responsible executive. A meeting-derived number is reviewed, compared, and cited. It never silently overwrites a canonical KPI.

Open question: how frequently are useful metrics stated verbally before they appear in writing?

Meeting metadata could answer how the fund is covering its portfolio: which companies have gone quiet, who actually holds each relationship, when anyone last spoke with the CEO or CFO, and where coverage disappeared after an internal staffing change. The strongest experience highlights gaps and context: "No one has recorded a conversation with Acme in 74 days. Its last update raised a runway concern, and two fund commitments remain open."

The goal is portfolio continuity and support coverage. This is explicitly not a meetings-per-partner leaderboard, which the research says has little value and creates perverse incentives. Absence of a note also does not prove no conversation happened, and coverage views must say so.

One partner meeting covers ten companies. PostMoney could split it into company-specific slices, cross-portfolio observations, fund-level decisions, follow-on and reserve considerations, and partner assignments, while keeping the whole meeting intact as one interaction. For IC, it could preserve the decision, alternatives considered, conditions, supporting and dissenting arguments, and the facts relied upon.

Over time this becomes a decision journal that answers "Why did we decline the follow-on?" and "What changed between the June and August portfolio reviews?" The research calls it the most valuable and the most sensitive work, and says it should follow the simpler single-company workflows rather than lead them.