Selling services to Gulf clients from Algeria

A Gulf client will buy from a supplier in Algeria when the work is clear and the risk feels small. What decides that is not the portfolio. It is whether the money can reach you without a detour, whether your Arabic reads like a person wrote it, and whether the distance feels managed rather than ignored.

What does a buyer who cannot visit actually check?

Three things, in the first conversation: can this person be reached, did they understand the brief, and what happens if it goes wrong. Nobody flies to Algiers to meet a developer, so the visit is replaced by a call, a scope and one small paid phase.

The call outweighs the email: the buyer is choosing someone they will chase for months. A person who answers, repeats the brief back and names a date is ahead of a cheaper quote that arrived as a PDF. Voice notes are ordinary business there; calling them unprofessional reads as distance.

The scope replaces the office visit: one page of what is included, what is not, what you need from them, and when each part lands. A buyer who cannot read what they are buying has only the price to compare, and price is the comparison you lose.

The paid phase replaces the contract they would have signed in person. A review, one screen, one integration — cheap for them, useful alone, and it shows how you work — the cheapest way to learn whether they pay.

Why does the working week keep slipping?

Because the weekend differs. Algeria works Sunday to Thursday, and so does most of the Gulf; the UAE runs Monday to Friday. A Thursday afternoon message from Dubai arrives when your week is already over.

The clocks add two to three hours, so a question sent at the end of your day is answered after their hours, and their reply waits for your tomorrow. Two exchanges consume two days without anyone being slow.

The fix is arithmetic, not effort. Answer inside their day and say which hours you answer in: "Sunday to Thursday, 9:00 to 17:00 Algiers time" is a promise a buyer can plan around. "Within 24 hours" sounds faster and never says whose.

Which Arabic do they write in?

Two Arabics, and confusing them is the failure this market punishes most.

The Arabic on your website is marketing Arabic: complete sentences, promotional verbs, a register nobody speaks. That is fine on a website. The Arabic in a client's thread is shorter and mixed with English — «عندنا ملاحظة على الصفحة، متى تقدر تعدّلها؟», then «الـ deadline», then a voice note. It drops case endings and stops mid-thought.

You do not need Gulf dialect. You need to stop writing like a brochure while the client writes like a colleague: plain Modern Standard Arabic, short sentences, their nouns instead of your adjectives, and the word they used. If they say «لوحة المتابعة», do not answer with «منصة تحليل الأداء».

Machine-translated prose is spotted immediately, and not by grammarians: pronoun agreement that drifts, sentences that open promisingly and end nowhere, calques like "comprehensive solutions" that nobody writes unprompted. If your Arabic is weak, write shorter and have a person read it aloud. And answer in the language you were written to.

How does the money actually get there?

This is where a good deal stops, and not for technical reasons. It is a set of questions with paperwork answers, each belonging to your bank and your accountant.

Which routes does your bank accept, in which currency, and what does it want alongside each? Which account receives the money, and does that change with the sender or the amount? What must the invoice contain at both ends? Who bears the transfer charge when an intermediary deducts a slice nobody quoted?

The client has a gate too. A Gulf company often pays through a finance portal and needs a supplier record or a purchase order before releasing anything. Ask before you quote: a supplier who cannot be registered cannot be paid, and the delay reads as your failure.

Currency, declaration and invoicing rules are for an accountant who knows your file and a bank that will process the payment, not for this page. Settle them before the first deliverable, while the amount is still small.

What convinces a buyer who will never see the office?

The items are boring and specific; what impresses locally rarely counts.

What the buyer checks	What answers it	What does not
Can I reach a person?	A named individual with a number that answers	A contact form and a "team"
Is this a real business?	An address matching the invoice and the site	A claim to be "global"
Have they done my thing?	A case study that names the constraint	Screenshots with no context

A named person converts a risk into a relationship. A real address comes second and must match the invoice, the footer and anything you sign; a post-office box alone reads as hiding. A case study comes third, and earns its place by naming the problem rather than the interface: "a wholesaler in Oran with three warehouses and one stock figure nobody trusted" reads as evidence, a carousel of screens is decoration.

How do you start, in order?

1. Ask for the buyer's supplier requirements and payment route before you send a price.
2. Write the scope as one page and paste it into the thread rather than attaching a file.
3. Take the first conversation by call or voice note, and repeat the brief back before answering it.
4. Quote in a currency the buyer holds, and state in writing who bears the transfer charge.
5. Cut the work so the first phase is small, paid and useful on its own.
6. Put your response window in their time zone, in writing.
7. Keep one thread per client, in the language they opened it in.

Where this goes wrong

The translated website. Impeccable portfolio, Arabic that reads like a manual, and the buyer stops imagining a long relationship.

The invisible overlap. A 24-hour promise, measured from nowhere, broken every Thursday.

Quoting in dinars. A price the buyer must convert puts the exchange rate into a conversation about the work.

The unannounced holiday. Vanishing for Eid without notice reads as unreliability; the buyer cannot know it was a public holiday here.

What this does not cover

No rates, no transfer costs, no market sizes, nothing about how long a deal takes. Everything touching currency, declaration, invoicing and tax is a question for an accountant and a bank, and the answer changes with the client's country as well as yours. It also assumes the buyer is a company with a finance department; an individual ordering a small site behaves like any individual buyer, and the risk moves to the first payment.

We build the systems these engagements produce — and the scope document a client across the Gulf can read without a call.