A warehouse manager at a building materials distributor in Paços de Ferreira, with 15 years of "radio in hand and paper in pocket", told us three years ago: "The ERP says I have 47 pallets of 25mm PVC pipe. I see 43 on the floor. Either the ERP is wrong, or I'm a crook." Neither was true. What was wrong was something no one had asked before: two years earlier, the system had not been informed of three partial customer returns. They were logged as "complete". The ERP wasn't lying. It was simply revealing a management gap that no one had seen because no one had access to the real numbers. That was the week that manager realised the ERP wasn't the enemy — it was the mirror the company needed but was afraid to look into.

Most Portuguese companies still don't have that mirror. In 2025, only 53.7% of companies in Portugal with 10 or more people used integrated enterprise management software — which means that close to half of the business landscape operates with rules living in the heads of three people, numbers in spreadsheets, and intuition as a compass. Meanwhile, productivity per hour worked in Portugal stood at around 67% of the EU average in 2022, a structural deficit that the lack of operational visibility helps to perpetuate. The difference between seeing and not seeing is not a question of technology. It's a question of competitiveness.

What the ERP does is count. What management needs is to see.

Implementing a vertical ERP in a Portuguese factory or distributor is rarely an exercise in "computerising the paperwork". In most cases, it is an exercise in revelation. And uncomfortable revelations tend to be resisted.

We see this repeatedly: a company with 60, 80, 120 employees operates with rules that live in the heads of three people. The CFO knows where the money is because they see it in the bank statement and the spreadsheet they do every night. The operations director knows that the OEE of line 2 is "roughly 65%" because they walk past it twice a week. The warehouse manager knows how many pallets of stock they have because they count them month by month. No one needs numbers — they need intuition. That works up to the point where it stops working. And when it stops, no one knows why.

An ERP comes in and says: "Your OEE isn't 65%. It's 58%. And do you know why? Because we have 340 minutes of unrecorded stoppages per week, 180 minutes of changeover that no one was accounting for, and 90 minutes of cycles slower than the standard — because no one had measured the standard." Full stop. There's no room for interpretation. There's no room for "my experience says it's different".

At that moment, one of three things happens. The company rejects the number ("The ERP is badly calibrated, we know it's 65%"). The company denies responsibility ("That's production's fault, we did our part"). Or the company turns inwards and asks itself: what else are we not seeing? The third option is an operational turnaround. The first two are the road to irrelevance.

The numbers reveal what intuition hides.

There is a paradox in the management of Portuguese industrial SMEs: the better the manager, the more dangerous it is to rely on intuition alone. A director who grew the company from 20 to 100 employees developed extraordinary reflexes. They see signals an MBA doesn't see. But those signals become increasingly noisy as the company grows. The intuition that worked with 40 people and 8 production lines does not scale to 120 people and 5 factories. It's not incompetence — it's organisational physics. And no amount of experience resolves physics.

The ERP forces the company to answer questions no one had asked because no one had the tools to ask them. What is the real cost of an unplanned line stoppage? Not the "estimate" — the real cost, with time, materials and overhead. How many hours of administrative work (approvals, validations, rework) are hidden in the procurement process? Not the "feeling" — the number of person-hours, week by week. What is the real compliance rate of the warehousing process? Not the opinion — the percentage of records that match physical reality. How much does it cost, in hard cash, for the company to have no visibility over work-in-progress stock? Not the "concern" — the working capital tied up.

These questions seem simple. But the answer requires integrated, audited and real-time data. And integrated, audited and real-time data requires an ERP that works. Before that, the question is "theoretical". After an ERP is correctly implemented, the question has an answer. And the answer, very often, is "We were losing far more money than we knew."

The operational turnaround doesn't begin when someone says "let's optimise". It begins when someone has the courage to look at the real number and ask "why is this the way it is?"

The implementation is the diagnosis. The diagnosis is the turnaround.

Implementing a vertical ERP — such as the ERP MULTI in a footwear or clothing factory, or in a distributor — is not an IT project. It is a management project that uses IT as an instrument. And that is precisely why it fails so often when it is treated as an IT project.

What we see working is this: the company enters the implementation with a team (CEO, CFO, operations director, IT manager, 1-2 shop-floor or warehouse supervisors). The change management is real, not a PowerPoint presentation. And during the 14-18 weeks of implementation, the company is forced to answer questions no one had had time to answer before. How do you define a "completed production order"? Because the ERP needs a definition, not an interpretation. Who approves a credit note? On what criteria? Because the ERP will automate that, and if there are no criteria, it will automate chaos. What is the standard cost of a part? Because the ERP needs a number, not "roughly".

The answer to each of these questions is a small turnaround. At the end of the 14 weeks, the company not only has an ERP — it has a map of its own operation that it did not have before. It has definitions. It has criteria. It has numbers. It has a common language.

Five years ago, we believed the turnaround came after the implementation: "Implement the ERP, stabilise, then optimise." We were wrong. The turnaround begins during the implementation, because that is when the company is forced to define itself. And a company that defines itself with clarity operates differently. Not because the ERP is "magic". Because the company finally knows what it is doing.

