Eight delivery centres · Six countries

Turn-key IT delivery
across the GCC
and Africa.

Design, engineering and managed delivery under one accountable model. From strategy and enterprise platforms to AI, mobile and managed services — delivered across the GCC, Africa and India.

  • Prototype1 week
  • Mobilisation24–72 hours
  • Capacity flex48 hours
  • DeliveryArabic & English

Experience delivered across

Ministry of InvestmentGovernment · KSA
Ministry of Industry & Mineral ResourcesGovernment · KSA
SalamTelecommunications · KSA
NedbankBanking · South Africa
Coca-Cola Beverages South AfricaFMCG & manufacturing · South Africa
Absa GroupBanking · South Africa
Life HealthcareHealthcare · South Africa

Engagements delivered by TurnQy leadership and delivery teams. Engagements marked 2018 and earlier were contracted under Mind Click and are presented as the experience of those teams. Completion evidence and named referees on request.

200+Consultants deployedAcross eight delivery centres
10+Years delivery leadershipGovernment and regulated sectors
6Countries of operationKSA · UAE · South Africa · India · Pakistan · Egypt
100+Concurrent projectsManaged under one delivery model
99.9%Managed uptimeContracted service level

01 — What we do

One partner from
idea to run.

Six practices, one accountable delivery model, four countries, two languages.

01

Enterprise Platforms

SAP, ServiceNow and Atlassian implemented, integrated and administered by the same people who engineered them — with Arabic localisation across the landscape.

SAP · ServiceNow · Atlassian

02

Digital Products

Enterprise portals, native mobile and full-cycle product engineering, with Arabic RTL and accessibility as first-class behaviour rather than a retrofit.

Web · Mobile · Product engineering

03

AI & Automation

Retrieval, agents and automation wired into the systems that already run the business, with evaluation gates and an on-call rota after go-live.

AI engineering · Agents · Retrieval · Automation

04

Data & GIS

ArcGIS Enterprise run as infrastructure, enterprise geodatabases, and the analytics and data platforms that make spatial and operational data one estate.

Enterprise GIS · Analytics · Data platforms

05

Quality & Transformation

Business analysis, architecture and shift-left quality engineering — the disciplines that decide whether a programme lands or drifts.

QA · Testing · Business analysis · Architecture

06

Managed Delivery

PMO, managed services, resource augmentation and delivery management — dedicated teams mobilised in 24–72 hours and flexed within 48.

PMO · Managed services · Augmentation · Delivery management

02 — Design Studio

Design
Studio®

Send us the assignment. Get back a bespoke design system — not a template with your logo dropped in.

Most offshore design is a production line: a stock kit, a colour swap, a Figma file nobody can build from. Ours is a studio. Researchers, product designers, content designers and a design engineer, working as one pod against your brand — with Arabic and English treated as equals from the first artboard, not retrofitted at handover.

You get the research, the rationale, the prototype and the tokens. Engineering gets a system it can build from without a translation meeting.

1 wkClickable prototype from a signed brief
2–3 wkFull design system, tokenised and documented
AR / ENBilingual and RTL by construction
WCAG2.1 AA held in both scripts
  1. 01

    Discovery & research

    Stakeholder interviews, competitor teardown, journey mapping and a written problem statement you can argue with.

  2. 02

    Concept & art direction

    Three distinct directions, not three shades of one. Typography, colour, motion and imagery decided deliberately.

  3. 03

    Prototype

    Clickable, on real content, in real Arabic — tested with real users before a line of production code exists.

  4. 04

    Design system

    Tokens, components, states, RTL behaviour, accessibility notes and a handoff spec engineering can build from.

  5. 05

    Design engineering

    A designer who writes the components. The system ships as code, not as a PDF that drifts in six weeks.

  6. 06

    Content design

    Microcopy, error states, empty states and onboarding — written in both languages by people who write, not translated.

Offshore the assignment. Keep the quality.

Brief the studio

03 — Platform Centres of Excellence

Practices we run as a
discipline, not a resource pool.

End-to-end SAP, localised.

