Kentucky (KY), United States
AI development for Louisville teams, inside your afternoon
The shop sits in Vancouver, British Columbia, and works with Louisville 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
- Louisville, United States
- your clock
- UTC-05:00 (America/Kentucky/Louisville)
- overlap
- 5 hours a day, 09:00-14:00 in Vancouver
- presence
- remote only, no office in Louisville
What fits in a 5-hour window
The overlap is real and it is bounded. Louisville 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 Louisville buyers usually bring us
The record for Louisville lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
air cargo
Booking, tracking and customs systems each speak their own dialect, and the job is a typed tool per dialect with an explicit contract and real retry behaviour.
Integrations are validated against live traffic: auth, pagination, rate limits, retries, and the failure modes that only surface under real load.
Closest service line: Forward-deployed engineering
bourbon distilling
Barrel inventory, warehouse position and blend history are the real dataset, and an agent that reads them is more use than one that writes tasting notes.
The first slice is thin and runs end to end: one real workflow, one real data source, and an agent with tools that change something rather than describe it.
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.
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, Louisville 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.