Built for the two sectors
that can least afford failure.

Banks answer to the regulator, and government entities answer to the public. This page sets out the eight problems we are asked to solve most often in the Kingdom's financial and public sectors: what we do about each one, the products involved, and how a first engagement starts.

Outcomes on this page describe what this kind of work typically achieves. They are not client results or guarantees.

Financial sector

For banks, fintechs & insurers

Every Saudi financial institution faces the same pressures: SAMA mandates arriving faster than delivery capacity, a legacy estate that slows every launch, and operations that still run on people and mailboxes.

01Challenge · SAMA regulatory deadlines

The mandate is due and the estate isn't ready

The situation

Open banking releases, instant payments and enforcement orders each land on an integration estate that is already at capacity. Each arrives as its own program, so identity, consent, security and core connectivity are built again every time. The regulator's date does not move.

What we do

We map the requirement to your systems and owners, then deliver it on shared components: FAPI-secured open banking, ISO 20022 payment connectivity and enforcement rules held as configuration. Each later requirement becomes a tested release on the same platform.

What you receive

  • Gap assessment and requirement-to-system map with owners
  • Architecture blueprint for the shared platform
  • Test packs, including security profile conformance
  • Runbooks and SLA reporting for go-live

Products involved

Typical outcomes

  • One platform and one team behind several mandates
  • Later requirements ship as tested configuration releases
  • Evidence for the regulator ready on request

Typical first step

An executive briefing on the mandate and its date. You leave with a written view of the gaps and the order in which to close them.

Book a briefing

02Challenge · legacy links & undocumented systems

Every launch dies in the integration layer

The situation

Product teams wait months because each new product or channel has to pass through point-to-point links nobody fully understands. Documentation is out of date, and every change carries regression risk. The integration backlog sets the launch date.

What we do

We reverse-engineer the estate into a complete inventory and decide with you what to keep, consolidate or retire. Migration runs in sequenced waves with strangler patterns and recorded-traffic replay, verified against real traffic at each step. A design authority keeps new work on governed, reusable APIs.

What you receive

  • Integration inventory and dependency map
  • Risk and rationalization analysis
  • Costed, sequenced modernization roadmap
  • API and event standards under a design authority
  • Regression packs built from recorded traffic

Products involved

Typical outcomes

  • New launches reuse existing services
  • Fewer point-to-point links to run, test and secure
  • Changes released with regression evidence

Typical first step

An integration estate assessment, fixed in scope and typically 2 to 4 weeks: inventory, risk map and a costed roadmap with a board-ready summary.

Scope an assessment

Track record: in programs our team has led inside the Saudi financial sector, 100+ point-to-point integrations were consolidated into one governed platform, integration time-to-market fell by 70%, and 500+ services were documented and governed.

03Challenge · manual back-office at scale

Operations still run on people and mailboxes

The situation

Payments, cards, KYC and trade teams take in hundreds of messages a day through shared mailboxes. Someone reads each one just to decide who should handle it, and managers see SLA risk only after a complaint. Reconciliations and registers take up whole teams.

What we do

We put AI agents to work inside your security boundary, one workflow at a time. They classify and route Arabic and English email, extract case details, match records and propose register updates. Consequential actions need maker-checker approval, and every decision is logged with its reasons.

What you receive

  • Baseline of volumes, handling time and SLA performance
  • Production-shadow deployment inside your network
  • Before-and-after metrics and go/no-go economics
  • Approval rules, audit trail and access design

Products involved

Typical outcomes

  • Requests reach the right team without manual sorting
  • SLA warnings arrive before a breach
  • More staff time spent on resolving requests

Typical first step

A 30-day AI automation pilot on one mailbox, reconciliation or register, measured against an agreed baseline, with a go/no-go decision on the economics.

Start a pilot

04Challenge · identity friction vs fraud risk

Onboarding friction is losing you customers

The situation

Each extra identity step costs conversions, and each step removed adds risk. Checks are often wired separately into each channel, so the app, web, branch and call centre behave differently. When a national identity service slows down, applications fail.

What we do

We build one identity layer for every channel. Nafath, Yakeen and Absher OTP sit behind one contract, with retries and circuit breakers for government APIs. Customers get one identity with adaptive, risk-based authentication, and tokens are FAPI-grade and shared with your open banking.

What you receive

  • Target identity architecture and risk policy
  • Integration with national identity services and your core
  • Resilience design for slow or unavailable services
  • Consent records aligned with PDPL

