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

Does this fund look like a fund run by the kind of firm the firm says it is.

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 configuration inputs against what the declared stage would expect, and counts how many sit where they should.

  • 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.

Both resolutions are legitimate and they mean different things. A firm that has classified itself a stage ahead of where it operates can restate the declaration, which is often the honest fix. A firm that genuinely is where it says it is can move the configuration. The instructive case is the third one: a firm that has grown into a new stage without noticing, whose fund still looks like the last one. That is the case this subscore exists to catch, and it is invisible from inside.

A question this raises: how fast do venture firms invest the money they raise

The honest answer starts with the fund's own terms. A fund declares an investment period, typically several years, during which it makes new investments; after it, remaining capital supports the existing portfolio. That declared period is a commitment to LPs, and it is the input the model reads. There is no industry-wide correct pace, and the published figures that circulate vary enough by strategy and vintage that quoting one would suggest a precision that does not exist.

The more useful answer is that pacing is best treated as a diagnostic rather than a target, and the two most direct statements of that come from opposite ends of the tooling question.

Fred Wilson puts it plainly: a firm should not manage to a pacing number, it should manage to the opportunity set it sees. But pacing is a great thing to track in the rearview mirror, by quarter and year, by dollars and by deals, and by new names against follow-ons. The purpose is self-awareness about whether the firm is getting out over its skis or its heels.

Tactyc, from the modelling side, treats pacing as one of the core workflows of data-driven managers, tracking whether the fund is on track in capital deployed and in portfolio count both in total and by stage, and reading it for course corrections. Same instinct: measure it continuously, do not manage to it.

The new-versus-follow-on split Wilson names is the most diagnostic cut of the three, because it distinguishes two different ways of being off pace. A firm deploying quickly on new names is building the portfolio faster than planned. A firm deploying quickly on follow-ons is concentrating into what it already owns. Those have opposite implications and the same headline number.

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.

Take it to your own fund

Run the model on your own fund.

The platform reads the Colibrí Architecture model against your own firm and funds.