Short answer. In many SME manufacturing firms the operation lives in islands: the quote in Word, the planning in Excel, the stock in another file, the bookkeeping in Exact. As a result you enter the same data over and over and you work with yesterday's numbers. A new, heavy ERP feels too expensive and too complex, and it does not solve the fragmentation on its own. The goal, one source with control and less manual work, often calls for a process that fits the islands you already have.
The quote sits in Word. The planning in Excel. The stock in yet another file. The bookkeeping in Exact. And at every step you enter the data again.
It feels like work, but it is retyping. And every time you do it, something can go wrong.
Islands of Excel and Word are not a system
Each file works fine on its own. Together they form a patchwork in which no one owns the whole. The quote does not know what the planning is doing, the planning does not know what is in stock, and the bookkeeping hears about it last.
The result: double work, errors at the handovers, and not a single point where the truth comes together.
You work with yesterday's numbers
Many manufacturers run Exact for their administration, but the reporting falls short for production. So you export to Excel to turn it into something usable. By the time that is done, you are steering on yesterday's numbers.
That is exactly the wrong moment. In production the situation changes by the hour: a rush order, a machine standing still, material that has not arrived. Yesterday's numbers do not show that.
Why a new ERP does not solve the fragmentation
The reflex is a big ERP. But for an SME manufacturer that often feels too expensive and too complex, and rightly so: a heavy package forces you into its process instead of the other way around, and the islands keep existing around it because the package does not cover your specific way of working.
A new package that does not remove your old fragmentation is just more expensive double work.
Where standard packages stop
The happy path is covered. For make-to-order manufacturing there are ERP and planning packages (Limis, CAPE and others) that handle the standard flow. The limit lies where your process deviates:
- A quote that runs through your own calculation and routing logic.
- Planning that accounts for your machines, changeover times and people.
- Cost price and post-calculation that include your hidden costs.
The question is not which package, but which goal you want to reach: control, numbers that add up, less manual work. That is why I first review your process thoroughly, because some islands have simply grown that way and can be done smarter or dropped. What remains, connecting quote, planning, stock and invoicing into one source, I build, fitted to what you already use. It has to be sorted one way or another. The question is whether it cannot be done smarter today than in separate files.
Frequently asked questions
How do I stop entering the same data over and over?
By making one system the source that quote, planning, stock and invoicing all draw from, so an order is entered only once. With separate islands that calls for a connection that fits what you already use.
Why is ERP often too expensive and too complex for an SME manufacturer?
Because a heavy ERP is built for large, standardized processes and forces you into its way of working. For a smaller manufacturer with its own way of working that means high costs and an implementation that still leaves Excel islands behind.
Why does the reporting in Exact fall short for production?
Because Exact is strong in administration, but production needs current numbers by the hour (planning, capacity, stock). That is why many firms export to Excel, and then you are steering on yesterday's numbers.
When is my manufacturing firm ready for custom work instead of a package?
When your process does not fit a standard package and you keep islands around it. Then a process that connects your existing systems is often cheaper and more fitting than a heavy new ERP.
Further reading
- Replacing Excel for production planning: from chaos to control
- You do not know what an order really costs until the post-calculation
I am Ricardo Theijs of RNT Projects. With a background in enterprise process management (UWV, Centric, G4S, MSc Business Process Management) I build systems that turn fragmented operations into one whole. I tell you honestly when a standard package is enough.
Running into this yourself?
I review your process and build the solution where a standard package falls short. Remote, with visible results in two weeks.
Let's talk