Indiana (IN), United States
AI development for Indianapolis teams, inside your afternoon
Magic Ship builds AI products from Vancouver, British Columbia. There is no office in Indianapolis, no local staff, and no local phone number. There is a 5-hour window each working day where decisions get made live, and a written record for the rest.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Indianapolis, United States
- your clock
- UTC-05:00 (America/Indiana/Indianapolis)
- overlap
- 5 hours a day, 09:00-14:00 in Vancouver
- presence
- remote only, no office in Indianapolis
What fits in a 5-hour window
The overlap is real and it is bounded. Indianapolis 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.
Use it for decisions, not status. Status is a document you can read at your own hour; a decision is the thing worth spending a live hour on, and there are only a few of those a week.
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 Indianapolis buyers usually bring us
The record for Indianapolis lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
pharmaceuticals
Regulatory documents and study reports have strict structure and strict traceability, so parsing that structure is the bulk of the schedule.
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
logistics
Carrier APIs, warehouse systems and customer portals all break differently under load, which is why the integration work is the project.
Every integration ships with its failure path written down: what retries, what alerts, and what a human is expected to look at.
Closest service line: Forward-deployed engineering
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.
Past that, the mechanics are ordinary. A scoping call, a written scope, weekly increments, and an invoice that matches what shipped. The one thing distance changes is when in your day the questions arrive.
The five lines we sell
Same five lines everywhere, Indianapolis 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 entries from the United States list, each written the same way as this one.
Start a project
Describe what is broken or what you want built. The reply comes from the engineer who would build it, and it covers scope, timeline and fit before anything else.