Contracts, generated and governed.
Start from a bilingual template, auto-fill it from live project data, route it for approval, then stamp and sign — with every version kept, immutably.
Six default contract templates cover the common cases, in Arabic and English. Placeholders fill themselves from project data — parties, scope, values, dates — so a contract is drafted in moments rather than rebuilt from a copy of the last one.
From there it's governed: the contract moves through an approval workflow, stamps and signatures are applied, and every change is versioned. Earlier versions are immutable, and change requests are tracked — so the history of an agreement is never in question. (Contracts are independent of ZATCA.)
Contracts
Six bilingual templates
Six defaults in Arabic and English, ready to use out of the box.
Auto-fill from project data
Placeholders populate from the project — parties, scope, values, and dates — with no re-keying.
Approval workflow
Contracts route for review and approval before they're issued.
Stamp & signature
Apply the company stamp and signatures to the approved document.
Immutable versioning
Every version is preserved and locked; change requests are tracked against it.
Independent of ZATCA
Contracts are their own workflow — no tax-invoicing dependency to manage.
See it on your projects.
Project Vision is in active development. Join early access to get a walkthrough on real data.