عContact us

Why Mutamad

Built here.
Not translated here.

The argument

A vertical-building project record does not begin with the first inspection request or end with an interim payment. It begins at tender and contract, passes through design, procurement, delivery, approval, and payment, then remains accountable through handover and archive.

When every phase lives in a separate system, the link breaks between what was requested, what the parties contracted, what was built, what was measured, and what was paid. Proving a decision becomes manual reconstruction across email, spreadsheets, and files.

Mutamad preserves that link. It is the system of record for vertical-building delivery, authored from Saudi contracting and site practice on primitives that adapt to each project.

What we did differently

The whole lifecycle, not an isolated document register.

Mutamad connects tender and contract to drawings, submittals, inspections, accepted work, certification, payment, and handover. Every phase can see the evidence before it and the consequence after it.

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.

The authorized human owns the decision.

Capability, membership, payment, and AI assistance do not grant contractual authority. Approval, signature, payment certification, and taking-over remain authenticated human actions under current project authority.

Ready building packs over one kernel.

A project starts from its sector pack: villa compound, apartments, residential tower, offices, showroom-and-office strip, hotel and serviced apartments, or school. Terms and policies vary; the project record stays one.

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.

Ask the record and get the evidence.

Ask Mutamad answers from project records and cites its sources. It can read, analyze, and draft, but it cannot approve, sign, certify, or perform a contractual action.

We interoperate where specialists own the tool.

We import programme and BOQ data and connect Industry Foundation Classes, BCF, and cleared-invoice references. We do not rebuild scheduling, estimating, CAD, or accounting engines.

The ledger

We built —

  • Arabic-primary forms with official Arabic stamps
  • Hijri and Gregorian dates throughout
  • A connected lifecycle from tender and contract to payment and handover
  • An audit record of the decision, authority, and evidence
  • Machine-generated numbering, locked at issue
  • Ready delivery packs for seven vertical-building sectors
  • Project intelligence that cites records and never replaces human authority
  • 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
  • Let payment or AI create contractual authority
  • Rebuild scheduling, estimating, CAD, or accounting tools
  • Build for a market we have not lived in

The point

The project is one lifecycle. Its record should be one too.

Walk through your project lifecycle with us.

Talk to us