Case study: Panda's Vancouver and Mexico City expansions

After validating the platform in the Greater Toronto Area (63,000+ charging hours delivered, 20,000+ rentals, 27+ months of continuous operation), the next question was: does the system actually transfer to a different city and a different country — and how fast?

We launched two new markets to test it. Vancouver in Canada. Mexico City in Mexico. Both went from zero to live within a month, on the same stack.

Why these two markets

The choices weren't accidental.

Vancouver was the obvious "second Canadian city" test. Same currency rails as Toronto, similar payment behavior, but a different geography, a different venue density, and a different on-the-ground team. If the platform handled it cleanly, it would tell us the playbook transfers within a country without a rebuild.

Mexico City was a more interesting test: a different country, a different currency (MXN), a different language at the customer-facing layer (Spanish), and a completely different payment landscape (OXXO, Mercado Pago, local cards). If the platform handled Mexico, it would prove the multi-region architecture wasn't hypothetical.

Where they are today

Both markets are early. Each was taken from kickoff to first live rental within about a month — that's the speed-to-live story we want to put on the table. The rental volume is still small, and we'd rather tell you that honestly than dress up a small number.

What we can confirm:

• The same software stack powers both, deployed without market-specific rewrites
• The same operator dashboard is in use across all three markets
• Localized payment rails are live in each — CAD on Canadian rails in Vancouver, MXN on Mexico's local rails (OXXO, cards, wallets) in Mexico City
• Customer-facing UI is localized — EN for Vancouver, Spanish (and English) for Mexico City
• The playbook for venue selection and operational rhythm is the same as Toronto — and so far, it's working

What the expansion tells a prospective operator

If you're evaluating whether to license Panda for your city, the most important question isn't "is Toronto a success?" — Toronto being a success is necessary but not sufficient. The real question is whether the platform was built as a one-city product or as a real multi-market system.

The honest test: can a team that didn't build the platform pick up the same stack and run a new market with it? Vancouver and Mexico City are the in-progress answer to that question.

So far:

• The platform onboarded both markets without bespoke engineering
• The payment rail switched cleanly to MXN in Mexico City (the integration we'd built for Mexican operators was real, not theoretical)
• The dashboard, alerts, payouts, and reporting all worked the same way
• The operating playbook from Toronto applied with regional adjustments (category mix, pricing tier, venue conversation tone)
• Both markets went from "we're going to do this" to first live rental within roughly a month — that's the practical measure of a platform being multi-region from day one vs. a platform that just claims to be

What we're still learning: the specific category-by-city calibrations. Hot pot performs in Toronto; what's the equivalent strongest category in Mexico City? The early data hints at it, and the next 12 months will sharpen the answer.

Why we're publishing this now (with limited data)

Two reasons.

First — operators considering licensing Panda for a new market (especially in Latin America or Europe) deserve to know that they wouldn't be the first one outside Toronto on the platform. Vancouver and Mexico City are already there.

Second — honesty about state. We could have waited 18 months and published this with bigger numbers. We'd rather give you the real shape now, including the part that's still being built.

What this means for you

If your city is in:

• North America (Canada, US, Mexico) — the platform is live in this region today. We can onboard a new operator with the same rails and dashboards already in production.
• Latin America — Mexico City is our first market here, but the architecture is ready for the rest of the region (we built it for it). Talk to us about your specific country.
• Europe — not yet directly operated by us, but the multi-region architecture is the same architecture that handles Mexico — extension to European markets is on the active roadmap. Early-mover operator conversations are happening.

What you can ask for on the demo

• Live look at the Toronto dashboard (the most mature market) — same surface you'd see for your network
• A walkthrough of how the multi-region rails actually work in practice
• The specific category mix that worked in Toronto, and the early signal from Mexico City
• A concrete first-90-day plan for your market

Apply to become an operator and we'll walk through everything live.