Techbanq

Decision guide · sourcing

In-Kingdom or offshore is a line through the work, not a side to pick

A part of every Saudi engineering programme genuinely belongs in the Kingdom: work on regulated data that must not leave, roles that carry localisation commitments, systems that need people physically at the site. Most of the rest is ordinary engineering that cares about quality and cost, not geography. Treating the whole programme as one or the other is how budgets are wasted in one direction and obligations missed in the other.

Information security for software delivery

  • ISO

    ISO/IEC 27001

    ISO/IEC 27001 certified

Certifications & registrations

Start from the constraints

The question is what must happen inside the Kingdom, not where developers sit

We do not have an office in Saudi Arabia

We serve organisations there from our Riyadh office and our engineering hubs in Lahore and Karachi, travelling for the parts of an engagement that need to happen in person.

Three kinds of constraint genuinely bind work to Saudi soil, and they are worth naming precisely because everything outside them is negotiable. The first is data: where a regulator or a customer contract requires that certain data stays in the Kingdom or is touched only from within it, the environments that hold that data — and sometimes the people who administer them — must be in-country, and no delivery model changes that. The second is people-based obligation: localisation programmes reward and in some sectors require Saudi hires in defined roles, and an organisation building a long-term engineering capability in the Kingdom is building it partly because those commitments are its own strategy, not just a rule. The third is physical presence: commissioning on a plant floor, installations, work inside a client's cleared facility.

Once those constraints are marked, what remains is usually the majority of the engineering: building features, writing tests, designing services, integrating systems through APIs that were built to be called from anywhere. That work is not made better by being done in Riyadh or worse by being done elsewhere; it is made better by senior people, clear ownership and enough overlap in the working day. The honest comparison starts only after the constrained work has been set aside, because comparing an in-Kingdom team and an offshore one on work that only one of them is allowed to do is not a comparison.

The unconstrained work

In-Kingdom and offshore delivery, weighed only on the work both may do

For the engineering that carries no residency, localisation or physical constraint, the two models differ on cost, talent access, speed to scale and what each contributes to the obligations you hold. Neither column wins every row.

OptionCost structure and its driversDepth of the talent pool you can reachSpeed to add or release capacityContribution to Saudization and long-term capabilityBest for
In-Kingdom teamGenerally the higher-cost option per engineer, driven by local salary levels, competition for scarce senior talent, and the recruitment and retention spending that competition forces. The premium narrows where roles are junior and widens where they are senior and contested.A growing but tight pool, heavily recruited by government programmes and large enterprises at once; certain specialisms are scarce enough that a vacancy can stay open for a long time regardless of budget.Slow to scale up, because each hire competes in the same tight market; slow to scale down, because a permanent team is a fixed commitment.Direct: every Saudi engineer hired and developed is the obligation met and the capability built, and the knowledge accumulates inside the organisation and the country.The regulated core, the roles that carry localisation commitments, and the leadership layer that owns the systems for the long term.
Offshore deliveryGenerally lower cost per engineer, driven by lower salary levels and living costs in the delivery country rather than by lower seniority; the gap narrows for the most senior roles, which are contested everywhere.Access to talent pools many times the size of the Kingdom's, so scarce specialisms that stay vacant locally can often be filled, provided the supplier actually screens for seniority rather than reselling availability.Fast in both directions: capacity is added from an existing bench and released when the work ends, which suits programmes whose demand is uneven.Indirect: offshore headcount does not count toward localisation, but it can free budget and senior local time for the Saudi hires that do, and it keeps delivery moving while those hires are found and grown.The build capacity, the specialisms the local market cannot fill, and workloads whose demand rises and falls.

The pattern that holds

Ownership and the regulated core in Riyadh, build capacity offshore

Illustrative arrangement

