Services · Mobile app development · Banking AI agents
Banking AI agent development Riyadh teams can put through their own risk committees: we design and build AI agents for banks, finance companies and fintechs headquartered in the capital. The agents read policies, prepare cases, answer customers in Saudi Arabic and English, and draft work for staff to approve. Each one runs inside your controls, logs every step, and never makes a credit or compliance decision on its own.
Riyadh is where most Saudi banks keep their head offices, close to SAMA, the Capital Market Authority and the Saudi Exchange. That puts compliance, risk and operations functions in one city, and those are the teams where a well governed agent saves the most hours.
200+ companies servedFrom a first store to an ADX listed developer
Agents we build for head offices
A bank's head office produces a steady stream of reading, checking and drafting: new SAMA circulars, alert queues, credit memos, policy questions from branches, vendor files. Much of it follows rules a capable analyst could write down. That is where an AI agent earns its place. It gathers the material, applies the documented rules, prepares a draft and hands it to a named person who approves, edits or rejects it.
We build these agents as narrow tools with clear limits rather than one general assistant. Each one has a defined task, a fixed list of systems it may read, an even shorter list of actions it may take, and a test set your team signs off before launch. The capabilities below are the ones head office teams in the capital most often ask us to scope first.
When SAMA or another authority issues a circular, the agent compares it with your internal policies and procedures, marks the clauses that appear affected, and drafts a gap note for the compliance owner. It cites the exact paragraphs it relied on so a reviewer can check its reading in minutes rather than reading the whole circular cold.
Compliance teams start each circular review with a cited first draft.
For transaction monitoring alerts, the agent pulls the customer profile, recent activity, prior alerts and screening hits into one case summary and suggests which documented typology the pattern resembles. It never closes or escalates an alert itself. Your level one investigator reads the summary, decides, and the agent records that decision with its reasoning.
Investigators spend their time judging cases, not collecting data.
Relationship managers covering large Riyadh corporates and regional headquarters spend hours assembling financial spreads, covenant history and sector notes. The agent drafts the standard memo sections from approved sources, flags missing documents, and leaves the credit judgement, rating and recommendation to the banker and the credit committee.
Memos reach credit review complete and consistently formatted.
Branch staff across the city ask head office the same questions every week about account opening rules, document requirements and product terms. An internal agent answers from your current policy library in Arabic or English, shows the source, and routes anything ambiguous to the policy owner rather than guessing.
Fewer repeat queries landing on head office inboxes.
Customers write the way people in Riyadh speak, not in formal Arabic. The service agent understands everyday Saudi phrasing, answers balance, card and transfer questions after the customer has authenticated in your app, and hands over to a human with the full conversation attached when the request needs one.
Routine requests resolved in the channel, complex ones handed over cleanly.
International companies setting up regional headquarters in Riyadh need corporate accounts quickly, and their finance teams often work in English. The agent explains document requirements, tracks what has been received, chases what is missing and keeps the relationship manager informed. Final KYC review stays with your onboarding team.
Corporate onboarding files move without repeated email chasing.
Banks assess technology and service providers against outsourcing and cyber security requirements. The agent reads vendor questionnaires and contracts, maps answers to your control checklist, and lists gaps and unanswered items for the third party risk team to follow up.
Third party reviews start with a complete gap list.
Head office staff raise access requests, password resets and application faults all day. The agent classifies each ticket, collects the details the resolver group needs, checks the request against your access matrix and opens the right workflow. Privileged access and production changes still go through your normal approval chain, with the agent only preparing the paperwork.
Tickets arrive at resolver groups complete and correctly routed.
From approved data marts and reports, the agent drafts the narrative for weekly and monthly packs: what moved, where thresholds were crossed and which items need an owner. Figures come from the source system, never from the model, and finance signs off the text.
Report narratives ready for review on the day the numbers close.
Every agent we deliver reports into one console showing its permissions, the model and prompt version in use, test results, escalation rates and a searchable log of actions. Risk and internal audit can review behaviour without asking engineering for extracts.
Second and third lines of defence see what each agent did and why.
Who this is for
Not every banking task suits an agent. The good candidates have documented rules, a clear owner, a measurable queue and a person who can approve the output. In Riyadh those conditions show up most often in head office functions, because that is where the volume and the rulebooks sit. Branch networks, call centres and operations hubs elsewhere in the Kingdom usually take their lead from decisions made here, so an agent proven at head office tends to travel. These are the four situations we hear about most.
Circulars, rule updates and supervisory requests arrive faster than policy owners can map them. We start with the circular analyst because it is low risk: it reads public documents and your own policies, and its output is a draft memo. Once the team trusts its citations, the same foundations support control testing and regulatory reporting checks.
Start with read only work, then widen.
Alert volumes rise with digital payments, and investigator time does not. An agent that prepares each case and proposes a typology can shorten handling time without changing who decides. We design it with your model risk team so tuning, testing and sampling follow the same discipline as your monitoring rules.
Newer SAMA licensed banks and payment companies in Riyadh often run lean operations teams and want agents in the design from the start. We build the customer agent and the internal operations agent on shared guardrails, so a product launch does not mean a new set of controls each time. Starting early also means the evaluation sets grow with the product, so by the time customer numbers rise, the bank already has months of evidence on how its agents behave.
Corporate clients expect quick answers in English and detailed documentation. Agents that draft memos, track onboarding files and summarise covenant positions give relationship managers more time with clients. The banker stays accountable for every recommendation that leaves the bank.
Agents support bankers; they do not replace credit judgement.
How we work together
Codeeo has a team in Riyadh alongside Dubai and Karachi, 80+ people in all, so workshops with your compliance and risk owners can happen in your offices. Most banks start with a fixed scope pilot for one agent, move to a retainer that adds agents on the same governance base, and some later take a dedicated team that works inside their delivery process. We have delivered 200+ projects across the UAE and the US and are rated 4.7 from 23 Google reviews.
Whichever route you take, the governance pieces stay with you: the evaluation sets, the approval rules and the logs. A second agent reuses them, which is why later agents usually move faster than the first.
A defined build with a deadline
We agree what the product has to do, write it down with a price and a date, and build exactly that. Changes are priced before they are made, not discovered on the invoice.
A product that keeps evolving
Named engineers who work your hours, join your standups and stay on the codebase. You direct the backlog; we own the quality of what ships.
Something live that needs looking after
A monthly block of hours for improvements, fixes and the small requests that otherwise wait months. Unused hours carry for a quarter.
Technology
Model choice follows your hosting and data rules: models deployed in your own cloud tenancy or on premises where required, retrieval over your approved document stores, and integration through your existing API gateway and identity provider.
01Mobile
02Data and cloud
03Marketing and tracking
Discovery and reviews in person in Riyadh, engineering across our teams.
Our Riyadh team runs workshops with your business owners, compliance and information security, and attends steering meetings in person. Engineering is shared across Riyadh, Dubai and Karachi, working in environments and accounts your bank provides. Where your policies require that certain data never leaves the Kingdom, developers work with synthetic or masked data and production access stays with your staff.
Schedule a free consultation and get a written recommendation, with costs, before you commit to anything.
Get in touchPROVEN RESULTS
Swift
Kotlin
Flutter
React Native
PostgreSQL
MySQL
MongoDB
AWS
Azure
Docker
GA4
Google Tag Manager
Search Console
Meta Pixel
Looker Studio