Home › Blog › The cross-border RevOps playbook: USD revenue, MXN operations, one comp plan

The cross-border RevOps playbook: USD revenue, MXN operations, one comp plan

A growing number of B2B SaaS companies are US-incorporated, sell to US enterprise buyers in USD, and run sales operations or engineering out of Mexico. The setup makes financial sense — talent cost, time-zone overlap, USMCA legal clarity — but RevOps complexity sneaks up on teams that did not plan for it. This is the playbook I run when standing up the back office for one of these companies.

The setup most teams end up with

The pattern is recognizable: a US Delaware C-corp, the US Inc. owns all customer contracts and books all revenue in USD, with a Mexican subsidiary (S.A. de C.V. or S. de R.L. de C.V.) that employs the engineering and sales operations teams. Customers are mostly US enterprise. The US entity charges the Mexican entity for services rendered under a transfer-pricing agreement. Reps and SDRs sometimes live in the US, sometimes in Mexico, sometimes both. Customer success is in Mexico City; the CRO is in Austin; the AEs are scattered.

None of this is exotic anymore. What is still exotic is doing it well from a RevOps perspective. Most teams I see ship the org chart and let the operational complexity build up as technical debt. Two years in, the comp plan is a spreadsheet maintained by one person, the forecast misses by 15-20% every quarter because timezone gymnastics distort the pipeline review, and Salesforce has three different currency configurations layered on top of each other.

Comp plan: pay in local currency, target in revenue currency

This is the single highest-impact decision. Most teams get it wrong the first time.

The temptation: pay reps in MXN because they live in Mexico and need to pay rent in pesos. Tie quota and attainment to MXN booked revenue because the comp plan is denominated in MXN.

Why it fails: your revenue is in USD. The MXN/USD rate moves 8-15% in a typical year. If a rep books $1M USD of ARR and the rate moves from 17 to 19 MXN/USD over the quarter, their MXN-denominated quota gets easier or harder by 12% with no behavioral change on their part. Comp plans are supposed to drive behavior. FX volatility decouples behavior from outcome.

