عContact us

Why Mutamad

Built here.
Not translated here.

The argument

For two decades, the way to manage construction documents on a project was to buy a platform built somewhere else. Melbourne. Carpinteria. London. Translate the chrome. Configure the forms. Train the team. Hope the consultant accepts the workflow.

The reason that path persisted is that no one had taken the time to author the alternative. The forms are specific. The chain of command is specific. The legal record is in Arabic. The Hijri date matters. A WIR is not an RFI, and an A-coded response is not an “approved.”

Mutamad is the product that took the time. Designed against the workflow you actually run — not the one your platform vendor was willing to support after a six-month configuration phase.

What we did differently

We started with the native form set.

WIR. NCR. MS. PQD. These are not templates you configure in Mutamad. They are the objects the product is built around. The A / B / C / D response codes your consultant uses are first-class fields, not custom strings someone added at kickoff.

We made Arabic the source of truth.

The signed Arabic record is the one with legal weight. Mutamad treats Arabic as the default locale and composes the form, the stamp, and the audit line for it first. English mirrors. We did not flip a layout right-to-left and call it done.

An audit trail that cannot be rewritten.

Every approval, every rejection, every edit: timestamped and recorded in a way that prevents deletion or retroactive modification. When the parties disagree, the audit trail is the record, not someone's memory.

We modelled the consultant chain.

The project gate is the consultant. The approval chain — contractor → consultant → client — is the default routing, not a workflow you configure for three weeks with an integration partner.

We generate the numbering. Once.

WIR-CIV-0287 is issued by the system. It does not get re-negotiated in a kickoff meeting. It does not vary by package. Numbering discipline is not a policy document — it is the schema.

We charge per project.

No per-seat, per-year, three-year-minimum conversation. No "enterprise" tier to unlock automation that should have been default. You pay for the project you are running.

We ship in days, not quarters.

No twelve-week implementation phase. No partner-led kickoff in a hotel ballroom. Bring the registers; we map them on import. The team starts logging this week.

The ledger

We built —

  • Arabic-primary forms with official Arabic stamps
  • Hijri and Gregorian dates throughout
  • Native WIR, NCR, MS, PQD with A / B / C / D response codes
  • An immutable audit trail that settles disputes
  • Machine-generated numbering, locked at issue
  • A contractor → consultant → client default chain
  • Per-project pricing
  • A 2026 craft bar

We did not —

  • Re-skin an American RFI / Punch model and call it Arabic
  • Bolt the product onto a database vendor's enterprise sales motion
  • Ship a configuration phase as the product
  • Translate the email templates and leave the audit trail in English
  • Price the product against a US general contractor's program budget
  • Make automation a tier upgrade
  • Build for a market we have not lived in

The point

Mutamad is not the only way to manage construction documents on a project. It is the one that was built for it.

See a live register. Twenty minutes.

Talk to us