Websites and products
Public sites, portals, SaaS products, directories, member systems, APIs, and internal tools built around a complete user task rather than a page count.
Work and capabilities
Build for the Lebanon operation, not a generic export.
The useful starting point is the workflow already in place: who uses it, what must stay working, where the data goes, and what changes for people in Lebanon.
Automation and integration
Connect CRM, identity, payments, documents, reporting, messaging, and operations with visible errors, safe retries, and a clear system of record.
Practical AI
Assistants, retrieval, classification, research, and workflow support with defined data access, human review, evaluation, and a fallback when the model is wrong.
Repair and modernization
Recover fragile systems, preserve useful data, replace risky dependencies, improve accessibility and performance, and leave a release path the owner can understand.
Country-specific acceptance
The Lebanon assumptions belong in the test plan.
Language, privacy behavior, commerce, accessibility, release timing, and support need named owners. These are the current issues to carry into discovery.
- Lebanon's electronic-transactions and personal-data rules, sector duties, consent, processors, transfers, security, retention, rights, and enforcement practice require local legal review.
- Currency, VAT, invoices, banking and payment availability, settlement, beneficial ownership, sanctions, and customer status require enhanced current diligence before contracting.
- Arabic and French require named reviewers; test RTL and mixed scripts, governorates, +961 numbers, currency presentation, mobile performance, and clear failure recovery.
Next step
Turn the Lebanon context into a workable brief.
The clearest scope starts with the actual Lebanon operation: people, access, content, transactions, deadlines, support, and acceptance.