A digitalisation grant is public money that pays part of a technology investment a company has already decided to make. It does not decide the investment for you, and it does not make a weak project viable. Knowing which of those sentences applies to your company is the whole of the preparation.
Quick Overview
Dig.IT is a Polish support instrument aimed at the digital transformation of small and medium-sized enterprises, run by the Industrial Development Agency — Agencja Rozwoju Przemysłu, usually shortened to ARP. It belongs to a family of instruments that co-finance an investment rather than fund it outright, which means the applicant always carries part of the cost and all of the risk.
This article does three things. It explains what the instrument is for, so that a management team can tell quickly whether their planned project is the kind of thing it supports. It sets out the preparation that determines whether an application is worth writing at all — work that has to happen before any call opens, because it cannot be done in the window between publication and deadline. And it is explicit about the competence problem, which is the part that grant money reliably fails to solve.
It also does something less usual, described in its own section below: it refuses to quote award ceilings, co-financing rates, eligibility thresholds or application deadlines. That refusal is deliberate and is explained rather than hidden.
What the Instrument Is, and Who Runs It
The managing institution is ARP, and this matters more than it sounds. A support programme is not a law: its terms live in call documentation that the managing institution publishes, amends and closes. The name of the programme, the name of the agency and the general purpose are stable designators. Everything with a number attached to it is not.
The purpose is straightforward. The instrument exists because the barrier to digitalisation in the smaller half of the economy is rarely conviction and almost always the initial outlay — software licences, hardware, integration work, the consultancy that makes the pieces fit and the internal time that nobody costs properly. Co-financing lowers that outlay. It does not lower the second barrier, which is that somebody in the company has to run the resulting system afterwards.
A management team reading this should treat the programme as one financing route among several rather than as the reason to digitalise. The European Digital Innovation Hubs network exists precisely to give smaller companies access to testing, advice and skills before they commit capital, and using it costs nothing but calendar time. A company that has done that groundwork writes a far better application than one that starts with the grant. That is also true of teams evaluating connectivity-dependent projects, where the technology choice itself decides the shape of the investment — the ground covered by 5G and IoT: The Synergy of Future Technologies.
Why This Article Quotes No Figures
Programme description as of: 2 September 2026.
Here is the honest position. At the time of writing, the programme documentation published by the managing institution could not be retrieved from a publicly readable source by the checks this article is subject to. Every award ceiling, co-financing rate, eligibility threshold and submission deadline in circulation for this programme therefore rests on secondary commentary rather than on the document that governs the money.
Publishing such a figure would be worse than publishing nothing. A reader could take it as the basis for a financial decision, discover on submission that the ceiling was different, that the rate had changed or that the call had already closed, and the article would have caused the loss. Support programmes close. Terms are amended mid-programme. A call announced for one quarter may open in another, or may not open again at all.
So the rule applied here is simple: parameters come from the call documentation in force on the day you apply, read directly from the managing institution, and from nowhere else. Anything this article told you about amounts would be out of date by the time you needed it, which is precisely why it tells you none.
The Investment Areas This Class of Instrument Covers
The catalogue of eligible costs is always defined by the call, but the shape of what digitalisation instruments support is consistent enough to plan around. The recurring areas are these:
- Process automation — removing repeatable handling from production, logistics, finance and customer service.
- Applied artificial intelligence — forecasting, classification, document handling and decision support built on the company’s own data.
- Sales and marketing systems — commerce platforms, customer relationship management, campaign tooling and the reporting that makes them accountable.
- Cloud infrastructure — migration of workloads and the operating model that has to come with it.
- Cybersecurity — protective controls, monitoring and the governance around them.
- Resource planning systems — the integrated backbone covering finance, inventory, production and orders.
Two observations are worth more than the list itself. First, security is not an optional line item to be dropped when the budget tightens; a digitalisation project that widens the attack surface without a corresponding control programme has made the company worse off, which is the reasoning that the NIST Cybersecurity Framework (CSF) 2.0 puts at the centre of its governance function. Second, artificial intelligence is where applications most often overreach, because it is easy to write and hard to operate. A company considering it should first read an unglamorous account of what actually works at this scale, such as AI in a small and medium-sized company (SME).
Preparation That Has to Happen Before a Call Opens
Applications fail on preparation far more often than on eligibility. The work below takes weeks and cannot be compressed into the window between a call being published and its deadline.
Start from the business outcome, not the technology. An application that says what the company will be able to do differently — and what that is worth — survives evaluation better than one that lists products. Then audit honestly: which processes are actually costing money, what state the existing infrastructure is in, and which competencies the team already has. Then draft the project: scope, budget including the company’s own contribution, sequencing, and the risks you can name.
The step that most companies skip is the financial one. Co-financing means the company funds a share from its own resources and carries the whole project through to completion before any reimbursement logic applies. That has consequences for cash flow, and it means the investment has to pay back in the ordinary commercial sense. Working out what the digitalisation actually changes about what the company can charge, and how it charges it, is part of the business case rather than an afterthought — the discipline covered in A Practical Guide to Effective Pricing Strategies.
Competence Is the Part No Grant Can Buy
Grant money buys systems. It does not buy the ability to run them, and the gap between those is where digitalisation projects go quiet.
The pattern is familiar to anyone who has watched an implementation from the inside. A resource planning system arrives, the consultants leave, and the organisation keeps its old spreadsheets running alongside it because nobody is confident enough in the new numbers to act on them. A model produces a forecast that nobody can interpret, so it is ignored. A cloud migration completes and the monthly bill doubles, because the people operating it were never taught that cost is now an engineering property.
The competencies that decide the outcome are unglamorous: reading data critically, understanding what a model can and cannot be trusted to say, recognising a security-relevant decision when one appears, and adapting a working process to a tool rather than the reverse. These are developed deliberately or not at all. Planning a digitalisation investment without planning the corresponding development of the team is planning to underuse the investment, which is the argument set out at more length in Digital Competencies and IoT in Business Development.
Where an Investment Grant Differs From a Training Subsidy
These are different instruments and confusing them wastes time. An investment grant of the Dig.IT class co-finances the acquisition and deployment of technology; the eligibility of training within it depends on the call’s cost catalogue. A training fund is the opposite in emphasis: it exists to finance the development of people and treats technology as context.
A company doing this properly usually needs both, sequenced. The training instrument prepares the team; the investment instrument buys the systems that team will operate. Trying to make one do the other’s job produces an application that fits neither, and evaluators notice. The training side of that pairing is described separately in How KFS Supports IT Skills Development.
What to Do With This
If your company has a digitalisation project it would fund anyway, an instrument like Dig.IT improves the economics of doing it sooner and at a larger scale. If it does not, the grant is not the reason to invent one — an application built backwards from available funding produces a system nobody asked for and a competence gap nobody planned.
The sequence that works: define the outcome, audit the ground truth, cost the project including your own contribution, identify the competence gap, and only then read the current call documentation to see whether what you want to do is eligible. In that order, the funding question becomes the last one you answer rather than the first.
Frequently Asked Questions
Who can apply for the Dig.IT grant?
Small and medium-sized enterprises registered and operating in Poland. Whether a specific company qualifies is settled by the size criteria and the formal conditions in the call documentation in force, not by a description of the programme in an article.
How much funding can a company receive?
The award ceiling and the co-financing rate are set by the call documentation. This article deliberately quotes neither, because at the time of writing neither could be verified against the governing document, and an unverified figure about public money is worse than silence.
Can employee training be financed from the grant?
The catalogue of eligible costs is defined by the call. Training that is necessary to operate the technology being deployed is a recurring element of digitalisation programmes, but eligibility has to be read from the current rules rather than assumed from precedent.
How long does the application process take?
That depends on the call schedule and on the number of applications submitted, so no useful figure exists in the abstract. What is under your control is the preparation — the audit, the project plan and the competence analysis — and that is the part worth starting before a call is announced.