You've won the DIMOP grant: the awarded amount is in place, and so is the settlement deadline. The harder part starts now — the actual implementation.
This article is about what comes after the award, where things usually slip, and how to start so that you don't just buy the funded system but genuinely use it. Written from real implementation experience, with practical decision points.
The grant is won. Now what?
The application phase is over. The grant writer stays with you up to submission, perhaps to the award decision, and from there a different profession takes over: delivery. This is where a lot of companies are left on their own.
That's understandable. The market is full of players selling the winning of a grant, with guides, submission help and success fees. Fewer people talk about what happens after the award: how the awarded budget turns into a working system, where implementation slips, and what to watch for so you don't end up with expensive software that nobody uses.
Yet this is the phase that decides whether the grant pays off.
The 5 typical pitfalls after the award
Across implementations, we see five recurring mistakes. None of them is the software's fault: every one of them is a process problem.
1. The committed scope drifts. The functionality committed to in the application isn't always the same as what day-to-day operations actually need. If the two drift apart, you either fail to deliver the commitment or you implement something nobody uses. It is worth clarifying right at the start what is a binding commitment and what is a real need, and then aligning the two.
2. Communication stalls. The classic never-ending project: implementation drags on for months, there is no predictable status report or milestone feedback, and after a while you have no idea where the project stands. The fix isn't technological, it's communication: regular, predictable feedback and visible milestones.
3. Data migration is underestimated. Years of data sit in the old system, or in Excel, and it has to be brought into the new one in a usable state. Almost everyone underestimates this. Assess up front what you have today and in what quality.
4. Adoption never happens. The system goes live, but the team doesn't switch to it: the old spreadsheet stays in use “just to be safe”. The funded system gathers dust. An implementation is half technology and half training the people who use it; skip that half and the investment doesn't pay back.
5. A last-minute scramble at settlement. The deadline closes in, the documentation is incomplete, and the final weeks turn into a rush. Preventing this is far cheaper than fixing it afterwards.
Settlement risk — and why the choice of supplier matters
The grant doesn't end when the money is transferred. Settlement requires orderly, verifiable documentation: what was delivered, when, and against which supporting document. If that isn't built up as you go, it becomes a problem at the deadline.
This is where the choice of supplier matters. Accredited supplier status (on the vallalkozzdigitalisan.mkik.hu portal) is not marketing copy but a verifiable classification, and it can also reduce settlement risk, because delivery and documentation can be aligned to the logic of the grant. On an earlier grant-funded implementation (details withheld at the client's request), that orderliness helped ensure the deadline-bound settlement didn't have to be pulled together in the final weeks.
What does a good implementation look like after the award?
A good implementation is the opposite of the pitfalls above. It is broken into milestones: instead of trying to do everything at once, it takes a narrow area live quickly — invoicing or inventory in a few weeks, say — and builds out from there. That way there is a tangible result in the first weeks, not only at the end of the project.
It comes with predictable communication: you know who is working on what and when you will see it. And it ends with handover and training: the team doesn't just receive the system, it learns to use it.
That is our approach too: a phased, agile and communicative implementation. Not because it sounds good, but because this is precisely what keeps the project from dragging on indefinitely.
When is it worth adding AI — and when is it not yet?
A DIMOP project often includes an AI element, and it is tempting to start with the cleverest feature straight away. The order is the other way round: first a stable foundation, then the AI on top. A “smart” feature running on unreliable data is worse than none at all.
Once the foundation is in place, the real, built-in AI features of Odoo 19 genuinely work for you, on your own data. A supplier invoice PDF becomes an accounting entry without manual data entry; on a customer record, a long email thread can be summarised or a follow-up message drafted. These are not separate chatbots but help built into the system, right where the data lives. But the order matters: the implementation comes first, the AI is what you build on top.
Realistic ROI and timescales — honestly
The thing worth knowing up front about payback is that it doesn't arrive in one big jump. What pays back fastest is eliminating manual data entry: duplicate work disappears where you used to retype data from one system into another. That is where the “one system, one source of truth” advantage comes from: month-end reconciliation gets shorter, and errors go down.
It would be irresponsible to promise a specific percentage: actual payback depends on your processes. What we can say honestly is that a funded system delivers real value when the implementation is carried through and the team genuinely switches over, not because of the software licence.
Who and when — a short checklist
Before you start on delivery, run through these:
- Have you won the grant, or are you still at the application stage? (It is worth planning the implementation as early as the award decision.)
- Is the relationship between the binding commitment and the real need clear?
- Is there an internal owner who will drive the project from your side?
- Do you know what data has to be migrated, and what state it is in?
- Is there a realistic milestone plan and predictable documentation for the grant settlement?
If you are unsure on several points, that's fine — this is exactly what an assessment is for, before the project starts.
Frequently asked questions
How long does a DIMOP implementation take?
With a phased approach the first area can be live within weeks; the full implementation will take longer accordingly. The key is not to attempt everything at once — the milestones are what keep the deadline under control.
What if settlement slips?
The risk of slippage is reduced by orderly documentation built up as you go. An accredited supplier's way of working is based on exactly this, which is why it is worth weighing this point when choosing a supplier.
Do I need a separate developer for the AI features?
The built-in AI features of Odoo 19 are part of the standard system, not separate development. They are applied to your existing data once the foundation is stable.
Can I change supplier after the award?
Yes, and sometimes that is the right move if the current implementation has stalled. With an open system such as Odoo this is easier, because you have access to your own data and to the logic of the system.
Do it properly — two steps for getting started the right way
Once the grant is awarded, the best thing you can do is not leave the implementation to chance.
If you are not yet sure where to start: download the free DIMOP implementation checklist — it helps you assess the committed scope, the data, the internal owner and the documentation required for the grant settlement before the project starts.
If you are already facing a concrete project: book a free 30-minute consultation with a Glazer-Innovation expert. We'll go through where you stand, what the biggest risk is, and in what order the implementation should start. We are an official Odoo Learning Partner and an accredited supplier with real, delivered grant-funded implementations behind us — we know what this phase looks like in practice, not just on paper.