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 Israel 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 Israel.
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 Israel 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.
- Privacy Protection Law, regulations, database and security duties, processors, transfers, tracking, retention, access, and breach obligations need current project-specific review.
- ILS, VAT, invoices, customer status, service classification, payment providers, identity, accessibility, and sector requirements should be confirmed before implementation.
- Hebrew and Arabic require qualified reviewers and true RTL testing across navigation, mixed text, numbers, forms, tables, mobile layouts, and accessible error states.
Next step
Turn the Israel context into a workable brief.
A useful first conversation covers the users, existing systems, language responsibility, data, payments, timing, and the evidence that will count as done in Israel.