San Jose, Costa Rica
AI development for San Jose teams, on your working day
The shop is in Vancouver, British Columbia, and it is one person deep. San Jose clients are worked with remotely, on a schedule that happens to line up: 6 hours of every working day sit inside both calendars at once.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- San Jose, Costa Rica
- your clock
- UTC-06:00 (America/Costa_Rica)
- overlap
- 6 hours a day, 09:00-15:00 in Vancouver
- presence
- remote only, no office in San Jose
6 hours of your day, every working day
San Jose runs 2 hours ahead of Vancouver. On a normal working day the two calendars overlap from 09:00 to 15:00 Vancouver time, which is 11:00 to 17:00 where you are.
A window that size means questions get answered while they still matter. Nobody sits on a blocker overnight, and a bad assumption gets caught in the hour it was made rather than in the following sprint.
The parts that still get written down are written down anyway: acceptance criteria, the decision log, and what changed in each weekly increment. A shared clock is not an excuse for an undocumented project.
What San Jose buyers usually bring us
The record for San Jose lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
medical devices
Design history files and regulatory submissions have to be traceable end to end, so retrieval carries the document identifier and the revision.
Hybrid search beats embeddings alone in nearly every corpus we have opened, and metadata filters behave as hard constraints or they are not filters.
Closest service line: Knowledge bases and retrieval
shared services
Centralized teams do the same task thousands of times, which makes them the best place to teach a practice and measure whether it held.
People ship real changes during the session, which is the only version of this that changes behaviour once we leave.
Closest service line: Training and enablement
Contracts, currency and where the data sits
Invoices are in US dollars. The engagement is remote, the contract is in English, and the working day lines up closely enough to keep decisions same-day.
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, San Jose 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 North America
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.