Community of Madrid (MD), Spain
AI development for Madrid teams, handed over in writing
Magic Ship is an AI development agency in Vancouver, British Columbia. Madrid and Vancouver share no working hours at all, and that is stated up front because it changes how the work runs: written handoff at the end of each side's day, a loop that turns once every twenty-four hours, and nobody waiting on a meeting.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Madrid, Spain
- your clock
- UTC+01:00 (Europe/Madrid)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Madrid
No shared working day, so the loop is written
Madrid 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.
It also produces a better record than a colocated project would. Everything of consequence exists as written text with a date on it, because writing is the only channel available.
- 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 Madrid. 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 Madrid buyers usually bring us
The record for Madrid 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.
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
telecommunications
Network inventory, provisioning and billing systems are the integration surface, and each one has retry semantics that a prompt cannot express.
Integrations are validated against live traffic: auth, pagination, rate limits, retries, and the failure modes that only surface under real load.
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.
Everything downstream of that is deliberately unremarkable. Fixed acceptance criteria, weekly shipping, a written decision log, and a first reply that tells you if Madrid work of this shape is not something we should take.
The five lines we sell
Same five lines everywhere, Madrid 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
Say what you are trying to build and what has already been tried. The reply is from a senior engineer, and it will tell you if the shape of the work is wrong before it tells you anything else.