Implementation, integration and managed services — certified consultants with deep Saudi-market expertise and Arabic localisation across the full landscape.

  • SAP C4C — sales, service, marketing and commerce; lead-to-order automation with Arabic localisation
  • SAP CPI — custom iFlows, API management and B2B/EDI across 20+ systems in hybrid landscapes
  • SAP BTP — CAP and Fiori/UI5 with Arabic RTL; extend S/4HANA without core changes
  • S/4HANA migration — greenfield, brownfield or selective transition with controlled cutover and hypercare
  • Process & RPA — intelligent automation accelerating straight-through processing
  • GRC — role design and audit-ready controls mapped to ZATCA and SAMA
Managed SAP uptime
99.9%
C4C deployment
8–12 wk
Integration effort cut
60%
Systems in hybrid landscapes
20+

Built to run — not just to launch.

ServiceNow value is not created at go-live. It is created in the months afterwards, in the workflows that get refined, the integrations that get built and the administration discipline that stops the platform drifting. TurnQy stays for that part.

  • Implementation and configuration across ITSM, ITOM and custom applications
  • Workflow engineering with Flow Designer and orchestration
  • Integrations to SAP, identity, finance and partner systems via IntegrationHub
  • CMDB design, discovery and service mapping
  • Service Portal, performance analytics and executive dashboards
  • Platform administration, upgrades and release governance
  • Managed platform support under agreed service levels
Service Operations / Incidents Priority: P1–P2 ⌄Group: All ⌄State: Open ⌄Last 24h ⌄ ServiceNow · Vancouver
MAJOR INCIDENT — INC0041288 · Payments API degraded Bridge open · 14 responders Updated 2 min ago Join bridge
Open incidents41
P1 active2
Breaching SLA (<1h)5
MTTR (30d)3h 12m↓ 18% vs prev
MTTA6m 40s
Resolved today12

OverviewAug 12 → Aug 19

Opened ⌄ vs Resolved ⌄

TueWedThuFriSatSunMon

OpenedResolved

Service impact

Payments APIDegraded
Auth GatewayOperational
Core Banking DBOperational
Notification SvcDegraded
Partner ESBOperational

OperationalDegradedOutage

Active incidents41 Open ⌄Group by: Assignment group ⌄
PriorityNumberShort descriptionState Assignment groupAssigned toSLAUpdated
P1 INC0041288 Payments API latency above thresholdCI: pay-api-prod-03 In Progress Payments L2 ARA. Rashid ▲ BREACHED +00:47
2m ago
P1 INC0041275 Nafath SSO intermittent failuresCI: sso-edge-02 In Progress Identity Ops MKM. Khoury 00:38 left
9m ago
P2 INC0041260 Geodatabase replication lag on spatial estateCI: gdb-sql-prod-01 On Hold Database Admins SVS. Varma 02:14 left
24m ago
P2 INC0041244 ZATCA e-invoice submission queue backing upCI: cpi-iflow-zatca In Progress SAP Integration NKN. Khan 04:02 left
41m ago
P3 INC0041231 Field app sync conflicts on offline recordsCI: field-sync-svc New Mobile Engineering LSL. Sithole 07:55 left
1h ago
P4 INC0041209 Confluence Arabic search returns partial resultsCI: conf-dc-02 New Atlassian CoE GKG. Khan 31:20 left
3h ago

Recently resolved · 19 Aug · INC0041188 Portal session drops · Affected services: Auth Gateway · View post-incident report →

Illustrative console built on TurnQy's ITSM implementation pattern — priority, assignment group, SLA clock and service impact modelled the way we configure them, re-skinned into the TurnQy system. Not a client estate.

01

Request

Captured through portal, mobile, email or integration.

02

Workflow

Routed and enriched against the service catalogue and CMDB.

03

Approval

Governed by role, delegation and audit trail.

04

Automation

Orchestrated across connected enterprise systems.

05

Resolution

Measured against service levels, not against effort.

06

Analytics

Performance surfaced to the people who own the service.

Bespoke stack, when the package doesn't fit.

Not every problem is a licence away from solved. Where a product would force the organisation to work around it, we build — on a mainstream, hireable stack the client can own after we leave.

  • .NET Core & ABP Framework — modular monoliths and services with audit, multi-tenancy and localisation built in
  • Angular & React — government portals, operational consoles and executive dashboards
  • Node.js & TypeScript — integration services, BFFs and job orchestration
  • SQL Server & PostgreSQL — transactional estates, reporting models and enterprise geodatabases
  • Identity — Nafath, SSO, OAuth2/OIDC, token lifecycle and device-safe sessions
  • Payments & e-invoicing — gateway integration with ZATCA-conformant flows
  • Azure — landing zones, CI/CD, observability and cost governance
