Most delivery platforms are designed for dense city demand and never reach smaller towns. We build delivery marketplace apps around the constraints of underserved areas — cash on delivery, WhatsApp login, and a catalog that grows without months of manual setup.
The Problem
Big-city delivery apps are built around order density. Smaller towns and remote neighborhoods need a different set of defaults.
Cash on delivery as the default payment method, not a fallback — most residents aren't ready for card-only checkout.
A catalog built from real, local store inventory instead of a copied big-city list.
Login that works for someone who's never installed an app before — WhatsApp OTP instead of email/password.
One person able to cover both shopping and delivering, since order volume in a new area rarely supports separate roles from day one.
Arabic that reads like Arabic throughout the product, not a translated afterthought.
Proven in the Field
A bilingual, cash-on-delivery marketplace with one app for both customers and drivers — live and shipping in Egypt's underserved towns.
ba2olak
Web + Mobile
Platforms shipped
6
Order status stages tracked
2
Languages supported
Read More
Two perspectives on the same problem — what the ideal solution looks like, and exactly how we built it.
Most delivery apps are built for dense city demand and never reach smaller towns. Here's what a genuinely good delivery experience looks like when it's designed around a small town's real constraints instead.
Read the ArticleGrocery and market delivery in Egypt rarely reaches smaller towns. Here's how we built ba2olak — a bilingual, cash-on-delivery marketplace with one app for both customers and drivers — and what we learned shipping it.
Read the Case StudyCommon Questions
Typically 6–12 weeks from first call to a live product, depending on scope — a single-town launch with core ordering and dispatch can move faster than a multi-city rollout.
Yes — we design cash-on-delivery as the default payment flow from the data model up, including driver settlement and reconciliation, not as an add-on retrofitted later.
Yes. A single app with role-based flows lets the same person shop and deliver, which keeps the platform viable at low order volumes in a new market — you can split into specialist roles later once volume justifies it.
Yes — Arabic is built in as the primary language across the whole product, not a translation pass added at the end, with full RTL support.
Tell us about the area or market you're serving and we'll design a delivery platform around its real constraints.
