The owner of a manufacturing company with 10 to 50 employees rarely asks whether they need digitalization at all. They ask where to start and in what order, so they do not sink money into a system the shop floor will not accept, or into a grant awarded for a project nobody has properly thought through yet. Digitalizing a manufacturing company rarely fails because of a poor choice of a specific system. It fails because of the wrong sequence of steps: an ERP bought without a process diagnosis, a grant application filed before choosing a vendor, an MRP module rolled out before anyone has cleaned up the data that today sits scattered across a dozen Excel sheets. This article lays out the full twelve month plan, from diagnosis to automation, and links to detailed guides for each stage, which we publish progressively on our blog.
Why digitalizing a manufacturing company is a year long project, not a one time purchase
Digital transformation of production in a small company rarely succeeds as one big rollout crammed into a single quarter. It succeeds as a sequence of stages, each one laying the foundation for the next: diagnosis shows where the problem really sits, financing lowers the cost of solving it, an ERP foundation puts the data in order, and only on that groundwork do MRP and process automation make sense. Reversing that order, for example rolling out an advanced MRP before basic product and warehouse data is in order, usually ends with a return to Excel within a few months.
On top of that comes a factor the company has no control over: the schedule of the National e-Invoice System (KSeF). From 1 February 2026, all taxpayers are required to receive invoices through KSeF, and taxpayers with sales exceeding 200 million PLN for 2024 must also issue invoices through it from the same date. From 1 April 2026, the obligation to issue invoices covers practically all B2B trade, and the smallest companies, with gross sales up to 10 thousand PLN per month, have until 1 January 2027. This schedule will not wait for a company to finish its own digitalization, so it is worth weaving it into the plan from the start, rather than treating it as a separate, unrelated project.
Months 1 and 2: diagnosis, before any purchasing decision
The first stage of the plan is not about comparing ERP vendor offers. It is about establishing where the company is actually losing time and money today: in double entry of data between a quote and an order, in a warehouse that does not match the actual stock, in quotes made from a salesperson's memory, or in production planned on a whiteboard. Without this diagnosis, a company very easily buys modules that answer a problem it does not actually have, while skipping the one that is genuinely holding back growth.
Our Digital Growth Diagnosis is an audit of 39 KPIs across 7 dimensions that pinpoints the company's specific bottleneck before any decision to buy a system is made. If you recognize your company in this description of data chaos scattered across spreadsheets, we gathered seven concrete signs of that state in the article running your company on Excel. The outcome of this stage is not a purchased system, just a list of three to five processes that are actually costing the company the most, and that list drives every later decision in the plan.
Months 2 and 3: financing, Dig.IT and other sources
With the priority list from the diagnosis in hand, it is only now worth checking whether part of the cost can be financed externally. A company from manufacturing or production services, operating for 5 years or longer, may qualify for support from the Dig.IT program (ARP, FENG 2.21), under the program's rules: a grant from 150,000 to 850,000 PLN, covering up to 50% of eligible costs, including ERP software, implementation and training among other things. Pilot round 1/2025, closed on 28 November 2025, showed the scale of interest: 146 applications came in for a combined 57.28 million PLN, against an allocation of 20 million PLN, nearly three times oversubscribed.
As of writing this article, the rules for round 2/2026 have not yet been published on digit.arp.pl, so before you plan a budget assuming a specific grant amount, always check the current status of the round directly on the program's website. We gathered a full map of the available digitalization financing sources, along with the settlement rules, on the digitalization financing page, and a checklist for a sudden start of the next round in the article Dig.IT round 2/2026. The outcome of this stage is a verified budget: what the company will finance itself, and what it might finance from a grant, without delaying the project itself for an uncertain date when the rules are announced.
Months 3 to 6: the foundation, choosing an ERP system and KSeF integration
The third stage is usually the longest and most expensive part of the whole plan: choosing and implementing an ERP class system that becomes the single source of data about the customer, material, order and production. The following stages, MRP and automation, rest on exactly this foundation, so it is worth giving it as much time as it actually needs, rather than speeding it up at the expense of source data quality.
Choosing and implementing the system
Selection criteria for a company of 10 to 50 people differ from the criteria of a large IT department: what matters is simplicity of maintenance without a dedicated team, the implementer's familiarity with the specifics of production, and a predictable maintenance cost after the first year. The market quotes a range of 20,000 to 80,000 PLN for a narrow scope implementation, according to humansoft.pl figures, and for a broader implementation, with a production module and integrations, the cost rises to 80,000 to 300,000 PLN, which the indicative range from symfonia.pl confirms. The license usually accounts for 10 to 50% of the whole budget, the rest is implementation work and training. A practical rule of thumb for planning: 1 to 3% of the company's annual revenue for the whole project, including the first year of maintenance. You will find the full selection criteria and a breakdown of costs by component in the articles ERP system for a small company and how much does an ERP implementation cost.
KSeF as part of the same project, not a separate patch
Since the obligation to issue invoices in KSeF will cover the company by 1 April 2026 at the latest anyway, it makes more sense to combine this change with the ERP implementation than to bolt a one off integration patch onto the old program. A system that has KSeF support built in from the start generates invoices with the full set of data from the order, instead of requiring manual completion before sending. We described the practical problems that companies report after the obligation starts in the article KSeF, problems after the start.
Months 6 to 9: MRP and production planning under control
Only once product, order and warehouse data lives in a single system does it make sense to switch on material requirements planning, MRP. Earlier, an MRP module would be calculating on incomplete or inconsistent data, which in practice generates more corrective work than benefit. At this stage, a company usually moves from planning on a whiteboard or in Excel to a system that calculates material requirements itself, based on the production plan and current warehouse stock.
We described the signs that manual planning has stopped being enough, and the maturity path from whiteboard through spreadsheet to full MRP, in the articles MRP for a small company and production planning in a small company. Companies that also need to track a multi level product structure, or raw material batches from receipt to shipment, will find a practical explanation in the articles BOM in practice and traceability in small scale production.
Months 9 to 12: process automation and the first conclusions from the data
The last stage of the first year is automating administrative processes that now have common, consistent data to work with: payment reminders, automatic approval workflows for purchase orders, a nonconformity register linked directly to the order, or a management dashboard built once instead of assembled by hand from several sources every month. This is also the moment to connect the sales department to the same system, because a technical quote requires pricing materials and production capacity, and a CRM disconnected from the ERP does not know that pricing.
We gathered ten concrete processes to automate before a company even considers buying a robot or a cobot in the article process automation in a manufacturing company, and we write about connecting sales with production in the article CRM for a manufacturing company. After twelve months, a company usually has its first full year of data from a single system, which makes it possible to assess whether the metrics set at the start of the project actually improved, and to plan the second year of digitalization with concrete numbers in hand, instead of just a hunch.
The manufacturing company digitalization plan in one table
The table below organizes the five stages described above into a single view, with an indicative duration and the outcome the company should have at the end of each stage.
| Stage | Months | What you do | Outcome at the end of the stage |
|---|---|---|---|
| Diagnosis | Months 1 and 2 | Audit of processes and data, no purchasing decisions | List of the company's priority bottlenecks |
| Financing | Months 2 and 3 | Checking available sources, including Dig.IT | Verified project budget |
| Foundation: ERP and KSeF | Months 3 to 6 | Choosing and implementing a system with KSeF integration | Single source of data on customer, material and order |
| MRP and production | Months 6 to 9 | Material requirements planning in the system | Requirements calculated automatically, not on a whiteboard |
| Automation | Months 9 to 12 | Workflows, reminders, dashboard, CRM connected to production | First full year of data to evaluate metrics |
How to be sure this order fits your company
The sequence in this article is a skeleton, not a ready made implementation plan for every company. The actual order and pace depend on how much the mess in specific processes is costing today, how large the team is, and how urgent the KSeF schedule is in your case. That is why the first stage, diagnosis, always comes before choosing a system, not the other way round. We publish further detailed guides to each stage of this plan, including comparisons of specific ERP systems and practical KSeF guides, progressively on our blog.
Wdrażamy systemy Odoo od 2011 roku, dla klientów w trzech krajach: w Polsce, Niemczech i Belgii, jako partner Odoo od około 2011 roku. Nasz pierwszy klient dostał działające demo dzień po pierwszej rozmowie, a pełny system ruszył po dwóch tygodniach. Ta firma została później przejęta przez niemiecką grupę giełdową, a ten sam rdzeń systemu działa w niej do dziś. To dobra ilustracja tego, że dobrze zaplanowana cyfryzacja nie musi oznaczać miesięcy oczekiwania na pierwsze efekty.
Frequently asked questions
Where should a small manufacturing company start digitalizing?
With a diagnosis of processes, not with choosing a system. Before you compare ERP vendor offers, it is worth establishing which specific processes are costing the company the most time and money today: double data entry, a warehouse that does not match actual stock, or quotes made from a salesperson's memory. This priority list drives every subsequent decision in the annual plan.
Can the twelve month digitalization plan be shortened?
Partly, yes, if the company already has its source data in order and a clearly diagnosed problem before the project even starts. In practice, the longest stage remains the foundation, meaning choosing and implementing an ERP system with KSeF integration, because the quality of that data determines whether the following stages, MRP and automation, work correctly at all.
Do you need an approved Dig.IT grant to start digitalizing a manufacturing company?
No. Diagnosis and choosing priorities do not depend on external financing, and waiting for a round's outcome without starting your own process analysis only extends the whole project. A company from manufacturing or production services, operating for 5 years or longer, may qualify for support from Dig.IT, under the program's rules, but you always need to check the status of the next round on digit.arp.pl before you plan a budget assuming a specific grant amount.
Can MRP and automation be implemented in parallel with choosing the ERP system, to speed up the project?
In theory yes, in practice it rarely pays off. MRP and administrative process automation rely on the same customer, material and order data, which only the foundation of an implemented ERP puts in one place. Starting these stages before the source data is stabilized usually ends up requiring fixes that cost more time than keeping to the planned order.
This plan works well as a skeleton, but the specific order and priorities for your company only become clear from a diagnosis of the data you operate on today. The Digital Growth Diagnosis is an audit of 39 KPIs across 7 dimensions that shows which stage of this plan your company should start from, before any purchasing decision is made.