Teahose.
SIGN IN
NEW HERE — WHAT TEAHOSE DOES
We read the entire AI & tech firehose — so you don't have to.
PODPodcastsAll-In, No Priors, Acquired…
NEWNewslettersStratechery, Newcomer…
PAPPapersPhysical AI research
PHProduct Huntdaily launches
VCInvestor ScoutSequoia, a16z, Benchmark…
CLAUDE DISTILLS →
7 reads, 30 sec each — free, 6 AM ET.
+ a live graph of the companies, people & themes underneath.
HOME/DATA DRIVEN VC/💥10 Takeaways from the DDVC Sum…
NEWS
// NEWSLETTER ISSUE
DATA DRIVEN VC

💥10 Takeaways from the DDVC Summit 2026

DATE March 26, 2026SOURCE DATA DRIVEN VCPARTICIPANTS ANDRE RETTERATH
// KEY TAKEAWAYS5 ITEMS
  1. 01Theme 1: The Agentic VC Firm Is Operational Today, Not Theoretical
  2. 02Theme 2: Data Infrastructure Compounds
  3. 03Theme 3: The VC Tech Stack Is Consolidating Around Category Winners
  4. 04Theme 4: The VC Interface Is Shifting From Dashboards to Conversational Consoles
  5. 05Theme 5: Non-Technical Team Members Are Becoming Builders
// SUMMARY

1. Key Themes

Theme 1: The Agentic VC Firm Is Operational Today, Not Theoretical

AI-powered, multi-step autonomous workflows are already being deployed across the full investment lifecycle — not just in experimentation.

"Current tools allow for 'agentic' workflows where AI handles multi-step processes like sourcing, screening, deal-flow management, research, legal drafting, or portfolio monitoring. Firms are already using these autonomous systems to manage daily investment routines and automate back-office functions. The future is now."


Theme 2: Data Infrastructure Compounds — Don't Chase Silver Bullets

The path to durable AI advantage in VC is built on clean, foundational data primitives — not flashy, all-in-one platforms.

"Alpha is achieved by investing in small, foundational data primitives that compound over time to create a unique firm edge. But most importantly, adoption requires change management and the right culture."


Theme 3: The VC Tech Stack Is Consolidating Around Category Winners

Firms are settling on known winners for commodity needs and reserving internal build capacity for proprietary differentiation.

"Avoid reinventing the wheel by purchasing established winners for standard needs like CRM (Affinity), entity matching (Foresight), or portfolio intelligence (Vestberry). Winners are evolving across categories; firms should buy what is available and only build what provides a proprietary edge."


Theme 4: The VC Interface Is Shifting From Dashboards to Conversational Consoles

The dominant software paradigm for VC is moving away from static dashboards toward AI-native, natural-language interfaces — with portability as a key feature.

"The industry is shifting from static, dashboard-heavy software to AI-native consoles where investors interact with data via natural language. This shift allows custom workflows to remain portable and independent of any single software provider."


Theme 5: Non-Technical Team Members Are Becoming Builders

"Vibe coding" — building tools through natural language prompts rather than traditional code — is democratizing software creation across every function in the firm.

"The bar for software creation has lowered, allowing anyone from accounting to legal to build tools using natural language and AI editors. Encouraging team prototypes provides engineers with clear 'living' specifications for building secure, scalable firm versions later."


2. Contrarian Perspectives

Perspective 1: Personal "Toothbrush" Tools Beat Enterprise Platforms

The conventional wisdom favors comprehensive, integrated platforms. The article argues the opposite: small, single-purpose tools built for individual workflows generate more adoption and better outcomes.

"Instead of all-in-one platforms, teams should build 'toothbrushes' = small, personal tools that do one specific job well. Hereby, professionals across the firm can transition from reactive roles to proactive strategic partners to founders and LPs."

The implication: enterprise VC software vendors selling monolithic suites may be structurally misaligned with how high-performing firms are actually organizing their workflows.


Perspective 2: Investors — Not Engineers — Should Own Workflow Prototyping

The prevailing assumption is that tech infrastructure in VC belongs to centralized engineering. The article argues that investor-led prototyping drives superior adoption precisely because it reflects individual investment "taste."

"Firms find that empowering investment teams to prototype their own solutions significantly increases adoption and better reflects individual investment 'taste.' While technical experts still manage core data infrastructure and security, firms find that empowering investment teams to prototype their own solutions significantly increases adoption."


Perspective 3: The Biggest AI Risk in VC Is Post-Investment, Not Pre-Investment

While most firms focus data sophistication on deal sourcing and screening, the article (via its sponsor) points to a blind spot: most funds revert to outdated tools once capital is deployed.

"Most funds use sophisticated data to find deals, then revert to 1990s spreadsheets to manage them. If your data strategy ends the moment the wire clears, you're only playing half the game. Don't let the alpha die post-investment."

This is substantiated by a framework described as "drawn from conversations with over 2,000 VCs."


