Vienna, Austria
AI development for Vienna teams, handed over in writing
Magic Ship is an AI development agency in Vancouver, British Columbia, with no presence in Vienna and no shared working hours with it. What that buys you is a full day of build time delivered as a written handoff, waiting when you sit down.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Vienna, Austria
- your clock
- UTC+01:00 (Europe/Vienna)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Vienna
No shared working day, so the loop is written
Vienna is 9 hours ahead of Vancouver. When we start at 09:00 it is 18:00 on the same day for you, and when we stop at 17:00 it is 02:00 on the next day. On the same calendar date there is no hour where both sides are at work.
Removing the shared hour removes the interruptions with it. A full Vancouver day of uninterrupted build time, handed over in writing, tends to move a project further than a day punctuated by four calls.
- 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 02: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: 08:00 in Vancouver is 17:00 in Vienna. 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 Vienna buyers usually bring us
The record for Vienna lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
banking
Policy documents, product terms and audit trails are the corpus, and an answer without a citation to the governing clause is worse than no answer at all.
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
international organizations
Reports, resolutions and country files span languages and decades. The design problem is filters that hold, not embedding choice.
It starts with your documents and your own analysts writing the questions the system has to get right before anyone will trust it.
Closest service line: Knowledge bases and retrieval
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.
Past that, the mechanics are ordinary. A scoping call, a written scope, weekly increments, and an invoice that matches what shipped. The one thing distance changes is when in your day the questions arrive.
The five lines we sell
Same five lines everywhere, Vienna 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
More entries from the Europe list, each written the same way as this one.
Start a project
Describe what is broken or what you want built. The reply comes from the engineer who would build it, and it covers scope, timeline and fit before anything else.