sayhi@zarasa.io
English

Salesforce · Latin America and the United States

Salesforce across Latin America: where we are and what changes country by country

Zarasa is a Salesforce Consulting Partner with 78 certifications, more than 120 delivered projects and a 4.85 out of 5 rating on AppExchange across 19 reviews. We work in twelve countries from four offices of our own. This page is the map: what we do in each one and what is worth knowing before you start.

Four offices of our own

We do not cover the region from a distance: we have an office in four of the twelve countries. That sets the time zone we answer in and the language the project is discussed in.

  • United States1000 Brickell Ave, Miami, Florida
  • MexicoAv. Tamaulipas 141, floor 3, Mexico City
  • Guatemala12 Avenida 21-06, Zona 6, San Nicolás de las Rosas, Mixco
  • UruguayFernández Crespo 2081, Ap. 305, Montevideo

The twelve countries, one by one

Each country has its own page, with the sectors, scenarios and questions specific to that market. This is the full map.

CountryOfficeWhat we are asked for mostPage
United StatesMiami, FloridaCompanies operating between the US and Latin AmericaOpen
MexicoMexico CityCorporations and growing companiesOpen
GuatemalaMixcoAgribusiness, manufacturing and retailOpen
El SalvadorSales and service moving to digital processesOpen
Costa RicaFree trade zones and shared services centresOpen
PanamaMultinational headquarters and logisticsOpen
Dominican RepublicLogistics, free trade zones, banking and infrastructureOpen
Puerto RicoPharmaceutical and Act 60 companiesOpen
ColombiaSales processes and service channelsOpen
ParaguayUnifying sales processesOpen
UruguayMontevideoOperations and service channelsOpen
ArgentinaAutomating operating workflowsOpen

What changes from one country to the next

There is more than one time zone

"We work in your hours" sounds fine until three time zones are involved. Guatemala, El Salvador and Costa Rica share the clock with Mexico City. Panama, Colombia, Puerto Rico and the Dominican Republic run an hour ahead. Paraguay, Uruguay and Argentina, three hours ahead of Guatemala. When a project crosses those blocks, the overlap window has to be designed, not assumed.

The project language and the head office language

In free trade zones and shared services centres the local team works in Spanish and reports in English. Our teams are bilingual, so documentation and training can run in one language and the working sessions in the other.

What gets integrated, and therefore how long it takes

Electronic invoicing is mandatory and different in several of these countries, and the ERP is almost never the same one. That is the part that varies most in time and cost between projects, far more than configuring Salesforce itself.

A new implementation, or rescuing an org that already exists

From scratch

There is no Salesforce yet, or there is one and nobody uses it. We start with the sales process and the data behind it, write down the scope, and go live with a measured baseline.

An inherited org

Salesforce is already running and has become hard to maintain: automations nobody understands, duplicated fields, a previous consultant who is gone. We take it as it is, review it, and decide with you what gets fixed, what gets rebuilt and what gets switched off.

FAQ

Do you work in countries where you have no office?

Yes. We have offices in four countries and projects in twelve. What changes without an office is physical presence, not delivery: meetings are remote unless the project justifies travelling.

What language do you work in?

Spanish and English. Our teams are bilingual, so documentation can run in one language and the sessions in the other. That is the usual setup when a local team reports to a head office in the United States.

Can I contract from one country and deploy in another?

Yes, and it is common in groups operating across several countries. It is worth settling early because it affects the contract and the currency, not the technical work.

Do you take over projects another consultant started?

Yes. It is one of the two ways we begin. We review the org as it stands and tell you what to fix, what to rebuild and what to switch off, before touching anything.

How long does an implementation take?

It depends on scope and on the integrations, which is what varies most between countries. A focused single-cloud implementation is usually measured in weeks; one with several integrations, in months. We estimate it against your case before you sign.

Which country are you in?

Tell us where your company operates and what is breaking. The first conversation is 45 minutes and costs nothing.

Talk to us