How to prep for an ESA Spark Funding defense?
On 20 January, shortlisted applicants will step into the ESA Spark Funding defence: a fast, focused pitch of 10 minutes, followed by 5 minutes of Q&A. By the time you enter the room (or join online), the evaluation board will already have read your proposal—so the defence isn’t a repeat of every detail. It’s your chance to re-cap the essence with confidence and make the panel feel that your project is real, feasible, and commercially relevant.
Your jury will typically include representatives from ESA Technology Broker Czechia, local authorities from the Ministry of Transportation, and ESA’s Commercialisation team—and may also include an industry expert. This mix matters: you’re not only speaking to technical evaluators, but also to people who will challenge your market logic, customer credibility, and delivery readiness.
In those 10 minutes, your mission is crystal clear: explain what problem you’re solving, present your solution, and make the technology transfer unmistakable. ESA Spark is about transfer that creates value—either space → terrestrial (a space-developed product, component, software, hardware, or know-how adapted for a new Earth application) or terrestrial → space (a terrestrial technology adapted for space use with clear commercial potential). If the panel has even a small doubt about what exactly is being transferred and why it matters, you’ll spend your Q&A trying to rescue clarity instead of strengthening confidence.
And commercial proof is not optional. Be ready to show who your customers are, what conversations you’ve already had, and why the market will pay attention. Letters of Interest carry weight—attach them wherever possible (even email exchanges count when done professionally). Your customer involvement should also be visible in your plan: referenced in your work packages and clearly reflected in your TEB (Technical/Technology Evaluation) story.
The Q&A will almost certainly probe: team competence (can you genuinely deliver, with the skills you claim?), technology transfer clarity (any ambiguity will be tested), work packages and timing (is the plan realistic?), budget (is it credible?), and your competitive landscape (do you understand who else is out there and why you still win?). The best defences feel calm because the team has rehearsed, aligned on roles, and can answer without improvising or overpromising.
A practical note: the defence is usually hybrid. Joining online won’t directly affect scoring, but attending in person can signal commitment. If your project includes a technology provider partner, bring them—especially if they hold key know-how or credibility. Finally, join/arrive at least 5 minutes early, test your setup, and treat the defence like what it is: a short, high-impact moment to prove your project is ready to move from proposal to reality. Results are typically communicated within two weeks (pass, pass with conditions, or fail)—so it’s worth preparing as if every minute on the day counts.
