Skip to Content

The Digital Maturity Test before Dig.IT: how to do it right and what it tells you about your company

The Dig.IT digital maturity test is not a box to tick, it is the starting point for a digitalization plan.
July 16, 2026 by
HADRON FOR BUSINESS SP Z O O, Tomasz Leppich
| No comments yet

Note for readers outside Poland: Dig.IT is a Polish grant programme run by ARP. Under the call rules, only micro, small and medium-sized companies doing business in Poland can apply. A company opens the Dig.IT rules, sees the list of attachments, and hits one item: the Digital Maturity Test. For many owners of manufacturing companies this is the first sign that a grant application is more than a form with financial data. The Dig.IT digital maturity test has to be completed before you submit the application, and its result goes into the assessment together with the rest of the documentation. The problem is that companies treat it like just another bureaucratic hurdle to tick off in the last week of the call. That is a mistake, because a test done well is a free mini-diagnosis of the company and a natural starting point for a digitalization plan, before the word grant is even mentioned.

What the Digital Maturity Test is in the Dig.IT programme

The Digital Maturity Test is a mandatory part of the funding application in the Dig.IT programme (ARP, measure 2.21 FENG). In short: before a company asks for a digitalization grant, it first has to assess how digital it is today. The test result shows the starting point against which the progress financed by the grant is later measured.

This makes sense from the programme's perspective: if ARP funds a change, it needs to know the level the company starts from. But the same result also has value for the company itself, regardless of whether the grant is ultimately awarded. It shows where the organization really stands in its processes, systems, data, and automation, before anyone starts planning a specific implementation.

Dig.IT requirements: who even takes the test

The digital maturity test only makes sense for companies that fit Dig.IT in the first place. Before you sit down to the test, check the basic requirements of the programme.

CriterionDig.IT requirement
Company sizeMicro, small, or medium (SME)
Years in operationA company operating for at least 5 years
IndustryIndustrial processing or manufacturing services
Grant amount150,000 to 850,000 PLN
Funding levelUp to 50% of eligible costs
Mandatory attachmentDigital Maturity Test

If a company meets these conditions, it may qualify for support, in line with the programme rules. The status of the current call always has to be checked directly on digit.arp.pl. Status as of 13 October 2026: the rules for call 2/2026 are published, and applications are accepted from 2 to 30 November 2026. We cover the whole logic of pairing a digitalization project with a grant in more detail on our digitalization funding page.

How to do the SME digital maturity assessment properly, not in a rush

Do not fill in the test in a single evening

The digital maturity test is usually a self-assessment questionnaire: the company rates how well it uses IT systems, data, and automation in its key processes, from quoting, through production, to invoicing and the warehouse. Check the exact set of questions and the scoring method for call 2/2026 in the rules and attachments at digit.arp.pl, but the logic of this kind of SME digital maturity assessment is usually similar: the more processes that live in Excel, email, and the owner's head, the lower the score.

Filling in the test in a hurry, just to attach it to the application, produces answers that are random and inconsistent with the rest of the project documentation. Done calmly, with the people who actually know the processes, it becomes a reliable picture of the company rather than one more formality to sign off.

Gather answers from across the company, not just from the management office

The owner usually sees the company differently than the production manager or the person responsible for the warehouse. A reliable test calls for a short conversation with the people who touch the process every day: how long it takes to prepare a quote, how many times a day the same data has to be retyped from one spreadsheet into another, what stock control looks like. These answers build the test score, but along the way they also give you a real description of the problem for the application itself.

How to read the test result and what it means for a digitalization plan

The digital maturity test result builds nothing on its own. The value appears only when the company turns it into a plan: what exactly to implement, in what order, and with what effect. A low score in data management usually means the first step should be a shared ERP-class system, rather than yet another extra spreadsheet or a single standalone app. A low score in the automation of production processes points instead to a production planning module or integrating the machines with the system, rather than a separate digitalization project with no connection to the rest of the company.

In other words: the test shows where it hurts, but it does not say what exactly to build and for how much. That step, turning the test result into a concrete, priced digitalization project, already calls for a separate diagnosis of the processes. That is exactly what our Digital Growth Diagnosis does, based on 39 indicators across 7 dimensions of the company: it takes the starting point from the test and turns it into an implementation plan with a concrete scope, budget, and timeline, which can then become the basis of a grant application.

The most common mistake: the test as a formality, not a map of the company

The most common mistake we see: a company treats the digital maturity test as a checkbox to tick off, fills it in superficially in the last week of the call, and plans the digitalization project separately, with no link to what the test actually showed. The result: an application in which the test and the project description do not hold together, because one was filled in by one person and the other written by someone else.

The order that makes sense is the opposite: first a reliable test and a diagnosis of the processes, then a digitalization project built on what the test actually showed, and finally a grant application that co-finances that specific project. The market usually estimates the cost of implementing an ERP system alone in a small manufacturing company at 20,000 to 80,000 PLN, and in broader terms with licenses at 80,000 to 300,000 PLN (according to humansoft.pl), with a rule of thumb of around 1 to 3% of annual revenue. Knowing these ranges already at the test stage helps keep the whole project within realistic bounds.

Frequently asked questions

Is the Digital Maturity Test mandatory for the Dig.IT application?

Yes. The digital maturity test is a mandatory attachment to the Dig.IT funding application. Without it the application is incomplete. It is worth treating it, though, not as a formality but as a free mini-diagnosis that shows the company's real starting point.

Does a good test result guarantee that the grant will be awarded?

No. A company may qualify for support, in line with the programme rules, but the award of the grant is decided by the assessment of the whole application, not the test result alone. The 1/2025 pilot showed that almost three times more applications came in than the allocation allowed, so the quality of the entire documentation matters, not just the test.

How long does it take to fill in the test well?

It depends on the size of the company, but a reliable approach, with a short conversation with the production, warehouse, and sales managers, usually takes a few days, not a single afternoon. That time pays off in a coherent application and a real picture of the company for further planning.

What should you do with the test result if the call is not open yet?

Exactly what is worth doing right now: turn the result into a digitalization plan before call 2/2026 opens on 2 November 2026. Companies that already have a ready, priced project on the day the call opens start with a clear advantage over those that are only beginning to prepare.

The test is the beginning, not the end. The digital maturity test result alone will build nothing until it turns into a concrete plan with a scope, budget, and timeline. That is exactly what we do in the Digital Growth Diagnosis: we take the starting point from the test and turn it into a project that may qualify for Dig.IT funding, and if no call happens to be open, it still stays with you as a ready action plan.

HADRON FOR BUSINESS SP Z O O, Tomasz Leppich July 16, 2026
Share this post
Tags
Archive
Sign in to leave a comment
How Much Does an ERP Implementation Cost in a Small Manufacturing Company? Real Ranges 2026
What an ERP implementation really costs in a small manufacturing company, and what drives the price.