Sia Partners · Senior AI & Data Product Manager, GCC Lead · 2023 to 2025
Transforming enterprise GenAI into a sovereign-ready platform designed for regulated GCC clients.
Led the GCC market strategy for Sia Agents, turning data residency, Arabic production readiness, ISO 27001 certification, and a low-risk pilot model into a repeatable adoption path for regulated buyers.
Executive Snapshot
- Sia developed Sia Agents, an enterprise GenAI platform for regulated and sovereign-backed clients. In the GCC, regulated buyers required data sovereignty, high-quality Arabic support, and compliance readiness before considering adoption.
- Early pilots revealed critical gaps, including weak Arabic parsing, reliability issues with answers, and concerns from prospects about data leaving the territory.
- I managed the GCC market for the platform, led pilots, developed the regional roadmap, and guided the core team to address client-specific requirements.
- I positioned compliance and data residency as commercial differentiators rather than technical requirements, and established a free pilot program that eliminated data risk for skeptical buyers.
- This approach resulted in a repeatable GCC adoption model, including over 10 pilots across four regulated sectors, an initial cohort of production clients, ISO 27001 certification, and AWS Marketplace listing.
The Challenge
Sia launched SiaGPT (later Sia Agents) as an enterprise GenAI platform with multi-LLM chat, document retrieval, and agentic workflows. In the GCC, the primary challenge was not technical readiness but establishing buyer trust.
Early pilots revealed gaps such as poor handling of Arabic documents, fabrication even with citations, and consistent concerns from prospects about data location. Strong demonstrations were insufficient to address these concerns with regulated buyers.
The constraints were structural: data sovereignty requirements for most sovereign clients, a lengthy government procurement cycle, Arabic quality standards matching English on real documents, and a globally distributed core team with competing regional priorities.
My Mandate
- Oversaw all Sia Agents GCC activities, both directly and by supporting other teams in market development.
- Led pilots across regulated sectors, including mobility, energy, public sector, and financial services.
- Developed the regional roadmap based on client feedback and influenced core team priorities.
- Positioned ISO 27001, data residency, and Arabic quality as key commercial market entry points.
- Bridged the gap between a globally focused product team and locally demanding regulated buyers.
What I Changed
Positioned data residency as the commercial entry point.
Leveraged the G42 and Microsoft partnership to enable LLM hosting within the UAE, incorporating this into all commercial proposals. Educated prospects on data residency implications and offered a free trial using publicly shareable documents, removing the primary barrier before contract commitment.
Established Arabic support as a mandatory roadmap requirement.
Early versions had poor Arabic parsing, leading to right-to-left parsing errors in client documents. I collected evidence, documented reproducible failures, and advocated for Arabic-first models such as Falcon, Noor, and Jais.
Structured the pilot process to reduce adoption risk.
The free pilot, limited to publicly shareable documents, allowed regulated buyers to validate the platform without exposing their data. This low-risk approach converted skeptical prospects who would not have engaged under standard terms.
Positioned ISO 27001 certification and AWS Marketplace listing as market entry requirements rather than overhead.
Recognizing that most GCC clients required ISO 27001 for procurement, I raised it early, initiated discussions with AWS, and ensured it was prioritized on the roadmap before it became a barrier.
Key Decisions and Tradeoffs
Data residency as the market entry point.
The G42 and Microsoft partnership enabled local LLM hosting within the UAE. I included this in proposals and paired it with a free pilot on safe documents, effectively reducing data risk to zero for the initial engagement.
Tradeoff: Slower, education-focused sales process versus a fast demo close.
Executive signal: I identified that trust, not capability, was the real barrier and addressed it structurally before seeking commitment.
Arabic as a market requirement, not a feature.
Arabic parsing failures appeared in initial client sessions. I documented these failures, established Arabic support as a strict requirement, and advocated for its inclusion in a globally prioritized roadmap.
Tradeoff: Ongoing pressure on the global roadmap.
Executive signal: I safeguarded GCC client credibility by treating localization as a prerequisite, not a feature.
ISO 27001 and AWS Marketplace as first-order priorities.
Most GCC procurement teams require ISO 27001. I raised this early to ensure it was included on the roadmap before it became a blocker, and initiated discussions with AWS Marketplace to expand enterprise reach.
Tradeoff: Reliance on certification timelines beyond my control.
Executive signal: I converted a compliance requirement into a commercial advantage before it became an obstacle.
Results and Validation
- 10+ pilots across four regulated sectors: mobility, energy, public sector, and financial services
- Converted the first cohort of GCC clients from low-risk pilots into production usage
- Improved Arabic document handling from unreliable parsing on real client files to production-acceptable performance
- ISO 27001 certification secured as a procurement enabler for regulated buyers
- AWS Marketplace listing, enabling enterprise procurement at an institutional scale
- Pilots showed clear time savings on knowledge and compliance workflows, especially document retrieval, policy Q&A, and compliance analysis
- Moved roughly one-third of pilots into long-term engagement discussions by the end of tenure
Client names are under NDA. ISO 27001 certification and AWS Marketplace listing are the public proof points.
What This Proves
This case demonstrates the ability to enter a market where trust is the primary commercial barrier, identify specific adoption gaps, restructure sales and pilot processes accordingly, and build a repeatable model that converts skeptical regulated buyers into production clients. The coordinated strategy for data residency, Arabic quality, and compliance readiness applies to any enterprise AI platform targeting GCC sovereign and regulated organizations.
Lessons Learned
- Trust is a commercial, not a technical, challenge. Despite strong platform capabilities, adoption was blocked by the lack of data assurance and language confidence.
- Localization is a prerequisite, not a feature. Arabic quality must match English on real client documents before the initial session concludes.
- Addressing procurement requirements early is a product leadership decision. Including ISO 27001 on the roadmap before it becomes a blocker demonstrates leadership; addressing it afterward is damage control.