Your LatAm customers assume you run on AWS or GCP, your app must ship with Google Play Services, and your AI features call Claude or OpenAI directly — a stack that is unreachable from inside China and that your engineers have never run in production. I have. I help you get it live: architecture, payments and compliance, end to end.
Not a matter of talent — these are problems that simply do not exist inside the domestic ecosystem.
Your team knows Alibaba Cloud, Tencent Cloud, the WeChat ecosystem and domestic push services. In LatAm, partners assume AWS or GCP, your app will not pass review without Google Play Services, and AI features are expected to call Claude or OpenAI. None of it is reachable from China, and there is no internal experience to draw on — the skills are learnable, the failure modes are not documented anywhere.
In Brazil the bulk of online payments runs on PIX; shoppers in Mexico, Argentina and Brazil expect instalments (cuotas / parcelado); domestic card brands like Elo and Hipercard are invisible to international gateways. Cross-border acquiring means higher fees, more declines and slow settlement, with reconciliation logic unlike anything at home. The wrong setup quietly costs you several points of margin.
LGPD data protection, a CNPJ entity and electronic invoicing (NF-e), Anatel certification for hardware, data residency requirements — none of this can be bolted on after launch. Architectural choices made without them usually end in a rebuild, at double the time and cost.
One person, working directly with your engineering lead. Nothing subcontracted, no junior consultants sent in my place.
Porting a domestic architecture one-to-one onto AWS or GCP usually breaks on cost, reliability or both. I handle architecture design and review, cost optimisation, Google Play Services and Firebase integration, CI/CD and observability, multi-region deployment and disaster recovery.
PIX integration and selection of local acquirers, instalments and domestic card brands, fraud and risk strategy, reconciliation, settlement and refund flows. The goal is approval rates and settlement speed on par with local players — not merely "checkout works".
The technical side of entity and tax structure, LGPD implementation, data residency and cross-border transfer design, and vetting of local vendors. I am not a lawyer — but I know which technical decisions turn into compliance landmines, and which local partners are worth talking to.
Claude / OpenAI integration and model selection, RAG and agent orchestration, tool calling and workflow design, evaluation harnesses and quality control, inference cost management. Teams often carry over assumptions from domestic APIs — pricing and capability curves abroad look nothing like them.
Concrete technical decisions and measurable outcomes beat adjectives.
I map the current state and the risks across three tracks — architecture, payments, compliance — and hand over a prioritised roadmap your team can put straight into a sprint plan. If I conclude I cannot add value, we stop here; I will not upsell the next stage.
I work alongside your team: architecture, implementation of the critical pieces, vendor negotiations, code review. The goal is that the capability stays with your engineers — you own and maintain it after I leave, rather than inheriting something nobody understands.
Technical decisions after launch, incident reviews, and evaluating what changes when you expand into the next market. Billed monthly, cancellable with a month's notice — no long lock-in.
Add me on WeChat and tell me what your company does, which market you are entering and where you are stuck. I will tell you straight whether I can help — and if I cannot, I will try to point you somewhere useful.