Corporate venture deals stall on strategic fit more often than on financial return. The blocking question is usually whether a business unit would actually adopt the technology, and it is answerable before the committee meets — by asking the unit's own operators rather than the sponsor who brought the deal in.
What is corporate venture capital?
Investment by an operating company into external startups, from the balance sheet or a dedicated fund. It differs from venture capital in that returns are only half the mandate.
The other half — strategic value to the parent — is what makes CVC diligence a different exercise rather than venture diligence with a different logo on it.
The funding source matters more than it appears. A balance-sheet program reports into a business function and inherits its priorities; a dedicated fund has its own governance and can hold a position the parent's current strategy does not favor. The second structure survives a change of chief executive better, the first is faster to deploy, and each produces a different failure mode.
Which two tests must a deal clear?
The fund's return test, which is broadly the venture question, and the parent's strategic test, which asks whether the business will actually use, sell or integrate what the company builds.
The two are usually assessed by different people on different timetables, and a deck built for the first frequently fails to address the second at all — a problem compounded where the category itself does not exist yet.
The timetables are the practical problem rather than the tests themselves. A fund committee meets on a schedule and a business unit responds to whatever is in front of it that quarter, so an approval requiring both is not one decision with two approvers but two decisions taken weeks apart. Anything that shortens the gap is worth more than a better argument.
Which test kills more deals?
Strategic fit, by a margin. Return cases are well understood and well argued by the time they reach a committee; adoption cases are frequently asserted rather than evidenced.
The specific failure is usually a business unit declining to commit operational attention, which is a different objection from disagreeing about the technology.
Naming the failure precisely matters because the two objections have different remedies. Disagreement about the technology is answered with evidence about the technology; unwillingness to commit attention is answered with evidence that the unit's own customers want it, or with a smaller first commitment. Treating the second as though it were the first produces more technical material and no movement.
What evidence does strategic fit need?
Evidence from the people who would adopt it — the parent's own operators, and the customers they serve. Market growth data answers the fund's question and not theirs.
That evidence is gatherable and it is rarely gathered, because it feels like internal politics rather than diligence.
The reluctance is understandable and expensive. Asking a business unit's operators what they would actually do feels like canvassing for support before a decision, and it is easy to defer. Framed as diligence rather than as persuasion — the same questions asked by a researcher rather than by the deal sponsor — it produces a more honest answer and is easier for everyone to agree to.
How do you gather both at once?
By scoping one research program against both tests from the outset. The customer conversations that support a return case can carry the adoption questions if they are designed to.
Running them sequentially — return case first, adoption case after the fund approves — means going back to a business unit that has already had the chance to decline once.
Designing one program for both also improves the return case rather than diluting it. Evidence that a specific set of customers would adopt the technology is a demand signal, which is what a venture case needs anyway, and it happens to be the same evidence the business unit is asking for. The two tests overlap more than the separate processes suggest.