Lebanon is usually seven hours ahead of Georgia, with seasonal clock changes.
Market brief
Put the Lebanon operating facts on the table.
This is a working brief, not a market-entry promise. Recheck it against the actual client, users, product, vendors, and launch date before treating any point as settled.
Arabic or French content by agreement; delivery in English
LBP and USD where lawful is the local currency reference. Contract currency, invoices, tax treatment, and settlement depend on the engagement.
Arabic and French require named reviewers; test RTL and mixed scripts, governorates, +961 numbers, currency presentation, mobile performance, and clear failure recovery.
Lebanon project decision record
| Decision | Evidence before build |
|---|---|
| Audience and language | Named audience, language owner, formats, accessibility, and support path |
| Data and vendors | Purpose, roles, hosting, transfer, retention, security, and incident owner |
| Commercial delivery | Customer, service, currency, tax adviser, invoice, payment, acceptance, and support |
Next step
Turn the Lebanon context into a workable brief.
Before a stack or schedule is chosen, identify who will use the system in Lebanon, who owns each decision, and which assumptions still need local confirmation.