Arabic is an operating language, not a translated interface.

01Native composition

طلب شراء رقم PO-2048

02Operational terms

الاعتماد · الحالة · المسؤول

04Print and forms

فاتورة ضريبية · ٢٠٢٦

A system can look translated and still fail in Arabic. We design direction, hierarchy, terminology, search, documents, data entry, print, and mixed-script behavior as one complete Arabic operating experience.

Native composition

01Native composition

طلب شراء رقم PO-2048

02Operational terms

الاعتماد · الحالة · المسؤول

04Print and forms

فاتورة ضريبية · ٢٠٢٦

Arabic receives a real right-to-left composition with mirrored layout logic, purposeful line lengths, Arabic typographic rhythm, and correct emphasis. It is not English content moved to the other side.

  • True RTL layout
  • Alexandria typography
  • Arabic information hierarchy
  • Mixed-script isolation

Operational terminology

01Native composition

طلب شراء رقم PO-2048

02Operational terms

الاعتماد · الحالة · المسؤول

04Print and forms

فاتورة ضريبية · ٢٠٢٦

Names for roles, policies, documents, fields, approvals, and institutional structures are treated as product decisions. The wording must match how the organization actually works.

  • Reviewed terminology
  • Institution-specific vocabulary
  • Consistent field names
  • Clear approval language

Arabic documents and retrieval

01Native composition

طلب شراء رقم PO-2048

02Operational terms

الاعتماد · الحالة · المسؤول

04Print and forms

فاتورة ضريبية · ٢٠٢٦

Nasaas accounts for Arabic reading order and reconstruction. Smart Archive builds Arabic-first retrieval. ERP carries Arabic through interface, search, workflow, documents, and print.

  • Reading order
  • Search and normalization
  • Arabic forms and outputs
  • English and Arabic records

English remains complete

01Native composition

طلب شراء رقم PO-2048

02Operational terms

الاعتماد · الحالة · المسؤول

04Print and forms

فاتورة ضريبية · ٢٠٢٦

English is not removed or reduced. Both languages are built as first-class operating experiences, with additional language needs shaped per deployment.

  • Equivalent routes
  • Localized metadata
  • Language-preserving navigation
  • Deployment-specific language scope

Begin with one system, one automation, or one AI agent.

01Need

Real work

02Design

Clear boundary

03Pilot

Working evidence

04Decision

Scale or stop

That may be all the organization needs, or the work can extend as far as its ambition requires. We begin with the real need and prove the value with the people who will own the result.

Choose where to begin