Software for Saudi businesses, built on your clock
We are an engineering team in Giza, Egypt, working with companies across Saudi Arabia. There is no Riyadh office — there is a team that speaks your language, keeps your working hours, and builds Arabic-first because that is how we build for ourselves.
Distance is a real cost. One hour is not distance
Saudi companies outsourcing software usually choose between a local firm at local rates and an offshore team several time zones away, where a question asked in the morning is answered tomorrow and Arabic content comes back needing rewriting.
Cairo is never more than an hour from Riyadh — the same clock from late April to late October, an hour behind it through the winter. A 10am call your time is 10am or 9am ours, and the working week overlaps almost entirely, including the shift around Ramadan. Questions get answered the same day because the day is the same day.
The language point matters more than it sounds. Arabic is not a translation layer we buy in — the product we run ships in Arabic and English with full right-to-left layout, and our own team writes the Arabic. You are not paying us to learn your market’s first language.
What working with us actually looks like
Every item here is something we built and still run ourselves — not a service line we have only read about.
On Riyadh time, or an hour behind it
We keep the same Sunday-to-Thursday week you do, overlapping for effectively the whole working day, with the Ramadan schedule shift already a normal part of our year rather than a surprise.
Arabic written, not translated
Interface copy, documentation and support content written by native speakers. The difference between written and translated Arabic is obvious to your customers even when it is invisible in a specification.
Right-to-left as the default case
Mirrored layouts, navigation, icons and typography, Arabic plural rules and number formatting — solved on our own product first, so it is ordinary work rather than a change request.
E-invoicing taken seriously
Any system that issues invoices in Saudi Arabia has to account for ZATCA e-invoicing requirements. We treat that as a scoped requirement with its own data model from the first design session — and we will say plainly that our own product bills in Egypt, so this is something we would build for you rather than something we can show you running.
Built for the digitisation push
Most of what Saudi SMEs are replacing right now is a manual process or a spreadsheet. That is precisely the work we do: model the real process, replace the painful part first, keep the numbers auditable.
Local payment reality
Payment habits in Saudi Arabia are not the European default — mada and Apple Pay carry the checkout, on a phone, in Arabic. We have built and still run a card-and-wallet checkout end to end (gateway integration, signed callbacks, retries, reconciliation), and we integrate the rails your provider supports rather than assuming a Stripe-shaped world.
Straightforward contracting
Fixed written scope, milestone invoicing, and code in your repository from the first commit. Cross-border engagement without the paperwork becoming the project.
Everything ends up yours
Source, infrastructure, accounts and runbooks in your ownership. Nothing about the handover leaves you needing us.
How we start with a Saudi client
The same sequence on every engagement, whatever the stack.
1. A call in your hours
Arabic or English, whichever you prefer. We listen to the problem rather than presenting a deck.
2. A written scope
What we understood, what we would build first, what we would leave out, and what it would take. Free, and yours to keep even if you take it elsewhere.
3. Build with you watching
Your repository, an environment you can open, and a weekly rhythm in your time zone.
Straight answers
The questions that actually come up on a first call.
No. We are based in Giza, Egypt, and work with Saudi clients remotely. We would rather be plain about that than claim a presence you would discover was a mailbox. What we do have is the same working week, a one-hour time difference, and native Arabic.
Yes. We invoice cross-border on milestone terms and can work with your finance team on whatever documentation your side requires.
We build for the requirements your business is subject to — e-invoicing being the most common — and we will tell you plainly where you need advice from a local accountant or lawyer rather than from your software team. We do not present ourselves as a compliance authority.
For a substantial engagement, yes, we travel. For most projects video works better and costs you less, and that is how we would expect to run yours from start to finish.
Building something for the Saudi market?
Tell us what you need. You will get an answer the same working day, and a written scope before anyone talks about a contract.
Every project starts with a scoping conversation and a written estimate before any code is written. No retainer required to talk.