Products involved

Typical outcomes

  • Fewer steps for low-risk customers, step-up when risk calls for it
  • The same identity experience in every channel
  • Fewer failed applications when a national service is slow

Typical first step

An executive briefing with your digital and fraud leads. We review the onboarding funnel and give you a written view of where friction and risk sit.

Book a briefing
Government sector

For ministries, authorities & public entities

Vision 2030 programs depend on integration: citizen services that span entities, mandates that must reach every bank, and internal operations still moving on paper and email. We design, build and run the integration that connects them, with KSA data residency by default.

05Challenge · cross-entity integration

Citizen services that span a dozen entities

The situation

A single citizen service can touch identity, payments and the systems of several entities, each with its own formats and SLAs. Links are built one pair at a time, so every new service adds connections to secure and monitor. Citizens supply documents for facts the state already holds.

What we do

We deliver a governed integration hub for the entity: one gateway to national platforms such as Nafath, Yakeen, Absher, GOSI and the National Address, with consistent data contracts and resilience patterns for external APIs. Applicants confirm facts at source under one consent.

What you receive

  • Service and data-flow inventory across entities
  • Integration hub architecture and API standards
  • Security design mapped to NCA ECC and your controls
  • Data contracts and consent rules aligned with PDPL
  • Monitoring, SLA reporting, runbooks and handover

Products involved

Typical outcomes

  • One governed gateway in place of many bilateral links
  • Fewer documents requested from citizens
  • Each service's dependencies and SLAs visible in one place

Typical first step

An executive briefing on one citizen service. We map its dependencies and give you a written view of the integration path.

Book a briefing

06Challenge · sector-wide program execution

Mandates that must reach every bank in the Kingdom

The situation

When an authority issues an instruction, such as an enforcement order, a directive or a data request, execution depends on the integration maturity of every institution that receives it. Formats and response times vary, and the authority has limited sight of what was actually done.

What we do

We apply the execution model our team has run inside a Saudi financial institution: standardized intake, versioned rules, an SLA clock per mandate, daily reconciliation and tamper-evident audit. For the authority we define message standards and conformance tests. For receiving banks, EnforceDesk executes the orders.

What you receive

  • Instruction message standards and API specifications
  • Onboarding guide and conformance test pack for institutions
  • Execution, reconciliation and evidence design
  • SLA and status reporting for the authority

Products involved

Typical outcomes

  • Instructions issued in one standard format
  • Status and evidence for each order available on request
  • New instruction types released as configuration

Typical first step

An executive briefing on the instruction flow. We map how it reaches institutions today and where execution and evidence break down.

Book a briefing

07Challenge · delivery ownership

Transformation programs stalled between vendors

The situation

Large government programs often have five vendors and no owner of the outcome. Each vendor delivers its own scope, the interfaces between them belong to nobody, and integration problems surface at acceptance testing or after go-live.

What we do

We take single-point accountability for the integration workstream: design authority, interface contracts between vendors, RFP authoring and vendor evaluation, delivery in production increments, and managed operations after go-live, including the 2 a.m. incidents.

What you receive

  • Integration architecture and interface control documents
  • End-to-end test plan and test packs
  • Cutover plans with checkpoints and tested rollback
  • Target operating model, runbooks and SLAs

Products involved

Typical outcomes

  • One accountable owner for the interfaces between vendors
  • Integration defects found in testing, before acceptance
  • A clean handover to operations, with runbooks and SLAs

Typical first step

A fixed-scope review of the program's integration workstream, typically 2 to 4 weeks: interfaces, owners, risks and a sequenced recovery plan.

Scope a review

08Challenge · correspondence & asset records

Internal operations still move on paper and email

The situation

Official correspondence arrives in shared inboxes and is forwarded by hand, so requests wait and some are lost. Asset registers live in spreadsheets that drift from what the entity actually owns, and the same audit findings return each year.

What we do

We deploy AI agents inside the entity's own network or private cloud. They route correspondence to the right department and keep the asset register in step with ERP, procurement and HR records. People approve every consequential change, and the audit trail records who decided what.

What you receive

  • Classification and routing rules per department
  • Register reconciliation against source systems
  • Approval rules and audit trail design
  • Baseline and before-and-after metrics at day 30

Products involved

Typical outcomes

  • Correspondence reaches the right department without manual sorting
  • Register differences found and resolved with approval
  • Audit-ready records of each change and its approver

