At a month-end meeting the finance team presents one margin, production indicates another, and neither figure is wrong: they come from different sources. One comes from the ERP, the other from a spreadsheet that one person updates by hand and that nobody updates during holiday weeks. Those assessing a modular ERP for small and mid-sized companies almost always start from a scene like this. Datasheets come later, once the problem is already clear.
The discussion that follows often turns on the wrong criterion: it comes down to counting how many modules the licence includes, while the useful question is which work steps today rest on personal memory and goodwill.
The ERP does not break: it empties
Administrative software rarely gives way from one day to the next. It keeps issuing invoices, recording orders and moving stock. Around that perimeter, however, a second information system grows that nobody ever declared: a file for due dates, one for job margins, a shared folder to coordinate deliveries, two phone calls because asking is faster than searching.
That parallel system holds up while the company stays small and the people stay the same. Then come another site, a new partner, a bank asking for quarterly results, and the fragility becomes visible to everyone. Nobody decided to work this way: it happened one spreadsheet at a time.
Excel is not to blame. It becomes a problem when it stops serving analysis and starts holding the company together. At that point the question of a modular ERP for small and mid-sized companies arises on its own, without anyone raising it in a meeting.
A modular ERP for small and mid-sized companies is assessed on processes, not on the list of modules
Modularity serves a concrete purpose: switching on first the areas that weigh most today and postponing the others without redesigning from scratch. Platforms built this way grow by addition rather than replacement: administration, sales and purchasing, warehouse, production, jobs, CRM, customer service, management control, workflow, treasury and data analysis.
The advantage is organisational before it is financial. A company that introduces six areas in the same quarter asks every department to change habits at once, and in that quarter nobody works well. Starting the project on two critical areas instead gives a measurable result before opening the next phase.
One condition the catalogues leave out: modularity makes sense when the modules share the same data. Three different products held together by nightly exports do not make an ERP; they make an integration to maintain.
Three days of work for a figure that should already exist
During the analysis at a company with twelve sites, the finance manager summed up the situation better than any diagnosis: she built the reports she needed to reason on the numbers in Excel, and completing them for all sites took her three days.
The problem was not slowness. Those reports should have come out of the ERP, and instead came from manual work repeated from scratch every time: three days of a senior finance person spent rebuilding something a well-configured system returns in a few minutes. By the second month nobody remembered any more the criterion behind one of the columns.
In cases like this a modular ERP project shows its most concrete value. Configuration brings structured data to where it is needed: free-text fields become coded fields, information is recorded only once and the twelve sites work on the same system. The reports that took three days now come out of the system in a few minutes, with each column’s criterion written into the configuration rather than in the memory of whoever built it. The platform made measurable what was previously guessed, and the senior person who spent three days in Excel now spends them analysing the numbers.
The conditions that make action urgent can be recognised without consultants: several companies or sites to consolidate, jobs whose margin is known only once they are closed, a warehouse that does not match physical stock, growth that has outrun the control capacity of whoever runs the company. When at least two of these signs coexist, the question is which process to start from, since intervening is already a given.
What to ask whoever proposes a modular ERP
Before signing, it is worth asking in writing how the vendor handles phases, data migration, analysis days, customisations, training and support after go-live. The same questions are useful even to those who will never contact us.
- Which areas go into the first phase and which stay out, and on what criterion.
- Who migrates historical data, and which data is carried over and which is not.
- How many analysis days the project includes before configuration, and who leads them.
- How a module is added in two years’ time: a new project or an extension of the existing configuration.
- Who answers after go-live, with what timing and through which channel.
- Which processes require customising the software and which can use the standard configuration.
- What training the contract includes and how many people can attend.
- What happens to electronic invoicing flows during the switch.
A vendor who answers “everything is configurable” to every item postpones the problem until the quote has already been signed.
Where a modular ERP project starts
In the projects we run, the most solid sequence starts from administration and the document cycle, because those are the areas where data originates. It then moves to warehouse and purchasing, then to production or jobs depending on the sector, and last to management control: a dashboard built on data that is still messy produces precise charts and wrong conclusions.
| Phase | What happens | What it asks of the company |
|---|---|---|
| Analysis and mapping | Processes are reconstructed as they really work, spreadsheets and phone calls included | Time from key people, without filters |
| Configuration | The areas chosen for the first phase are set up on the platform | Quick decisions on coding and rules |
| Data migration | Master data, items and history move to the new system | Cleaning the starting data |
| Training and testing | Users try the real flows before go-live | The presence of the people who will use the system |
| Go-live and support | The system goes into production with close support | Precise reports in the first weeks |
Electronic invoicing is worth checking separately, because flows to the Italian Revenue Agency’s exchange system (SdI) do not tolerate days of suspension.
At Aesir Srl we are a Gold Partner of NTS Informatica, and the heavy part of the work is process mapping and training people rather than the licence. Within the same organisation we also handle CRM and sales data quality and treasury: when the ERP has to talk to the rest of the information system, the company does not coordinate three vendors passing responsibility back and forth. Our five business units, Aesir Operations & Security, Aesir Cloud Platform, Aesir Intelligence, Aesir Business Solutions and Aesir Digital Labs, cover infrastructure, applications and data under the same contract. We work on projects across Italy and, on specific request, in Switzerland, the United Kingdom and the United States.
Frequently asked questions
Can the project start with only some modules?
Yes, and in most cases it is the recommended choice. You switch on the areas that solve the most urgent problem, bring operations up to speed, then assess the next extension on the results achieved.
Is a modular ERP only for manufacturing companies?
No. Service companies working by job or on recurring contracts often have a more urgent need, because the cost of work delivered is less visible than the cost of a material.
How complex is it to replace the existing ERP?
Complexity depends on the starting data more than on the software. Duplicate master data, inconsistently coded items and incomplete history lengthen the migration more than any functional requirement.
What are the phases of a project?
Process analysis and mapping, choice of areas, configuration, data migration, training, testing, go-live and support in the following weeks. The phases cut to save time are analysis and training, and they are the two that end up costing most.
Let’s talk
Anyone who suspects a problem of this kind can check it on their own. Two measures are enough: how many spreadsheets are needed to close the month, and how many days pass between closing and the moment management sees a reliable margin. If that number of days is excessive, the cause lies in the information system and not in the people who work with it. A modular ERP serves to reduce those days, not to add screens.
If you would like to explore the topic or assess your company’s situation, fill in the form at the bottom of the page or write to support@aesir-tech.it: we will book a free consultation and start from your numbers.