Prince Edward Island (PE), Canada
AI development for Charlottetown teams, inside your afternoon
We are in Vancouver, British Columbia. You are in Charlottetown. Nobody from this shop is, and nobody pretends to be. The two working days touch for 4 hours, and that window is spent on decisions rather than on status.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Charlottetown, Canada
- your clock
- UTC-04:00 (America/Halifax)
- overlap
- 4 hours a day, 09:00-13:00 in Vancouver
- presence
- remote only, no office in Charlottetown
What fits in a 4-hour window
The overlap is real and it is bounded. Charlottetown sits 4 hours ahead of Vancouver, so the shared part of the day runs 09:00 to 13:00 our time and 13: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 Charlottetown buyers usually bring us
The record for Charlottetown lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
aerospace
Certification evidence has to trace to a document revision, so retrieval returns the clause and the revision it came from rather than a confident paraphrase.
Recall gets measured before anybody comments on the wording, because a fluent answer drawn from the wrong passage is the worst outcome on offer.
Closest service line: Knowledge bases and retrieval
bioscience
Assay results and protocol drafts want a tool layer over the lab systems, plus an eval suite a scientist trusts enough to stop double-checking every run.
The eval harness gets built beside the first feature, so week three can prove that week two did not quietly make the output worse.
Closest service line: AI products, built end to end
Contracts, currency and where the data sits
This is a domestic engagement. Invoices are in Canadian dollars, the contract is Canadian, and nothing crosses a border on the way to you or on the way back.
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, Charlottetown 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 Canada
Same treatment, different clocks, and in some cases a different answer.
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.