Ohio (OH), United States
AI development for Cleveland teams, inside your afternoon
We are in Vancouver, British Columbia. You are in Cleveland. Nobody from this shop is, and nobody pretends to be. The two working days touch for 5 hours, and that window is spent on decisions rather than on status.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Cleveland, 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 Cleveland
What fits in a 5-hour window
The overlap is real and it is bounded. Cleveland 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 Cleveland buyers usually bring us
The record for Cleveland lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
health care
Clinical and administrative documents demand citation and access control at retrieval time, not a disclaimer at the bottom of the answer.
The golden-question set is the deliverable nobody thinks to ask for, and it is the only way to show that a change helped.
Closest service line: Knowledge bases and retrieval
manufacturing
Procedures, drawings and shift reports hold the answers. Getting them out is an ingestion problem far more often than it is a model problem.
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
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.
Beyond that, the shape of an engagement does not change with distance: a scoping call, a thin end-to-end slice, then weekly increments against acceptance criteria fixed in advance. If we are not the right shop for Cleveland work, you get told that in the first reply rather than after a proposal.
The five lines we sell
Same five lines everywhere, Cleveland 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.