First-year reviews of corporate venture programmes almost always open with the same number: how many deals were done. It is the easiest figure to produce and the easiest to defend in front of a steering committee. It is also the number that carries the least information about whether the programme will still exist in three years. A programme can close eight investments in twelve months and be structurally dead. Another can close two and be in excellent health.
This article sets out what a first-year review should measure instead. Three indicators, none of them a count of transactions, carry more predictive weight than deal volume: how long a decision takes, whether the internal sponsors renew, and where the deals actually came from.
Why Deal Count Fails as a First-Year Metric
Deal count fails for a structural reason, not a philosophical one. In year one, the number of investments a programme closes is mostly a function of how much capital was allocated and how loose the investment criteria were. Both are decisions taken before the programme started. Counting deals therefore measures a budget line and a mandate, not the performance of the team executing them.
It also creates the wrong incentive at the worst possible moment. A team that knows it will be judged on volume at month twelve will lower its bar in month ten. The investments made in that window are the ones most likely to be written off, and they are made precisely when the programme has the least experience to price risk.
There is a second problem. Deal count is not comparable to anything. A corporate that made four investments cannot tell from that number whether it did well, because it has no internal baseline and the external benchmarks compare organisations with different mandates, different capital and different definitions of what counts as a deal.
Decision Cycle Time: The Metric That Predicts Everything Else
The single most informative first-year measurement is the time between first meaningful contact with a company and a documented decision, positive or negative.
It matters for two reasons. The first is competitive: in a contested round, a corporate investor that needs several months to reach a decision is not really in the round. Founders learn this quickly and stop bringing their better opportunities. The programme then experiences a slow degradation of the quality of what it sees, which is invisible in the deal count and fatal to the thesis.
The second reason is diagnostic. Decision cycle time is the only metric that aggregates every structural weakness of a programme into one number. A committee that meets quarterly, an approval chain that runs through a legal department with no venture experience, a mandate ambiguous enough that nobody is sure who can say yes: all of it shows up as elapsed days. When the number is bad, the cause is almost always in the governance design rather than in the team.
Two figures are worth tracking separately: the time to a negative decision, and the time to a positive one. A programme that says no quickly and yes slowly is behaving rationally under an unclear mandate. A programme that says no slowly is wasting the founder's time and its own credibility, and it will be remembered for it.
Sponsor Renewal: Whether the Programme Still Has Internal Buyers
A corporate venture programme is not funded by its returns in year one. It is funded by the continued belief of a small number of executives who agreed to sponsor it. The relevant measurement is therefore whether those sponsors are still actively engaged twelve months in, and whether any new ones have appeared.
This is measurable without ceremony. Which business units requested an introduction to a portfolio company. Which executives attended an investment committee they were not required to attend. Which internal budget holders volunteered a proof of concept. These are observable events, they can be counted, and they are recorded in a calendar rather than in a reporting system.
Sponsor attrition is the most reliable leading indicator of a programme being paused, and it precedes the formal decision by several quarters. A programme that has lost its internal buyers can still be closing deals right up to the week it is suspended, which is exactly why deal count gives no warning.
The counterpart is that a programme with growing internal demand can survive a poor investment year. Corporate venture programmes are rarely shut down for underperformance in a portfolio that is too young to have performance. They are shut down when nobody senior is left to defend them.
Proprietary Sourcing Share: Where the Deals Actually Came From
The third measurement is the share of the pipeline that reached the programme through a channel it built itself, as opposed to through an intermediary who also sent it to everyone else.
The distinction is not about pride of authorship. A pipeline that comes entirely from bankers, accelerator demo days and inbound decks is a pipeline that any competitor can reproduce at the same price, and it will be priced accordingly. A pipeline that comes from a corporate's own operating relationships, from its customers, from its technical teams and from the alumni networks around its sector is the only part of the sourcing function that a competitor cannot buy.
In year one, the absolute share will be low, and that is expected. What the review should look at is the direction of travel across the four quarters, and whether the proprietary channels that exist are maintained by someone whose job it is, or by whoever happened to have time.
This is also the metric most often reported dishonestly, because the definition is elastic. A useful discipline is to define the categories before the year starts, in the mandate agreement and to make the person who sourced the deal name the channel at the moment the company enters the pipeline rather than at the review.
Three Numbers That Look Useful and Are Not
Paper markups. A revaluation in year one reflects the entry price of the next investor, not the judgment of the programme. Reporting it as performance builds an expectation that the same line will keep rising, and it will not.
Portfolio company count. This is deal count with a different label. It answers the same budget question and carries the same incentive problem.
Pipeline volume. The number of companies reviewed measures how much noise reached the team. Without a qualification step, a larger pipeline is a cost, not an asset. If pipeline is tracked at all, it should be tracked as the share that passed a first qualification, and that ratio is more interesting than the total.
What the Year-One Review Should Actually Decide
A first-year review has one useful purpose: deciding whether the programme continues as designed, continues with a changed design, or stops. Framed that way, the three measurements map directly onto the decision.
Decision cycle time tells you whether the governance design works, and it is the one thing that can be fixed quickly without renegotiating anything upstream. Sponsor renewal tells you whether the programme still has a constituency, which determines whether it has a second year at all. Proprietary sourcing share tells you whether the programme is building an asset or renting one, which determines whether the third year is worth funding.
None of these require a reporting function, a data team or a new tool. They require a definition agreed before the year starts, which is a governance question rather than a measurement question, and which belongs in the mandate agreement alongside the fee and approval terms. Programmes that discover in month eleven that they never defined what they were going to measure will spend the review arguing about definitions rather than making a decision.
Frequently Asked Questions
Should returns be measured at all in year one?
They can be recorded, but they should not be used to decide anything. A portfolio built over twelve months has no realised outcomes and its unrealised marks reflect market conditions rather than selection quality.
What is a reasonable decision cycle time for a corporate investor?
There is no defensible universal figure, and any number presented as a standard should be treated with suspicion. The useful comparison is internal: the time the programme took in the fourth quarter against the time it took in the first, and the gap between its negative and positive decisions.
Who should own these measurements?
The programme itself, with the definitions fixed externally. When the team both defines and reports the metric, the definition drifts toward whatever the team is achieving.
Do these metrics apply to an outsourced programme?
They apply more strictly. When a programme runs through an external manager, decision cycle time and sourcing channel are the two variables the corporate is actually paying for, and both should appear in the mandate rather than in a quarterly slide. The cost comparison between the two models rests on the same variables.
Conclusion
Deal count survives as a first-year metric because it is easy to produce and nobody has to defend the definition. The cost of that convenience is that the review measures a budget decision taken a year earlier and learns nothing about whether the programme works.
Decision cycle time, sponsor renewal and proprietary sourcing share are harder to collect, mostly because they require agreement on what they mean before the year begins. What they offer in exchange is a review that can reach a decision: continue, redesign, or stop. A first-year review that cannot reach one of those three conclusions has measured the wrong things.