Khadamat connects people in Kuwait with local cleaners, plumbers and handymen. Customers find providers on a map, describe the job and book; providers sign up in the same app to take that work; and an admin panel runs subscriptions and platform activity above both. Live on the App Store and Google Play.
Job volume, provider numbers and revenue are the client's to publish, and they are not on this page. What is on this page is what was built and why it was built that way.
Khadamat — Arabic for "services" — is a marketplace for everyday jobs in Kuwait: cleaning, plumbing, bathroom work, maintenance and the rest of the list a household or an office needs done once and done properly. A customer opens a map, sees who is nearby, checks a provider's profile and reviews, describes the job with photos and a completion date, and sends the request. From there the two sides chat in real time, the booking is confirmed, and the customer can track the provider on the way.
It was built for VGA, the Kuwaiti client behind Connect and Munasbati on this site. The brief covered both sides of the market and the operator above them: a customer experience, a provider experience, and an admin panel for registrations, subscriptions and platform statistics. It went live on Google Play in May 2025 and on the App Store in June.
Finding someone to fix a leak or deep-clean a flat usually means asking around, calling a number someone forwarded, and agreeing a price and a time over the phone with no record of either. There is no profile to check, no review history, no way to show the problem before the visit, and nothing to point at afterwards if the job goes wrong.
A marketplace fixes that only if both sides actually use it. Customers will not post a job where no providers are visible, and providers will not maintain a profile where no jobs arrive. The product had to make the first request easy for a customer, make joining easy for a provider, and give the operator enough control to keep the provider side trustworthy — in Arabic and English, and paid for the way Kuwait pays.
Every decision aimed at the same thing: shorten the distance between "something is broken" and "someone is on the way" for the customer, while keeping the provider side worth joining and the platform worth running.
Customers and providers download the same app and choose who they are at sign-up. One listing to market, one release that ships both sides, and one codebase where a fix to chat or booking reaches everybody at once.
The booking form takes the type of service, a written description, a completion date and photos of the problem. The provider sees what they are walking into before they accept, instead of finding out at the door.
The home screen is a map of providers near the customer, filtered by service category. Location is the first thing that decides who can actually do the job, so it is the first thing the customer sees.
Chat, booking updates and provider tracking run over Socket.io, with push, email and SMS carrying the same events when the app is closed. Both sides look at the same booking at the same moment.
KNET and MyFatoorah are both in the build, and the interface runs right-to-left in Arabic as well as left-to-right in English — not a translation layer added after launch.
Registrations, provider subscriptions, platform activity and statistics are managed from an Angular dashboard with role-based access, so the client's team operates the platform without a developer in the loop.
Khadamat is one of several products we have built for VGA in Kuwait — the payment, localisation and admin patterns here are shared with Connect and Munasbati.
The standard way to build a two-sided services app is a customer app and a separate provider app. It is what we did for Connect's drivers, and for a fleet it is the right call. For a local services marketplace, where the supply side is a cleaner or a plumber signing up from a link someone sent them, it doubles the work in the wrong places.
The two sides still get different experiences — a customer sees a map and a booking form, a provider sees packages, requests and operations — but they are configurations of one product rather than two products that have to be kept in step.
Kuwait's national debit network at checkout.
Payment aggregator for cards and local methods.
Nearby providers on a map, and the provider tracked on the way.
Social sign-in alongside phone number and password.
Building a marketplace where both sides have to show up?
The customer and provider experiences ship in a single Flutter app on both stores; the admin panel is internal. All three read the same bookings.
Every tool below is in the build — no résumé-ware.
It depends on who the providers are. For a delivery fleet with shift tools, navigation and earnings, a separate driver app earns its keep — that is how we built Connect. For a local services marketplace, where a cleaner or a plumber joins from a link, one app with the role chosen at sign-up is usually better: one listing, one release, and no second download standing between a provider and their first job. Khadamat ships both sides in one app on both stores.
Yes — Khadamat is that app for Kuwait: customers find providers on a map, send a request with photos and a date, chat in real time and track the provider on the way, while an admin panel runs registrations and subscriptions. The Gulf-specific parts are what usually catch teams out: local payment gateways, Arabic right-to-left layouts, and SMS as a reliable channel alongside push.
Khadamat integrates KNET and MyFatoorah. KNET is the national debit network most Kuwaiti customers pay through, and MyFatoorah covers cards and local methods for merchants already set up with them. We build local rails in from the first sprint rather than adding them after an international gateway fails to convert.
Khadamat uses subscription packages on the provider side, administered from the admin panel, so the platform earns from providers who are present and not only from completed jobs. The packages, their limits and who is on which one are the operator's to manage, not something that needs a developer to change.
It depends on how many sides the marketplace has and what each needs on day one. A Khadamat-style build — customer and provider experiences in one app, real-time chat and tracking, two payment gateways and an admin panel — is scoped in phases and quoted fixed-price after a free scoping call, so you can see the first phase working before funding the rest.
One app for both sides, map-first discovery, real-time chat, KNET and MyFatoorah, an admin panel your team runs.
See how we'd scope yours.