Clickable prototype from signed brief
1 week
MVP to production
8–12 wk
Accessibility held, both scripts
WCAG 2.1 AA
Handover documentation coverage
100%

Enterprise agility at scale.

Certified Atlassian practitioners and SAFe coaches — from initial deployment through complex migrations to ongoing governance.

  • Jira Cloud and Data Center implementation and configuration
  • JSM setup for ITSM workflows and SLA management
  • Confluence knowledge bases with Arabic content support
  • Jira Align for portfolio and programme-level visibility
  • Migrations from legacy systems with zero data loss
  • Automation reducing manual work by 50–70%
  • Integrations with DevOps, CI/CD and enterprise tooling
NCVC / Nova Core / Board All issuesActiveBacklog Jira Software · Sprint 24
⚲ Filter ARMKSVNK+3 Epic ⌄Type ⌄ Display ⌄
Epic: Payments Rework12 issues · 34 pts

To do8

NCVC-148

Arabic invoice template for ZATCA phase 2

FeatureRTL

PAYMENTS5AR

NCVC-151

Audit gateway response time under load

Performance

PAYMENTS3SV

NCVC-156

Bilingual receipt export

Feature

ONBOARDING8GK

In progress5 / 6

NCVC-142

Enable payment retry with idempotency keys

FeatureAPI+2

PAYMENTS5NK

NCVC-139

Duplicate settlement rows on retry

BugSev2

PAYMENTS3MK

NCVC-133

Nafath sandbox credentials rotation

Blocked

PAYMENTS2AR

In review3

NCVC-128

Refund workflow approval matrix

FeatureGovernance

PAYMENTS8LS

NCVC-124

RTL regression pack for checkout

QA

ONBOARDING3SV

Done11

NCVC-117

Payment gateway sandbox integration

PAYMENTS5NK

NCVC-112

Currency rounding on partial refunds

PAYMENTS2MK

NCVC-108

Arabic number formatting utility

ONBOARDING1GK

Nova Core NCVC-142 1 / 2  ˄ ˅

Enable payment retry with idempotency keys

Retries on the payment submission endpoint currently create duplicate settlement rows when the gateway acknowledges late. Introduce an idempotency key issued at request time, persisted with the transaction, and honoured on replay for 24 hours.

Acceptance criteria

Sub-tasks 1 / 3

NCVC-151Audit gateway response time under loadSV
NCVC-152Persist idempotency key with transactionNK
NCVC-153Replay guard + 409 handlingAR

2 branches · 1 pull request · Build passing

Activity

NK

Nayeem Khan moved this to In Progress 4 min ago

AR

A. Rashid linked INC0041288 as caused-by 22 min ago

Illustrative board and story built on TurnQy's Jira configuration pattern — swimlanes by epic, WIP limits, story points, acceptance criteria and a linked incident — re-skinned into the TurnQy system. Not a client project.

01

Assessment

Current-state analysis and readiness evaluation.

02

Roadmap

Tailored transformation plan aligned to business objectives.

03

Training

SAFe, Scrum and Kanban courses with Saudi case studies.

04

Coaching

Embedded support through the first three to six Program Increments.

05

Sustain

Metrics dashboards and continuous improvement ceremonies.

Platform-grade geospatial. Not desktop mapping.

ArcGIS Enterprise administered as infrastructure — federated Server, published services, enterprise geodatabases, and field capture that synchronises back into the estate rather than into a spreadsheet.

  • ArcGIS Enterprise deployment, federation, Portal and Server operations
  • Map, feature, image and geoprocessing service publishing, tuned for load
  • SQL Server and PostgreSQL geodatabases, versioning, replication, spatial indexing
  • Field Maps and custom capture with conflict handling and audit
  • Map-led operational dashboards and executive visibility

AI engineered and operated, not demoed.

