Designing a Venture Vehicle That Can Actually Deploy

Most first vehicles are designed backwards. A target size is chosen because it sounds credible, a standard structure is copied because it is standard, and the thesis is written to justify both. Deployment is treated as a downstream execution detail rather than the constraint that should have determined every prior decision.

A vehicle that cannot deploy on schedule fails twice: once on returns, and again on the manager's ability to raise a second one.

1. Verify pipeline before fund size

Fund size is an output. The inputs are the number of investable opportunities the manager can actually source per year at the target stage, the median check, the reserve ratio, and the deployment period.

Verification means a named pipeline with real companies, real stages, and an honest read on which of them the manager could plausibly win — not a market-size argument. If the verified count implies a smaller fund, the smaller fund is the correct fund. Managers who force the larger number end up either drifting from thesis or concentrating unintentionally, and both are visible to LPs at the next raise.

2. Align thesis, geography, stage, check size, and reserves

These five parameters have to be mutually consistent, and in practice at least one is usually out of line.

1. 01

   Thesis versus geography

   A narrow technical thesis inside a single metro rarely produces enough qualified deals. Either widen the footprint or widen the stage band deliberately, rather than discovering the shortfall in year two.

2. 02

   Stage versus check size

   Writing meaningful checks at a stage where rounds are small creates ownership the founder will resist and follow-on obligations the reserve model has not funded.

3. 03

   Reserves versus concentration

   A reserve policy written after the first three investments is a policy written by circumstance. Decide the ratio, the trigger, and who approves the exception up front.

4. 04

   Deployment period versus sourcing capacity

   A three-year deployment period assumes a sourcing engine running at full pace from month one. Most managers spend the first year raising, which effectively compresses deployment into two.

3. Let deployment determine the vehicle

Structure should follow the deployment pattern the strategy actually implies.

• A closed-end fund suits a defined vintage, a bounded deployment window, and an exit horizon LPs accept.
• An evergreen structure suits recycling, longer holds, and strategies where the exit timing is genuinely unknown.
• SPVs suit concentrated, opportunistic positions and are an honest way for a first-time manager to build a track record before a blind pool.
• A syndicate suits deal-by-deal conviction and an investor base that wants selection rights.
• Hybrid and public-private structures suit mandates carrying policy or regional obligations alongside a return requirement — and are the structures most likely to fail on governance if it is improvised.

4. Governance and economics under institutional review

Institutional LPs decline vehicles at the final stage for reasons that have nothing to do with the thesis: valuation policy that is not written, allocation and conflicts handled by custom, key-person terms that do not reflect who actually does the work, reporting that cannot be produced quarterly without heroics.

Fee and carry structure should be defensible against comparable vehicles and, more importantly, should fund the operating capability the strategy requires. A management fee that cannot pay for sourcing at the promised pace is a structural problem disguised as discipline.

5. Operating capability before first close

Sourcing, diligence, portfolio support, and reporting are the machinery. They should exist — as documented process, defined roles, and working systems — before capital arrives, because the deployment clock starts at close and the first year sets the pace narrative for the entire fund.

Across $200M+ in venture funds and capital vehicles created and deployed, the consistent pattern is this: the vehicles that deployed well were designed around what the manager could actually see and act on, and the ones that struggled were designed around what the market said a fund of that type should look like.

Vehicle count reflects prior leadership and advisory work across confidential mandates. No specific vehicles, LPs, or returns are disclosed or implied.