Typical first step

A 30-day AI automation pilot on one mailbox or one register, measured against a baseline, with a go/no-go decision at day 30.

Start a pilot
By role

What each role gets

The same engagement answers different questions for different people. This is what each role typically takes away.

COO · Head of operations

Fewer manual touches and SLAs you can see

  • Shared mailboxes triaged and routed under your rules
  • One live view of platforms, queues and batch jobs
  • A measured go/no-go decision before you scale
CIO · CTO

An estate you can describe, govern and change

  • Integration inventory, blueprint and costed roadmap
  • Platforms in your data centre or private cloud
  • Test packs, runbooks and handover, or 24/7 managed operations
Head of digital

Launches that reuse what is already built

  • Reusable APIs for each new product or channel
  • Fewer onboarding steps and one customer identity across channels
  • Open banking and partner APIs ready for third parties
Compliance · Risk

Evidence on request and controls by design

  • Tamper-evident audit trails on regulated flows
  • PDPL-aligned consent records and KSA data residency by default
  • Maker-checker on rule changes and AI actions
Programs and mandates

Saudi programs and mandates, mapped to our offer

Each program below places specific demands on the integration layer. Here is what it asks of you and how we help.

  • Open banking

    SAMA Open Banking Framework

    SAMA's framework covers account information and payment initiation services, with API specifications, a security profile built on the FAPI standards, and operational guidelines.

    What it asks of you

    Onboard authorized third parties, check their certificates, hold every customer consent, secure each call to the KSA security profile, and report on service levels.

    How we help

    ConsentHub runs third-party onboarding, consent and the APIs, with FAPI 1.0 Advanced today and ready for 2.0. We connect it to your core and payment hub.

  • Payments

    Instant payments

    The instant payment system (IPS) moves retail payments between banks in seconds, around the clock, alongside SARIE, the real-time gross settlement system.

    What it asks of you

    Core banking, limits and fraud checks that answer in seconds at any hour, post each payment once, and reconcile daily.

    How we help

    PayConnect links your payment hub and core for SARIE, IPS, bulk and SADAD-style biller payments: ISO 20022 orchestration, verify-and-hold, idempotent posting and reconciliation.

  • Enforcement

    Tanfeeth enforcement

    Court enforcement orders reach banks electronically through Tanfeeth, each with a deadline to respond: account blocks, garnishments, transfers of held funds and lifts.

    What it asks of you

    Execute each order correctly across a customer's accounts within the deadline, handle shortfalls, and prove later what was done.

    How we help

    EnforceDesk executes orders as versioned catalogue services, with a typed obligation ledger, daily reconciliation and a tamper-evident audit trail. New requirements usually ship as configuration packs.

  • Identity

    Digital identity with Nafath

    Nafath is the national digital identity service, used to authenticate people and approve requests, often alongside Yakeen and Absher OTP.

    What it asks of you

    Use national identity services consistently in every channel, keep onboarding working when one is slow, and handle identity data under the PDPL.

    How we help

    KYCLink puts one contract over Nafath, Yakeen and Absher OTP. OneSign adds Nafath federation and risk-based step-up. VerifyFlow confirms applicant facts at source.

  • Data protection

    Personal Data Protection Law (PDPL)

    The PDPL governs how personal data is collected, processed, disclosed and transferred outside the Kingdom, and gives individuals rights over their data.

    What it asks of you

    A lawful basis for each use, consent records where consent is the basis, data subject rights, breach handling and control over transfers abroad.

    How we help

    KSA data residency by default, platforms inside your boundary, PDPL-aligned consent records and role-based masking. Our advisory work covers PDPL readiness.

These summaries simplify the official texts for orientation. The regulator's published requirements and your compliance function remain the reference.

How we start

How an engagement runs

Each stage has a fixed scope and ends with something your board can act on.

  1. Brief

    A 90-minute executive briefing on one problem you own. You leave with a written point of view.

  2. Assess or pilot

    A fixed-scope estate assessment, typically 2 to 4 weeks, or a 30-day AI pilot measured against a baseline.

  3. Build

    Delivery in production increments, each tested against recorded traffic, with runbooks and SLAs agreed before go-live.

  4. Run

    Handover to your team, or managed operations 24/7 with monthly SLA reporting at executive level.

Start with one briefing

Tell us about the mandate, the stalled program or the process that is causing problems. In 90 minutes we work through it with you, and you leave with a written view of scope and sequence.