North Carolina (NC), United States
AI development for Charlotte teams, inside your afternoon
We are an AI development agency based in Vancouver, British Columbia. Charlotte 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
- Charlotte, 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 Charlotte
What fits in a 5-hour window
The overlap is real and it is bounded. Charlotte 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 Charlotte buyers usually bring us
The record for Charlotte lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
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.
Answers cite the passage they came from. A retrieval system without span-level citation gets used twice and then quietly abandoned.
Closest service line: Knowledge bases and retrieval
energy
Operational data is high volume and low tolerance for a wrong answer, so the eval harness and the fallback behaviour get built before the interface.
The eval harness gets built beside the first feature, so week three can prove that week two did not quietly make the output worse.
Closest service line: AI products, built end to end
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 Charlotte work, you get told that in the first reply rather than after a proposal.
The five lines we sell
Same five lines everywhere, Charlotte 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.