How to Run a Weekly VC Pipeline Review

A weekly pipeline review helps a venture team decide which opportunities deserve attention now. In a small fund, the meeting has to turn source information into explicit decisions and follow-ups, because the same people are often managing sourcing, diligence and portfolio work.

The review works best when deal stages, owners and next actions are maintained between meetings. The venture pipeline guide explains the difference between process stages, current statuses and work still to be completed.

Prepare a decision-oriented queue

Before the meeting, identify new qualified deals, waiting founder responses, overdue internal commitments, diligence blockers, upcoming investment committee reviews and opportunities with changed financing deadlines. Each record should show its owner, last substantive activity, open questions and proposed next action.

A founder uploading a new model counts as material activity because it can answer a financial question. A record opened or reformatted by an analyst leaves the substantive status unchanged. Keep this distinction visible when reviewing stalled deals.

A 30-minute agenda for a lean fund

First five minutes: urgent founder and introducer commitments

Review missed responses and deadlines that affect the firm's reputation or ability to join a round. Assign an owner and reply date, including a clear decline when the investment case has already failed.

Next ten minutes: active diligence and evidence gaps

Look at questions that could change the investment decision. Identify the missing report or reference, what the team will do with it, and when the work should finish. Move an opportunity only after it meets the intended stage gate.

Next ten minutes: partner decisions and upcoming approvals

Surface deals whose owners need guidance, including processes ready for investment committee. Confirm which decisions can be made now and which require a formal memo or additional transaction evidence.

Final five minutes: owners, dates and closure

Read back the commitments and record them against the relevant deal. For deferred items, establish the triggering event that should bring the deal into a future review.

An example decision register

Example, for a fictional process: Deal A, Active Diligence, customer reference outstanding, associate owns interview request by October 14; Deal B, First Meeting completed, partner decides by October 13 whether to begin deeper work; Deal C, Declined, investment owner records the rationale and sends a founder response by October 12. These dates illustrate an action format, rather than a standard service level.

Review pipeline health between meetings

Once the immediate decisions are cleared, inspect the dealflow metrics that explain where opportunities accumulate. Conversion and time-in-stage are useful when cohort definitions and the process's expected pace are explicit.

Avoid allowing a weekly meeting to become an exercise in updating field labels. A decision log and a well-maintained next-action queue are more valuable than another presentation containing old statuses.

Using Treto for the review

Treto's Pipeline Intelligence is designed to surface stage movement, blockers and next actions from maintained investment context. The team can review supporting material and prior conclusions before accepting a proposed change. Any founder communication or investment decision follows the firm's own approval process.

Questions investors ask

What should every weekly VC pipeline review decide?

The meeting should establish what changed, which deals require a decision and what the next action is for each open blocker. Named owners and deadlines turn the discussion into work. The fund can then review overdue commitments between meetings without rebuilding the same context each week.

How should a small VC firm handle stalled opportunities?

Identify whether the delay comes from waiting on a company, internal analysis or an approval owner. Record the next meaningful event and a follow-up date. If the current evidence no longer supports the thesis, a documented decline closes the process and preserves the rationale for future reference.