North Carolina (NC), United States
AI development for Raleigh teams, inside your afternoon
The shop sits in Vancouver, British Columbia, and works with Raleigh 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
- Raleigh, 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 Raleigh
What fits in a 5-hour window
The overlap is real and it is bounded. Raleigh 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 Raleigh buyers usually bring us
The record for Raleigh lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
life sciences
Study documents, protocols and submissions have rigid structure, and honouring that structure at ingestion time is what makes retrieval accurate.
It starts with your documents and your own analysts writing the questions the system has to get right before anyone will trust it.
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.
A block of sessions across a few weeks beats one long day, because the practice needs real work in between sittings.
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.
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 Raleigh work, you get told that in the first reply rather than after a proposal.
The five lines we sell
Same five lines everywhere, Raleigh 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
Write down the problem in whatever form you have it. You get a straight answer about scope, timeline and whether this is work we should be doing at all.