The gap in enterprise AI is not the model. It is retrieval quality, evaluation, data residency, cost control and the on-call rota after go-live.

  • Retrieval pipelines with chunking, embeddings, reranking and enforced citations
  • Tool-using agents wired into SAP, ServiceNow and core systems — bounded and reversible
  • Evaluation harness with golden sets in both scripts; no release without a measured delta
  • Guardrails, PII handling and documented refusal behaviour
  • Traces, token cost per workflow, latency budgets and drift alerts

04 — Delivery expertise

One operating model.
Two platforms. No re-keying.

Most estates run ServiceNow and Atlassian as two islands and pay for the gap in re-typed demand, lost test evidence and change records nobody can trace back to a story. We run them as one chain under a single data contract.

  1. StrategyServiceNow SPM
  2. DemandServiceNow · BRM
  3. DesignFigma · JPD
  4. BuildJira Software
  5. TestXray · Automation
  6. ReleaseServiceNow Change
  7. RunITSM · CMDB · SLA
  8. ImprovePower BI · Analytics

One data contract across the bridge. Demand and gates cross into Jira; status, test verdicts and release packages cross back into ServiceNow. Nothing is re-keyed in either direction, which is why a change record can always be traced to the story that caused it.

ServiceNow scope

Governance & performance
IT Governance · Performance Analytics — the KPI hub for every process
Delivery & portfolio
Demand · Projects · Release · AI PoC · Products · Strategy — SPM
Configuration backbone
CMDB · IT Assets · Capacity — one CI model referenced everywhere
ITSM core
Incident · Service Request · Change · SLA engine — Service Portal
Quality & practice
Quality Control · BRM · Workforce · Knowledge · Compliance · EA

Atlassian scope

Jira Product Discovery
Requirements discovery, elicitation and prioritisation
Jira Software
Delivery backlog · sprints · gated build workflow
Xray
QA and testing — plans, runs, defect traceability
ServiceNow bridge
Bi-directional — demand and gates in, status and verdicts back
One data contract
No re-keying in either direction, ever

05 — Digital transformation engineering

From signed brief to
clickable prototype in one week.

Web portal or mobile app — one week to something a stakeholder can click, in their own content, in their own language. Not a slide, not a static mockup. A running prototype that becomes the production codebase rather than being thrown away.

Day 1

Brief locked

Scope, users, content and success measures agreed and written down.

Day 2–3

Art direction

Direction chosen, component shells drawn, real Arabic and English content in place.

Day 4–5

Build

React or Angular shell wired to mock services on the real design tokens.

Day 6

Walkthrough

Clickable on a device, in both scripts, with the edge cases visible.

Day 7

Decision

Proceed, pivot or stop — on evidence, before the budget is committed.

.NET CoreServices, APIs, ABP Framework, audit and multi-tenancy
React & Next.jsEnterprise portals, consoles, design-system components
AngularGovernment portal front ends and workflow applications
PostgreSQL & SQL ServerTransactional estates, reporting models, geodatabases
Microsoft AzureLanding zones, CI/CD, observability, cost governance
Swift · iOSNative delivery, offline-first, device-safe sessions
Kotlin · AndroidNative delivery, phased rollout and rollback ownership
FigmaDesign systems, tokens, bilingual and RTL components
SAPS/4HANA, C4C, CPI, BTP with Arabic localisation
ServiceNowITSM, ITOM, Flow Designer, IntegrationHub, CMDB
AtlassianJira, JSM, Confluence, Align, automation
Esri ArcGISEnterprise, Portal, Server, Data Store, Field Maps
Power BIExecutive and operational reporting, bilingual
GitHubSource control, review and CI workflows
DockerReproducible builds and runtime packaging
KubernetesContainer orchestration and scaling

06 — Mobile engineering

Native iOS and Android,
built for the field.

Inspectors in Jubail with no signal. Field crews on a fibre route outside Tabuk. A citizen filing a request in Arabic on a four-year-old handset. That is the operating environment we design for — not a demo on office wi-fi.

  • Native iOS and Android delivery; cross-platform where it earns its place
  • Offline-first architecture with resumable synchronisation
  • GPS, geofencing and geo-tagged evidence capture
  • Secure sign-in, token lifecycle and device-safe sessions
  • Arabic RTL, store compliance and phased rollout with rollback ownership
  • Crash monitoring and post-release support under agreed service levels
SwiftKotlinFlutter React NativeFirebase

