Lisbon, Portugal
AI development for Lisbon teams, handed over in writing
Magic Ship is one shop in Vancouver, British Columbia. Between Vancouver and Lisbon there is no same-day overlap to sell you, so the engagement is built the other way around: everything that matters is written down, and the day you start is the day after ours finished.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Lisbon, Portugal
- your clock
- UTC+00:00 (Europe/Lisbon)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Lisbon
No shared working day, so the loop is written
Lisbon 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.
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.
- 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 Lisbon. 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 Lisbon buyers usually bring us
The record for Lisbon lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
startups
Speed is the whole argument, so we build the thin slice first, wire the agent to real tools and real state, and let that shape the roadmap.
Week one puts something running in your environment against real state, because an agent that can only talk teaches nobody anything about the hard part.
Closest service line: AI products, built end to end
tourism
Availability, pricing and local knowledge have to come from your systems, because a model that improvises an opening time creates a support ticket.
The first slice is thin and runs end to end: one real workflow, one real data source, and an agent with tools that change something rather than describe it.
Closest service line: AI products, built end to end
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 Lisbon work of this shape is not something we should take.
The five lines we sell
Same five lines everywhere, Lisbon 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
If you are comparing markets, these are the other Europe entries in the record set.
Start a project
Tell us what you are trying to build. A senior engineer reads every message and answers on scope, timeline and fit. If your problem is not one we should take, that is the first thing you will hear.