The fix: denominate the comp plan in USD. Set quota in USD. Calculate attainment in USD. Calculate the commission payout in USD. Then convert the payout to MXN at the end of each month, using a fixed published reference rate (Banxico FIX or the company's published month-end rate) plus a small buffer to absorb the timing risk between booking and payroll.

The buffer is the part that matters. Pay the rep at, say, FIX minus 2%. The 2% is the company's hedge against the rate moving against them between when the deal closes and when payroll runs three weeks later. The rep gets a transparent, FX-volatility-free comp plan; the company holds a small predictable FX risk. Everyone can plan.

Tax treatment is a separate question, and it is the one place where you must have a Mexican tax attorney in the loop. ISR (income tax) and IMSS (social security) apply to the MXN-equivalent payout. The 2% buffer can be partially offset by carefully structured "viáticos" and benefits packages, but that gets into territory beyond this post. Talk to a real attorney.

Forecasting across two time zones

The mistake here is to run the forecast call on US-East-Coast time and inherit the rest of the planet's problems. CST and CDT cover Mexico City; PST/PDT cover the West Coast; AEDT covers Australia if you sell there. By the time you reconcile what "last day of the quarter" means for a deal whose customer is in Sydney and whose AE is in Mexico City, you have created a 36-hour ambiguity window where deals slip in mysterious ways.

Pick one canonical time zone for the entire revenue calendar — almost always UTC or the US East Coast equivalent — and run every cutoff against it. The last day of Q3 ends at 11:59 PM ET, period. Salesforce has a per-org timezone setting; align it. Every rep, regardless of where they sit, sees deal close dates and quarter cutoffs in the canonical zone. Avoid the trap of "well, my AE in Mexico City says it is still Tuesday her time" — that path leads to deals booking in the wrong quarter and reps gaming the calendar.

The forecast meeting itself should be scheduled twice if you have meaningful headcount in both Pacific and Eastern: an 8:00 AM PT and a 10:00 AM ET option, both reviewing the same data. The CRO can pick which one to attend; managers run both with consistent agendas. This is more meeting load than running one canonical meeting, but it is the only way to keep AEs in Mexico City and Los Angeles equally engaged.

Salesforce: currency, locale, language

Three settings, three trap-doors.

Currency. Turn on Multi-Currency in Salesforce. Set the corporate currency to USD. Add MXN as a secondary currency with a rate that updates automatically (DatedExchangeRates with a daily refresh from a trusted FX feed, not the rep doing it manually). Every Opportunity has a CurrencyIsoCode field; reps should not change it, but admins need to know how to interpret it when a Latin American customer's contract is denominated in MXN.

Locale. Set every user's locale to match where they actually work, not where the company is headquartered. A user with English (United States) locale will see "5/12/2026" but a user with English (Mexico) locale will see "12/5/2026." This matters because reports default to user-locale formatting. A consolidated pipeline review that includes both locales reads inconsistently unless you normalize.

Language. Optional but worth it: enable Spanish as a UI language for users who want it. The data is the same; the labels translate. Users who want to operate in Spanish can; users who want English can. The flag is per-user and costs nothing.

One detail nobody warns you about: the Currency field on Account, Contact, and Opportunity records can be confusing when AccountCurrency = MXN but the deal is in USD. Pick a convention and document it. Common one: Account currency matches the customer's billing entity currency; Opportunity currency matches the contract currency. Train reps on the distinction.

Commission calculation: do it in USD, pay in MXN

The commission calculator (see the commission case study for the underlying model) should run in USD throughout. Compute quota attainment, accelerator tier, kickers, and gross commission all in USD. The last step is a single column conversion to MXN using the published rate.

For reps' own self-verification: build the calculator so it shows both columns. Rep sees "$24,500 USD commission earned this period → ₱422,500 MXN gross." Transparency. The next person who tries to negotiate the conversion has already lost the argument.

Bilingual operations docs and enablement

If your Mexico-based ops team and your US-based commercial team need to share the same playbooks, you have two viable options:

Single English source. Everyone operates in English. This works for senior teams where English fluency is uniformly strong. Cost: less inclusive, particularly for junior CSMs and SDRs in the Mexico office.

Maintained bilingual docs. Every playbook, SOP, and enablement deck lives in both languages, with a documented owner who keeps them in sync. Cost: real maintenance overhead. You will need a freelance bilingual editor in the loop, and you must treat translation as a content version-control problem, not a one-time export.

I have run both. The maintained-bilingual approach pays back when the team grows past about 30 people in the Mexico office, because the productivity drag of "wait, what does this English term mean exactly" compounds with headcount. Below 30, single-source English usually wins on simplicity.

The five mistakes I see most often

1. Comp plan denominated in MXN. Already covered. FX volatility kills the behavioral signal of the plan.
2. Quarter cutoffs interpreted by rep's local time. A few wrongly-stamped deals per quarter cost real money once you are tracking attainment seriously.
3. Salesforce currency rates updated manually. Someone forgets; reporting drifts; one bad month nobody notices until the CFO's variance report calls it out.
4. Treating the Mexican subsidiary as "the back office" in vocabulary. Reps and CSMs in Mexico City are not back-office. They are commercial. Pipeline reviews and forecast calls should include them as peers; comp plans should match the US equivalents (in USD-denominated terms); enablement should be designed for both audiences. The org chart can subordinate the entity; the operating model should not subordinate the people.
5. No published policy on what currency the contract gets denominated in. Reps occasionally negotiate MXN-denominated contracts because the customer prefers it. This creates an FX risk the company holds for the contract term. There should be a written policy — usually USD-only — and any exception requires approval.

The half-day setup

If you inherit a US-MX RevOps setup that is already running but messy, here is the half-day audit to do first:

1. Check Salesforce: is Multi-Currency on? Is corporate currency USD? Is the rate updating automatically? (15 min)
2. Check the comp plan: is quota in USD or MXN? If MXN, calculate the FX-only attainment swing from the last year. Bring the number to the CFO. (45 min)
3. Check the forecast call agenda: what time zone are quarter cutoffs in? Is it written down? (15 min)
4. Check the playbooks: are they monolingual or bilingual? Is there an owner? (30 min)
5. Check the org chart for the operational reality: are the Mexico-based commercial roles compensated and reviewed as peers to US-based equivalents? (45 min)
6. Write up the gaps, prioritize the top three, present to the CRO and CFO. (90 min)

This is the work I do in the first week of every cross-border engagement. The setup is more common every year and almost nobody has fully figured it out. Get the comp plan, time zones, and Salesforce currency right and you have eliminated the three failure modes that account for most of the operational drag. Everything else is execution.