Virginia (VA), United States
AI development for Richmond teams, inside your afternoon
We are an AI development agency based in Vancouver, British Columbia. Richmond clients get a remote engagement with a real, bounded overlap: 5 hours a day when both sides are awake and working. Everything that does not fit in it moves to writing, deliberately.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Richmond, 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 Richmond
What fits in a 5-hour window
The overlap is real and it is bounded. Richmond 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.
We spend that window on the things that are expensive in writing. Scope calls, eval walkthroughs, and the awkward conversation about what to cut. Everything else moves to text 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 Richmond buyers usually bring us
The record for Richmond lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
financial services
Research, filings and internal policy are the corpus. Hybrid search with metadata filters as hard constraints, plus span citations, or it does not ship.
Chunking follows the structure of the document instead of a character count, which is the whole difference between a useful index and an expensive one.
Closest service line: Knowledge bases and retrieval
logistics
Carrier APIs, warehouse systems and customer portals all break differently under load, which is why the integration work is the project.
We work embedded with your team, or with your customer teams, and the unit of delivery is a deployment rather than a document.
Closest service line: Forward-deployed engineering
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, Richmond 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 rather than a job spec. You get an answer on scope, timeline and whether we are the right shop, written by the person who would do the work.