The VC Sourcing Analyst Playbook: A Week in the Life
A week in the life of a VC sourcing analyst: the Monday list refresh, mid-week verification and outreach, Friday attribution, and the metrics a sourcing analyst owns.
Key Takeaway
The sourcing analyst is the engine room of outbound venture, and the role is more systematizable than most funds admit. This playbook walks a real week: Monday watchlist refresh from leading indicators, Tuesday verification pass, Wednesday outreach block, partner meeting prep, Friday attribution and list hygiene, plus the metrics a sourcing analyst owns end to end and the automation that scales one analyst into a pipeline that feels like a team.
The sourcing analyst job exists because partners' attention is the scarcest resource in a fund. The analyst's output is a small number of high-quality meetings per week; everything else the role involves, list-building, verification, CRM hygiene, is instrumental to that output. This playbook is one full week, written for the analysts running it and the emerging managers who are the analyst.
Monday: the list refresh#
The week starts with data, not email. Refresh the watchlist from every leading source: referrals logged over the weekend, accelerator batch updates, and signal systems. The core artifact is the ranked list of companies worth attention this week; for users of this site, the weekly startups to watch is exactly this artifact, generated from the 350+ organization panel's acceleration data.
Two Monday rules: first, cap the list at what the fund can actually engage this week (a list of 200 is a lie; 15 is a plan). Second, write the one-line hook per company now, because the hook is what survives into Wednesday's outreach. A company whose engineering acceleration crossed threshold is a hook; "looks interesting" is not.
Tuesday: verification#
Verification is where analyst judgment earns its salary. For each Monday candidate, the pass is: is the signal real (baseline-relative, not a hack-week artifact, the heuristics in the signal vs noise guide), is the stage context right (last round date, typical interval to next, the stage math), and is there a warm path (shared connection, the etiquette in the warm intros guide).
Expected output: the 15-name Monday list becomes 3-6 verified candidates with hooks, stage context, and intro paths mapped. Kill rate below 50 percent means Monday's signals are too loose; above 90 percent means you are over-filtering and leaving early sight on the table.
Wednesday: outreach block#
Outreach is a block, not a background activity. Warm first (intros requested through the mapped paths), cold second (evidence-led, two minutes to read, the best practices format). The analyst's cold email should lead with verifiable work: a shipped product, a growing open-source project, a measured acceleration pattern. Evidence converts; adjectives do not.
Track sends, replies, meetings booked, by channel. Weekly volume targets vary by fund size; the ratio to watch is reply-to-meeting, because it prices your hook quality.
Thursday: partner prep and meetings#
Meetings the analyst takes directly (first-pass screens) plus prep memos for partner meetings: one page, the hook, stage context, the verified evidence, the open questions. A good memo writes the two questions the partner should ask, not a summary of the deck. The deal pipeline stages explainer covers where memo-writing sits in the funnel.
Friday: attribution and hygiene#
The unglamorous half of the week that makes every other half measurable. Log outcomes against sources (channel, signal, referrer) so Monday's list gets smarter; age the pipeline (anything past 90 days in stage advances or exits, the discipline in the pipeline explainer); update the CRM or spreadsheet with the week's exits and reasons. Friday is also when the analyst reviews the scorecard: meetings per week by channel, watchlist conversion, reply rates.
The metrics a sourcing analyst owns#
- Sourced meetings per week, by channel.
- Watchlist-to-meeting conversion (signal quality).
- Reply rate on outreach, by hook type.
- Time from signal to first meeting (the speed metric leading indicators move).
- Source attribution of funded deals, rolled quarterly.
These five numbers, honestly kept, are the difference between a sourcing operation and sourcing activity. The emerging manager playbook covers the same loop at solo scale, and the sourcing channels overview explains why each metric maps to a channel decision.
The automation that scales one analyst#
The repeatable parts of the week are increasingly automatable, and the honest 2026 stack: list generation from public data (GitHub acceleration, hiring, releases) is fully automatable, as this site's existence proves; verification is human judgment plus machine pre-chew (the acceleration-doubled-against-baseline check is a query, not an opinion); outreach drafting is assisted, sending is human; attribution is mechanical once logging is habitual. The analyst's irreducible core is exactly the part machines cannot do: deciding which three of fifteen deserve the fund's reputation this week. The AI in VC deal sourcing guide covers the assistant landscape without the hype.
Key takeaways#
The sourcing analyst week is a loop: refresh, verify, reach out, meet, attribute. The loop's value compounds through Friday's logging, not Wednesday's volume. Own five numbers, cap the list, write hooks not summaries, and automate the mechanical half so the judgment half gets your full attention. Run the loop for two quarters and the fund has what no vendor sells: a sourcing instrument calibrated to its own thesis.