All work · Launching

Khawarz

خوارز

A Kuwaiti AI company gets an Arabic-first website that explains custom AI agents to enterprises and sends every enquiry to the founders, plus a matching company profile in Arabic and English, all editable from its own admin.

Khawarz, enterprise AI agents · Kuwait
Engineered and delivered by Whisky 11.

The staging site ↗
Client
Khawarz, enterprise AI agents
Region
Kuwait
Status
Launching
Delivery
Whisky 11

The problem and context

Khawarz, a Kuwaiti company that builds custom AI agents for enterprises, needed a site that explains agents to decision-makers in Arabic first, collects qualified enquiries, and lets the founders change their own content, plus a company profile they can send ahead of meetings.

Who uses it

  • Enterprise decision-makers in Kuwait and the GCC, in Arabic or English
  • The Khawarz team, who receive and follow up enquiries
  • Admins who edit content, sections, media and SEO without a developer

What was built

  • Arabic and English site: hero, what we build, the founders' story, industries, architecture, FAQ and a one-page enquiry form
  • Admin with password, authenticator codes and passkeys: sections on and off, every text in both languages, media, leads with Excel export, analytics, SEO and an activity log
  • Enquiries saved and emailed to an editable list of recipients, with a one-tap WhatsApp reply
  • Company profile PDF in Arabic and English, generated from the same copy as the site

How it works

  1. A visitor lands on the Arabic site (English one click away), sees what Khawarz builds, a live agent example and the founders' story.
  2. They send one short enquiry form; it is saved and emailed to the team with a one-tap WhatsApp reply.
  3. Admins sign in with a password plus an authenticator code or a passkey, then edit any text in both languages, switch sections on or off, and export leads to Excel.
  4. The same copy feeds the Arabic and English company profile PDFs, so site and profile never disagree.

How the system fits together

  • Server-rendered pages on Cloudflare Workers (Hono), no client framework, a strict content security policy.
  • Cloudflare D1 holds content overrides, leads, analytics counts and the admin audit log; R2 holds uploaded media.
  • Lead email through Resend; cookie-free first-party analytics; structured data and llms.txt follow whatever the admin edits.
  • Profile PDFs rendered from the site's copy with Playwright.

Technology stack

  • Hono on Cloudflare Workers
  • Cloudflare D1 + R2
  • Resend
  • Playwright (PDF)

Delivery and current status

  • Staging is live and reviewed with the client; launch on the client's own domain is next.
  • Every change ships with automated tests and a live check of the deployed version.
  • Hand-over moves the site, database and email to the client's own Cloudflare and Resend accounts.

Evidence

  • 225 automated tests
  • Checked at 10 screen sizes, phone to desktop
  • Production launch on the client's domain in progress

Scope and operating limits

  • Impact figures are placeholders until the client confirms real numbers.
  • The client owns its content, leads and accounts after hand-over.

← All work · Start a project