When Kuwait delivery needs a platform, not another WhatsApp group

The job is running a delivery day in Kuwait. A restaurant places an order, someone assigns a rider, the rider proves the drop, and money has to land in the right wallet.

That is not “an app.” It is four seats: merchant, dispatcher, driver, and the fleet company that pays the rider. WhatsApp and a sheet can hold a small day. They break when two people assign the same order, or when cash on delivery has no owner.

What we decide on a first call

How many merchants and riders you already have, not the number on a pitch. Who assigns today, and what they do when a rider goes silent. Whether addresses are area / block / street, and whether cash is still common. Who holds the float.

If you have one dispatcher and a dozen drops, a product is usually early. Fix the sheet and the group rules first.

If several companies share riders, or merchants are already asking for a login, the job is a platform. The Manzil delivery case study is that shape: merchant portal, live map, driver offers, fleet company view, KWD wallets, Arabic and English. We will not start from a feature list copied off a screenshot.

This is not the field-photo address reader. Reading a house number off a phone photo is a later, narrower job. We will keep them apart.

What we will not sell as the first slice

We will not open with a routing model if nobody trusts the live map. We will not add an “AI dispatcher” before offers, timeouts, and a manual override exist.

Kuwait-specific pieces — KNET or MyFatoorah wallets, RTL copy, area-block addresses — belong in the brief. They do not replace the question of whether you need four apps or one honest board.

That sequencing is AI consultancy. A product build comes after you can name the seats and the money path.

Bring one day’s WhatsApp thread and the sheet you already use. Book thirty minutes or write hello@jamilglobal.com.