Sao Paulo (SP), Brazil
AI development for Sao Paulo teams, inside your afternoon
Magic Ship is an AI development agency in Vancouver, British Columbia. Between here and Sao Paulo 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
- Sao Paulo, 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 Sao Paulo
What fits in a 3-hour window
The overlap is real and it is bounded. Sao Paulo 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.
Inside it: the standup, the demo, and any decision that needs two people to agree in real time. Outside it: the build, the review comments, and the written answer to the question you asked at the top of your day.
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 Sao Paulo buyers usually bring us
The record for Sao Paulo lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
banking
Policy documents, product terms and audit trails are the corpus, and an answer without a citation to the governing clause is worse than no answer at all.
Chunking follows the structure of the document instead of a character count, which is the whole difference between a useful index and an expensive one.
Closest service line: Knowledge bases and retrieval
financial technology
Core systems, ledgers and payment rails each carry their own auth, pagination and rate limits, and none of it survives being described in a prompt.
Recurring patterns get pushed back into your platform, so the next account receives a supported capability rather than another one-off.
Closest service line: Forward-deployed engineering
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.
Everything downstream of that is deliberately unremarkable. Fixed acceptance criteria, weekly shipping, a written decision log, and a first reply that tells you if Sao Paulo work of this shape is not something we should take.
The five lines we sell
Same five lines everywhere, Sao Paulo 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
Tell us what you are trying to build. A senior engineer reads every message and answers on scope, timeline and fit. If your problem is not one we should take, that is the first thing you will hear.