3. Companies Identified

OpenClaw

  • Description: A VC workflow automation tool
  • Why mentioned: Featured in a live demo as a centerpiece example of how to "automate VC" with agentic AI
  • Quote: "How to automate VC with OpenClaw"

Affinity

  • Description: Relationship intelligence CRM
  • Why mentioned: Cited as an established category winner for CRM that firms should buy rather than rebuild
  • Quote: "Purchasing established winners for standard needs like CRM (Affinity)"

Foresight

  • Description: Entity matching and data infrastructure tool
  • Why mentioned: Named as a proven winner in the entity matching category within the VC tech stack
  • Quote: "Entity matching (Foresight)"

Vestberry

  • Description: Portfolio intelligence platform for data-driven VCs
  • Why mentioned: Cited as the established winner for portfolio management; also served as the newsletter's sponsor, with a playbook based on conversations with 2,000+ VCs
  • Quote: "Portfolio intelligence (Vestberry)"; "Drawn from conversations with over 2,000 VCs, it's a comprehensive, field-tested framework for data-driven portfolio management"

Goodwin

  • Description: Global law firm
  • Why mentioned: Listed as a summit partner, with the event covering "automating legals with AI"
  • Quote: "Thanks again to all speakers, participants, our partners Affinity, Foresight, Goodwin, and Originalis"

Originalis

  • Description: Legal tech / AI company (partner context)
  • Why mentioned: Listed as a summit partner alongside the legal automation theme
  • Quote: "Our partners Affinity, Foresight, Goodwin, and Originalis"

4. People Identified

Andre Retterath

  • Description: Author of the Data Driven VC newsletter; general partner at Earlybird Venture Capital (per newsletter context)
  • Why mentioned: Summit organizer and author distilling 10 takeaways from the DDVC Summit 2026
  • Quote: "Hi, I'm Andre and welcome to my newsletter Data Driven VC which is all about becoming a better investor with data and AI."

Maryama & Georgiy (last names not provided)

  • Description: Core team members behind the DDVC Summit
  • Why mentioned: Acknowledged by name for organizing the summit
  • Quote: "Thanks again to all speakers, participants, our partners...and our amazing team around Maryama and Georgiy - you rock!"

5. Operating Insights

Insight 1: Automate the "Crappy Work" First to Unlock Human Leverage

The clearest ROI from AI in a VC firm comes from eliminating low-value repetitive tasks — freeing investors for the relationship-intensive work AI cannot replicate.

"Investors should leverage automation for repetitive tasks like data entry and screening to free up capacity for high-value relationship building. By becoming 'builders' of their own workflows, team members can eliminate manual 'crappy work.'"

Tactical implication: Map your firm's daily workflows and identify the highest-volume, lowest-judgment tasks (e.g., CRM data entry, inbound screening, LP reporting drafts) as the first automation targets.


Insight 2: Connect Core Data Sources Directly to an LLM for an Analyst-Grade Command Center

Rather than building complex bespoke software, firms can create a powerful AI operating layer by simply wiring existing tools to a language model.

"By connecting core data sources like Slack, CRM, and email directly to an LLM, firms can automate high-level analyst tasks such as autonomous startup scouting, deep company research, and initial founder outreach. This approach allows the investment team to iteratively refine complex system behaviors through plain English feedback and persistent memory files rather than traditional code maintenance."

Tactical implication: Treat your LLM as the integration layer — not a standalone chatbot — to avoid expensive custom development while achieving agentic outcomes.


Insight 3: Security and Compliance Must Scale With Democratized Building

As non-technical team members begin building and sharing tools, the risk surface expands. Expert oversight of data exposure is non-negotiable.

"While AI lowers the barrier to building, exposing sensitive information to external models creates significant risk. Security and compliance must be managed by experts, especially when moving from personal 'toothbrushes' to shared firm-wide tools."

Tactical implication: Establish a data classification policy and AI usage governance framework before broadly enabling vibe coding across the firm — not after.


6. Overlooked Insights

Insight 1: Investor Prototypes as Living Specs for Engineering

A subtle but high-value workflow pattern buried in the article: investor-built prototypes aren't just useful in isolation — they serve as functional requirements documents for the engineering team to productionize.

"Encouraging team prototypes provides engineers with clear 'living' specifications for building secure, scalable firm versions later."

This reframes the role of rapid prototyping from a shortcut to a formal step in the product development cycle — reducing the translation loss between what investors need and what engineers build.


Insight 2: Workflow Portability as a Strategic Moat Against Vendor Lock-In

The shift to conversational, console-based interfaces carries a strategic implication that the article only briefly surfaces: independence from any single software vendor.

"This shift allows custom workflows to remain portable and independent of any single software provider."

As VC tooling consolidates (see Theme 3), firms that build their core logic in natural language against an LLM layer — rather than inside a proprietary platform — retain the ability to switch vendors without losing operational continuity.