Questions buyers ask us. Straight answers.

There is no public price list, because price follows scope and we scope before we quote. The main cost drivers are the number and complexity of workflows, how many systems it must integrate with, the depth of roles and approvals, whether you need mobile as well as web, and whether we host and operate it afterwards. After a free 30-minute discovery call, we map your workflow and confirm scope, timeline and price in a written proposal, so you see the shape and cost of the first module before committing to the whole build.

Timelines depend on scope; we confirm them in a written proposal after discovery. We work in modules, so you see something real early instead of waiting for one large launch, with further modules following in controlled stages. A focused internal system moves differently from a full platform such as an Arkan-based construction or ERP rollout, which is why we commit to dates only against a defined scope.

They depend on the project, so we set them out in the proposal and agreement for each engagement. You see them in writing, alongside scope, timeline and price, before you commit to anything.

Yes, if you need one. Mention it when you get in touch, and we will sign it before you share the details.

Our team works Sunday to Thursday, 8:00 AM to 6:00 PM Gulf Standard Time (GST, UTC+4). Any extended support is agreed per engagement and set out in the agreement.

Yes. For the tailored system we build for you, you own the source code and the intellectual property for that custom work. Our own products and tools — Arkan, LuminaEduSync, Vloud and ErrorLens — and the reusable engineering patterns behind our practice stay ours, but the system we build around your business is yours to keep, move, or extend. We put this in writing in the agreement, so there is no ambiguity later.

You do. Customer data in our products belongs to the customer.

Operating is optional and priced separately from the build, because owning the code means you can host it wherever you choose. If you want us to run it, the ongoing cost covers hosting through Vloud, monitoring through ErrorLens, updates and support, sized to your environment and the level of coverage you need. We set it out in the written proposal alongside the build, so you can decide whether operating it yourself or having us run it makes more sense.

We deploy to Microsoft Azure and AWS, or to your own cloud account if you prefer. Vloud, our hosting and operations platform, runs our own products and client systems, with role-based access control, production monitoring and ErrorLens watching for issues. Security is designed into the architecture from the start: permissions, approvals and access control are built in early, not bolted on later. Customer data in our products belongs to the customer.

Yes. Arkan is offered as SaaS, and on-premise and hybrid deployments are also available. We agree the right model for your organisation during discovery and set it out in the proposal.

Yes. Arabic and English are working languages across the company, so you can work with our team in either, from the first call to support. We build bilingual Arabic and English systems, including right-to-left interfaces and bilingual data, and ArkanCS and ArkanPM offer Arabic and English interfaces. Tell us your preference when you get in touch. This website itself is currently in English.

Yes. Every product we build is ours and is offered as SaaS. ArkanCS covers construction management, ArkanERP covers ERP for project-driven businesses, ArkanPM covers property management and LuminaEduSync covers school operations and timetabling. Vloud is our hosting and operations platform, which also hosts client systems, and ErrorLens is our error monitoring and debugging product. There is no public price list; get in touch and we will show you a live demo in a meeting. See them all on our products page.

Size matters less than fit. What we look for is a workflow that genuinely matters to your business and has outgrown spreadsheets, WhatsApp approvals, and disconnected tools. Because we build in modules, a smaller company can start with one system that earns its keep and grow from there, without paying for scope it does not need yet. If the work is real and you want it built properly, you are not too small.

Our delivery model is built to catch that risk before it becomes expensive. Because we architect first and build in modules, you review and sign off on usable parts in stages rather than discovering problems at one large final launch — if a direction is wrong, we catch it early and correct course. Scope, milestones, and what "done" means for each module are agreed in writing, so expectations stay concrete. If something is not right, we fix it against that agreed scope; you are never left with a half-finished system and no path forward.

No. Construction and real estate are our deepest strength — that is where Arkan lives and where we understand the workflows best — but our core capability is building tailored systems for any operations-heavy business. We also build for automotive operations, government and the public sector, education and enterprise operations, and for other operations-heavy businesses. If the workflow is the business and generic software does not fit it, we can build for it.

We use AI-assisted workflows to move faster across prototyping, documentation, testing support, and debugging — part of why we ship quickly. But our engineers stay accountable for architecture, review, security, and production readiness. AI improves velocity; engineering discipline protects quality. You are hiring builders who own the outcome, not an automated code generator.

It starts with a conversation about the workflow you are trying to build or fix, not a sales deck. Submit the form and our team will get in touch to arrange a free 30-minute discovery call. From there we map how your business actually works and confirm scope, timeline and price in a written proposal, so you see the shape, sequence and cost before committing to a full build.