Portfolio Efficiency

Are you configured for the fund you are actually on

Lifecycle stage is self-declared, and this subscore reads whether the fund's configuration agrees with the declaration. A mismatch says the two disagree; it does not say which one is wrong, and the instructive case is a firm that grew into a new stage without noticing.

The question

Do the fund’s size, company count and ownership targets fit its declared lifecycle stage?

A General Partner confirms whether the firm is at Conviction, Cadence, or Continuity, and the platform never transitions a firm on its own. This subscore reads whether the fund's configuration is consistent with the declaration.

Four indicators, counted

The subscore checks four inputs against the model’s expectations for the declared stage. Those are calibration choices, not universal requirements for a venture firm. This check assesses the plan’s shape; it does not measure deployment pace.

  • Industry scope

    How broad a mandate the stage would expect.

  • Portfolio count

    How many positions the stage would expect.

  • Ownership target

    How concentrated those positions would be.

  • Fund size

    What scale of fund the stage implies.

Counting rather than averaging is deliberate. It means the subscore moves in visible steps and that a General Partner can see exactly how many of the four are in place, rather than reading a smooth number that hides which input is the problem.

Why a mismatch is not a verdict

Stages are different frontiers rather than a ladder, and the model does not treat a newer firm as a weaker one. A mismatch here says the declaration and the configuration disagree; it does not say which one is wrong.

A flagged result can prompt a review of the declared stage, the fund plan, or both. It can also reflect a deliberate choice the model does not capture. Start by explaining that choice rather than changing inputs simply to improve a score.

What this subscore does not read

It does not read pace. This subscore is about the shape of the configuration against the declared stage, not about how quickly capital is going out of the door. Deployment pace shows up elsewhere: the platform records it over time, and the deployment phase a fund has reached does change how the engine weighs its subscores, so a fund is not read the same way in its first year as in its seventh.

It also cannot see the firm's reasoning. A firm deliberately running a fund that looks like an earlier stage, because it is rebuilding after a partner change or testing a new thesis, is doing something coherent that the configuration cannot express.

Sources

  • PacingFred Wilson, AVC, October 2019Against managing to a pacing number and for tracking it in the rearview mirror, by dollars and deals and by new names and follow-ons.
  • Top Six Workflows of Data-Driven Venture ManagersTactycTreats pacing as a tracked workflow: capital deployed and portfolio count in total and by stage, read for course corrections.

Bring it into your own fund

Explore your fund’s design.

Bring your capital, portfolio and team into one view, and see where the plan may need a closer look.