07 — Enterprise GIS

Platform-grade geospatial.
Not desktop mapping.

ArcGIS Enterprise administered as infrastructure — federated Server, published map, feature and geoprocessing services, enterprise geodatabases, and field capture that synchronises back into the estate rather than into a spreadsheet.

LayersMapFieldsFilterSymbologyArcGIS Enterprise · Portal 11.2
Saudi Arabia with industrial estates and fibre backbone routes
Industrial estate Fibre node Backbone route
01

Administration & topology

ArcGIS Enterprise deployment, federation, Portal and Server operations, upgrade and patch discipline.

02

Services & publishing

Map, feature, image and geoprocessing services tuned for load, with cache strategy and monitoring.

03

Enterprise geodatabase

SQL Server and PostgreSQL geodatabases, versioning, replication and spatial index tuning.

04

Field to enterprise

Field Maps and custom capture synchronised into the estate, with conflict handling and audit.

Why one group. A slow map service is usually a geodatabase, a service-tuning and an application-query problem at the same time. When those three specialists report to one delivery lead, diagnosis takes hours. When they work for three vendors, it takes weeks.

08 — AI engineering

AI that gets operated,
not demoed.

The gap in enterprise AI is not the model. It is retrieval quality, evaluation, data residency, cost control and the on-call rota after go-live. We engineer that part — with privacy, explainability and Saudi compliance as design inputs.

01

Retrieval & document intelligence

Arabic and English extraction, classification and grounded retrieval over contract, permit and policy estates — with citations, so an answer can be checked.

Arabic + English at scale

02

Agents & automation

Tool-using agents wired into SAP, ServiceNow and core systems for invoice processing, reconciliation and case triage — bounded, logged and reversible.

60% manual effort removed

03

Conversational assistants

Arabic-capable assistants for customer service, HR and helpdesks — up to 80% faster response.

04

Predictive analytics

Demand, churn and operational-risk models with monitored drift and documented evaluation.

05

Vision AI

Quality inspection, asset monitoring and security applications using computer vision.

The engineering underneath

01Evaluation harness

Golden sets in both scripts; no release without a measured delta.

02Retrieval pipeline

Chunking, embeddings, reranking and citation enforcement.

03Guardrails

Input and output policy, PII handling, refusal behaviour.

04Observability

Traces, token cost per workflow, latency budgets, drift alerts.

05Deployment

In-Kingdom hosting options; versioned prompts and models.

06Run

On-call, incident process and periodic re-evaluation after launch.

Responsible AI & compliance

Data residency

In-Kingdom hosting options with residency confirmed before design is baselined.

Human in the loop

Decision points stay with accountable officers; the model advises, it does not sign.

Auditability

Inputs, outputs and model versions logged so an outcome can be reconstructed.

Model governance

Provenance, drift monitoring and documented evaluation against PDPL requirements.

09 — Client success stories

Real outcomes
from real projects.

Measurable results across government, telecom, finance and industrial sectors. Reported without client names where confidentiality applies; the named engagement record follows below.

Government · IT outsourcing

Digital portal for a Saudi ministry

Launch a citizen-facing digital portal within 90 days to support Vision 2030 initiatives.

90Days — on schedule, team mobilised in 48 hours
200,000+Citizen registrations in the first month
ZeroCritical findings at security audit

Telecom · Atlassian CoE

Atlassian migration for a telecom group

Migrate 8,000+ Jira issues from on-premise to Cloud with zero downtime and full governance.

ZeroLoss across 8,000+ migrated issues
60%Reduction in administrative overhead
500+Users on a bilingual knowledge base

Finance · AI engineering

AI assistant for banking customer service

Reduce call-centre load with an Arabic-capable assistant integrated to core banking.

70%Queries resolved without human help
5m → 10sResponse time reduction
+25%Customer satisfaction score

Industrial · Agile coaching

SAFe transformation for a manufacturing group

Scale agile practice across 12 business units with portfolio governance.

150+Practitioners trained over six months
30%Improvement in time-to-market
PMOEstablished with bilingual dashboards

10 — Clientele

Enterprises we have
delivered for.

Named engagements across government, banking, telecommunications, healthcare and manufacturing — executed in Riyadh and Johannesburg, supported from the Dubai entity and the India delivery centres.

