Budapest, Hungary
AI development for Budapest teams, handed over in writing
One shop, Vancouver, British Columbia. Budapest sits on the other side of a full day, so nothing about this engagement runs on meetings. It runs on written handoffs, logged decisions and review that happens while the other side is asleep.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Budapest, Hungary
- your clock
- UTC+01:00 (Europe/Budapest)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Budapest
No shared working day, so the loop is written
Budapest 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.
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 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 Budapest. 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 Budapest buyers usually bring us
The record for Budapest lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
automotive
Supplier portals, warranty systems and dealer software rarely offer a clean API, so integrations either get validated against real traffic or they are decoration.
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
business services
The people doing the work know where the time goes. Teaching them to drive the tools on their own files beats a platform rollout nobody asked for.
The written notes stay with the team, and they are written to be edited rather than filed.
Closest service line: Training and enablement
Contracts, currency and where the data sits
Invoices are in euros or US dollars. 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.
The rest is the same everywhere: we scope it, we build a thin slice against your real data, and we hand back something your own team can maintain. No retainer you cannot cancel and no seat licences.
The five lines we sell
Same five lines everywhere, Budapest 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 of Europe, all of it worked remotely from Vancouver.
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.