At a glance
At a glance
What AGILE changes
The Programme for Agile and Rapid Defence Innovation (AGILE) is a €115 million instrument intended to move emerging and disruptive technologies, including civilian technology adapted for defence, from lab to field in months rather than years. Challenges will reflect capability needs identified with Member States. Council and Parliament reached political agreement on 15 July 2026, Parliament adopted its position at first reading on 6 October 2026, and the Commission expects the programme to be operational on 1 January 2027.
Three design choices matter for anyone preparing to apply. An eligible SME can participate individually; a consortium is not a general requirement. Funding can reach 100% of eligible costs. And the Commission has set a four-month time-to-grant target, alongside fast-track access to testing and experimentation facilities and dedicated matchmaking with defence primes.
For an SME entering defence, that is a route centred on its own solution, with far less of the partnership assembly that EDF demands. The detailed conditions will arrive with the work programme and calls, and any specific opportunity has to be assessed against those.
Applying alone does not mean delivering alone
The simplification is real, but look at where AGILE places its value: testing, integration, and uptake. Those are the steps an SME cannot perform by itself. The test runs in someone else’s facility, on someone else’s data, under someone else’s security regime. Integration happens inside a prime’s programme. Uptake depends on a buyer’s decision.
Under EDF, the consortium agreement forces those relationships into writing before submission. AGILE’s single-applicant route takes away the obligation but not the need. And a four-month award followed by a one-year programme leaves no slack to discover, after the grant, that the facility is booked, that the contact who was so helpful cannot authorise access, or that the prime’s innovation team will sponsor the trial while nobody owns what happens next.
The practical conclusion is simple. The commitments EDF forces you to document, AGILE leaves you to secure for yourself, and earlier.
Three things to settle before you apply
First, define what a successful test should enable. Start from the operational benefit rather than the technical metric. For a data or AI solution, improved accuracy matters only through the task it helps a user perform: identify the decision that should improve, the conditions in which the solution must work, and the limits the user needs to understand. Then name the decision the evidence should support. Is it a further operational trial, an integration activity, or a procurement conversation? Agree who will review the result and what they need to see. That lets the SME design the demonstration around evidence someone will actually use.
Second, separate expertise, access and authority. They are three different contributions, and they rarely sit with the same person. An expert can help design a test. A facility operator can explain what is technically possible. The person able to approve the activity or commit resources may be somewhere else entirely. A short expression of interest is the right tool here: what the organisation can provide, who can authorise it, when it is available, and which data access or security permissions are needed. Where an arrangement remains provisional, record the assumption, name who can confirm it and set a decision date, so that a slipped testing window is visible to the people responsible for the plan and budget.
Third, prepare the prime’s side of integration. AGILE’s matchmaking gives primes a reason to engage early, and the useful question to put to them is what happens after a successful demonstration. Which programme would receive the technology? Who owns integration, who accepts the result and who supports it afterwards? An innovation team can sponsor a trial; the receiving programme carries the interfaces, the delivery commitments and the support arrangements. Bringing both to the table produces evidence both sides can use, and gives the SME an honest view of the distance between a good test and operational use. Purchasing remains a separate decision.
Put it in the plan
These conversations should leave your team able to state, on a single page:
The level of detail should fit the project. The point is that every participant understands their commitment, and that the schedule and budget reflect it. AGILE compresses the timeline, so the invitation to decision-making arrives sooner. Bring the right people into the conversation before the application, and let the plan follow.
At iMotivat, our work spans bid writing and PMO, which in practice means connecting what a proposal promises with the responsibilities, dependencies and decisions needed to deliver it. If you are preparing for AGILE’s first calls, that work can start now.
What AGILE changes
The Programme for Agile and Rapid Defence Innovation (AGILE) is a €115 million instrument intended to move emerging and disruptive technologies, including civilian technology adapted for defence, from lab to field in months rather than years. Challenges will reflect capability needs identified with Member States. Council and Parliament reached political agreement on 15 July 2026, Parliament adopted its position at first reading on 6 October 2026, and the Commission expects the programme to be operational on 1 January 2027.
Three design choices matter for anyone preparing to apply. An eligible SME can participate individually; a consortium is not a general requirement. Funding can reach 100% of eligible costs. And the Commission has set a four-month time-to-grant target, alongside fast-track access to testing and experimentation facilities and dedicated matchmaking with defence primes.
For an SME entering defence, that is a route centred on its own solution, with far less of the partnership assembly that EDF demands. The detailed conditions will arrive with the work programme and calls, and any specific opportunity has to be assessed against those.
Applying alone does not mean delivering alone
The simplification is real, but look at where AGILE places its value: testing, integration, and uptake. Those are the steps an SME cannot perform by itself. The test runs in someone else’s facility, on someone else’s data, under someone else’s security regime. Integration happens inside a prime’s programme. Uptake depends on a buyer’s decision.
Under EDF, the consortium agreement forces those relationships into writing before submission. AGILE’s single-applicant route takes away the obligation but not the need. And a four-month award followed by a one-year programme leaves no slack to discover, after the grant, that the facility is booked, that the contact who was so helpful cannot authorise access, or that the prime’s innovation team will sponsor the trial while nobody owns what happens next.
The practical conclusion is simple. The commitments EDF forces you to document, AGILE leaves you to secure for yourself, and earlier.
Three things to settle before you apply
First, define what a successful test should enable. Start from the operational benefit rather than the technical metric. For a data or AI solution, improved accuracy matters only through the task it helps a user perform: identify the decision that should improve, the conditions in which the solution must work, and the limits the user needs to understand. Then name the decision the evidence should support. Is it a further operational trial, an integration activity, or a procurement conversation? Agree who will review the result and what they need to see. That lets the SME design the demonstration around evidence someone will actually use.
Second, separate expertise, access and authority. They are three different contributions, and they rarely sit with the same person. An expert can help design a test. A facility operator can explain what is technically possible. The person able to approve the activity or commit resources may be somewhere else entirely. A short expression of interest is the right tool here: what the organisation can provide, who can authorise it, when it is available, and which data access or security permissions are needed. Where an arrangement remains provisional, record the assumption, name who can confirm it and set a decision date, so that a slipped testing window is visible to the people responsible for the plan and budget.
Third, prepare the prime’s side of integration. AGILE’s matchmaking gives primes a reason to engage early, and the useful question to put to them is what happens after a successful demonstration. Which programme would receive the technology? Who owns integration, who accepts the result and who supports it afterwards? An innovation team can sponsor a trial; the receiving programme carries the interfaces, the delivery commitments and the support arrangements. Bringing both to the table produces evidence both sides can use, and gives the SME an honest view of the distance between a good test and operational use. Purchasing remains a separate decision.
Put it in the plan
These conversations should leave your team able to state, on a single page:
The level of detail should fit the project. The point is that every participant understands their commitment, and that the schedule and budget reflect it. AGILE compresses the timeline, so the invitation to decision-making arrives sooner. Bring the right people into the conversation before the application, and let the plan follow.
At iMotivat, our work spans bid writing and PMO, which in practice means connecting what a proposal promises with the responsibilities, dependencies and decisions needed to deliver it. If you are preparing for AGILE’s first calls, that work can start now.
June 20, 2026 | Governance
June 9, 2026 | Governance
June 20, 2026 | Governance
June 9, 2026 | Governance
© 2026 iMotivat B.V – All Rights Reserved
© 2026 iMotivat B.V – All Rights Reserved
