A CEO of a weaving mill in the Vale do Ave says that PT2030 finances "everything that's modern" — cloud, AI, automation. The following month, he receives the rejection notice for his ERP project because "it's not eligible: it's generic software". Full stop.

We see this happen again and again. And the confusion is understandable. PT2030, PRR, COMPETE 2030, Norte 2030 — the names look alike, the rules change with every call, and what works for a metalworking firm in Aveiro may be refused for a clothing manufacturer in Famalicão. It's not incompetence on the part of applicants. It's that the Portuguese regulatory framework for financing digital innovation was designed with categories into which vertical enterprise software doesn't fit well. And nobody says this out loud.

What PT2030 finances — and why

PT2030 (the umbrella that encompasses PRR, COMPETE, Norte 2030, etc.) has a clear logic: it wants Portuguese companies to be more competitive, more sustainable, more environmentally friendly. It finances actions that demonstrate measurable impact in one of these vectors.

That's why it finances well:

  • Automation of production processes — a robotic arm, an assembly cell, a vision system. There's clear ROI, there are labour savings or increased output, there's a metric.
  • Energy transition — solar panels, biomass boilers, thermal efficiency. It reduces emissions, there's certification, there's a baseline vs after.
  • Traceability and circularity — a project that allows a brand to verify that its fabric comes from certified recycled fibre. It fits within the EU Strategy for Sustainable and Circular Textiles. There's compliance, there's innovation.
  • Product or process innovation — a new formulation, a new material, a new design. It has a patent or protection. It has real technical risk.

This is well documented. The managing authorities (IAPMEI, CCDR-N, etc.) know what they want. The problem isn't here.

What PT2030 does not finance — and why it's right, but it hurts

A vertical ERP for industry — even if it's the difference between a clothing manufacturer surviving or disappearing — is considered "generic software" or "investment in current fixed capital" (that is, disguised operating cost). It's not eligible.

A real-time production capture solution that measures OEE is eligible if it's integrated into an automation cell (the hardware pulls the software). On its own, it isn't.

BI and dashboards for data analysis — even if it transforms the way an operations director makes decisions — do not qualify for funding. It's "current management software".

Is a people management platform that reduces absenteeism by 12% through predictive analytics innovative? Yes. But it doesn't fit into the "digital business innovation" category the way PT2030 defines it. It lacks the "innovative solution not available on the market" stamp.

The logic is: if the software exists on the market, it isn't innovation. It's adoption. And adoption is operational — you pay for it with operating profit, not with public funds.

This is right. Portugal can't subsidise what every company buys. But it means that a textile SME that urgently needs an ERP that models its 400 knitwear SKUs with 5 axes of variation can't get funds for it. It pays on its own. And often it can't.

The trap: "software + something"

This is where the confusion turns into frustration. Many applicants try to get around the rule by attaching the software to an "innovation" project — for example, an ERP + a custom digital Kaizen module for continuous optimisation.

We see this happen. And the approval rate is low. Because the managing authority sees that 80% of the cost is standard software, 20% is cosmetic customisation, and rejects it. Or approves it, but with a 40% cut in the software investment.

The result: the company either gives up, or finances the ERP on its own and tries to recover the software money within the innovation project (which distorts the project). Both scenarios are bad.

There are exceptions. If a company manages to demonstrate that it needs truly custom software — because its process is so specific that no standard vertical solution covers it — and that this customisation is what generates innovation, then there's a way forward. But it requires rigorous technical documentation, and many application consultants don't know how to read industrial software specifications.

What we advocate — and where we see change

We believe PT2030 should have an explicit category for "adoption of vertical software in industrial SMEs". Not because the software is innovation — it isn't — but because the lack of a management tool is a structural barrier to competitiveness. A company that still manages stock in Excel can't compete with one that has branch integration and real-time visibility.

The reality: Portugal has 99.9% SMEs, 77.9% of employment is in them, but only 53.7% of companies (10+ people) used enterprise management software in 2025. The gap is structural. And it's not because CEOs don't want it — it's because the investment is high, the ROI is long, and the risk is real.

There are signs of change. COMPETE 2030 has started to accept "integration of information systems" as eligible, provided you demonstrate impact on process innovation or operational efficiency. PRR, for specific sectors (textiles, footwear, distribution), has created more permissive support lines. But it remains a delicate consultancy task — and not every SME can afford to pay an experienced funds consultant to write the dossier.

How to apply — if you decide to try