ClientEngagementExecuted inPeriod
Government · Kingdom of Saudi Arabia
Ministry of Industry & Mineral Resources
Ministry of Investment
Digital transformation management across national industrial and investment platforms. Riyadh2025 – Present
Telecommunications · Kingdom of Saudi Arabia
Salam Agile delivery consulting — cadence, governance and release discipline across platform teams. Riyadh2022 – 2024
Banking, healthcare & manufacturing · South Africa
Nedbank
Banking & financial services
Enterprise programme management across regulated core banking change. Johannesburg2018 – 2022
Coca-Cola Beverages South Africa
FMCG & manufacturing
Carve-out and roll-in programme management with quality assurance ownership. Johannesburg2018
Life Healthcare
Healthcare
Senior delivery consulting across clinical and corporate systems change. Johannesburg2016 – 2018
Absa Group
Banking & financial services
Portfolio management and quality engineering across a multi-programme estate. Johannesburg2007 – 2016

Engagements from 2018 and earlier were contracted under Mind Click and are presented as the experience of TurnQy's leadership and delivery teams rather than as TurnQy contracts. Named referees, completion evidence and contract detail are provided on request and as part of any formal submission.

19Years of continuous enterprise engagement
06Enterprise and government clients
05Regulated sectors served
02Countries of execution

11 — Where we operate

Eight centres.
Six countries. One model.

Core business in the Kingdom of Saudi Arabia and South Africa. A regional hub in Dubai holding the contracting entity. Offshore engineering from two Indian delivery centres, and resource hubs in Lahore and Cairo for surge capacity and Arabic-native engineering — with seven hours of daily overlap with Riyadh.

TurnQy delivery geography across Saudi Arabia, the UAE, South Africa and India

Core delivery

  • RiyadhKingdom of Saudi ArabiaDelivery HQ · programme governance, architecture and client-facing leadership
  • JohannesburgSouth AfricaNineteen years of continuous enterprise engagement in banking, healthcare and manufacturing
  • Cape TownSouth AfricaEngineering capacity and specialist talent into GCC and local programmes

Regional hub

  • DubaiUnited Arab EmiratesContracting entity — TurnQy FZCO LLC — and GCC coordination point

Resource network

  • LahorePakistanSurge capacity in engineering, QA and support · UTC+5
  • CairoEgyptArabic-native localisation, content design and QA on Riyadh hours

ODC / engineering

  • HyderabadIndiaOffshore development centre carrying the majority of TurnQy engineering
  • VisakhapatnamIndiaSecond ODC for capacity, resilience and a second recruitment market

Follow-the-sun coverage

06:0009:0012:0015:0018:0021:00
Riyadh KSA · Core
09:00 – 18:00
Dubai UAE · Hub
08:00 – 17:00
India Hyderabad · Vizag
07:00 – 16:00
South Africa JHB · CPT
09:00 – 18:00
Pakistan Lahore · Resource
07:00 – 16:00
Egypt Cairo · Resource
09:00 – 18:00

7 hours of daily overlap with Riyadh

01

Managed Services

24/7 run, monitoring and continuous optimisation at a 99.9% uptime service level.

02

Dedicated Teams

Scalable squads mobilised in 24–72 hours, flexed within 48 hours.

03

Fixed-Scope Projects

Defined outcomes, milestones and price for a clear end state.

04

Staff Augmentation

Embed certified specialists directly into your teams on demand.

05

Co-Development

Build together, with seamless handoff or ongoing support.

06

PMO-as-a-Service

Governance, portfolio visibility and bilingual executive dashboards.

12 — Leadership

The people accountable
for your delivery.

Delivery accountability is personal before it is contractual.

Jahanara Khan

Managing Director — GCC

Commercial strategy, client relationships and contracting governance.

Jahanara Khan

Gulnara Khan

Managing Director — India

Delivery capability, capacity planning and offshore centre growth.

Gulnara Khan

Nayeem Khan

Chief Operating Officer — India

Engineering standards, delivery execution and service performance.

Nayeem Khan

Vikram Indla

Delivery Head — Riyadh

Programme governance, architecture decisions and committed service levels.

Vikram Indla

Extended director biographies and professional histories are available in the full leadership pack on request.