Next chapterRead the announcement

Announcement

How Tayseer Innovations works across Saudi Arabia and the UAE: an open letter to clients and partners

The Dubai skyline in silhouette against a pink and orange sky at dusk, reflected in still water

As our work in both markets grows, we are setting out plainly how we staff projects, where data sits, what happens when something breaks, and what we will not promise.

Tayseer Innovations is publishing this letter for the people who have to decide whether to trust a technology company with something that matters: the heads of technology, risk officers, compliance teams and procurement leads at the institutions we work with, and those who are considering it.

Most of what a vendor publishes about itself is written to impress. This is written to be checked. It sets out how we work today across Saudi Arabia and the UAE, so that anyone relying on us can hold us to it, and anyone assessing us can compare it with what they see in practice.

Why we are writing this now

Established in 2016 and built on the Kuraimi Group, Tayseer Innovations has grown into a fintech company in Saudi Arabia and the UAE, with over 5,500 professionals from more than 20 nationalities, serving over 4 million customers regionwide with agentic AI, digital banking and core banking technology.

Growth changes things. A small team can run on personal trust, because the client knows the person who will answer the phone. A larger organisation has to replace that with something written down, so that the client's experience does not depend on who happens to be on their project.

We also hear the same questions in almost every first meeting. Where will our data sit? Who will actually be doing the work? What happens at night? What are you certified for, exactly? It seemed better to answer them once, in public, and to stand by the answers.

Two markets, one way of working

Saudi Arabia and the UAE are not one market, and we do not treat them as one. They have different regulators, different expectations on where data may live, different procurement processes and, often, different assumptions about how a vendor should behave in the room.

What stays the same is how we run the work. A client in Riyadh and a client in Dubai get the same delivery practices, the same security controls and the same standard of documentation. What changes is everything local: the team, the regulatory reading, the language of the conversation and the deployment choices that follow from them.

The Kingdom Centre tower in Riyadh against a warm orange sky
Our teams work from offices in Riyadh and Dubai, close to the institutions they serve.

In practice, that means three things.

  • Each engagement has a lead based in the same country as the client, who knows the local regulatory context.
  • Work is carried out by teams who operate in Arabic and English, and client documents are produced in whichever the client needs.
  • Decisions about a client's project are made close to that client, rather than being sent up a long chain and waiting.

Where your data sits

This is usually the first question, and it should be. We do not start from a preferred hosting arrangement and then ask the client to accept it. The institution decides where its data lives, and we design around that.

Depending on the institution and its supervisor, that can mean deployment on premises, in a private cloud or in a regional cloud with defined residency. Each has real consequences for cost, for how quickly updates can be made and for who may touch what, and we will set those out honestly rather than steering towards whichever suits us.

What our people can and cannot see

Access is granted for a task and removed when the task is finished. Support staff do not hold standing access to client production systems as a matter of convenience. Where a client's policy requires it, access is supervised, recorded or carried out from within the client's own environment.

What our AI systems can and cannot see

The same principle applies to software as to people. Our agentic AI systems are given the narrowest access the task allows, and customer data is not used to train general models. A client's data does not become our asset, and it does not become anyone else's either.

How we staff a project

Anyone who has bought technology services will recognise the pattern where senior people attend the sales meeting and different people turn up on the first day. We would rather be judged on what happens after the contract is signed, so we have tried to make that visible.

  1. The people named in a proposal are the people who do the work, and any change is agreed with the client first.
  2. Every project has a single accountable lead with the authority to make decisions, not just to relay them.
  3. Clients can meet the engineers working on their systems, and are encouraged to.
  4. Handover to operations is planned from the first week, not left until the end.

Long engagements inevitably see people change roles or move on. When that happens, the client hears from us first, there is an overlap, and the knowledge is written down rather than walking out of the door.

What happens when something breaks

Everything breaks eventually. A vendor who tells you otherwise has not been running systems for very long. What distinguishes a serious operator is what happens in the first hour, and whether the client hears about it from them or from their own customers.

For platforms we operate, service levels are agreed in writing and monitored around the clock. When an incident occurs, we tell the client what we know as soon as we know it, including when the honest answer is that we do not know yet. A named person stays with the incident until it is closed.

We would rather call you with an incomplete answer at three in the morning than a complete one at nine.

After a significant incident, the client receives a written review covering what happened, why it happened and what will change. We write these for the people who have to explain the event to their own management and, if necessary, to their regulator. We do not write them to protect ourselves.

What we are certified for, and what we are not

Our information security management system is certified to ISO/IEC 27001:2022. That is a specific statement about a specific scope, and we will share that scope with anyone assessing us.

We do not claim certifications we do not hold. If a control you need falls outside our scope, we will tell you where the boundary is, rather than letting you assume it is covered. Where a partner's certification is what applies, we will name the partner and let you see their documentation.

Regulated institutions answer to their own supervisors, and no vendor can answer on their behalf. Our job is to make that answer easier to give, by being precise about what we do and clear about what we do not.

What we will not do

A company's standards show as much in what it refuses as in what it offers. So here, in plain terms, are some things we will not do.

  • We will not publish client names, transaction volumes or incident details as marketing. What a client tells us stays between us until they say otherwise.
  • We will not present illustrative figures as measured results.
  • We will not promise a delivery date we do not believe, in order to win a piece of work.
  • We will not tell you a project is going well when it is not. Bad news gets worse with age.

We have turned down work on these grounds, and we expect to do so again.

How we work with partners

We do not build everything ourselves, and we would be suspicious of anyone in this industry who claimed to. Our banking hardware estates rely on manufacturers, and our software runs alongside systems from many other vendors. A client's experience should not fall apart at the point where one company's responsibility ends and another's begins.

So when a partner is involved, we say who they are, what they are responsible for and whose certification applies to what. If something fails between two systems, we stay on the problem until it is resolved, rather than sending the client back and forth between suppliers. And where a partner's product is not the right answer for an institution, we say so, even when it would be easier and more profitable not to.

What this means if you already work with us

Nothing in this letter should be new to you. If any of it does not match your experience, we want to know, and we would ask you to tell your project lead or to write to us directly. We would rather hear it from you now than discover it at renewal.

If you are assessing us, please use this letter as a checklist. Ask our teams to show you how each of these commitments works in practice, and ask to speak with the people who would actually be on your project. Send us your vendor assessment as well, because most institutions already have one. You will get a straight answer, including where the answer is no.

What comes next

We will review this letter once a year and publish any changes, so that it remains a description of what we do and not a record of what we once intended. As regulation in both countries develops, and as the technology changes what is possible, some of the details here will change too. The principles should not: tell clients the truth, keep their data theirs, and be there when something goes wrong.

You can read more about how we handle institutional data on our Trust & Security page, or contact the team with any question this letter leaves open.

About Tayseer Innovations

Established in 2016 and built on the Kuraimi Group, Tayseer Innovations is a fintech company in Saudi Arabia and the UAE: over 5,500 professionals from more than 20 nationalities, serving over 4 million customers regionwide with agentic AI, digital banking, and core banking technology.

Media contact

info@tayseer.me
  • Sample post
  • Company
  • Saudi Arabia
  • UAE
All news

More news

More from the newsroom