If you have an industrial SME and a project involving software, here's what we see working:

  • Frame the software as an instrument of a larger objective — operational efficiency, traceability, circularity, process innovation. Don't apply for "ERP". Apply for "Value chain optimisation project with systems integration".
  • Document the baseline — how long it takes today, what the cost is, what the error rate is. Real numbers.
  • Document the after — what the time, cost and error rate will be afterwards. And how much each element of the project costs (software, consultancy, integration, training).
  • If possible, involve a technology partner (like us) who can validate that the solution is appropriate and that the budget is realistic. This increases credibility.
  • Read the specific call for the funding line — PRR is different from COMPETE 2030, which is different from Norte 2030. Each has different eligibility criteria.

And honestly? If your project is "just software", with no process innovation, no automation, no sustainability, no circularity — don't apply. Use operating cash flow, pay for the solution in 12-18 months, and move on. It's often faster and less bureaucratic.

The final provocation

PT2030 is right not to subsidise "adoption of standard software". Public money shouldn't pay for what is normal operating cost. But this leaves a gap: the SME that urgently needs a vertical ERP to compete internationally, but can't get funding, falls behind. And the Portuguese industrial fabric grows weaker.

The solution isn't funding. It's that application consultants, technology partners, and managing authorities better understand the difference between "off-the-shelf software" and "specialised vertical software". A solution that was designed for clothing manufacturers — with support for subcontracting, for multiple price tiers, for overtime control, for batch traceability — isn't generic. It's specific. And it would deserve a category of its own.

Until then, the rule is: if you can demonstrate operational impact and sustainability, apply. If it's "just software", pay for it yourself.

Sources

  • INE (Instituto Nacional de Estatística). Sociedade da Informação e do Conhecimento 2025. Data on the use of enterprise management software in companies with 10 or more people.
  • European Commission. Digital Decade: 2025 Progress Report. Digital intensity in Portuguese SMEs.
  • INE. Estrutura das Empresas Portuguesas 2023. Distribution of SMEs, employment and turnover.
  • Government of Portugal. Recovery and Resilience Plan (PRR) — Component Empresas 4.0. 2021. Allocation of 650 million euros for digital transition.
  • IAPMEI (Instituto de Apoio às Pequenas e Médias Empresas e à Inovação). Eligibility Guides — PT2030, COMPETE 2030, Norte 2030. Funding criteria for software and digital innovation.
  • European Commission. EU Strategy for Sustainable and Circular Textiles. 2

Frequently asked questions

Does PT2030 finance enterprise management software (ERP)?

Not directly. PT2030 considers ERP "generic software" or "operating cost", hence not eligible. Except if you integrate it into a larger project of automation, traceability or process innovation, where the software is an instrument, not an objective. Even so, approval is rare and requires rigorous technical documentation.

What's the difference between eligible and non-eligible software in PT2030?

Eligible software has measurable impact on automation, sustainability, circularity or product/process innovation. Non-eligible software is "adoption" — BI, dashboards, standard ERP, people management platforms. The logic: if it exists on the market, it isn't innovation. It's operational, you pay for it with profit, not public funds.

Can I apply for an ERP if I attach it to an innovation project?

In theory yes, but the rejection rate is high. PT2030 sees that 80% of the cost is standard software and 20% is cosmetic customisation, and rejects it or cuts 40% of the investment. It only works if you prove that the software is truly custom because your process is unique and that customisation generates real innovation.

What kind of industrial software does PT2030 finance?

Real-time production capture systems (OEE) integrated into automation cells; traceability platforms that prove circularity; vision or IoT solutions connected to robotics; software that supports process or product innovation with real technical risk. Always as an instrument, never as an end.

Do PRR, COMPETE 2030 and Norte 2030 have different rules for software?

Yes. COMPETE 2030 has started to accept "integration of information systems" if you demonstrate impact on innovation or efficiency. PRR has created more permissive specific lines for textiles, footwear and distribution. Norte 2030 follows regional criteria. But the common denominator is: software must be an instrument of something larger, never an end in itself.

How do I document a software project to increase the chances of approval?

Focus on the objective, not on the software. Document the baseline (time, cost, error today), the after (time, cost, error afterwards), and the impact on operational efficiency, traceability or innovation. Break down costs: software, consultancy, integration, training. Prove that without the software, the objective can't be achieved. This is more important than the name of the tool.

If PT2030 doesn't finance ERP, how do SMEs manage to invest?

They pay on their own with operating profit, or try to frame the ERP as part of a larger eligible project (automation, traceability, circularity). There are also credit and guarantee lines (IAPMEI, banks) for industrial software. But non-repayable funding is rare. The reality is that around 46% of companies with ten or more people still don't have management software.