LAFTAH · لفتة
One system for the construction operating cycle — projects, procurement, inventory, workforce, documents, finance, and reporting — built as a modular monolith so every module shares the same data instead of syncing copies of it.
The operational context everything else hangs off of.
Requisition through receipt, with three-way matching.
A real movement ledger, never a bare editable quantity.
The vendor-side mirror of customer contracts.
Labor hours become labor cost, on the record.
AI-assisted extraction, reviewed before it counts.
A real double-entry ledger underneath everything else.
Supplier and customer invoices, vendor and customer payments.
Budget vs. committed vs. actual vs. forecast — computed live.
Trial balance, P&L, AP/AR aging, and project profitability.
A ZATCA integration boundary — built honestly, not oversold.
Every record belongs to one organization, enforced everywhere.
Procurement, in practice
Purchase requisitions, RFQs, and purchase orders, routed through a configurable approval workflow.
Illustrative product view
Requisition through receipt — every supplier invoice matches against what was ordered and received.
Documents, in practice
Nothing from an extraction posts to the books unreviewed: a human confirms or corrects it first.
Illustrative product view
Nothing from an extraction posts to the books unreviewed — a human confirms or corrects it first.
LAFTAH is a modular monolith by design — not microservices, not a patchwork of disconnected tools. Every module reads and writes the same underlying data, so a purchase order, a timesheet, and a posted invoice all show up correctly wherever they matter.