Saudi businesses are commissioning more software than ever: customer apps, internal portals, booking systems, ERP integrations and, increasingly, AI assistants. Many of them work with a development team outside the Kingdom, either to add capacity or because the right specialists are hard to hire locally at short notice.
Outsourcing can work very well for a Saudi company, but a few things matter more here than they would for a project in London or New York. This guide covers the questions to settle before you sign, so the team you hire builds something that fits Saudi customers, Saudi regulation and the way your business actually runs.
Start with what you actually need
Before comparing vendors, be clear about the kind of engagement you want. Most Saudi clients fall into one of three groups:
- A defined product or system. A customer app, a supplier portal, a CRM or a POS. You want a fixed scope, milestones and a price.
- Extra engineers for an existing team. You already have a product and an IT lead, and you need developers who take tickets from your backlog and join your meetings.
- Integration and automation work. Connecting the systems you already pay for, such as your accounting software, your ERP, WhatsApp and your website, so data stops being copied by hand.
The right partner for one of these is not always the right partner for another. Ask each vendor which of the three they do most often, and ask to see work of that type.
Arabic and right-to-left are not a translation task
If your customers or staff use Arabic, the product has to be designed for it from the first screen, not translated at the end. A team that has not built bilingual products before will often underestimate this.
Check that the team understands:
- Right-to-left layouts. Navigation, icons with direction (arrows, progress bars, back buttons), tables and forms all mirror in Arabic. Modern frameworks support this well, but only if the interface is built with it in mind.
- Mixed text. Arabic sentences with English product names, numbers, phone numbers and email addresses need careful handling so they display in the right order.
- Fonts and typography. Arabic fonts behave differently at small sizes and in bold. The design should be tested with real Arabic content, not placeholder text.
- Dates and numbers. Decide early whether you show Hijri, Gregorian or both, and whether you use Western or Eastern Arabic numerals.
- Search. Arabic search needs to cope with spelling variations, diacritics and different forms of the same letter.
A simple test: ask the vendor to show you an Arabic version of something they have built, and click through it on a phone.
Personal data and the PDPL
Saudi Arabia's Personal Data Protection Law (PDPL) came into force in September 2023, and full enforcement by the Saudi Data & Artificial Intelligence Authority (SDAIA) began in September 2024 after a one-year grace period. If your system stores data about customers, patients, employees or anyone else in the Kingdom, it applies to you.
For an outsourced project, the practical questions are:
- Where will the data live? The PDPL places conditions on transferring personal data outside the Kingdom. SDAIA's regulations allow transfers in defined cases, often with safeguards such as SDAIA's own standard contractual clauses and a risk assessment. Hosting production data in a Saudi cloud region is often the simplest route.
- Does the development team need real data at all? Usually it does not. Developers can build and test with anonymised or synthetic data, and only the production environment holds real records.
- Who has access? Access to production systems should be limited to named people, logged, and removed when the project ends.
- Is privacy built in? Your system will likely need a clear privacy notice, a record of what personal data is processed and why, and the ability to export or delete a person's data on request.
None of this has to slow a project down, but it needs to be in the plan from the start. Your development partner is not your lawyer, so take legal advice on your own obligations, and choose a team that can implement what that advice requires.
ZATCA e-invoicing, if your system issues invoices
If the software you are commissioning creates tax invoices, such as a POS, an ordering system, a billing portal or an ERP module, it needs to work with the Zakat, Tax and Customs Authority's e-invoicing rules (often called Fatoora).
Phase 2, the integration phase, is being rolled out to taxpayers in waves according to their revenue. Under Phase 2, invoicing systems generally need to:
- produce invoices in the required XML format with the mandatory fields;
- add a cryptographic stamp and a unique identifier to each invoice;
- show a QR code on simplified (B2C) invoices;
- connect to ZATCA's Fatoora platform for clearance or reporting;
- store invoices securely so they cannot be altered.
Check your own wave and deadline with ZATCA or your tax adviser, then make e-invoicing an explicit line in the project scope. Ask the vendor how they will handle onboarding with ZATCA's sandbox and how they will test it before go-live. Bolting compliance on after launch costs more than building it in.
Working hours and communication
Time zones are one of the easier parts of working with a team in Pakistan. Saudi Arabia is on UTC+3 and Pakistan on UTC+5, so there are only two hours between Riyadh and Lahore, and most of the working day overlaps.
The thing to agree is the working week. The Saudi weekend is Friday and Saturday, while most Pakistani companies work Monday to Friday. In practice, a good team agrees a shared schedule: Sunday availability for urgent matters, and planning and demos on the days you both work. Settle this in the first week, not when something breaks on a Sunday morning.
Also agree:
- The language of the project. Most technical work happens in English, but if your stakeholders prefer Arabic for meetings or documents, say so up front.
- One channel for decisions. WhatsApp is convenient, but important decisions should be written into your project tool so nothing is lost.
- A regular demo. Working software every one or two weeks, on a link you can open yourself.
Contracts, ownership and payment
Whoever you hire, the contract should cover:
- Intellectual property. All code, designs and documents become yours on payment.
- Your accounts from day one. The code sits in a repository you own, and cloud hosting is in your company's account, not the vendor's.
- Milestones tied to working software. Payments follow delivered, tested releases rather than time passing.
- Support after launch. A defined warranty period for bugs, and clear terms for ongoing support.
- A registered counterparty. Work with a properly registered company so invoices and contracts are on a formal footing.
Most international clients pay by bank transfer in USD, and some in SAR. Agree the currency and invoicing schedule before work starts.
Common mistakes Saudi buyers make
- Choosing on price alone. The cheapest quote often means junior engineers and rework later.
- Leaving Arabic to the end. Retrofitting right-to-left support into a finished product is slow and expensive.
- Forgetting compliance in the scope. If PDPL and ZATCA requirements are not written into the proposal, they are usually not in the price either.
- A long project with no early release. Start with a small, paid first milestone and judge the team on what they deliver.
How NextiForce works with Gulf clients
NextiForce is a Lahore software company, registered as Nextiforce (SMC-Private) Limited with the SECP in Pakistan. We build custom business software, AI agents, voice AI and automation for clients in the UK, US and the Gulf, and every engagement starts with a short scoping call and a written proposal covering the outcome, the first release, the timeline and the cost. You can see what we offer on our services page.
If you are planning a system for your Saudi business, tell us what you need and a senior engineer will reply within one business day.