The tender wanted the same twelve documents again, in Arabic, by Thursday
Electromechanical contractor · Category 4 · about thirty-five staff · 2026
Engagement overview
Engagement details are anonymised and composited to protect client confidentiality.
The situation
A contractor bidding for ministry maintenance work and subcontracting from a larger prime. Each tender arrived as a hundred or more pages of Arabic conditions, read by the owner on his phone, late at night, to find the bid-bond amount, the classification demanded, the local-content percentage and the submission date. An assistant then assembled the same supporting documents, licence, classification, PIFSS clearance, SME-status proof, as scanned PDFs, again. The tender was extended twice; the pack was re-uploaded twice.
What was breaking
The re-submission burden was already real. The amendments to the Public Tenders Law published on 27 September 2026 (Law 94 of 2026, in force three months after publication) then raised the stakes for small contractors: a tender must be awarded to an SME whose compliant bid is within ten percent of the lowest, at least thirty percent of awarded works must be subcontracted locally with a tenth of that reserved for SMEs, and the threshold for direct contracting without the Central Agency for Public Tenders rises from KD 75,000 to KD 1,000,000. More tenders the firm could win, and a prime asking for subcontracting evidence the firm had never had to produce.
Source Law 94 of 2026 amending the Public Tenders Law (Gazette, 27 September 2026)
What we built
Two parts. First, Arabic tender extraction: upload the PDF, receive a checklist of requirements, amounts, dates and required attachments, each with a page reference so the owner can verify the line against the document. Everything is presented as "found on page N", never as advice. Second, a maintained company dossier that produces a bid pack on demand, with the version date on every supporting document and a warning when one will expire before the submission date, plus a per-contract ledger of subcontracting percentages, built ahead of the law's entry into force.
- Tender conditions.pdf
- Licence scan.pdf
- Classification.pdf
- PIFSS clearance.pdf
- SME status proof.pdf
- Bid bond2% of bid value, valid 90 daysPage 7
- Classification requiredCategory 4 or higher, electromechanicalPage 12
- Submission deadlineSun 14 Dec 2026, 13:00Page 31
What stayed untouched
The CAPT and ministry portals: a person uploads. The estimator's pricing spreadsheet. The accountant.
Where AI did the work
Reading Arabic tender conditions and pulling out what matters, with the page it came from. The dossier and the bid pack are plain workflow.
AI did the reading
Where the data lives
Supporting documents and tender files are stored and processed inside Kuwait.
What changed
The owner reads a checklist first and the tender second. Expiry warnings arrive before the bid window, not inside it. The subcontracting ledger answered the prime's first request in an afternoon.
All case studies Next case The ratio changed every time a permit was issued →
- reads a checklist first and the tender second
- Expiry warnings arrive before the bid window
- in an afternoon
Get this as a package
The system in this case study is available as a fixed-scope package, with a stated delivery time and an indicative price range.