Core Finding: A Four-Phase Deployment
Analysis indicates the international rollout cannot be a single project. It must be bifurcated into four distinct phases based on extreme differences in legal, financial, and technical complexity. Critical, non-negotiable blockers in several markets (Singapore, KSA, UAE, NZ) prevent an immediate, unified launch.
Critical, High-Priority Blockers
1. Legal Blocker (Singapore)
Requirement: Must have a local Unique Entity Number (UEN) to register an SMS Sender ID.
Block: Cannot send any SMS until a legal business entity is established in Singapore.
2. Infrastructure Blocker (KSA)
Requirement: Saudi law mandates data residency.
Block: Supabase has no KSA/MEA data region. Storing data elsewhere is a compliance violation.
3. Product Blocker (UAE & KSA)
Requirement: Local carriers are one-way SMS only and ban URLs in messages.
Block: All product workflows relying on 2-way SMS (e.g., "Reply YES to confirm") will fail.
4. Financial Blocker (New Zealand)
Requirement: A mandatory Dedicated Short Code is required for all A2P messaging.
Block: This incurs a $1,600 one-time setup fee and a 3-month commitment.
Recommended Phased Deployment Plan
UK & Canada
Low complexity, well-documented requirements, and no major financial or legal hurdles.
Australia & Ireland
Moderate complexity. Require mandatory registration with local regulators (ACMA, ComReg), introducing admin lead times.
New Zealand
Gated by a financial decision: leadership must approve the $1,600 setup fee. Procurement takes 6-8+ weeks.
Singapore, UAE, KSA
Not currently feasible. Moved to R&D / Legal track to solve core blockers (UEN, 1-way SMS, Data Residency).
SMS Per-Message Cost Analysis (USD)
The financial model must account for extreme volatility in variable costs. Sending a single SMS to the Middle East is over 25x more expensive than to Canada, fundamentally impacting unit economics.
Required Data Infrastructure Plan
A single global database is not compliant. Data must be segregated into new, region-specific Supabase projects to satisfy data residency laws like GDPR, PIPEDA, and PDPA.
- Canada: Deploy project to ca-central-1
- UK / Ireland: Deploy project to eu-west-2 (London) or eu-west-1 (Ireland)
- Australia / NZ: Deploy project to ap-southeast-2 (Sydney)
- Singapore: Deploy project to ap-southeast-1 (Singapore)
- KSA / UAE: CRITICAL GAP. No MEA region exists. Deployment to KSA is non-compliant.