What is custom software development in Saudi Arabia, and who actually needs it?
Custom software development is building a system around one business's own process instead of renting a general tool that thousands of companies share. In Saudi Arabia the typical results are trade portals for distributors, job and asset trackers for contractors, booking and membership back offices, and dashboards that join data from several platforms the business already pays for.
Not every company needs it. A ten-person firm with ordinary sales, accounts and HR is usually better served by good subscription tools and a tidy setup. The case for custom software development in Saudi Arabia gets strong when three things are true at once: your process differs from the standard (pricing by customer tier, multi-step approvals, unusual scheduling), staff re-type the same data into several systems every day, and the people using it split between Arabic and English speakers who each need a comfortable screen.
The honest first step is therefore not a design, but a short review of what you already run. We list the tools, the manual steps between them and the decisions people make by hand, then show which parts a subscription could cover and which parts justify code. Sometimes the answer is a small integration rather than a new system, and that is a cheaper answer worth hearing before you commit.
Build or buy: when custom software beats SaaS for a Saudi company
Build when the software is part of how you win customers or control cost; buy when it is a utility every business runs the same way. Payroll, generic accounting and email are utilities. The quoting logic of a spare-parts wholesaler, the dispatch rules of a water-delivery fleet or the approval chain of a contractor bidding on sub-packages usually are not.
Cost over time matters too. A subscription priced per user looks cheap at five seats and less cheap at eighty branch staff, drivers and dealer logins, especially when most of them need only one screen. A custom system has a larger bill up front and smaller running costs: hosting in your cloud account plus whatever maintenance you choose.
Buy a subscription tool when
A mainstream product already covers most of your workflow, you have fewer than a couple of dozen users, you need it next week, and nobody on your side has time to take part in design sessions.
Build custom software when
Staff keep parallel spreadsheets to work around the tool, per-user fees keep climbing, you need Arabic and English users on the same records, or two platforms must talk to each other and no connector exists.
Mix the two when
Standard accounting or a hosted store works well but the gap between them is manual. A thin custom layer that moves data between systems is often the best value.
Signs your spreadsheets and subscription tools have hit their limit
The clearest sign is duplicated effort: the same order, invoice or job typed into two or three places by different people. Every re-keying step costs hours and introduces mistakes that surface later as disputes with customers or gaps in VAT records.
Other warning signs are easier to miss because the team has adapted to them. Managers wait until month end to see branch figures because someone must merge exports by hand. Dealers call or send WhatsApp messages to ask for statements that should be self-service. Approvals happen in chat threads, so nobody can prove later who agreed a discount. And the Arabic-speaking warehouse team works from printouts of an English-only tool.
- The same data is typed into more than one system every day
- Month-end reports depend on one person merging spreadsheets
- Customers phone or message for information a portal could show
- Approvals and discounts are agreed in chat with no audit trail
- Per-user subscription fees grow faster than revenue
- Staff avoid a tool because it only works well in English
- A key integration is “coming soon” on the vendor's roadmap for years
If four or more of these apply, a scoped custom system is worth pricing. If only one or two do, start with an integration or automation, for example through our AI automation services for Saudi SMEs.
How much does custom software development cost in Saudi Arabia?
With us, custom software development for a Saudi business starts from US$900 for a first release, quoted and invoiced in US dollars. Quotes from other developers vary widely, and the gap is rarely about hourly rates alone; it comes from how clearly the scope is defined, how many systems are involved and who carries the risk of changes.
Six factors move the number. User roles and permissions: a system with an admin and one user type is far simpler than one with branch managers, accountants, drivers and external dealers. Workflow depth: every approval step, status and notification adds screens and tests. Integrations: each outside system, whether a Salla or Zid store, a POS, an accounting package or a shipping carrier, needs its own connection and error handling. Data migration: cleaning years of spreadsheets costs more than people expect. Reporting: a handful of fixed reports is cheaper than a flexible dashboard. Mobile: a companion Android and iOS app sharing the backend starts from US$600.
Running costs are separate and yours to see directly: cloud hosting billed by the provider to your account, any paid APIs such as WhatsApp messaging, and optional maintenance after the free two months, from US$120/mo. The price table on this page and our full pricing show starting points for every service.
How an offshore team scopes custom software for a Saudi business
Scoping remotely works when it is structured: we replace a site visit with recorded screen-shares of how work really happens today. You or a team lead walks through the current process on a video call, sharing the spreadsheets, forms and tools involved, and we ask the awkward questions about exceptions, because exceptions are where custom systems get expensive.
From that we write a scope document in plain English, with Arabic terms where your team uses them. It lists user roles, the screens each role sees, the statuses a record moves through, every integration, the reports needed on day one and, just as important, what is out of scope for the first release. Then comes an itemised quote in about two working days, broken into milestones.
What we ask you to prepare
Sample documents with real layouts (invoice, delivery note, job card), the current spreadsheets with a few rows of anonymised data, a list of the tools you pay for, and the names of the people who approve each step.
What the scope document contains
Roles and permissions, a screen list, record lifecycles, integration list, data to import, reports, hosting region, languages, and a short list of deliberate exclusions for phase two.
Why a first release stays small
Shipping the core workflow in weeks, then adding features from real use, costs less than building every idea before anyone has tried the system.
Arabic and English admin panels: building both from day one
A bilingual admin panel means every screen, label, validation message, PDF and email template exists in Arabic and English, and each user chooses their language. Adding Arabic after launch is slow and error-prone, so in custom software development for Saudi Arabia we design both directions at the start.
Right-to-left is more than flipping the text. Tables, breadcrumbs, progress steps, icons with direction (arrows, “next” buttons) and charts all need mirroring rules, while phone numbers, invoice numbers and codes stay left-to-right inside Arabic sentences. We use CSS logical properties so one layout serves both directions, and we test with realistic Arabic data, including long company names and mixed Arabic-English product codes, not placeholder text.
Data itself raises decisions: whether customer and product names are stored in both languages, how search handles Arabic letter variants, which numerals print on documents, and whether dates show Hijri alongside Gregorian. The team writes English; you supply or approve the Arabic interface wording, and we load it into translation files your staff can later edit without a developer.
- Per-user language setting that persists across devices
- Mirrored layouts, tables and navigation for Arabic
- Bilingual PDFs for invoices, quotes and statements
- Arabic-aware search that tolerates common spelling variants
- Translation files editable by your team after handover
ZATCA-ready invoicing hooks in custom software development for Saudi Arabia
If your custom system issues invoices, it has to fit Saudi e-invoicing. According to ZATCA, phase one (generation) applied from 4 December 2021, and phase two (integration) started on 1 January 2023 in waves, requiring invoicing solutions to connect with ZATCA's systems and produce invoices in the required format. ZATCA's technical guidelines describe XML invoices: standard tax invoices are cleared by the FATOORA platform, which adds a cryptographic stamp and QR code, while simplified invoices are reported within 24 hours of being generated.
A “ZATCA-ready hook” is our term for building the invoice module so that step is straightforward. Every invoice, credit note and debit note is stored as structured data with the fields the format needs, numbering is sequential and never reused, invoices cannot be silently edited after issue, and the system can hand each document to an integration component and store the cleared or reported result.
Then you choose how to connect: through accounting or e-invoicing software that already handles FATOORA onboarding, or through a direct integration built for your system. The direct route gives more control and more responsibility; our ZATCA e-invoicing integration guide compares both. Whether and when your business falls into a wave is confirmed with your accountant, not by us.
Where should your data live? Hosting region and data residency choices
Decide the hosting region before development starts, because it shapes the cloud services available and your data-protection paperwork. For most private Saudi SMEs, the question is balancing latency, cost, available services and the Personal Data Protection Law's rules on transferring personal data outside the Kingdom, which SDAIA details in its Regulation on Personal Data Transfer Outside the Kingdom.
Options now exist inside the country. For example, Google Cloud runs its Dammam region (me-central2), and its documentation says customers with a Saudi billing address buy access through the reseller CNTXT. Other international and Saudi providers offer local data centres too, and availability changes, so we check the current list of services for your stack rather than assume.
Organisations with extra obligations should confirm them first. The National Cybersecurity Authority's Essential Cybersecurity Controls apply to government bodies, their affiliated companies and private operators of critical national infrastructure; if that is you, your security team or regulator sets the hosting rules and our work follows them. Whatever the region, the account is opened in your business's name, so you hold the keys and the bills.
PDPL and custom software: what the build does to support compliance
Saudi Arabia's Personal Data Protection Law came into force on 14 September 2023, and SDAIA's guidance gave organisations a one-year grace period ending on 14 September 2024. Custom software that stores customer, employee or dealer data should make the controller's obligations easier to meet, and much of that is engineering.
SDAIA's guide for controllers expects records of processing activities, procedures for handling data breaches and respect for data subjects' rights. In a build, that becomes: collecting only fields with a stated purpose, role-based access so a driver cannot open a customer's full history, encryption in transit and at rest, audit logs showing who viewed or changed personal data, export and deletion functions for data requests, and retention rules that purge old records automatically. We can also produce a data map of what the system stores and where, which your advisers can use for the records they must keep.
Compliance itself remains your business's responsibility, confirmed by your own lawyer; we do not give legal advice or certify anything. For websites and apps facing the public, see PDPL compliance for websites.
Connecting your custom system to Salla, Zid, Foodics, accounting and WhatsApp
Much custom software development in Saudi Arabia is really integration projects with screens on top. A distributor wants online orders from its Salla or Zid store to land in the warehouse queue; a restaurant group wants Foodics sales beside purchasing costs; a clinic wants bookings to trigger WhatsApp reminders; everyone wants totals to reach the accountant without re-typing.
We connect through official APIs and webhooks where the platform offers them, and through scheduled imports of exports where it does not. Each connection gets retry logic, a log of what synced and a screen that shows failures in plain language, so a missed order is noticed the same day, not at stock-take.
Accounting deserves care. Tools such as Qoyod or Wafeq may offer an API or an import format; the choice decides whether invoices sync live or in batches. WhatsApp messages go through the WhatsApp Business Platform with templates approved by Meta; our WhatsApp automation for Saudi businesses page covers that channel in depth.
- Online stores: orders, customers, stock levels and returns
- POS: daily sales by branch, items and payment method
- Accounting: invoices, receipts and customer balances
- Shipping carriers: labels, tracking numbers and delivery status
- WhatsApp: order updates, reminders and approval requests
- Spreadsheets: scheduled imports while older tools are phased out
How long does custom software development take in Saudi Arabia?
A focused first release usually takes 6–12 weeks from approved scope with us. The range depends mostly on integrations and on how quickly your side answers questions and reviews screens, not on typing speed.
Weeks one and two produce the scope sign-off, the data model and clickable screens for the main flows in Arabic and English. Weeks three to six build the core workflow, roles and the first integration, with a demo at the end of each week on a staging link. The remaining weeks add reporting, the rest of the integrations, data import and user testing with a few of your real staff. Go-live is followed by a short hypercare period where we watch logs daily and fix anything the first real week reveals.
Things that stretch the calendar: waiting for API access from a platform or vendor, legacy spreadsheets that need heavy cleaning, approval of Arabic wording, and scope added mid-build. We flag each risk at kick-off and show its effect on the date before you decide, so a delay is a choice rather than a surprise.
Milestone contracts, quotes in USD and budgeting in riyals
Your written quote breaks the project into milestones, each with a list of deliverables you can check on staging, and the payment schedule is tied to those milestones as set out in that quote. Nothing is billed before you approve the quote in writing, and any change in scope gets its own written estimate first.
Quotes and invoices are in US dollars and paid by Wise, bank wire or PayPal; invoices are issued from India. Because the Saudi riyal is pegged to the dollar, the riyal cost of each milestone is predictable when you set your budget. How a payment to a provider outside the Kingdom is treated for VAT or withholding tax is a question for your accountant, and we will give them whatever invoice details they ask for.
Contract terms such as confidentiality, notice and what happens if either side stops are agreed in your quote and our terms. If your procurement team uses its own contract template, send it early and we will read it before quoting.
- Milestone 1: scope, data model and approved screen designs
- Milestone 2: core workflow working on staging
- Milestone 3: integrations, reports and data import
- Milestone 4: user testing, fixes, go-live and handover
Who owns the source code after custom software development in Saudi Arabia?
You do. The code lives in a Git repository created under your organisation's account from day one, the cloud account and domain are in your name, and we work inside them as invited users you can remove at any time. This is the single most important clause to check with any provider, because code held by the developer turns a one-off build into a permanent dependency.
Handover is a checklist, not a zip file. You receive the repository with its history, infrastructure notes that explain how the system is deployed, environment settings stored safely, an admin guide for your team, a short technical guide for any future developer, and a recorded walkthrough of the codebase. Third-party licences, such as a paid component or API, are listed with their owners and renewal dates.
After go-live you get two months of free maintenance for fixes and small adjustments. After that, care starts from US$120/mo, or you can move the system to an in-house developer or another team. Because the code uses mainstream tools and is documented, that move should take days of reading, not months of rebuilding.
Which tech stack suits custom software development in Saudi Arabia?
We pick boring, widely known technology so your system is easy to hire for later. Typical builds use a TypeScript front end with React or Next.js, a Node.js or Python backend, PostgreSQL for data, background workers for integrations and scheduled jobs, and object storage for documents. Mobile companions use Flutter or React Native against the same API.
Security basics are part of every build: single sign-on or strong passwords with two-factor login for admins, role-based permissions checked on the server, encrypted backups with a tested restore, and separate staging and production environments. Performance gets the same attention as on a public site, because warehouse staff on a slow connection will abandon a screen that takes ten seconds to load.
If the project includes public pages, such as a dealer sign-up page, a service catalogue or a help centre, those are built to be crawled and quoted: fast, with clear headings, structured data and self-contained answers that search engines and AI assistants can use. The logged-in portal behind them stays private and out of search results. For a site that needs sustained visibility, pair the build with monthly SEO services in Saudi Arabia.
Working with a custom software team in India from Saudi Arabia
The time difference is small: India is 2.5 hours ahead, so a Riyadh day from 9 am to 5 pm is 11:30 am to 7:30 pm for us, and your Sunday to Thursday week overlaps our working days almost entirely. Calls happen in your morning or early afternoon; progress lands on staging while you sleep less than a normal night's worth of hours behind.
Communication runs on WhatsApp for quick questions, with replies seven days a week, plus a weekly demo call and a shared board listing every task and its status. Meetings are in English; Hindi is also spoken within the team, and Arabic content comes from your side.
Why a remote team in India at all? For a well-scoped system, you get experienced developers who also handle hosting, integrations and support, without paying for an office, sales team or account managers in between. What you give up is in-person workshops and a local entity to sign with. We are candid about the limits: no site visits, no hardware installation, no large teams of twenty, and no legal advice.
Your first two weeks
Days 1–2: screen-share sessions on your current process and a list of documents to collect. Days 3–5: scope draft and itemised quote. After approval: your repository and cloud account are set up, and by the end of week two you click through Arabic and English screen designs for the main workflow.
Who you talk to
The third of us runs planning and your weekly demo, one of us leads the full-stack build, and another of us handles cloud setup, data work and any AI or reporting components.
Red flags when hiring for custom software development in Saudi Arabia
The biggest red flag is a confident total price before anyone has seen your process. A quote given in the first call either hides large assumptions or will grow through change requests. Ask how the number was built and which parts are estimates.
Watch for ownership language too. If the developer hosts the system on their own servers, keeps the repository, or licenses the software to you rather than transferring it, you are renting, not buying. Be wary of proposals that promise every feature from a long wish list in the first release, of platforms built on a proprietary framework only that vendor knows, and of teams who cannot show you a staging link during the build.
Finally, check how Arabic is handled. “Arabic support” can mean a translated menu over an English layout. Ask to see a right-to-left table, an Arabic invoice PDF and Arabic search in an earlier project demo or a prototype built for you.
- Fixed total quoted before any scoping session
- Code or hosting held in the developer's accounts
- No weekly demo or staging link during the build
- Proprietary framework that only one vendor maintains
- Arabic added as translated labels over an English-only layout
- Vague answers about invoice numbering and ZATCA fields
- No written plan for maintenance, backups or handover
Worked example: a hypothetical Jeddah spare-parts wholesaler
Consider a made-up wholesaler in Jeddah selling vehicle spare parts to about sixty workshops across the western region. Orders arrive by phone and WhatsApp, prices depend on each workshop's tier, stock sits in an accounting package, and salespeople check availability by calling the warehouse. The owner is weighing a subscription ERP against something built.
The build-or-buy review would likely show that accounting and payroll should stay on existing subscriptions, while the tiered pricing, order approvals and workshop self-service are the unusual parts. The custom scope would be a dealer portal in Arabic and English where workshops search parts by code or name, see their own prices and place orders; an internal screen for the warehouse to pick and pack; approval steps for orders over a credit limit; and nightly sync of stock and invoices with the accounting tool, with invoice data structured for the business's ZATCA route.
A first release could follow the milestone plan above in roughly 8–10 weeks, with hosting in a region the owner chooses and WhatsApp notifications when an order ships. This is an illustration of how we would scope such a project, not a past client or a promised result; your quote would reflect your actual process.
Checklist before signing a custom software development contract in Saudi Arabia
Use this list with any provider, including us. Each line should have a clear written answer before the first payment.
- Scope lists roles, screens, statuses, integrations and exclusions
- Milestones have deliverables you can test on staging
- Repository, cloud account and domain are in your organisation's name
- Hosting region is agreed and matches your data-protection advice
- Arabic and English are both in scope, with who supplies Arabic wording
- Invoice module stores structured data for your ZATCA route
- Audit logs, backups and restore testing are included
- Data import from existing spreadsheets is estimated separately
- Handover documents and a walkthrough are listed as deliverables
- Maintenance terms after launch are written down