Custom ERP vs Ready-Made Software: How to Choose

A business owner who needs a system has two roads. Buy a ready-made ERP package and set it up, or have a system built for the business. Both can be the right answer. The wrong answer is choosing without knowing what you are trading.

I build custom systems, so you might expect me to say "always go custom". I will not. Here is the honest comparison.

When ready-made software is the right choice

Ready-made ERP is strong when your work looks like everybody else's work.

• Your processes are standard. Buying, selling, stock and accounts follow the usual pattern.
• You need it quickly. A package can be running in weeks.
• You have people to manage it. Someone on your team can learn the package and look after it.
• You are happy to change your process to match the software. This is the real cost, and many owners do not see it until later.

If these are true for you, buy a package. Do not pay to rebuild what already exists.

When a custom ERP is the right choice

Custom software earns its cost when the way you work is different, and that difference matters.

• Your process does not fit the screens. If staff must enter one real event in three places, they will stop entering it.
• Your industry has its own shape. A textile processing mill tracks one lot through many stages, with loss and reprocessing on the way. General inventory software does not model that well.
• You are paying for modules you never open. Large packages are built for everyone, so most of what you see is not for you.
• You must keep your data on your own network. Some businesses will not put their figures on someone else's servers.
• Your staff already have a way of working. When I replaced the mill's old system, I kept the screen numbers people already knew. Training took far less time because nothing felt new.

The costs people forget

With ready-made software:

• Licence or subscription fees, often for every user, every year
• Paid customisation each time the package does not fit
• Work that still happens in Excel beside the system

With custom software:

• It takes longer before the first screen is in use
• You depend on the developer, so choose one who documents the system and hands over the code
• Someone must maintain it after launch

A middle road that works well

You do not have to build everything at once. The approach I recommend to most owners:

1. Find the one department where the pain is worst
2. Build that module first and put it in real use
3. Add the next department only after the first one is trusted

You spend in steps, you see results early, and you can stop at any point with a working system.

Five questions to ask before you decide

1. Can I describe my process in the software's words, or only in my own?
2. How many people must enter data at the same time?
3. Which three reports do I need every single day?
4. Where must my data be kept?
5. Who will look after the system in two years?

If your answers sound like a normal trading business, a package will probably serve you well. If they sound like nobody else's business, a system built for you will cost less in the long run than years of working around the wrong software.

Still unsure? Describe your business to me. I will tell you plainly which road I would take, even when the answer is "you do not need me".

Related reading: 7 signs your factory has outgrown Excel and Access and what decides the cost of custom ERP software.