Fourteen years in EU research funding, and enough EIC proposals run through our evaluation engine, has made one thing clear: the objections come up again and again. They're rarely about the science being wrong. They're about the proposal not pre-empting the exact questions an EIC reviewer is trained to ask.

EIC funding is built around high-risk, high-reward innovation — which means reviewers are actively looking for reasons a technically strong proposal still isn't EIC-shaped. Here are the ones that come up most.

"Why EIC, specifically?"

EIC evaluators are told to assess additionality: would this project happen anyway, on roughly this timeline, without EIC funding? A proposal that reads like a well-funded lab's natural next step — rather than a leap that private or national funding wouldn't otherwise take — invites exactly this objection. It's not enough to need money; you need to make the case that this specific risk profile is why EIC is the right instrument.

Fix: Name explicitly what conventional funding routes would not support about this project — the risk level, the timeline, or the ambition — and make that the spine of your Excellence argument, not a footnote.

A thin state-of-the-art delta

"Novel" and "innovative" appear in almost every EIC proposal; they mean nothing to a reviewer without a precise comparison. The proposals that score well name the two or three closest existing approaches and state, in concrete technical terms, what specifically changes and why that change was not achievable before now.

Fix: Build a short, explicit comparison table against the two or three nearest alternatives. If you can't fill it in precisely, your differentiation isn't sharp enough yet either.

Team composition that doesn't match the ambition

Pathfinder proposals are judged partly on whether the team can plausibly pursue a genuinely uncertain research direction — which needs scientific depth, not commercial packaging. Accelerator proposals are judged on the opposite failure mode: strong technical founders with no visible commercial, regulatory or go-to-market capability on the team, which reads as execution risk regardless of how good the technology is.

Fix: For Pathfinder, foreground scientific track record and prior high-risk work. For Accelerator, make sure the team page visibly answers "who takes this to market" — not just "who built it."

IP and freedom-to-operate treated as a formality

A one-paragraph IP section asserting that "freedom to operate will be confirmed" reads as unexamined risk, not as a minor administrative point. Reviewers scoring Accelerator proposals in particular are looking for evidence that IP strategy has actually been thought through against known competitors and prior art — not promised for later.

Fix: Name the IP position you actually hold today — filed, pending, trade secret, or none yet — and what the plan is to close the gap, with a realistic timeline attached.

Market sizing without a bottom-up basis

Large addressable-market figures sourced from a single market report, with no bottom-up build from actual customer segments and unit economics, are one of the fastest ways to lose credibility on an Accelerator application. Reviewers see this pattern often enough to discount top-down numbers by default.

Fix: Build your market size from the customer segments you can actually name and reach first, then show how that expands — not the other way around.

None of these are science problems. They're the gap between what a technically excellent team assumes is obvious and what a reviewer, reading cold, needs stated explicitly. Closing that gap is usually a matter of days, not months — but only if you catch it before submission.