Softwise builds mobile apps, SaaS platforms, CRM systems, and ERP integrations for clients in Saudi Arabia. The work is done by 20+ in-house developers covering iOS, Android, data, and AI, with no subcontracting, delivered remotely from the head office in Tunis in English, French, or Arabic. Saudi Arabia is one of the markets behind Softwise's 100+ delivered clients, alongside Tunisia, France, United Arab Emirates, and Canada.
The same catalogue as every other market, delivered by the same in-house team of 20+ developers.
Native applications built by in-house mobile engineers who also handle store submission, review responses, and the fixes that follow a release. Swift for iOS and Kotlin for Android, so the app behaves the way each platform expects.
SaaS platforms covering authentication, roles, billing, dashboards, and the multi-tenant architecture underneath them. Work ships in tested increments, so the product can be steered while it is being built.
ERP integrations, custom CRM builds, and Salesforce or HubSpot wired into the systems around them. Data engineers sit on the same team as the application developers, so the integration is architecture rather than a patch added at the end.
The requirements that shape most Saudi builds. What each one asks for, and how we approach it.
ZATCA Phase 2 requires invoices to be generated in a structured electronic format, cryptographically stamped, and reported to the Fatoora platform, with a QR code on simplified tax invoices. When invoicing is part of a product we build, that format, stamp, and reporting flow are designed in from the start rather than retrofitted after launch.
Saudi Arabia's Personal Data Protection Law sets rules for how personal data is collected, stored, and transferred, including across borders. Those rules are answered with architecture: which region the database runs in, what leaves it, and what a backup replicates. The decisions are made with you and written down, so where your data lives is a fact rather than a guess.
Nafath is the national app Saudis use to sign in with a verified national identity, and mada is the domestic debit network a Saudi checkout is expected to accept. Where a product needs either, Nafath is treated as an authentication integration in the identity layer, and payments are scoped around mada alongside the other methods your customers actually use.
Proof from the market itself: what shipped for a Saudi client, and what it replaced.
An operations company in Riyadh dispatching field technicians for maintenance contracts. They resold their internal dispatch tool to two partner firms by cloning the codebase, and were maintaining three diverging copies. Every bug was fixed three times. Adding a fourth customer meant a fourth copy.
3 diverging codebases consolidated into 1, onboarding cut from weeks to under a day
In-house Softwise engineers, no subcontractors
Working with us
Languages, hours, and travel, stated plainly rather than implied.
Delivery in English, French, and Arabic. Requirements, reviews, and day-to-day questions run in the language your team works in, with the same engineers who are building the product.
Riyadh runs two hours ahead of Tunis. Delivery is aligned to Gulf working hours, so calls, reviews, and answers land inside your working day rather than a message behind it.
Remote by default, with travel to your location when a project calls for it. One office, in Tunis, and no office in Saudi Arabia.
Yes. Saudi Arabia is one of the markets Softwise has delivered in, out of 100+ clients across Tunisia, France, Saudi Arabia, the UAE, and Canada. Delivery is remote from the head office in Tunis, in English, French, or Arabic, with travel when a project calls for it.
Yes. ZATCA Phase 2 requires invoices in a structured electronic format, cryptographically stamped and reported to the Fatoora platform, with a QR code on simplified tax invoices. Softwise designs that format, stamping, and reporting into the product from the start, rather than retrofitting an existing billing flow after launch.
Data location is an architecture decision made with you, not a default: which region the database runs in, what crosses a border, and what backups replicate. Saudi Arabia's PDPL governs how personal data is collected, stored, and transferred, so those choices are documented against your requirements and reviewed with you before launch.
Yes. Softwise delivers in English, French, and Arabic. Requirements, reviews, and day-to-day communication can run in Arabic with the same in-house engineers who are building the product. Arabic-language interfaces are scoped as part of the build rather than treated as a translation task bolted on at the end.
Riyadh is two hours ahead of Tunis, so most of a Gulf working day overlaps. Softwise aligns delivery to Gulf working hours, which keeps calls, reviews, and questions inside your working day instead of a message behind it. Time-sensitive releases are scheduled in your hours, not ours.
No. Softwise has one office, in Tunis, Tunisia, and no Saudi entity, CR number, or local phone number. Delivery is remote, in English or Arabic, with travel to Saudi Arabia when a project calls for it. The same in-house engineers who build the product are the ones you work with.
The same in-house team delivers all five.
Native iOS and Android from developers who ship them weekly. Store release and post-launch fixes included.
Read more →/002/Auth, billing, dashboards, and an architecture that survives your next 10x in users. Shipped in tested increments.
Read more →/003/Data engineers on the same team as the app developers. The integration is designed in, not bolted on.
Read more →/004/Custom CRM builds, and Salesforce or HubSpot wired into the systems your team already uses. Your pipeline and your product data stop disagreeing.
Read more →/005/We automate what your people repeat, then add AI where it moves a number you already track.
Read more →