A Saudi enterprise is standing up a digital programme larger than the local market can staff on its timeline. Part of the estate touches data that must stay in the Kingdom, the organisation carries localisation commitments it takes seriously, and the backlog is far bigger than the team it can hire this year.

  1. 01Architecture and product ownership, the administration of regulated environments and the roles that carry localisation commitments are held by the in-Kingdom team, which is hired deliberately and kept senior.
  2. 02Feature delivery, testing and the specialisms the local market cannot fill run offshore, working in the in-Kingdom team's repositories and pipelines under its review, with access designed so regulated data never crosses the line.
  3. 03The split is revisited as the local team grows: work that began offshore for capacity reasons moves in-Kingdom when the people exist to own it, so the hybrid is a stage in building the capability, not a permanent ceiling on it.

The obligations are met by the people who can meet them, the backlog moves at the pace the business asked for, and the arrangement is honest on both sides of the line — nothing regulated leaves, and nothing ordinary waits a year for a hire.

Our role

We are the offshore half of this pattern, and we say when work must be local

Techbanq delivers from Pakistan. We do not have an office in Saudi Arabia, and this page is written from the offshore side of the line it describes — which is exactly why the line has to be drawn honestly.

  1. 01

    The constraint review comes first

    Before we scope anything, we go through the programme with you and mark what residency, localisation or physical presence binds to the Kingdom — because an offshore supplier that scopes that work for itself is creating your compliance problem, not solving your delivery one.

  2. 02

    Delivery designed for the distance

    Our teams work in your repositories and your pipelines, inside overlap hours agreed in the contract, with the work reviewed where you can see it — so the offshore half behaves like an extension of the in-Kingdom team rather than a parallel organisation.

  3. 03

    Built to hand across the line

    Everything we build is documented and owned in your accounts from the first commit, so when your local team grows into a piece of the work, moving it in-Kingdom is a handover, not a renegotiation.

Which side of the line each piece of work sits on is a judgement we make with you, not for you — and where the honest answer is in-Kingdom, we say so and scope ourselves out of it.

Common questions

What buyers ask

Does building offshore conflict with our Saudization obligations?+

Not inherently, because localisation obligations attach to your workforce and to defined roles, not to every line of code your systems contain — but the two interact and should be planned together. The workable pattern is to treat them as separate decisions made on the same map: identify the roles your commitments require you to hire and grow locally, staff those deliberately and give them real ownership, and then use offshore capacity for the build work that no obligation touches. What goes wrong is drift, where offshore capacity quietly absorbs the roles that were meant to become local hires because it is easier than recruiting. That is a governance failure, not a property of the model, and the fix is a split that is written down and revisited rather than left to gravity.

Which engineering work genuinely cannot leave Saudi Arabia?+

Less than most programmes assume, but the part that cannot is absolute. Work is bound to the Kingdom when a regulation or a contract requires specific data to stay in-country or to be accessed only from within it, when a system lives in a client environment that only cleared, on-site people may enter, or when the task is physical — commissioning, installation, anything on a plant floor. The important discipline is to trace each claim of "this must be local" to its actual source, because programmes accumulate assumed constraints: a rule that applies to production data gets extended by habit to test environments with synthetic data, or a residency requirement on one system quietly becomes a policy for all of them. Verify each one, keep the real constraints hard, and release the assumed ones — the difference is usually a large share of the budget.

Can we start a programme offshore and bring the work in-Kingdom later?+

Yes, and it is often the realistic sequence — but only if the move is designed in from the start rather than hoped for at the end. The conditions that make it work are concrete: the code lives in repositories you own from the first commit, decisions and operational knowledge are documented as they are made, your own people hold the architecture even while the typing happens offshore, and the contract names the handover as a deliverable with a shape. Under those conditions, moving a piece of work in-Kingdom when you have hired for it is a transition measured in weeks. Without them, the offshore supplier has become the only holder of the knowledge, and the move you planned as a handover becomes a rebuild you have to fund twice.

A short review of your programme that marks which work must be in-Kingdom, which can be delivered offshore, and how the two halves are governed as one team.

Draw the line for your programme