Frequently Asked Questions

• How much does a project cost?+

  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 afterward. We start with a short discovery that maps your workflow and turns it into an architecture and a phased plan, so you see the shape and cost of the first module before committing to the whole build. One honest self-check: if a core internal system is worth a real annual investment to your operation, you are in range; if you are shopping for the cheapest possible vendor, we are not the right fit.

• Are we too small for you?+

  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.

• Do we own the code and the IP?+

  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 — Arkan, 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.

• What does "operate" cost on an ongoing basis?+

  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 quote this as a clear monthly or annual figure, not a vague retainer, so you can decide whether operating it yourself or having us run it makes more sense. Many clients have us operate the system through the first period, then revisit once their own team is comfortable.

• How long does a typical project take?+

  It depends on the engagement, and we work in modules so you see something real early instead of waiting for one large launch. A focused internal system or a first product module typically reaches a usable first release in a few months, with further modules following in controlled stages. A full platform — an Arkan-based construction or ERP rollout, for example — is a longer, phased program measured across quarters, while a well-scoped AI workflow tool or MVP can move faster. We commit to timelines against a defined scope after discovery, not before.

• Where is our data hosted, and is it secure?+

  We can host in-region, including the UAE and the wider GCC, when data residency matters to you or your regulators. Hosting runs through Vloud, our own cloud operations layer, with role-based access control, production monitoring, and ErrorLens watching for issues — the same stack we run our own products on. Security is designed into the architecture from the start: permissions, approvals, and access control are built in early, not bolted on later. If you prefer your own cloud account or an existing provider, we can deploy there instead.

• Do you work in Arabic as well as English?+

  Yes. We build and operate systems for Arabic and English users, including right-to-left interfaces and bilingual data, and we run client conversations, documentation, and support in both languages. This is native to how we work across the UAE and the GCC, not an add-on. Arabic and English environments are a standard part of our Arkan platforms.

• Are Arkan, Vloud, and ErrorLens real, live products?+

  Yes. Arkan, Vloud, and ErrorLens are real products we build, host, and operate ourselves — not concepts or slideware. Arkan covers construction management, project-driven ERP, and property management; Vloud is our cloud deployment and hosting layer; ErrorLens is our AI-assisted debugging and monitoring layer. You can see them on our products page; they are the proof behind how we build and run software for clients.

• What happens if the build runs into trouble, or we are not happy?+

  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.

• Do you only work in construction and real estate?+

  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 facilities management, service and maintenance operations, logistics and field teams, multi-branch operators, enterprises, and select product teams. If the workflow is the business and generic software does not fit it, we can build for it.

• How do you use AI, and who is responsible for quality?+

  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.

• How do we get started?+

  It starts with a conversation about the workflow you are trying to build or fix, not a sales deck. From there we run a short discovery to map how your business actually works and turn it into an architecture and a phased plan, so you see the shape, sequence, and cost before committing to a full build. The fastest way to begin is to tell us what is slowing your operation down.

Still have a question? Tell us about the workflow you are trying to build or fix and we will answer it directly — an engineer replies, not a sales bot. Or email hello@digitalcubic.com.