EIC Advanced is a stage-gated, demand-driven deep tech pilot. A strong proposal needs more than novelty: it must enter at the right maturity, benchmark the solution against the state of the art, involve users from the outset and turn a short Stage 1 project into evidence that can justify progression toward real-world development and uptake.
Ruthless separates Stage 1 validation and benchmarking from Stage 2 development and user testing, while keeping the selected Challenge and demand-side evidence central to the case.
Stage 1 proposals are assessed against Excellence, Impact and Quality and efficiency of implementation. Passing the thresholds is necessary but not sufficient because portfolio balance also shapes the final selection.
The proposal should define a compelling problem, show clear novelty against the state of the art and translate breakthrough claims into credible performance improvements that can be tested during Stage 1.
EIC Advanced expects potential for market creation or transformation, wider adoption and scale-up, plus credible attractiveness to users, industry, procurers or investors. User commitment is part of the technical de-risking story, not a late dissemination task.
The work plan, resources and applicant capacity must fit a short validation and benchmarking action. Access to testing infrastructure, measurable milestones and fast risk reduction matter more than a broad work programme that tries to do everything.
The common weakness is treating the pilot like a standard research grant. The proposal sounds ambitious but does not define the benchmark, user pull or fast evidence needed to justify the next stage.
The proposal is relevant to deep tech generally but not tightly aligned with the selected Advanced Innovation Challenge.
TRL 4 readiness is asserted without showing what has already been demonstrated and what remains uncertain.
Benchmarking is described as testing activity without a clear comparator, metric or decision threshold.
Letters of intent or user references are present but do not influence the validation plan or adoption logic.
The nine-month work plan spreads effort across too many objectives instead of reducing the uncertainties that matter most.
Stage 2 is described as automatic continuation rather than a new gate requiring stronger evidence, real-world readiness and user uptake potential.
Claims stay generic instead of naming actors, baselines, target values, timing, quantities or accountable owners.
Important claims rely on assertion instead of recognised references, comparable evidence or verifiable proof points.
The review focuses on whether the proposal can survive a fast, evidence-driven selection process rather than whether it reads like a polished generic innovation proposal.
Ruthless checks whether the selected Challenge, use case, starting maturity, user interest and access to testing infrastructure are clear and mutually consistent.
Findings surface vague comparators, weak metrics and feasibility claims that cannot generate decision-grade evidence within Stage 1.
The evaluation checks whether users, integrators, procurers or other stakeholders influence the technical validation, adoption barriers and value proposition from the outset.
The Priority Action Plan identifies what Stage 1 must prove so a later Stage 2 case can credibly support real-world development, testing, scale-up and market uptake.
Deeper context for teams preparing, reviewing or revising this type of application.
What the first EIC Advanced application wave reveals about extreme competition and why proposal differentiation must be evidence-led.
A practical guide to turning ambition into benchmarks, thresholds and measurable evidence that evaluators can assess.
Why stronger justification comes from traceable evidence and logic rather than adding more text to a weak claim.
Find the weak logic, evidence gaps and revision priorities while there is still time to change them.
We use essential cookies to make the site work. Optional cookies, such as analytics, are disabled by default. You can accept, reject, or configure your preferences.
See: Privacy Policy