Locations · Sao Paulo, SP
Sao Paulo moves quickly and expects the same from its suppliers. We build web and mobile products, add AI where there is a real job for it, and run the marketing behind them, remotely from a Vancouver studio and inside your working hours.
Remote from Vancouver, on-site when useful Weekly working demos Reply within one business day
4,812
Active users
99.98%
Uptime
142ms
p95 latency
Yes. OlDevs works with Sao Paulo organisations from the Vancouver studio, remotely by default, travelling to Brazil when a project genuinely benefits from time in the room.Sao Paulo is five hours ahead of Vancouver, so your afternoon meets our morning and that is where the calls go. The work spans web development, web apps, Android and iOS, full-stack engineering, AI development and performance marketing.
Key facts
Services
Seven services from one accountable team — delivered remotely in your working hours.
Built for Sao Paulo State
The local rules and realities we design for from the first call.
The Brazilian General Data Protection Law, enforced by the ANPD, sits behind every data decision on a Sao Paulo build. We design the consent moment, keep collection tight, and give people a working way to see and remove what you hold, with your counsel reviewing the wording.
Brazil has the Inclusion Law and the eMAG model for government sites, and we build to WCAG 2.2 AA in every sector. Screen reader labels, keyboard routes, visible focus, contrast that survives daylight, and forms that recover gracefully when someone makes a mistake.
Portuguese is the product language and English appears where business crosses borders. We write Brazilian Portuguese copy properly, test layouts against its longer phrasing, and format dates, currency and addresses the way people in Sao Paulo actually read them.
If the database and the backups belong in a Brazilian cloud region, that is settled before the first deploy rather than during a review. We record which services touch personal data, where each one runs, and who holds the account keys.
Sectors
Fintech interfaces have to feel safe and move quickly at the same time. We build onboarding, dashboards and back office tools with clear states, careful error handling, and security review folded into the schedule instead of bolted on at the end.
Head offices coordinate operations that stretch far past the city. We build reporting portals, field-facing apps and integrations that hold up on poor connections, designing for the person entering data in a truck and not only the analyst reading it later.
Slow pages and an awkward checkout lose shoppers here as surely as anywhere. We build storefronts and mobile apps around the real path to purchase, then improve them with analytics and testing once genuine traffic is passing through.
Startups need something usable in front of customers before the runway argues otherwise. We scope a first version that ships, show a working demo every week, and keep the code plain enough that the wrong guesses can be replaced quickly.
Process
Discover
Calls in your early afternoon, a read through everything you already have, and a written scope at the end of it: what we are building, what we are not, and what is still unknown.
Design
Screens designed in a shared file and reviewed while we are both online. Portuguese wording, accessibility and the mobile case are agreed here rather than argued about mid-build.
Build
Short cycles, one accountable team, and a working demo every week deployed somewhere you can open it. Questions raised in your afternoon are answered while you are still at your desk.
Launch
The release is rehearsed first: hosting region confirmed, backups verified, accessibility and speed checks passed. We go live with the team on the call and stay through the first hours.
Grow
Afterwards we look at what people really do, fix what gets in their way, and add carefully. SEO, paid media, email and CRO run from the same studio that built the product.
Nearby
FAQ
No. There is one studio and it is in Vancouver, British Columbia, running since 2014. Sao Paulo clients are looked after remotely, with calls scheduled in Brasilia Time, and we travel to Brazil when the work justifies it: a discovery workshop, a launch week, or time with your internal team.
By putting every live conversation in the overlap, which is your early afternoon and our morning, and by writing the rest down. Decisions are recorded the same day, the demo environment updates overnight for you, and no question sits waiting a full day for an answer.
Yes. Where your policy or your reading of the LGPD calls for it, we host the primary database and the backups in a Brazilian cloud region and keep a written record of every service that processes personal data. The choice is made before the build, and you hold the cloud accounts.
Yes, and we treat it as the first language of the product rather than a translation layer added late. Copy is written for a Sao Paulo reader, interfaces are tested with the longer phrasing in place, and an English version is planned alongside it when partners abroad need one.
That works well. We take a defined piece, agree where our code meets yours, work in your repository if you prefer, and keep one person accountable for the whole engagement. Notes and documentation are written as the work happens, so a handover is never a project of its own.
Send the brief, or an outline of the problem if the brief does not exist yet. You will have a reply within one business day, then a call in your afternoon to work through scope, constraints and timing. After that we prepare a quote for you to review before anything is committed.
Let’s connect
We’ll reply within one business day, in your working hours, with next steps and a tailored quote — no obligation.