The ERP buyer’s guide — read it before you sign with any vendor
Choosing an ERP is a decision you live with for years, and the whole market sells the same promises in the same words. This guide works against any vendor — including us: when you actually need a system, what your real options are, and the questions that separate serious partners from salespeople.
Signs your business has outgrown Excel and WhatsApp
The symptoms are familiar to anyone who has lived them: the stock number in the sheet disagrees with the shelf, month-end close takes a week of manual reconciliation, and a customer asking about an order triggers a search expedition through WhatsApp groups. If one employee going on leave freezes information nobody else holds, or big decisions rest on numbers that are "roughly right" — the problem is no longer discipline, it is expired tooling. Excel is a superb analysis tool; it was never designed to be an operational database ten people write to at once.
Build from scratch? Buy? Or "a developer we know"?
Building custom gives you a perfect fit, but the real cost is not the initial development — it is ten years of maintenance and hiring people to understand code written by someone long gone. The freelancer looks faster and cheaper, but is a single point of failure: when he gets busy or leaves, your system is orphaned and undocumented. Buying — global, local or open-source — gives you the maturity of thousands of companies before you, and the real question is never "does it work?" but "who implements it, and what happens when I need a change?". Each path has its use case; choose knowing the deferred price of each.
Ten questions to ask any vendor — in writing
The full guide phrases all ten so you can put them in front of a vendor verbatim. The heaviest four: who owns the data, and can I export all of it in an open format without asking permission? What is the upgrade path — do my customizations survive it or break? How deep is the Arabic — screens and reports that genuinely run right-to-left, or a translation skin over a foreign system? And what does leaving cost if I walk away in three years? A serious vendor answers in writing, inside the contract; the one who dodges the exit question is telling you his plan without meaning to.
Red flags that mean: slow down
Beware a quote that does not separate licensing from implementation from support, and a vendor promising to switch every department on at once — successful rollouts move in phases. Beware even more the one who pushes for a signature before seeing your data or asking about your actual workflow, or who builds your customizations inside the system core, cutting you off from every future upgrade. The clearest flag: references you cannot verify. Ask to speak with a real customer running the system today — one call saves months of regret.
Pilot before you commit — a proper trial
A real pilot is not a demo on pre-staged data. It is a trial instance loaded with a sample of your items, your customers and your invoices, operated by the employee who will actually use it — not their manager. Pick one complete cycle — customer order to cash collected, say — and measure it yourself: did the team finish without calling the vendor at every step? Did the numbers match your books? A successful pilot does not mean signing for everything; it means moving to the next phase under a clear contract.
Realistic implementation timelines by company size
A small company with one core cycle typically goes live within a few weeks if its data is clean. A mid-size company with multiple branches or activities needs one to three months, in phases where each area stabilizes before the next begins. Larger organizations are measured in phases, not in a single end date. The golden rule: a promise dramatically shorter than that does not mean a faster vendor — it usually means nobody has sat down with your real business yet.
We wrote it vendor-neutral — because we answer the same ten questions in writing
Every rule in this guide applies to us too: the "Why Jirsi" page answers data ownership, upgrade path and exit cost question by question — on the same foundation our vertical products run on today.
Why Jirsi ←Is this guide genuinely neutral, or marketing in disguise?
The ten questions and the red flags work against any vendor — including us — and the guide names situations where ERP is honestly not your right move yet. Our only pitch is one page at the end showing how we answer the same questions ourselves. Judge for yourself.
We are a small company — is ERP premature for us?
The measure is not headcount but the cost of chaos: if inventory errors and late collections eat your time daily, you are late, not early. The guide includes a checklist that settles the question for your specific case.
We tried a system before and the rollout failed — what prevents a repeat?
Most failures are implementation failures, not software failures: open-ended scope, data migrated without cleaning, a team never trained on its own screens. The pilot chapter exists specifically to cut off that scenario.
Does "open source" mean lower quality and weaker support?
Usually the opposite: open code is tested by thousands of companies, and you are not hostage to a single vendor for support or survival. Quality is measured by the same ten questions — data ownership and upgrade path — not by the license type.
If I download the guide, will sales calls chase me?
No. You get the guide and a handful of emails with similar practical content, with unsubscribe available from the first one. No calls unless you ask for one.
Download the full buyer’s guide free — and if you want a straight opinion on your situation, a call with Saleh is one message away.