Context
Regional expansion at a D2C commerce business is not copy-paste. Mexico, Chile, Colombia, and Bombavista each run on different payment infrastructure, have different customer expectations, different return and exchange behavior, different marketing dynamics, and different operational setups. The product challenge is maintaining enough coherence to ship efficiently, while not pretending the differences don't exist.
This work spans eight years and three roles — from engineering the initial expansions to owning the product strategy across all four markets.
Problem
- Markets needed shared UX foundations, but also needed their own local logic at the moments that mattered — payment methods, catalog rules, regional pricing, local operations.
- Product and engineering decisions made for the primary market (Mexico) regularly created friction in secondary markets — not because of bad intent, but because "default" behavior wasn't designed to accommodate variation.
- Stakeholders across markets needed enough coordination to move together, but market teams also needed to be able to execute locally without waiting for central decisions on every detail.
Approach
The work looked different depending on the role. As an engineer, it was shipping the services that made market launches possible — payment integrations, catalog rules, localized flows. As a Product Tech Lead and later Senior PM, it was holding the tradeoff between platform coherence and local market needs in every roadmap and launch decision.
Decisions
- Maintain shared platform logic while surfacing local differences at the right layers — not at the presentation layer where it creates UX fragmentation, but at the data and rules layer where it's expected.
- Keep market needs visible in roadmap decisions as first-class requirements, not edge cases to be handled at launch.
- Design the coordination model between central product and market teams to minimize bottlenecks without losing quality control.
Impact
- Successful product launches and sustained operations across four markets with different commercial, operational, and regulatory conditions.
- Platform architecture that handles regional variation without branching into separate products for each market.
- A working model for how local market needs surface in central product and engineering decisions — without requiring a separate roadmap for each market.