Riyadh and Jeddah keep a Sunday to Thursday week, and Karachi does not

Four days that land on top of each other, and two that do not

Riyadh, Jeddah and Dammam run on UTC+3 and Karachi on UTC+5. Neither country observes daylight saving, so the difference is two hours in January and two hours in July. A Karachi day from nine to six covers seven in the morning to four in the afternoon in Riyadh, which is most of a Saudi working day rather than a slice of one.

The week is where an unstated assumption turns into a monthly argument. Saudi Arabia works Sunday to Thursday and takes Friday and Saturday. Pakistan works Monday to Friday and takes Saturday and Sunday. Monday through Thursday both sides are at their desks and the only difference is those two hours. The remaining two days each belong to one side alone, and they behave nothing like each other.

Sunday is the expensive one. Left unaddressed, a question raised on Sunday morning in Riyadh waits until Monday, which means the first day of your week is the day your supplier is least present for, and that is the worst day of the five to lose. The fix is not a promise, it is a rota: a named person covering a stated Sunday window in Saudi time, with the day taken back later in the week, written into the arrangement. It should also be honest about what Sunday cover is. One person on a Sunday can answer, unblock and escalate. One person on a Sunday cannot build, cannot deploy anything risky and cannot make a decision that needs three people in a room.

Friday is the useful one and almost nobody plans for it. It is a full working day in Karachi with nobody in the Kingdom waiting on an answer, which makes it the natural home for the work that needs uninterrupted hours. It also decides the release calendar. Anything that could break should land on Thursday evening Saudi time or on Sunday morning, never on Thursday afternoon, because Thursday afternoon is the last hour anybody in Riyadh is available to notice.

Reduced working hours through Ramadan are normal across the Kingdom and the whole delivery calendar moves with them. Agreeing that in advance is a ten minute conversation. Discovering it in the middle of a launch is not.

The PDPL, which is the part a Saudi buyer will actually ask about

Saudi Arabia has a Personal Data Protection Law. It came into force in September 2023, the compliance grace period ended in September 2024, and the Saudi Data and Artificial Intelligence Authority is the regulator. A separate regulation covering the transfer of personal data outside the Kingdom was issued in 2024. Nothing on this page is legal advice and your own adviser should confirm what applies to your situation.

What a supplier can usefully speak to is the shape of the obligation rather than its clauses. A supplier sitting outside the Kingdom is not itself the problem. An undocumented transfer is. The regulator has not published a list of countries treated as adequate, so a transfer abroad is expected to rest on an approved mechanism such as standard contractual clauses, and the regulator has published templates for those.

Three things change concretely inside the build. Where the database sits stops being a default chosen by whoever set up the first tool and becomes a decision made in week one. Every third-party service that will touch personal data gets listed before anything is connected, rather than reconstructed under pressure eighteen months later. And a deletion request has to reach every copy, which includes the automation platform's own execution history and any logs held by a model provider, not only the record in the CRM.

That last one is the test worth applying to any supplier, including this one. Ask them to name every place a Saudi customer's phone number would exist in the system they are proposing, and whose servers each of those sits on. A design that has been thought about answers with a list and a diagram. A design that has not answers with the word compliant.

Arabic is not optional in this market, and Wobble does not have it

Wobble works in English and Urdu. In the Emirates that limit is survivable because so much business runs in English. In the Kingdom it is a harder boundary, because Arabic is the language of the market and of the regulator, and pretending otherwise on a sales page would be the exact kind of claim this company spends the rest of the site refusing to make.

So the scope divides cleanly. An internal system used by English-speaking staff is something Wobble can build and be answerable for. An Arabic customer-facing agent is not something Wobble can be accountable for alone, because accountability for language means a person who reads it reviewing every template, every fallback and every escalation before launch and again after every change. There is no version of that a supplier can do without the language.

Two arrangements work. Your own Arabic speaker owns the copy and the sign-off, with time allocated for it rather than squeezed in. Or a local partner is contracted for it, so the responsibility is written down and belongs to somebody. What does not work is a supplier running the copy through a model and nobody checking, and that is common enough that it is worth asking about directly.

One more question belongs in the first call rather than the fifth. If you are buying through a government-linked entity or as part of a large contract, ask whether the supplier is required to be locally registered. That is a procurement question and it settles everything before technical fit becomes relevant.

Voice works differently here than it does in the Emirates

Saudi Arabia permitted voice calling over internet applications in 2017, so calls through the ordinary messaging apps generally work in the Kingdom. That is not the position on UAE networks, which is set out on the Emirates page. If you operate in both countries, that is two channel designs rather than one, and a proposal that assumes otherwise was written for whichever market the supplier knows better.

