Choosing an HR system for SMBs in the Gulf.

The questions that matter most for MENA SMBs are different from those a US or European buyer would ask. Bilingual support, local compliance, mobile-first usage, pricing transparency, and data residency are where vendors built outside the region fall short — and where the cost of choosing wrong shows up six months into the rollout.

Question 1: Is Arabic native or translated? Ask the vendor to show you a salary certificate template generated in Arabic from scratch. If they can't, or if the Arabic comes out as awkward machine translation, that's your answer. Native Arabic means the templates are composed in Arabic by Arabic speakers, not run through a translation API.

Question 2: How do you handle Hijri dates? Ramadan, Hajj leave, religious holidays — these all live on the Hijri calendar. A system that only shows Gregorian dates makes HR translate dates in their head. Ask to see a leave request for Hajj on the system; the date picker should default to Hijri.

Question 3: What labour-law defaults come pre-configured? Jordan's 14-day annual leave, Saudi's 21-day, the UAE's 30-day after one year, maternity weeks, SSC rates, EOS calculations — these should be in the system out of the box. If the vendor says "we'll work with you to configure those," expect three months of consulting fees before you can run payroll.

Question 4: What does the mobile app actually do? Most employees never log into the web app. Ask for an iOS and Android app store link and try the app yourself. Can you clock in? Request leave? See your payslip? Push notifications? If the mobile app is a hidden screen embedded in a webview, your field teams will not use it.

Question 5: How is pricing presented? Vendors who hide all prices behind "contact sales" are signaling that the price is negotiable based on how desperate you look. The vendors most likely to give you a fair deal are the ones with a public pricing page. Per-employee-per-month in your local currency is the gold standard; per-active-user without a public number is the warning sign.

Question 6: Where is the data stored? "Cloud" is not a region. Ask: AWS, GCP, Azure, or something else? Which region — Bahrain, Frankfurt, Singapore, somewhere in the US? Can you choose? If the answer is "our default is the US," your IT team will struggle to approve procurement on data residency grounds in 2026.

Question 7: Can you import existing employees in bulk? Ask the vendor to show a 1,000-row CSV import live. Time it. If it takes more than 10 minutes (including error handling), expect the implementation period to be measured in months. Bulk import is the moat between a 2-week rollout and a 6-month one.

Question 8: What's the audit log story? Compliance reviews need a record of every read, write, and permission change. Ask: can I export the audit log as CSV? How long is it retained? Can I see who accessed an employee's salary record last Tuesday? If the answer is vague, your compliance team will not approve.

Question 9: How does SSO work? If you have Okta, Azure AD, or Google Workspace already, ask for SAML or OIDC support and which plan tier includes it. If SSO is a Scale-only feature and you're a 100-person company, factor that into the decision.

Question 10: What's the upgrade path if we double in size? Some HR systems scale beautifully from 50 to 500 employees; others fall over at 200. Ask: do you have customers at 500+ employees? Can I talk to one? What changes operationally when we cross 500? The vendors with confident answers have done it; the vendors without have not.