Most of the ERP work we do starts with a company that bought something first. ERP is the software that runs finance, stock, purchasing and payroll in one place. The product they bought was perfectly reasonable. It was also built for a market with different tax rules, different invoicing expectations, and customers who read left to right.
Where bought software holds up
Accounting, payroll and the system that tracks your customers and sales are close to solved. If your requirements there are ordinary, buy. The vendor has spent more on that one part than you could ever justify, and connecting it to your other systems is a well trodden path.
Buying also wins when your process is genuinely standard and you are willing to change the parts that are not. That second clause is where most implementations come apart, because nobody says out loud during selection that the business will have to adapt.
Where it stops holding up
VAT in dirhams, calculated and filed the way the Federal Tax Authority requires, is not a checkbox in a foreign product. Neither is an invoice in two languages, a customer who pays a deposit at booking and the balance at collection, or a production queue that moves work between branches.
We built a till and ERP system for the apparel trade here because tailors, abaya and kandura ateliers work in a way no international product copes with. Measurements saved against a customer. Deposits. Work in progress across several branches. Order updates over WhatsApp, because that is where the customer already is.
You can force a foreign product to do some of that by paying somebody to alter it. Then you own those alterations permanently, and every time the vendor releases an update somebody has to make them fit again.
The middle option people forget
Buy the ordinary parts, build the part that makes you different, and connect the two properly. Accounting from a product, the operational core built for how you work, one well-defined place where they meet.
This is usually right and it is the hardest to sell internally, because it needs somebody in your organisation to own the join rather than a single vendor to blame.
The question that decides it
Cost is the wrong test. Ask whether the way you do this particular thing is an advantage you would defend, or simply how you ended up doing it after fifteen years.
Build the first. Buy the second and change your habits to match. Getting it wrong in either direction is expensive: writing your own accounting ledger from scratch is a waste of everyone's time, and bending your entire order process around a product designed for another market is worse.
One practical test
Take your three most awkward orders from last month. Not the typical ones, the awkward ones. Ask the vendor to put them through the system from start to finish during the demonstration, in front of you, without preparation.
You will learn more in that hour than from any feature comparison.
Working through this on a live programme?
A 45-minute call with the engineer who would run the work. We will tell you whether AI is the answer, including when it is not.