Harju, Estonia
AI development for Tallinn teams, handed over in writing
We build AI products from Vancouver, British Columbia, and we work with Tallinn 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
- Tallinn, Estonia
- your clock
- UTC+02:00 (Europe/Tallinn)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Tallinn
No shared working day, so the loop is written
Tallinn 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.
The honest version of this is a selling point. You get a full uninterrupted Vancouver day of work delivered as a written handoff, and we get your review waiting for us in the morning. Two shifts a day, no overtime.
- Everything built during our day lands in one written note before we close the laptop. No status meeting stands in for it.
- Your morning starts with that note and a set of pull requests to review, which is a better start than a calendar invitation.
- Every decision worth arguing about is written down where the code is, with the reasoning and the date attached.
- Questions come with a recommendation, because a question that needs a reply before work continues costs a full day here.
One live call a week, and it is scheduled honestly: 07:00 in Vancouver is 17:00 in Tallinn. 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 Tallinn buyers usually bring us
The record for Tallinn lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
digital government
Public services run on statute, policy and forms. Retrieval that quotes the rule and links the form is the only version a citizen-facing tool can ship.
The golden-question set is the deliverable nobody thinks to ask for, and it is the only way to show that a change helped.
Closest service line: Knowledge bases and retrieval
financial technology
Core systems, ledgers and payment rails each carry their own auth, pagination and rate limits, and none of it survives being described in a prompt.
We work embedded with your team, or with your customer teams, and the unit of delivery is a deployment rather than a document.
Closest service line: Forward-deployed engineering
Contracts, currency and where the data sits
Invoices are in euros. GDPR makes storage location a design question rather than a footnote, so the index, the logs and the model calls get pinned to European regions where your provider offers them, and that is settled in week one. Estonian buyers tend to have the answer already, which shortens the conversation.
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 Tallinn work, you get told that in the first reply rather than after a proposal.
The five lines we sell
Same five lines everywhere, Tallinn 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 Europe
Each one has its own page, its own overlap arithmetic and its own industries.
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.