The venture capitalist's notes are the raw material of investment intelligence. A founder meeting where a GP asks sharp questions and generates useful insights but captures nothing is a conversation; the same meeting with structured notes becomes intelligence that can be compared against other companies, surfaced when a similar company appears six months later, and reviewed when assessing whether the thesis at investment time is holding.
The four templates here address the most consequential VC note-taking contexts: founder meetings that generate company and founder intelligence, market research that needs dated captures, board meetings where decisions and concerns need a record, and reference calls where what people say and don't say is the primary data.
Template 1: Founder Meeting Notes
The founder meeting generates two distinct types of intelligence: company intelligence (what the business is doing, how it's performing, what the strategy is) and founder intelligence (how the founder thinks, communicates, handles challenge, and assesses their own situation). Both are important; most meeting notes capture only the former.
FOUNDER MEETING NOTES
Date: [Date of meeting]
Company: [Company name]
Stage: [Current funding stage + ARR/traction]
Meeting type: [ ] First meeting [ ] Diligence [ ] Portfolio board [ ] Portfolio check-in
[ ] Follow-on evaluation [ ] Reference/expert
CONTEXT:
How this meeting came about: [Referral source / cold / portfolio company / conference]
What I knew going in: [Prior context — had they submitted a deck? Did I know the sector?]
My investment thesis relevance: [How this fits or doesn't fit current investment focus]
COMPANY INTELLIGENCE:
Business overview:
What they do: [Clear description — product + market + customer]
Stage and traction: [ARR / customers / growth rate / team size]
Funding: [Total raised + last round details]
Strategy and differentiation:
How they see their differentiation: [What they say makes them different]
Their view of competition: [Who they name + how they describe the competitive landscape]
My assessment of the competition reality: [Do I agree with their competitive framing?]
Roadmap and priorities:
What they're focused on: [Near-term priorities]
What they're not focused on that I'd expect: [Gaps in what they're addressing]
Metrics and performance:
Key metrics shared: [What they shared + the specific numbers]
What they didn't share that I'd expect: [Information gaps — may be significant]
Trend direction: [Are things improving, stable, or declining?]
FOUNDER INTELLIGENCE:
Communication style:
How they presented: [Prepared vs. adaptive; clear vs. technical; confident vs. defensive]
How they handled questions they didn't like: [Engagement level with hard questions]
Insight quality:
Did they have genuine market insight or surface-level knowledge?
Specific evidence: [What they said that was or wasn't evidence of depth]
Counter-intuitive insights they offered: [The most interesting non-obvious thing they said]
Self-awareness:
How did they characterize their challenges?: [Did they identify real problems or minimize them?]
How did they talk about their team and what they're missing?: [Are they honest about gaps?]
How did they talk about the competition?: [Honest assessment or dismissive?]
Resilience and adaptability:
Evidence of resilience: [What have they navigated or how have they adapted]
Evidence of learning: [How have they changed approach based on what they've learned]
QUESTIONS ASKED AND ANSWERS:
Q: [Question I asked]
A: [Summary of their answer — notable specifics or vagueness]
Q: [...]
A: [...]
CONCERNS:
Primary concern: [The biggest concern coming out of this meeting]
Secondary concerns: [Other things to investigate]
ASSESSMENT:
Investment excitement level: [ ] High [ ] Moderate [ ] Low [ ] Pass
Next step: [What happens next — second meeting / introduce to partner / pass with note / watchlist]
Pass reason (if passing): [Specific reason]
DB UPDATE:
[ ] Company logged in CRM with current status
[ ] Deal stage updated
[ ] Pass reason documented (if passing)
[ ] Watchlist criteria set (if watchlisting)
The "what they didn't share that I'd expect" field surfaces significant information gaps. The founder who doesn't mention customer churn when discussing retention, or doesn't mention burn rate when discussing the financing plan, may have a good reason (they're not tracking it separately, it came up in a different part of the conversation) or may be avoiding the topic. The explicit check is what makes the gap visible.
The "how they handled questions they didn't like" is one of the most predictively useful fields in founder assessment. Founders who engage genuinely with hard questions — who acknowledge the challenge, share what they're doing about it, and show they've thought about the risk — demonstrate the board engagement that makes venture relationships functional. Founders who deflect, minimize, or redirect from difficult questions demonstrate how they'll behave in board meetings when things are hard.
Template 2: Market and Sector Research Notes
Market research captured without dates, without explicit source identification, and without investment implications documented is hard to use when the research is needed six months later.
MARKET AND SECTOR RESEARCH NOTES
Date captured: [Today's date]
Sector/Market: [What market or technology area this research covers]
Research type: [ ] Analyst report [ ] Expert interview [ ] Industry publication
[ ] Conference presentation [ ] Regulatory document [ ] Academic research
[ ] Founder/operator conversation [ ] Company materials
SOURCE:
Source name/author: [Publication + author if applicable]
Publication/presentation date: [When this was originally published — may differ from capture date]
Source credibility: [Is this a credible source for this type of claim?]
Archive URL: [archive.org backup — especially important for web content and regulatory documents]
CONTENT CAPTURED:
What this source covers: [Summary of the main content]
Key claims with supporting data: [The most important points + the evidence cited]
Market size or growth claims: [If any — with the methodology noted if available]
Named companies and their positions: [What companies are mentioned + how they're characterized]
INVESTMENT INTELLIGENCE EXTRACTED:
What this tells us about market dynamics: [Competitive structure, value chain, market evolution]
What this implies for investment thesis: [Specific implications for thesis development or validation]
What this tells us about investment timing: [Early / right timing / late signals]
What questions this raises: [What else needs to be researched]
CONFIDENCE IN THIS SOURCE:
Why I trust this source: [Basis for credibility]
What I'd verify before using in an IC memo: [What needs primary source confirmation]
Currency risk: [Any reason this might be outdated at time of capture?]
KB UPDATE:
[ ] Sector KB updated with intelligence from this source
[ ] Thesis updated based on new intelligence
[ ] New questions added to research agenda
Template 3: Board Meeting Notes
Board meeting notes for portfolio companies serve two purposes: creating a record of board decisions and action items, and capturing the company intelligence that builds over time into the portfolio company KB.
BOARD MEETING NOTES
Date: [Date of board meeting]
Company: [Company name]
Meeting type: [ ] Regular board [ ] Special board [ ] Observer [ ] IC meeting
ATTENDANCE:
Board members: [Who was present]
Observers: [Who observed]
Management: [Founders + executives who presented]
Absent: [Who wasn't there]
BUSINESS CONTEXT (from management presentation):
Performance since last board: [Key metrics + trend vs. plan]
Key developments: [What happened at the company since last board]
Strategic focus: [What management is focused on]
WHAT THE METRICS TELL ME (my read, separate from what management says):
Are things improving, stable, or deteriorating: [My assessment]
The most important metric trend: [What matters most]
What's missing from the management narrative: [What they're not discussing that seems important]
BOARD DISCUSSION:
Topic 1: [What was discussed]
Key perspectives: [What different board members said]
My contribution: [What I added to the discussion]
Topic 2: [...]
DECISIONS MADE:
[ ] [Decision]: [Details — what was decided, who agreed, any conditions]
[ ] [...]
Note: distinguish decisions from discussions. Items discussed but not decided remain open.
CONCERNS RAISED:
[ ] [Concern]: Raised by [who] — response from management: [what they said]
Resolution: [ ] Addressed to my satisfaction [ ] Needs follow-up [ ] Ongoing concern
MY OPEN CONCERNS:
[Concern I have that wasn't raised or wasn't adequately addressed in the meeting]
ACTION ITEMS:
[ ] [Company action]: [Owner at company] by [date]
[ ] [Board action]: [Who] by [date]
[ ] [My action]: [What I committed to] by [date]
SUPPORT PROVIDED:
Introductions offered: [Who I offered to connect them with]
Resources offered: [What other support I offered]
FOUNDER INTELLIGENCE UPDATE:
What this board meeting added to my understanding of the founders: [Any new observations]
Update to founder assessment: [Any change to prior assessment]
COMPANY TRAJECTORY ASSESSMENT:
Current trajectory: [ ] Ahead of plan [ ] On plan [ ] Behind plan [ ] Pivoting
Confidence in the team for the next phase: [My current confidence level + basis]
Key risk for next board: [What I'll be watching]
KB UPDATE:
[ ] Portfolio company KB updated
[ ] Founder pattern KB updated (if applicable)
[ ] Investment pattern KB updated (if applicable)
The "what the metrics tell me (my read, separate from management narrative)" is the intellectual discipline that prevents board engagement from becoming passive acceptance of management framing. Management presents metrics in the context they choose; the board member reads metrics in the context of the full company trajectory and board history. Maintaining a separate record of the investor's read — before and after the management presentation — ensures the board engagement includes independent assessment.
Template 4: Reference Call Notes
Reference calls generate the most sensitive and consequential intelligence in VC: firsthand assessments of founders and key executives from people who've worked with them. The notes need to capture both what was said and what wasn't said.
REFERENCE CALL NOTES
Date: [Date of call]
Reference: [Role description — NOT name in the document; track identity separately]
Reference type: [Prior manager / peer / direct report / co-founder / customer / investor]
Company context: [How they worked with the founder — which company + approximately when]
How connected: [Who made the introduction]
MY ASSESSMENT OF REFERENCE QUALITY:
Credibility: [Is this a credible, knowledgeable reference for the assessment we need?]
Objectivity: [Any reason to suspect bias — positive or negative?]
Confidence to be candid: [Did they seem comfortable sharing honest assessments?]
ABOUT THE FOUNDER:
Performance summary:
How would you describe [Founder]'s performance in your time together?
Reference answer: [Their actual words — direct quotes preferred for significant assessments]
Strengths they highlighted:
What are they exceptional at?: [Specific strengths named + examples]
Weaknesses or growth areas:
What would you say they need to develop?: [Specific areas + examples]
My observation: [Did they hesitate here? Did the answer feel complete?]
Leadership and team:
How do they build and lead teams?: [Evidence of leadership style]
How do people respond to working for them?: [Team dynamics evidence]
Integrity:
Any situations where their integrity or judgment was tested?: [How they describe this]
Anything that gave you pause?: [Explicit check for concerns]
Working with them in a board or investor context:
How do they receive feedback and challenging input?: [Evidence of coachability]
How do they handle pressure or adversity?: [Evidence of resilience]
WHAT WASN'T SAID:
Questions that got vague or redirected answers: [What they avoided]
Areas where the reference was notably less enthusiastic: [What generated hesitation]
What I'd expect a strong reference to say that this one didn't: [Gaps in the endorsement]
OVERALL REFERENCE ASSESSMENT:
Strong endorsement: [ ] Yes [ ] Partial [ ] Weak [ ] Effectively negative
Would this reference work with the founder again: [Yes / No / Maybe + what they said]
What this reference added to my assessment: [What changed or was confirmed]
What this reference raised as a concern: [Any new concerns]
DB UPDATE:
[ ] Reference intelligence added to deal file
[ ] Founder assessment updated based on reference
The "what wasn't said" section is the most under-appreciated part of reference call note-taking. References who choose not to say negative things directly often signal through omission: they praise specific areas enthusiastically and become vague or general when asked about others; they answer questions about strengths with specific examples and questions about weaknesses with generalities. The gaps in the endorsement are often as informative as what's explicitly said.
Key Takeaways
-
Founder meeting notes capture two distinct intelligence streams. Company intelligence (what the business is doing + the metrics + strategy) and founder intelligence (how they think, handle hard questions, assess their own situation, and demonstrate insight). Most meeting notes capture only the former; the latter is often more predictive.
-
"What they didn't share that I'd expect" surfaces significant information gaps. The founder who doesn't mention a metric I'd expect them to track or the topic I'd expect them to address may have a good reason or may be avoiding the subject. The explicit check makes the gap visible rather than invisible.
-
Market research notes lead with the date of original publication, not the capture date. Market intelligence from a report published two years ago has a different currency than intelligence from a report published last month, even if captured on the same day. Both dates matter for assessing currency.
-
Board meeting notes separate the investor's read from the management narrative. Management presents metrics in the context they choose; the independent "what the metrics tell me" section ensures the investor's independent assessment is captured alongside the management presentation.
-
Reference call notes document what wasn't said, not just what was. The most significant reference call intelligence is often in the omissions: the area where the enthusiastic reference becomes vague, the question about weaknesses that gets generic answers, the endorsement that's specific on some dimensions and general on others. What isn't said is often what the reference is unwilling to say.
Conclusion
Four note-taking templates structure the most consequential VC research and relationship contexts: founder meeting notes that capture both company and founder intelligence with explicit fields for information gaps and how founders handle difficult questions; market research notes that lead with the capture date and original publication date and extract investment implications; board meeting notes that separate the investor's independent read from the management narrative and distinguish decisions from discussions; and reference call notes that explicitly document what wasn't said alongside what was. The templates are only useful with the discipline that surrounds them: the CRM update after every founder meeting, the KB update after every market research session, the portfolio company KB update after every board meeting, and the deal file update after every reference call.
See also: Web Clipping vs. Bookmarking.