What it means in practice is that a Saudi build has a genuine choice: a telephone number, an internet calling channel, or both. The question that decides it is not which is more modern. It is which one your customers already use to reach you, which you can answer by looking at where last month's enquiries actually arrived. The rest of what sits inside a voice build is on AI voice agents.

Availability is a regulator's decision in both countries and it has changed before, so verify the current position with your own operator rather than taking it from any agency page.

If you searched for a marketing agency in Riyadh or Jeddah

A large share of the Saudi searches that reach this company carry no AI word at all. They are typed as advertising agency, digital marketing agency, branding agency or social media agency with Riyadh, Jeddah or Khobar attached. The buyer behind them is usually not shopping for technology. They want more enquiries and they want the ones they already get to be answered.

There is a real limit on how much of that brief this company can take here, and it follows directly from the language. An agency that cannot write Arabic copy cannot run your Arabic paid social, and no amount of clever targeting compensates for creative nobody in the room can read. So the honest scope in the Kingdom is the machinery behind the marketing: lead capture, response speed, CRM, follow-up and reporting, plus English-language campaign management where the audience genuinely is English-speaking. Arabic creative belongs to somebody who writes Arabic. The systems side is described on AI sales systems and CRM automation.

No Saudi client, so ask for something better than a case study

Wobble publishes twenty five or more engagements across Pakistan, the United States, Australia, Germany and Mexico, and not one of them is in the Gulf. That is on the work page and it is not going to be dressed up here.

A buyer facing a supplier with no client in their market has better questions available than asking for a case study that does not exist. Three of them do most of the work.

1. A reference from a market with the same shape. Not the same country. The same difficulty: voice at volume, data somebody regulates, and a first language the supplier does not speak.
2. A first engagement small enough that a bad outcome is affordable. One system, one measurable number before and after, a defined end date, and a decision point rather than a renewal that happens by silence.
3. A written exit. The system lives in your own accounts, you own the keys, and leaving costs a handover rather than a rebuild. That is the whole subject of ways to own your AI system.

The same three questions are worth asking of any supplier that is new to your market, including the local one whose office you can visit.

When to say no in the first week

If your own policy or your customer's policy requires personal data to remain in the Kingdom and never be accessed from outside it, this arrangement is the wrong shape for the parts of the system that touch that data, and that is a policy decision rather than an obstacle to argue with.

If procurement requires a locally registered supplier, resolve that before anybody scopes anything.

If the customer-facing language is Arabic and nobody on your side can own the copy, wait until somebody can, because that gap cannot be closed by the supplier.

And if the work genuinely needs somebody in the room in Riyadh, hire for that locally and use a remote team for the parts that do not need a body in the building.

Common questions

How many working days do we actually share with a team in Pakistan?

Four. Monday to Thursday both countries are working and the only difference is two hours, since Riyadh is UTC+3 and Karachi UTC+5 with no daylight saving on either side. Sunday is a Saudi working day and a Pakistani weekend. Friday is the reverse. A European supplier loses the same two days, and starts its day when Riyadh is already at eleven.

What happens on Sunday, when Saudi Arabia works and Pakistan does not?

Nothing good, unless it is arranged in advance. Without cover, a Sunday question waits until Monday and you lose the first day of your week. The workable answer is a named person covering a stated Sunday window in Saudi time, with the day taken back later, written into the arrangement. Sunday cover means answering, unblocking and escalating. It does not mean building or deploying.

Does the Saudi PDPL stop us using a supplier outside the Kingdom?

Not on its own, and your adviser should confirm the detail for your situation. The law came into force in September 2023 with the grace period ending in September 2024, and a separate regulation covers transfers outside the Kingdom. No adequacy list has been published, so a transfer abroad is expected to rest on an approved mechanism such as standard contractual clauses. The problem is an undocumented transfer, not a foreign supplier.

Can Wobble deliver in Arabic?

No. Wobble works in English and Urdu. English-language internal systems are within scope and Wobble can be answerable for them. An Arabic customer-facing agent needs a person who reads Arabic reviewing every template, fallback and escalation before launch and after every change, which means either your own Arabic speaker or a contracted local partner owns that work.

Does WhatsApp calling work in Saudi Arabia?

Generally yes. The Kingdom permitted voice calling over internet applications in 2017, which is not the position on UAE networks. A Saudi build therefore has a real choice between a telephone number and an internet calling channel, and the answer should come from where last month's enquiries actually arrived. Availability is a regulator's decision, so verify it with your own operator.

Does Wobble have Saudi clients?

No. The published portfolio covers Pakistan, the United States, Australia, Germany and Mexico, with nothing in the Gulf. With no local proof available, the useful things to ask for are a reference from a market with the same shape of difficulty, a first engagement small enough that a bad outcome is affordable, and a written exit that leaves the system in your own accounts.