A remote studio for Riyadh and Jeddah teams that need software in the repo.

Most KSA briefs we see are not “make us a Dubai clone.” They are Arabic-first enterprises in Riyadh or Jeddah that still run English for engineering, plus a WhatsApp layer the vendor ignored. Vision 2030 slides do not help. A written scope for one workflow does.

Riyadh buyers often sit in large groups or giga-adjacent vendors. Jeddah and Dammam briefs look more like operators who need an admin, a CRM, or a support bot that survives a Sunday queue. We take the second kind more often. If you need a 200-person on-site crew in KAFD, we are the wrong call.

KSA PDPL is not UAE PDPL. We write a data map: hosting region, logs, export, and who can replay a transcript. We do not move production data onto a laptop to go faster. If your group IT will only approve a named cloud in-kingdom, say that on the call before we quote.

Money is SAR and 15% VAT for most commercial work. The product UI may still show SAR, AED, or USD depending on who pays. We treat currency and invoices as requirements, not a later “localization sprint.” The week is Sunday–Thursday. GST overlap covers a Riyadh afternoon without a 10pm standup.

Arabic is the customer language. English is how we write tickets and code. We reserve RTL, type, and overflow. We will not auto-translate a privacy notice or a brand line. If the tender requires native Arabic authorship, we will say no.

Services that show up repeatedly: WhatsApp-official chat, RAG on policy PDFs, bilingual-ready UI, auth that survives group SSO, and MVPs for teams around Hub71’s neighbors who also operate in KSA. There is no Tadawul execution product unless you bring venue docs — we do not invent a local broker story.