What changes when management can see.

An operations director who, three months ago, said "we produce X units per month" now says "we produce X units per month, with an OEE of 73%, an average cycle time of 4.2 minutes, a scrap rate of 2.1%, and a planning compliance of 89%". Suddenly, they have language. And language enables conversation. And conversation enables decision. When the production manager says "line 3 has an OEE of 68% and line 2 has 79%", it's no longer opinion — it's fact. And facts enable prioritisation.

A procurement manager who didn't know a supplier's real lead time (because it depended on how many times the supplier forgot to reply, or how many times the order was re-done due to an administrative error) now knows. They have 12 months of data: average time between order and arrival, variance, quality compliance, quantity compliance. And when they know, they can negotiate. And when they can negotiate, the cost of purchasing falls — not by "squeezing" the supplier, but by eliminating variance. A supplier that delivers in 45 days with a deviation of ±15 days is more expensive than a supplier that delivers in 48 days with a deviation of ±2 days, because variance costs working capital.

A garment factory in Famalicão that operated with "safety stocks" that no one had calculated (they were "experience") now has stocks calculated on the basis of real advanced planning. Real demand, real lead time, real variance. Working capital falls by 8-15% without raw material ever running short even once. And when working capital falls, the company can invest elsewhere — maintenance, product innovation, or simply breathe.

This is not "optimisation". It is management. And management is what is missing when the company grows beyond the size at which the intuition of three people can keep everything in check.

Honesty about what changes and what doesn't.

An ERP doesn't solve everything. An ERP won't turn a non-competitive product into a competitive one. An ERP won't solve quality problems that are product design problems, or staff qualification problems. An ERP won't turn a factory with reactive maintenance into a factory with preventive maintenance if there's no investment in people and processes. An ERP won't save a flawed commercial strategy.

What an ERP does is enable management to see, measure and decide based on reality, not intuition. What it does next is the company's decision. That is the line most failed implementations cannot cross: the company expects the ERP to solve the problem. The ERP only shows what the problem is.

We see this clearly when we visit factories. A well-executed implementation of KORA Productivity (real-time production capture and OEE) on a textile line reveals what is happening — stoppages, cycles, scrap, causes. But the decision to "invest in preventive maintenance", or "redesign the process", or "accept this OEE as acceptable and focus on another indicator" belongs to the company. The ERP is the mirror. What to do with the image is the manager's responsibility.

The best measure we have of a successful implementation is not "the client is happy with the ERP". It's "the client is uncomfortable with what the ERP revealed — and is acting on it". Because that means the company has entered a cycle of continuous improvement. And cycles of continuous improvement are where real turnarounds are born. Not dramatic ones. But real ones.

Sources

  • INE (Statistics Portugal), 2025. Use of enterprise management software in Portugal — data for companies with 10 or more people.
  • Eurostat, 2022. Productivity per hour worked — EU27 comparison.
  • European Commission, 2025. Digital Intensity Index of SMEs — Digital Decade 2030.

Frequently asked questions

What is an operational turnaround?

An operational turnaround is the transformation process that occurs when a company implements an ERP and, through the real data the system reveals, is able to identify and correct operational inefficiencies that were previously hidden. It begins when management has the courage to look at the real numbers and question why things work the way they do.

Why do many managers distrust the ERP's numbers?

Managers with many years of experience develop extraordinary reflexes and trust their intuition. When the ERP reveals numbers different from those they expected, the first reaction is often to reject the system, arguing that it is badly calibrated. This happens because the intuition that worked with small companies does not scale to larger organisations.

What is the problem with running a company on intuition alone?

Intuition works up to a point, but it doesn't scale. As the company grows in people and complexity, the signals a manager can process become increasingly noisy. No amount of experience resolves this problem of organisational physics. Without integrated and audited data, the company operates with rules living in the heads of a few people.

How many Portuguese companies still don't use an ERP?

According to the article, in 2025 only 53.7% of companies in Portugal with 10 or more people used integrated enterprise management software. This means that close to half of the Portuguese business landscape operates without integrated operational visibility, relying on spreadsheets and intuition.

What did the ERP reveal in the case of the warehouse manager in Paços de Ferreira?

The ERP recorded 47 pallets of PVC pipe, but the manager counted only 43. The discrepancy was not a system error, but a management one: there were three partial customer returns logged as complete two years earlier. The ERP revealed a gap that no one had seen because no one had access to the real numbers.

Why should an ERP implementation be a management project and not just an IT one?

Because the ERP forces the company to answer fundamental questions no one had had time to answer before: how do you define a completed order? Who approves credits and on what criteria? What is the real standard cost? The ERP requires precise definitions, not interpretations. That is why success depends on management decisions, not technical configurations.

How does the Portuguese productivity deficit relate to the lack of operational visibility?

Productivity per hour worked in Portugal stood at around 67% of the EU average in 2022. The article suggests that the lack of operational visibility — caused by the absence of integrated systems — helps to perpetuate this structural deficit. Without real data, companies cannot identify and correct inefficiencies.