Product Design Company in São Paulo

The number follows what you actually build: a scoped design sprint at paulistano rates, a full product design engagement (discovery, research, design system foundation, end-to-end flows, prototype, usability testing in pt-BR), or a full design system build for a Brazilian fintech or retail platform, modelled on the Magalu vibe-DS or Nubank morpho scale. Sao Paulo rates sit above Belo Horizonte and Curitiba because of the Nubank, Itau Cubo, and DPZ&T talent premium. We quote in BRL with a parallel USD column for export clients.

We design in Portugues do Brasil first for any product whose primary audience is Brazilian. This matters more than non-Brazilian buyers expect. pt-BR and pt-PT diverge on roughly 30% of common UI vocabulary: usuario versus utilizador, tela versus ecra, celular versus telemovel, arquivo versus ficheiro, time versus equipa, time-out versus tempo limite. A Portugal-localised flow drops on a Sao Paulo user and reads as foreign within seconds. We maintain separate pt-BR and pt-PT copy banks when the cliente needs both, and we never machine-translate UI strings between them. English versions are exported in parallel for cross-border SaaS, with the pt-BR version remaining canonical.

Pix (the Banco Central instant payment rail launched in 2020) is now the default Brazilian payment expectation, with parcelamento sem juros (instalment purchases without explicit interest) covering roughly 80% of Brazilian e-commerce by volume. Our checkout designs default to Pix as the first option, surface parcelamento with clear CET disclosure (Custo Efetivo Total under Banco Central Resolucao 3.517/2007 and CDC plain-language requirements), and handle the boleto fallback for unbanked or distrustful users. The CPF or CNPJ entry field is positioned and validated according to the buyer profile branch. We do not import US or European checkout patterns wholesale because they will visibly underperform in pt-BR usability sessions.

Yes. Every flow ships with an LGPD consent state diagram aligned with ANPD guidance — explicit opt-in for sensitive data, granular cookie consent on first visit (we follow the ANPD orientation note from 2023), legal basis disclosure under Article 7, and data subject rights surfaces for ARCO equivalents (acesso, retificacao, anonimizacao, eliminacao, portabilidade, oposicao). CDC compliance (Lei 8.078/1990) covers plain-language price disclosure, instalment CET clarity, no-questions refund within seven days for online purchases (Article 49), and visible contact channels for the SAC (Servico de Atendimento ao Consumidor) per Decreto 11.034/2022. Public sector clients additionally pass eMAG accessibility and Lei Brasileira de Inclusao requirements.

We benchmark against the studios and in-house teams that genuinely set the paulistano bar: Nubank design (Latam fintech UX leader), Magazine Luiza design (omnichannel retail under Adriana Aroulho), DPZ&T, Africa Creative, Almap BBDO, Loducca, AKQA Sao Paulo, R/GA Sao Paulo, Wieden+Kennedy Sao Paulo, Cubo Itau in-house product design, Itau design system team, and the design teams at Globo and Folha. Academic pipeline comes from USP FAU (Faculdade de Arquitetura e Urbanismo da Universidade de Sao Paulo), ESDI (Escola Superior de Desenho Industrial) at UERJ, FAAP, IED Sao Paulo, and Mackenzie. We hire and partner against that benchmark rather than against a generic global portfolio average.

Public sector and SOE (Petrobras, Banco do Brasil, Caixa Economica Federal, EBSERH) work must pass eMAG (Modelo de Acessibilidade em Governo Eletronico) compliance, currently aligned with WCAG 2.1 at AA. Private sector targets WCAG 2.2 AA. The Lei Brasileira de Inclusao da Pessoa com Deficiencia (Lei 13.146/2015) makes digital accessibility a legal obligation for any public-facing site or app — and the Public Ministry has begun acting on complaints under Article 63. We test with NVDA on Windows, VoiceOver on iOS, and TalkBack on Android using Portugues do Brasil voice profiles, and we ship an accessibility statement with each release that documents the conformance level and known gaps.

Yes, and we treat it as a given. Brazilian mobile usage is the highest in Latin America, with roughly 84% of internet sessions happening on smartphones (CGI.br TIC Domicilios annual survey), heavy use of WhatsApp for commerce (the WhatsApp Business and Cloud API stack is a critical surface in Brazil, more than in any other major market), and bandwidth constraints in suburban Sao Paulo and across the Norte and Nordeste regions. Our designs default to mobile-first Figma frames, optimise for low-end Android devices (Motorola, Samsung A-series, Xiaomi), and design WhatsApp commerce flows (catalog, checkout, official chatbot via Twilio or Take Blip) as a first-class channel, not an afterthought.

A focused design sprint runs four to six weeks. A full product design engagement for a paulistano fintech or marketplace (research, system, end-to-end flows, prototype, usability testing in pt-BR, handoff to a Sao Paulo engineering team) runs sixteen to twenty-eight weeks. A full design system build modelled on the Magalu vibe-DS or Nubank morpho scale runs twenty-four to forty weeks. We work in two-week sprints on Brasilia time and run weekly critiques with the cliente design lead in Portuguese, not async Slack threads. Discovery and research take longer than non-Brazilian buyers expect because recruiting NSE C and D participants in Sao Paulo state requires a local panel, not a Western European or US recruiter remote.