Saudi Arabia
Sunbeam is based in Lucknow, India. We work remotely with companies in Riyadh and elsewhere in Saudi Arabia that want an engineering partner for a website, an internal system, an automation or a knowledge tool. We do not have an office in the Kingdom, and we do not operate a Saudi legal entity. Commercial terms are agreed in writing with the company that hires us.
Served remotely from Lucknow. Riyadh is 2 hours 30 minutes behind India. No Saudi office.
The market
Riyadh is the capital and the centre of government and large corporate headquarters. Jeddah remains the main commercial port city on the Red Sea. The Eastern Province holds much of the energy and industrial economy. Across those places, private companies are under real pressure to run more of the business digitally: customer portals, internal operating systems, and cleaner hand-offs between branches. Vision 2030 is the public programme behind a lot of that expectation. We are not a registered vendor to that programme. We are a studio you can hire for a specific system.
The fit is a company that already knows the operation and wants it built carefully: a family group professionalising how branches report, a services firm that has outgrown a shared inbox, a product team that wants a partner in India for a defined slice. English is our delivery language. If customers need Arabic, we can engineer right-to-left layout and a language switch. The Arabic copy, and the review of that copy, need to come from your side.
We are the wrong partner if you need a team on the ground in Riyadh, a local commercial registration, or Arabic-speaking project management. Say that early and we will say so too.
Time overlap
Saudi Arabia uses Arabia Standard Time, UTC+3, with no daylight saving. India uses India Standard Time, UTC+5:30, also with no daylight saving. The difference is fixed: India is 2 hours 30 minutes ahead.
A practical shared block is 11:30 to 18:30 in Lucknow, which is 9:00 to 16:00 in Riyadh. That covers a Riyadh morning and early afternoon without asking the India team to work through the night. Friday remains an important prayer day in the Kingdom; the official weekend is Saturday and Sunday, which matches our weekend. We schedule live work on the days your team is actually available and keep the overlap for decisions.
Scope, design approval and anything that would block the next day belong in the overlap. Status can be read beforehand.
Questions that appear after 16:00 in Riyadh are answered in writing and picked up next morning, rather than by stretching the call late into the India evening.
Remote delivery
You get one studio, a named way of working, and software that lives in accounts you control. We agree the hosting region and the access model before build, because where data sits is a business decision in the Kingdom, not an afterthought.
We ask where the application and its data should live, who administers the cloud account, and which people may see production. Your advisers interpret the Saudi Personal Data Protection Law. We implement the technical constraints they give us. We do not give legal advice.
Calls, tickets and specifications are in English. Arabic interfaces are a layout and content problem we can build, with your reviewers accepting the copy.
Name one person who can accept a product decision. Remote work across a 2 hour 30 minute gap fails when approval is spread across a group that never meets the overlap together.
Services that fit
Branch operations, customer portals and the knowledge a distributed company keeps losing are the usual reasons to hire us. A marketing site is in scope when it is part of that same customer journey.
Corporate and product sites, and customer-facing web apps, structured so an Arabic and English experience can exist without two unrelated codebases. Content remains your responsibility. We are responsible for the system that presents it.
Portals, CRMs and internal tools for groups that need one view of a customer, a job or a branch. We design the roles explicitly. A headquarters user and a branch user rarely need the same screen.
Handoffs between the tools you already license, reminders, and document intake are the practical automations. AI is introduced where a draft or a classification saves time and a person still approves anything customer-facing or financial.
Multi-branch companies accumulate procedures that no new manager can find. A retrieval tool over approved documents, with citations back to the source, is the version we will build. An open-ended chatbot trained on a shared drive is the version we will argue against.
Lucknow is the studio. These services are available to clients here and anywhere else we work.
Local questions
No. We serve Saudi teams remotely from Lucknow, India. We do not claim a Saudi commercial registration.
India is 2 hours 30 minutes ahead of Saudi Arabia, and neither country uses daylight saving. 11:30 to 18:30 in Lucknow is 9:00 to 16:00 in Riyadh. That is the block we use for live decisions.
Yes. We can implement right-to-left layout and language switching. Your team supplies and reviews the Arabic copy. Our working language for delivery is English.
We agree hosting, ownership of the cloud account and access rules before build. Your counsel interprets the Saudi Personal Data Protection Law. We implement those technical constraints. We are not a law firm.
Customer portals, internal operating systems, websites tied to a real enquiry path, automation between tools you already use, and knowledge tools grounded in documents you maintain.
We agree scope, assumptions and responsibilities in writing with the organisation that is hiring us. There is no local entity in the Kingdom on our side.
Other places
Remote delivery for Dubai and the wider UAE. The time difference is 1 hour 30 minutes, so most of the working day overlaps.
A Lucknow studio for Indian companies outside our city pages, and for overseas teams looking for a software development partner in India.
Remote product and systems work for UK teams. The live window is a UK morning and a Lucknow afternoon. No UK office.
Remote engineering for US product and operations teams. East Coast has a short live window. Pacific time is an async relationship.
Tell us who is affected and what a better month would look like. We will recommend a practical next step.