Here is the number first, because most articles make you scroll for it. A working three-sided delivery platform, the kind of product Jahez or HungerStation runs, starts from around SAR 30,000 (about $8,000) and takes 16 weeks or more. A single restaurant group's own ordering app is a different project entirely and sits in the SAR 11,000 - 17,000 range. Everything between those two numbers depends on decisions you have not made yet, so let's walk through them.
What the Saudi delivery market actually rewards
Jahez did not win because its app had more features than anyone else's. It won on two boring metrics: restaurant density per city and delivery-time reliability. When a customer in Buraidah or Khamis Mushait opens the app, they either see forty restaurants they recognize or they see six and never come back. HungerStation holds Riyadh and Jeddah through sheer coverage; Careem leans on its ride network. The gap, if there is one for a new entrant in 2026, is in secondary cities and in specific verticals (groceries, pharmacies, home kitchens) where the big three are thinner.
This matters for budgeting because it tells you where the money should go. Founders often ask us for loyalty tiers, AR menus, and social feeds in version one. What actually moves the needle is a merchant onboarding flow so simple a restaurant signs up in ten minutes, and a dispatch engine that assigns the courier who will genuinely arrive fastest. Build for density and reliability first. Decorate later.
You are building three apps and a brain
A marketplace like Jahez is not one app. It is four coordinated pieces:
- Customer app: browsing, cart, live order tracking on a map, payments, ratings.
- Courier app: shift management, order offers with accept/reject timers, navigation, proof of delivery, earnings.
- Merchant app or tablet view: incoming orders, prep-time confirmation, menu and stock control, daily settlement reports.
- Dispatch and admin: the brain. Automatic order-to-courier assignment based on distance and load, surge zones, refund handling, commission settings, and the operations dashboard your team lives in.
Each side has its own users, its own edge cases, and its own ways to fail. The courier app alone needs battery-friendly GPS tracking, offline tolerance for dead zones, and a fair assignment algorithm (couriers uninstall apps that starve them of orders). This is why the full platform sits in our advanced tier and why anyone quoting you MVP money for all of it is quoting a demo, not a business. We covered the same anatomy for the Kuwaiti and Emirati market in our Talabat cost breakdown; the architecture is nearly identical, the payment stack is not.
The Saudi-specific parts people underestimate
Payments. In Saudi Arabia, mada is not optional. A large share of card payments run on mada debit rails, and Apple Pay adoption is among the highest anywhere. You get both through a licensed local gateway such as HyperPay, Tap, or PayTabs, not by dropping in a generic international SDK. Gateway onboarding needs your CR and bank account and can take a couple of weeks, so we start that paperwork in week one, in parallel with design, instead of discovering it in week ten. Add STC Pay and cash-on-delivery reconciliation and you have a payment layer that deserves its own test plan.
Arabic-first UX. Not "Arabic translation added at the end." The interface is designed right-to-left from the first screen, with English as the mirrored secondary. Numerals, plurals, address forms, and notification copy all behave differently in Arabic, and a flipped-at-the-last-minute layout is instantly visible to Saudi users. Bilingual RTL builds are our native ground, and it shows most in small things like how a courier's name and ETA read in a push notification.
Addresses. Much of the Kingdom does not order to a street address; people drop a map pin and add "the house with the white gate." Your checkout, courier navigation, and support tooling all need to treat the pin as the source of truth. Plus VAT-compliant invoices on every settlement report, because your merchants' accountants will ask.
What it costs in 2026
Our published app tiers, in both currencies:
- MVP: SAR 11,000 - 17,000 ($3,000 - 4,500), typically 8-12 weeks. A focused single-audience app. In delivery terms: one restaurant brand's own ordering app, or a customer-app pilot running on manual dispatch behind the scenes.
- Mid-scope: SAR 17,000 - 30,000 ($4,500 - 8,000), typically 12-16 weeks. Customer plus merchant sides with online payments and an admin panel; courier logistics still handled by your own small team with lightweight tooling.
- Advanced: from SAR 30,000 (from $8,000), 16+ weeks. The full three-sided platform: all three apps, automated dispatch, live tracking, mada and Apple Pay via a local gateway, and the operations dashboard. This is the "app like Jahez" tier, and there is no honest shortcut below it.
We deliver remotely from Cairo (one hour from Saudi time), which is why these figures sit well under Saudi agency pricing for the same scope, often 30-50% less. The working rhythm is the same either way: written acceptance criteria before code, a staging link you can open from day one, a fresh build on your own phone every week, and payments that fall due per accepted deliverable rather than per date on a calendar. You sign an NDA before sending us anything sensitive, and once the last invoice clears, everything is in your name: code, designs, both store accounts and the signing keys. The full scope checklist lives on our food delivery app development page.
The honest alternative for restaurant groups
Now the part most vendors skip. If you own three burger branches in Riyadh, you do not need a marketplace. You need your own ordering app: your menu, your branches, mada and Apple Pay, pickup and delivery through your own drivers or a third-party fleet. That is an MVP-tier build, SAR 11,000 - 17,000, and it pays for itself by moving orders off aggregator commissions that eat 15-30% of every ticket. Several of the most profitable delivery apps in the Kingdom are exactly this: one brand, loyal customers, zero commission. Building a marketplace to solve a single group's commission problem is the most expensive mistake in this category. Match the build to the business.
Where to start
Before asking anyone for a quote, write one page: your launch city, your first fifty target restaurants (or your own branches), and who delivers the food in month one. That single page will tell you your tier, and it makes any proposal you receive checkable against something concrete. If you want a second pair of eyes on it, our Saudi app development team reads plans like this every week. Send yours over on WhatsApp with your city list and we will come back with a written scope and a fixed price, before you commit to anything.
