Ireland, Ireland
AI development for Dublin teams, handed over in writing
The desk is in Vancouver, British Columbia. Dublin is far enough around the world that our working days do not touch on the same date, which is a fact worth stating in the first paragraph rather than discovering in week two. The work is handed over in writing instead.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Dublin, Ireland
- your clock
- UTC+00:00 (Europe/Dublin)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Dublin
No shared working day, so the loop is written
Dublin is 8 hours ahead of Vancouver. When we start at 09:00 it is 17:00 on the same day for you, and when we stop at 17:00 it is 01:00 on the next day. On the same calendar date there is no hour where both sides are at work.
There is a real cost and it is worth naming: an answer to a blocking question can take a working day to reach you. We handle it by sending the proposed answer with the question, so silence means agreement rather than a lost day.
- The Vancouver day ends with a written summary: shipped, broken, blocked, and the one thing we need you to decide.
- That summary is waiting at 01:00 your time, alongside the diffs it refers to.
- The decision log lives in the repository rather than in a chat thread, so it is still readable a year later.
- Anything that would block us gets asked as a proposal you can approve in a sentence, not as an open question.
One live call a week, and it is scheduled honestly: 09:00 in Vancouver is 17:00 in Dublin. Neither side takes a bad hour for that one. The call simply lands on two different calendar dates, which is a scheduling detail rather than a hardship.
What Dublin buyers usually bring us
The record for Dublin lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
software headquarters
Big product organizations already have the tools. What they lack is a written practice and a repo shaped so the tools produce reviewable work.
The deliverable is committed to your repository. Context files, path-scoped rules, and checks an agent can run against its own output.
Closest service line: Codebase and team optimization
pharmaceuticals
Regulatory documents and study reports have strict structure and strict traceability, so parsing that structure is the bulk of the schedule.
Most retrieval failures are ingestion failures, so the early weeks go into parsing and chunking rather than into rewording a prompt.
Closest service line: Knowledge bases and retrieval
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.
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 Dublin work, you get told that in the first reply rather than after a proposal.
The five lines we sell
Same five lines everywhere, Dublin 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
Send the problem. If it is a fit, you get scope and a timeline. If it is not, you get told that in the first reply instead of after a discovery process.