Loading...
Emerging Manager VC · persona overview
How a $40M Fund I emerging manager landed in 3 oversubscribed AI-infra rounds in 2026 by sourcing from engineering signals 6-8 weeks before bankers circulated decks.
A two-person investment team at a $40M Fund I emerging-manager VC had committed to closing 12 investments over 18 months. They lacked the sourcing volume of larger firms but had strong founder-engineer reputation. Their differentiated thesis: invest in pre-round AI-infra companies before the warm-intro network surfaced them. Code-side sourcing was the operational engine that made this thesis executable.
Every Monday morning, the team reviewed the weekly First Look digest. Filtered by sector (AI infra, developer tools, AI/ML) and stage (pre-seed to Series A). Flagged 6-10 companies showing engineering acceleration above the +50% threshold.
For each flagged company, opened /signal/[slug] to read engineering momentum, contributor influx, and language-bias signals. Cross-referenced against the company's homepage, careers page, and founders' Twitter/LinkedIn.
For top 3 candidates each week, used /sector/[slug] hubs to position the company against tracked sector peers. Read the why-it-matters and what-we-track editorials to ground the partner-meeting discussion.
Used /fund/[competitor]/portfolio pages to map which a16z, Sequoia, and Index Ventures portfolio companies adjacent to the candidate. Avoided rounds where multiple large funds had already committed.
Outreach email referenced the engineering-acceleration data ('we noticed your contributor count went from 8 to 23 in the last 4 weeks') instead of generic 'I want to learn more.' Reply rate ~35% vs ~5% baseline for cold-warm outreach in this segment.
Over 12 months, the team closed 9 investments — 7 of them were companies first surfaced via engineering-acceleration signals. 3 of the 9 rounds became oversubscribed (a16z, Sequoia, Index Ventures led after the emerging-manager team's investment), validating the pre-round sourcing thesis. The Fund's LP report cited code-side sourcing as a differentiated motion.
No. This is an illustrative composite of workflows we observe in onboarding and demo conversations. Names, specific deals, and identifying details are omitted by design. The structure of the workflow (what URLs the persona uses, what questions they ask, what action they take) is representative.
Emerging Manager VC. For the full persona-specific overview, see /for/emerging-managers.
A weekly Monday First Look digest review filters by sector and stage for engineering acceleration above a +50% threshold; each flagged candidate is deep-dived on /signal/[slug] before founder outreach. The cadence, not headcount, is the engine.
In this composite, outreach referencing specific contributor-count acceleration (for example, 'your contributor count went from 8 to 23 in 4 weeks') drew roughly 35% reply rates versus a ~5% cold-warm baseline — a 5–7× lift.
9 closes over 12 months, 7 of them first surfaced via engineering-acceleration signals; 3 of the rounds became oversubscribed after larger funds (a16z, Sequoia, Index Ventures) followed in, validating the pre-round sourcing thesis.
Corp Dev Director
How a hyperscaler Corp Dev director moved from sector-level scouting to a 4-target shortlist in 3 days using engineering-signal data.
PE Operating Partner
How a PE Operating Partner used engineering-signal benchmarking to surface a portfolio-company performance gap before it became a board issue.
Non-Engineer Tech VP
How a non-engineer VP Platform consolidated 4 observability vendors to 2 by grounding the decision in publicly observable engineering velocity.
Technical Founder
How a technical founder used engineering-signal data to position the fundraise narrative, identify the 4 most-aligned investors, and pre-empt the 'how are you different from X' question.
Academic Researcher
How an empirical-finance PhD candidate used the published methodology and open dataset to validate a venture-finance leading-indicator hypothesis.
Tech Journalist
How a senior reporter at a major tech publication grounded a sector trend story in publicly observable engineering-signal data — without coordinating with company PR.
The free Acceleration Watch runs on the same engineering signal these workflows use — five breakout teams every Sunday, in plain English, no code-reading. Onboarding to any paid tier includes a guided walkthrough of the workflow that matches your role.