District of Columbia (DC), United States
AI development for Washington teams, inside your afternoon
We are in Vancouver, British Columbia. You are in Washington. Nobody from this shop is, and nobody pretends to be. The two working days touch for 5 hours, and that window is spent on decisions rather than on status.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Washington, 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 Washington
What fits in a 5-hour window
The overlap is real and it is bounded. Washington 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.
What we do not do is stretch that window by pretending either side works longer than it does. It is a fixed budget of shared hours a week, and it gets spent on purpose.
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 Washington buyers usually bring us
The record for Washington lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
government contracting
Solicitations, past performance and compliance matrices repeat. Retrieval over your own past submissions cuts the writing, not the review.
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
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.
We prove one wedge and then widen it. Rewriting the whole practice on day one is how these efforts die.
Closest service line: Codebase and team optimization
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.
The rest is the same everywhere: we scope it, we build a thin slice against your real data, and we hand back something your own team can maintain. No retainer you cannot cancel and no seat licences.
The five lines we sell
Same five lines everywhere, Washington 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
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.