Tel Aviv District, Israel
AI development for Tel Aviv teams, handed over in writing
We build AI products from Vancouver, British Columbia, and we work with Tel Aviv teams without a single shared working hour. No office there, no staff there. What replaces the shared day is a written handoff, decisions logged as they are made, and review that happens on your morning rather than in a call.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Tel Aviv, Israel
- your clock
- UTC+02:00 (Asia/Jerusalem)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Tel Aviv
No shared working day, so the loop is written
Tel Aviv is 10 hours ahead of Vancouver. When we start at 09:00 it is 19:00 on the same day for you, and when we stop at 17:00 it is 03:00 on the next day. On the same calendar date there is no hour where both sides are at work.
That is not an apology. A loop that turns once every twenty-four hours, in writing, is a faster way to build software than a calendar full of half-attended calls, and it forces the decisions into a form somebody can read six months later.
- A handoff note goes out at the end of every Vancouver working day: what shipped, what broke, and what needs a decision from you.
- You read it at 03:00, or whenever your day starts, and review the pull requests it points at.
- Decisions are logged as they are made, in the repository, so neither side has to reconstruct why something was done.
- A blocking question arrives with a proposed answer attached, so the default outcome is progress rather than a stalled day.
One live call a week, and it is scheduled honestly: 07:00 in Vancouver is 17:00 in Tel Aviv. That hour is outside our working day and inside yours. We take the awkward end of it, because it is our job to be reachable.
What Tel Aviv buyers usually bring us
The record for Tel Aviv lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
cybersecurity
Security teams want agent output they can review line by line, which means small diffs, checks the agent runs itself, and rules scoped per path.
Small diffs, explicit boundaries and locally runnable checks are what make agent output reviewable instead of merely plausible.
Closest service line: Codebase and team optimization
venture capital
Memos, data rooms and portfolio reporting are the corpus, and the value shows up when retrieval can hold one company and one round as a hard filter.
Recall gets measured before anybody comments on the wording, because a fluent answer drawn from the wrong passage is the worst outcome on offer.
Closest service line: Knowledge bases and retrieval
Contracts, currency and where the data sits
Invoices are in US dollars. Sunday is a working day for you and not for us, which we plan around rather than discover in week three.
Beyond that, the shape of an engagement does not change with distance: a scoping call, a thin end-to-end slice, then weekly increments against acceptance criteria fixed in advance. If we are not the right shop for Tel Aviv work, you get told that in the first reply rather than after a proposal.
The five lines we sell
Same five lines everywhere, Tel Aviv included. Most engagements are one of them, sometimes two.
- AI products, built end to end
- Knowledge bases and retrieval
- Codebase and team optimization
- Training and enablement
- Forward-deployed engineering
The languages, models and infrastructure underneath all five are listed on the Magic Ship stack page, with what each one is good for and where it is the wrong choice.
Other markets in Asia
Same treatment, different clocks, and in some cases a different answer.
Start a project
Write down the problem in whatever form you have it. You get a straight answer about scope, timeline and whether this is work we should be doing at all.