Maryland (MD), United States
AI development for Baltimore teams, inside your afternoon
Magic Ship builds AI products from Vancouver, British Columbia. There is no office in Baltimore, no local staff, and no local phone number. There is a 5-hour window each working day where decisions get made live, and a written record for the rest.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Baltimore, United States
- your clock
- UTC-05:00 (America/New_York)
- overlap
- 5 hours a day, 09:00-14:00 in Vancouver
- presence
- remote only, no office in Baltimore
What fits in a 5-hour window
The overlap is real and it is bounded. Baltimore sits 3 hours ahead of Vancouver, so the shared part of the day runs 09:00 to 14:00 our time and 12:00 to 17:00 yours.
The window is best spent where being live actually helps: a design argument, an eval review, a scope cut. Progress reporting is a document, and a document does not need both of us awake.
What moves to writing is not a downgrade. A daily handoff note at the end of the Vancouver day, decisions logged when they are made, and review on the pull request itself means your morning starts with the answer rather than with a meeting invitation.
What Baltimore buyers usually bring us
The record for Baltimore lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
cybersecurity
Security teams want agent output they can review line by line, which means small diffs, checks the agent runs itself, and rules scoped per path.
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
health care
Clinical and administrative documents demand citation and access control at retrieval time, not a disclaimer at the bottom of the answer.
Hybrid search beats embeddings alone in nearly every corpus we have opened, and metadata filters behave as hard constraints or they are not filters.
Closest service line: Knowledge bases and retrieval
Contracts, currency and where the data sits
Invoices are in US dollars. A US buyer engaging a Canadian company is routine, and the form your accounts team will ask for is a W-8BEN-E, which we have ready before the first invoice.
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, Baltimore 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 United States
More entries from the United States list, each written the same way as this one.
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.