Delaware (DE), United States
AI development for Wilmington teams, inside your afternoon
The shop sits in Vancouver, British Columbia, and works with Wilmington teams at a distance. Your day and ours share 5 hours. That is enough for the conversations that need voices, and not enough to run a project on calls, which is fine.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Wilmington, 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 Wilmington
What fits in a 5-hour window
The overlap is real and it is bounded. Wilmington 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.
A partial overlap punishes projects that run on meetings and rewards ones that run on written acceptance criteria. We build for the second kind, which is how we would run it anyway.
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 Wilmington buyers usually bring us
The record for Wilmington lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
corporate law
Precedent banks and executed agreements only pay off with clause-level retrieval, span citations, and metadata filters that behave as hard constraints.
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
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.
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.
Beyond that, the shape of an engagement does not change with distance: a scoping call, a thin end-to-end slice, then weekly increments against acceptance criteria fixed in advance. If we are not the right shop for Wilmington work, you get told that in the first reply rather than after a proposal.
The five lines we sell
Same five lines everywhere, Wilmington 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
Same treatment, different clocks, and in some cases a different answer.
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.