South Carolina (SC), United States
AI development for Charleston teams, inside your afternoon
The shop sits in Vancouver, British Columbia, and works with Charleston 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
- Charleston, 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 Charleston
What fits in a 5-hour window
The overlap is real and it is bounded. Charleston 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 Charleston buyers usually bring us
The record for Charleston lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
shipping
Vessel systems, port calls and documentation flows each need their own integration, built against live data and real timeouts.
Reconciliation and idempotency are designed in at the start, because retrofitting them after the first duplicate transaction is expensive.
Closest service line: Forward-deployed engineering
aerospace
Certification evidence has to trace to a document revision, so retrieval returns the clause and the revision it came from rather than a confident paraphrase.
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
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, Charleston 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
More of United States, all of it worked remotely from Vancouver.
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.