Software development · Custom builds
Custom software development in Saudi Arabia: backends, internal tools and integrations
Custom software development is software written for one organisation's way of working: the backend behind an app, the internal tool a team uses daily, the interface joining two systems never meant to share data. Interkey has built custom enterprise applications for organisations in Saudi Arabia since 1999. Below: what gets built, which engagement model fits, how a project runs, and what drives cost.
In short, for decision-makers
- What it is: backends and APIs, integrations, internal tools and enterprise web applications, built to your process.
- How it is bought: a scoped project, a dedicated team, or specialists added to your team; quote only.
- What you keep: source code, documentation and the deployment pipeline, at handover.
- Where it runs: on your infrastructure, inside the Kingdom where required, or on a cloud you choose.
At a glance: what custom software development covers
| Type of work | What it usually is | What you have at the end |
|---|---|---|
| Custom backend and APIs | Service layers, business rules and APIs behind web and mobile apps | A documented backend your team can deploy |
| System integration | Interfaces between an existing system and a new one | A written contract and owner per interface |
| Internal tools | Approval flows, exception queues, admin screens, dashboards | A tool built around how the team works |
| Enterprise web applications | Portals and service platforms in Arabic and English | Right-to-left support designed in |
| Data processing tools | Jobs that clean, reconcile and move records between systems | Records that agree across systems |
| Delivery pipeline | CI/CD, container images and monitoring | Releases that are routine rather than an event |
What custom software development in Saudi Arabia has to cover
Writing the code is rarely the hard part of a custom build. The hard part is what surrounds it: a government platform with its own integration requirements, an ERP with no documented interfaces, an Arabic interface that must read naturally rather than as mirrored English, and data that may have to stay inside the Kingdom. A build that ignores these looks finished at the first demo and stalls at acceptance testing.
Read more
So custom software development in Saudi Arabia has to cover four things beyond the feature list: integration with the systems already running; Arabic and English as equal requirements; hosting that matches the data classification; and a handover that lets you change and deploy the software without its original authors.
The team works from Riyadh on the Sunday to Thursday week, and Interkey contracts as a Saudi entity, commercial registration 1010156897. For Interkey as a software company, its history since 1999 as IKeyData, data partner to Tadawul, and its disciplines, see software development at Interkey.
Custom backend development and integration with existing systems
Custom backends and APIs
The largest share of the work: APIs, service layers, the business rules that decide what each request may do, and the database design underneath. A typical brief is a mobile app or portal that needs a backend the current system cannot provide, or an internal system that must serve a new channel without being rewritten. Interkey designs the API first, agrees it with the teams who will call it, then builds the service behind it with automated tests on every change.
Read more
Integrations
Few builds stand alone. Each interface gets a written contract agreed before building (what is sent, how often, what a valid message is, what happens on an error), is designed so a request sent twice is not processed twice, and has a named owner and monitoring, so a dropped record is found by an alert rather than at month-end. Where a system offers no API, the interface goes through its database, files or a message queue. The patterns are on our system integration page; once interfaces multiply, API management governs who may call them, at what rate and in which version.
Relatedsystem integration
Internal tools development
Internal tools are the software only your staff see: the approval flow that replaces an email chain, the queue where exceptions wait for a decision, the admin screen over a database only one engineer can query today. They rarely justify a product licence, yet they are often where the most hours are lost.
They pay back soonest when built with the people who use them. Interkey runs requirements sessions in Arabic with those people directly, not through a translation layer, and builds the first version around one real workflow before adding the next. Access follows the roles you already manage.
Data processing tools belong here too: jobs that clean, reconcile and move records between systems, built by the same team as our data integration services.
Relateddata integration services
Enterprise application development in Arabic and English
Enterprise application development covers the larger builds: customer and partner portals, service platforms, and applications the organisation will run for years. Three things decide whether they last:
- Arabic designed in: right-to-left layouts, mixed Arabic and Latin text, Arabic search and sorting, and dates and numbers in both languages. Right-to-left support added at the end is visible to every Arabic-speaking user.
- Built to be deployed: container images, CI/CD pipelines and, where the platform calls for it, Kubernetes, so a release is routine. See our containers and Kubernetes page.
- Built to be watched: monitoring designed in before go-live, with alerts the team trusts rather than noise it learns to ignore.
Relatedcontainers and Kubernetes
Engagement models: which one fits your project
Which model fits depends less on the technology than on where the domain knowledge sits.
| Model | Fits when | Accountable for the outcome | How it is priced |
|---|---|---|---|
| Scoped project delivery | The outcome can be defined and nobody inside has time to own it | Interkey, against the agreed scope | Per project, after discovery |
| Dedicated team | The work is ongoing and priorities change | Shared: your product owner sets priorities, Interkey runs the team | For the team and the period |
| Augmentation | Your team lacks one skill, such as a database specialist or a DevOps engineer | Your team | Per specialist and period |
The case to avoid is a fixed-price project for a problem nobody has defined yet. And before choosing a model, check whether to build at all: if a configured product already meets the requirement, buying is usually cheaper, and stays cheaper because someone else carries the maintenance. Build when the process is what sets you apart, or when no product fits without changing how the business works.
How a custom software project runs
-
Discovery.
A short, paid look at the existing systems: what each allows, who can change it, how long approvals take. It sometimes ends with a recommendation not to build as proposed.
-
Scope and model.
The work is written down under one of the three models: what is in, what is out, what your team provides.
-
Design the contracts.
APIs and data models are agreed with both sides before the code that depends on them.
-
Build in increments.
Working software at regular reviews, tested with realistic data, including Arabic text and malformed records.
-
Release alongside what exists.
New services run in parallel with what they replace until the outputs agree.
-
Hand over.
Source code, documentation and the deployment pipeline transfer to you.
-
Operate, if wanted.
Your team runs it, or Interkey supports it from Riyadh under a managed services agreement.
What drives the cost and timeline of custom software
Interkey publishes no package price for custom software, because two projects with the same feature list can differ several times over in effort. The drivers are:
- The systems it must connect to: how many, whether their interfaces are documented, and who approves changes on their side.
- What already exists: extending a system that stays in service differs from a new build.
- Arabic and English scope: interfaces, documents and search designed and tested in both languages.
- Hosting rules: a self-managed platform inside the Kingdom takes more engineering than a managed cloud service.
- Your team's share: work done for you, or alongside your engineers.
Duration follows the same drivers. As an estimate, engagements range from a scoped build of several weeks to a platform engagement lasting years; a firm timeline comes after discovery.
What to ask a software development company in Saudi Arabia before you sign
- Has the supplier read the interface documentation of the systems involved, or is it assuming an API exists?
- Is there a paid discovery phase, and what happens if it shows the project should change?
- Under the proposed model, who is accountable for the outcome?
- Are the source code, documentation and deployment pipeline yours at handover, in the contract?
- Is acceptance testing done in Arabic with the people who will use the software?
- Who supports it after go-live, from where, and under what written scope?
Questions buyers ask
What kinds of custom software does Interkey build for organisations in Saudi Arabia?
Mostly backends and APIs, integrations, internal tools, and Arabic and English web applications, with the delivery pipeline and monitoring around them. Much of the work extends or connects systems that already run the business.
How much does custom software development cost in Saudi Arabia?
It is quoted per engagement, after a short paid discovery phase. The price depends on the systems to connect, what already exists, the language scope, hosting rules, and the engagement model. Interkey publishes no package price.
How long does a custom software project take from discovery to go-live?
As an estimate, from several weeks for a scoped build to years for a platform engagement. It depends on the systems involved, how quickly their owners approve interface changes, and how much is new. A firm timeline follows discovery.
Should we choose a fixed-scope project or a dedicated development team?
A scoped project when the outcome can be defined and nobody inside has time to own it; a dedicated team when the work is ongoing and priorities change. If your engineers lack one skill, add specialists instead.
Can the software and its data stay inside Saudi Arabia?
Yes, where your data classification requires it: on infrastructure inside the Kingdom, including a self-managed container platform, or on a cloud region your policy allows. Hosting is decided in discovery, because it changes the design and the cost.
Who maintains the software after launch, and can our own team take it over?
Either. Source code, documentation and the deployment pipeline transfer to you, so your team can change and deploy it. Interkey can also support it from Riyadh, on the Saudi working week, under a written managed services scope.
Next
Read next
Next step
Scope your custom software project
Tell us what the software should do, what it must connect to, and who will use it. We will propose a discovery scope and the engagement model that fits.
Or directly
+966-11-2180999 [email protected]Tawuniya Towers, North Tower, 7th Floor, King Fahad Highway, Olaya, P.O. Box 56835, Riyadh 11564, Saudi Arabia