Our work

Proof you can inspect: the systems we build and run ourselves.

Client names stay confidential. Here is the kind of work we have delivered for clients, the products we build and run ourselves, with their interfaces, architecture decisions and trade-offs, and illustrative examples of how a client engagement starts.

See delivered workExplore the build story

Delivered for clients

Work we have delivered.

Client names stay confidential. Here is the kind of work we have delivered.

  • Delivered · Contracting
    A UAE contracting company

    Odoo ERP implementation.

  • Delivered · Automotive
    An automotive services company

    A customer portal and mobile application. Automotive operations ↗

  • Delivered · Public sector
    A UAE public-sector authority

    AI-based automated design validation. Government & public sector ↗

01 / Digital Cubic product build

ArkanCS. An approval is more than a status.

Construction work moves between people, documents and decisions. The system needs to retain who acted, in which role, and against which record.

Inside the architecture

Every decision has a context.

Document
The record being reviewed.
Approval event
The decision and its history.
Actor + role
Who acted and in what capacity.

These relationships support delegation, approval history and role-based visibility.

Explore ArkanCS
Illustration of connected architecture layers, records and decision pathways
AI-generated architecture illustration. The explanation draws on our published Arkan architecture article; the image is not a product interface or client artefact.
  • The requirement

    Keep the decision in context.

    Drawings, submittals and inspections need clear ownership as work moves from site to office.

  • The design decision

    Model the event, not just the result.

    Arkan’s published architecture describes an approval as an event against a document, performed by an actor holding a role.

  • What this supports

    Rules that can evolve.

    Delegation and approval history sit within the model, keeping each decision connected to the person and record behind it.

Read the decision and its trade-off

A single status field is simple, but it only remembers the latest state. An event model retains the actor, role and history; those relationships also need deliberate modelling and maintenance.

Our published article explains this choice across Arkan’s construction and ERP platforms. Its contractor scenario is an explanation of the architecture, not a separate customer case study.

Read the architecture article

More from our product work

Different operations. Deliberate systems.

Five more Digital Cubic products: the business platforms, and the platform we operate them on.

Explore each product to inspect its interface and operating scope. Names and figures in the LuminaEduSync screenshot are blurred.

Illustrative engagement examples

What a first engagement could look like.

Five common starting points. These remain illustrative scopes, not the delivered work above and not client case studies.

Related expertise

Bring this thinking to your next system.

Start a conversation

A similar challenge in your organisation?.

Free 30-minute discovery call. Bring the workflow; we’ll tell you whether it’s a product fit, a custom build or neither.

Discuss a similar build