Ireland, Ireland
AI development for Cork teams, handed over in writing
Magic Ship is an AI development agency in Vancouver, British Columbia, with no presence in Cork 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
- Cork, Ireland
- your clock
- UTC+00:00 (Europe/Dublin)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Cork
No shared working day, so the loop is written
Cork 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.
Treated properly it is the better arrangement. Nobody blocks on a meeting, every decision exists as text with a date on it, and the work moves while the other side sleeps instead of while the other side waits.
- 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 Cork. 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 Cork buyers usually bring us
The record for Cork lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
pharmaceuticals
Regulatory documents and study reports have strict structure and strict traceability, so parsing that structure is the bulk of the schedule.
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
medical devices
Design history files and regulatory submissions have to be traceable end to end, so retrieval carries the document identifier and the revision.
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
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.
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, Cork 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
Where else the same work happens in Europe, with the numbers redone per market.
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.