News
How I Prepare a FEADER Project When There’s No Call Yet
- 13/04/2026
- Aids
A FEADER project is not prepared when the submission window opens: it is built beforehand, with technical criteria and a technical report capable of defending the investment. From my experience at AGB Ingeniers, I have seen that the difference between “wanting to invest” and “having real chances” lies in defining the objective well, requesting coherent quotes, and organizing the documentation in time. Getting ahead is not rushing: it is arriving ready when the call becomes active.
By Ana González, CEO and Agricultural Engineer – Industrial consultant in energy efficiency and grant management at AGB Ingeniers
There is a phrase I hear every year in agri-food companies: “when FEADER is published, we’ll look into it.” I understand it, because day-to-day operations in an industry leave little room to stop, plan, and organize paperwork. But I also know, because I have seen it too many times, that this phrase is the boundary between competing with real chances or arriving too late.
A FEADER project is not built at the moment the window opens. It is built beforehand. In fact, the best applications I have supported from AGB Ingeniers did not succeed because of “luck” or because they were “paying attention,” but for something much simpler: they were prepared while others were still starting to improvise.
I am writing this article from my own methodology, exactly as I work with companies when there is still no published call. This is not theory. It is a way of thinking about an industrial project with logic, technical coherence, and one very clear central idea: if the investment makes sense, it must be prepared as if tomorrow you were asked to defend it.
When there is still no FEADER call, the smart work consists of defining the project, organizing the documentation, and building a defensible technical report so you arrive with an advantage when the window opens.
The first step is not the “grant”: it’s the investment
Before talking about FEADER, I always ask the same question: what do you really want to improve in your plant? Not what you want to buy, but what you want to achieve.
In agri-industry, almost every investment responds to a real need: increasing capacity without losing control, reducing waste, improving traceability, stabilizing quality, automating a critical point, modernizing industrial refrigeration, reducing consumption, or strengthening food safety. The investment is usually clear inside the company. What is not always clear is how to turn that need into an explainable and defensible project.
That is why the first task, when there is still no call, is to translate intention into a concrete industrial objective. Because FEADER does not usually reward shopping lists. It rewards projects with meaning.
The key: building a clear technical story
This is where the difference lies between a correct file and a competitive one: the technical story.
I approach it as a narrative that must be simple and verifiable. What problem exists today? What impact does it have on costs, quality, time, or risk? What solution is proposed and why is it the right one? What changes in the process? How will the result be measured?
When a company hasn’t done this exercise, something usually happens: the investment is good, but the project is not understood from the outside. And in grants, the evaluator is not inside your factory. They need you to explain it with industrial logic.
At AGB Ingeniers we work a lot on that “translation” because that is where the project is won. And the best part is that it can be done without a call. In fact, that’s when it makes the most sense, because it can be done calmly and with criteria.
Quotes: requesting them properly is part of the project
One of the biggest mistakes I see is requesting “quick” quotes when there is already urgency. Generic quotes, with vague concepts, no breakdown, unclear scope, or difficult to compare. Those quotes may be enough to buy, but many times they are not enough to build a solid file.
When there is still no call, the approach changes: quotes are requested with technical intent. You define clearly what will be done, what is included, what will be integrated, what will be installed, and what will be commissioned. Then the quote arrives aligned with the technical report, not in conflict with it.
This saves a lot of time later. And above all, it avoids the typical “this doesn’t match” moment when there is no longer any margin.
The invisible part: checking whether the plant is “ready”
There are companies that have a clear investment and a perfect quote… and still get blocked. Why? Because the factor nobody wanted to look at appears: outdated technical documentation, installations that are not organized, expansions not reflected, machinery changes without documentation, or administrative requirements that have been left for “later.”
When there is still no call, it is the ideal time to review this without urgency. Not to complicate things, but to avoid the company running two races at the same time when the window opens: preparing the file and fixing the house from the inside.
Planning the justification from minute one
Let’s answer what many companies ask: “and then what?”
In grants, the project doesn’t end when it is awarded. An equally important phase begins: implementation and justification. And most surprises happen there, when evidence is missing or what was promised cannot be demonstrated.
That is why, even without a call, I always prepare with the company a basic idea of how it will be justified: what documents will exist, what evidence will be kept, what indicators will be measured, who will sign what, and how impact will be demonstrated. It doesn’t have to be perfect; it has to be thought through.
Why this method works (and why I defend it)
Because it changes the dynamic. The company stops reacting and starts leading.
When the FEADER call arrives, you are not starting: you are executing. And that shows in everything: in the calm, in the coherence of the file, in the quality of the technical report, in the agility to submit, and in the later confidence to implement and justify.
At AGB Ingeniers we see it as a way of working aligned with industry: a competitive company does not improvise important investments. It plans them. FEADER, when prepared well, accelerates that strategy.
The final message: FEADER is worked on before it is published
If your agri-food company already knows it needs to invest, don’t wait for the call to be published to start building the project. What makes the difference is not finding out earlier; it is being prepared earlier.
At AGB Ingeniers we can help you organize the investment, define the scope, build the technical report, and leave the file ready to compete when FEADER becomes active. Because in grants, as in industry, getting ahead is not a slogan: it is method.
Frequently asked questions
Can you start preparing FEADER if there is still no call?
Yes. In fact, it is the best time to define the project, organize documentation, and build a defensible technical report without pressure.
What is the most important thing to avoid being left out?
Arriving with a solid file: a well-defined investment, coherent quotes, a clear technical narrative, and organized documentation.
What tends to fail most in a project?
Lack of coherence between what you want to do, what is quoted, and what is explained in the technical report. And then, the final justification due to missing evidence.
How can AGB Ingeniers help?
By turning a necessary investment into a defensible project: technical report, documentary coherence, coordination with suppliers, and preparation for implementation and justification.