Back to resources

AllocatorBase research note · Operating framework

How to measure capital velocity without invented benchmarks

Capital velocity is not a market average. It is the observed movement of a defined pipeline through documented decision stages, evidence, and next actions.

Updated August 2026 8 min read Operating guide

Methodology note

This is an operating framework, not an industry benchmark study. Cycle time and outcome data vary by strategy, vehicle, allocator mandate, decision process, market conditions, and the quality of a team’s underlying records. Use your own defined pipeline and documented criteria as the source of truth.

01 · Define the measure

Capital velocity is a control metric, not a promise.

A useful measure starts with a defined population: qualified allocator opportunities associated with a live strategy or vehicle. The measure then tracks whether those opportunities move through a stated operating model—with evidence—rather than whether the team generated a high volume of activity.

The point is not to compress every timeline. The point is to see where a pipeline is waiting, whether the wait is supported by a credible decision process, and which next action is owned. That makes an operating discussion possible before a stalled stage becomes a reporting surprise.

02 · The measurement record

Four fields are enough to begin.

01

Start date

Which documented event starts the clock: first qualified conversation, data-room access, or an IC-ready review?

02

Stage evidence

What evidence must exist before a prospect can move from research to active evaluation, diligence, or a decision path?

03

Elapsed time

How many days has each qualified opportunity spent in its present stage, and what is the stated next action?

04

Ownership

Who owns the relationship, the research standard, and the next action—and is that ownership visible to the team?

Add probability, fit, or engagement fields only when their inputs are documented and their use is reviewable. A score is a prioritization aid, not proof that an allocator will allocate.

03 · Build stages around evidence

Do not use activity as a proxy for progress.

A meeting, an opened email, or a copied contact record does not establish mandate alignment or decision readiness. Stage definitions should state the evidence required for progression: a relevant mandate indicator, a named decision process, a diligence request, a defined next step, or another internally agreed signal.

Stage questionExample evidence to recordWhat to avoid
Why is this allocator in coverage?Documented mandate, channel, strategy, or portfolio context.Treating firm size or a generic contact record as mandate fit.
What is the decision path?Known decision-maker, governance step, research finding, or diligence requirement.Assuming an introduction establishes decision readiness.
What moves it forward?A dated, owned next action with a stated purpose.Open-ended follow-up with no owner or decision hypothesis.

04 · Review velocity by segment

A blended cycle hides the operating question.

Review elapsed time within comparable allocator segments rather than relying on a single aggregate. Separate the pipeline by the factors that determine its work: allocator channel, strategy, geography, relationship posture, vehicle, or a team’s internal coverage tier. The aim is to identify the stage where the evidence standard or next-action discipline is failing.

When a segment is slow, treat it as a research question. Is the mandate assumption weak? Is the decision path unknown? Is the right owner missing? Or is the stage definition being used as a holding area? Those questions are more useful than comparing an internal pipeline to an unsourced market average.

05 · Establish a review cadence

Make the measurement operational.

Weekly

Review high-priority opportunities, missed next actions, and stage entries lacking evidence.

Monthly

Compare stage aging by allocator segment, strategy, channel, and relationship owner.

At decision points

Record the specific evidence that changed a priority, timing assumption, or coverage decision.

The measure should change the next review.

A capital-velocity metric is useful when it makes one stalled decision path visible, assigns one next action, or causes a coverage assumption to be revisited. It is not useful when it creates a generic benchmark with no relationship to the mandate, evidence, or data in the actual pipeline.

AllocatorBase

See the operating gaps before the next reporting cycle.

Review the Capital Formation Audit or inspect a public allocator record to see how evidence and next actions can be organized around a live raise.

Book a Demo