South Carolina (SC), United States
AI development for Greenville teams, inside your afternoon
The shop sits in Vancouver, British Columbia, and works with Greenville 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
- Greenville, 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 Greenville
What fits in a 5-hour window
The overlap is real and it is bounded. Greenville 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 Greenville buyers usually bring us
The record for Greenville lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
automotive
Supplier portals, warranty systems and dealer software rarely offer a clean API, so integrations either get validated against real traffic or they are decoration.
Progress is counted in deployments rather than features, which is the only honest way to measure this kind of work.
Closest service line: Forward-deployed engineering
advanced manufacturing
Work instructions, tolerance specs and supplier drawings sit in scanned PDFs, so parsing and chunking decide whether a process engineer ever gets an answer back.
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
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.
Everything else is the same as it would be for a client down the street from us: scope, a thin slice in week one, then weekly increments you can stop at any time. The distance changes the schedule, not the contract.
The five lines we sell
Same five lines everywhere, Greenville 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
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.