Rhode Island (RI), United States
AI development for Providence teams, inside your afternoon
Magic Ship builds AI products from Vancouver, British Columbia. There is no office in Providence, 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
- Providence, 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 Providence
What fits in a 5-hour window
The overlap is real and it is bounded. Providence 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.
Use it for decisions, not status. Status is a document you can read at your own hour; a decision is the thing worth spending a live hour on, and there are only a few of those a week.
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 Providence buyers usually bring us
The record for Providence lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
health care
Clinical and administrative documents demand citation and access control at retrieval time, not a disclaimer at the bottom of the answer.
Most retrieval failures are ingestion failures, so the early weeks go into parsing and chunking rather than into rewording a prompt.
Closest service line: Knowledge bases and retrieval
higher education
Faculty and staff need the failure modes as much as the workflows, so sessions run on their own courses and repos and end with a written practice they keep.
The written notes stay with the team, and they are written to be edited rather than filed.
Closest service line: Training and enablement
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, Providence 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
If you are comparing markets, these are the other United States 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.