Rio de Janeiro (RJ), Brazil
AI development for Rio de Janeiro teams, inside your afternoon
Magic Ship is an AI development agency in Vancouver, British Columbia. Between here and Rio de Janeiro there are 3 shared working hours a day. The engagement is designed against that number rather than against an assumption that everyone is online together.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Rio de Janeiro, Brazil
- your clock
- UTC-03:00 (America/Sao_Paulo)
- overlap
- 3 hours a day, 09:00-12:00 in Vancouver
- presence
- remote only, no office in Rio de Janeiro
What fits in a 3-hour window
The overlap is real and it is bounded. Rio de Janeiro sits 5 hours ahead of Vancouver, so the shared part of the day runs 09:00 to 12:00 our time and 14:00 to 17:00 yours.
The window is best spent where being live actually helps: a design argument, an eval review, a scope cut. Progress reporting is a document, and a document does not need both of us awake.
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 Rio de Janeiro buyers usually bring us
The record for Rio de Janeiro lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
offshore energy
Well files, inspection reports and vendor documentation run to millions of pages, and the retrieval design has to pin an answer to a well and a date.
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
tourism
Availability, pricing and local knowledge have to come from your systems, because a model that improvises an opening time creates a support ticket.
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. Cross-border payments from Brazil take longer than they should, so invoice dates are set with that in mind.
The commercial part stays deliberately boring. Fixed acceptance criteria per increment, weekly shipping, and a written record of every decision. Nothing about working from Vancouver instead of Rio de Janeiro changes what you are buying.
The five lines we sell
Same five lines everywhere, Rio de Janeiro 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 South America
Where else the same work happens in South America, with the numbers redone per market.
Start a project
Say what you are trying to build and what has already been tried. The reply is from a senior engineer, and it will tell you if the shape of the work is wrong before it tells you anything else.