Questions and answers

No. Both the HR management system and the warehouse & inventory system are in development. We state that on every page rather than implying otherwise, because discovering it later would waste your time and ours.

It means the scope is being designed and built, and that what you see described is intent rather than delivered functionality. Practically, it means the useful conversation right now is about your operations and whether what we are building fits them — not a demonstration or a purchase.

Because at this stage what a business tells us can still shape the product. If your operation has a requirement we have not accounted for, it is far easier to address now than after release. If you would rather wait, that is entirely reasonable and we will say so.

We are not publishing a release date. A date we are not confident in is worse than no date, and a company that gives you one it cannot keep has told you something about how it will behave later.

Both. We operate through two complementary paths: standardized Arkanex applications and tailored ERP solutions. Our services include custom development, integration, deployment support and ongoing technical support, and an engagement may combine more than one of them when the need calls for it.

Usually you do not, and that is worth hearing from a company that sells it. Custom development earns its cost when a process is genuinely specific to your business and is a real source of advantage or difficulty. If a ready-made product covers it, adapting to the product is normally cheaper and lower-risk.

That is what the integration service is for, and it is assessed case by case — what a connection involves depends on what the other system allows. We will tell you what is straightforward, what is awkward, and what is not worth doing.

Ongoing technical support is one of the four services, and we treat deployment as a beginning rather than a handover. Systems need adjustment as processes change; we plan for that instead of treating it as an exception.

Businesses that have outgrown spreadsheets and informal coordination, but are not yet running a large enterprise platform. If you have a dedicated systems team and an established software estate, you probably need a different kind of supplier.

With a conversation about how your business currently operates — not a product demonstration. From there we scope the work explicitly, including what it does not cover. The stages are described on the How We Work page.

Yes, and we treat both as first-class rather than translating one into the other at the end. Retrofitting Arabic into a system designed in English is expensive and usually done badly, so we design for both from the start.

We do not publish pricing, because the honest answer depends on scope and we would rather not quote a number that turns out to be meaningless. Cost is discussed once there is a shared understanding of what the work involves.

You do. We also think you should be able to get it out in a usable form, and we would rather be kept because the system is worth keeping than because leaving is difficult.

It is used to respond to your enquiry. A full privacy notice is being prepared, and until it is published the contact form on this site stays closed rather than collecting personal data without one.

Your data is yours and your processes should be documented well enough that another supplier can pick them up. Building a dependency that is painful to unwind is a way of keeping clients we would rather not use.