| Company | Function | Understandings | Global level | Zone level | Country level |
|---|---|---|---|---|---|
AB Tasty | There is no "zone level" company management because there is the same number of countries and zones. Decision has been made to keep the management only at country level. | CEO | None. | VP Country | |
AB Tasty | Each country localize the global CSM framework to the country level. | VP Customer Success | Customer Success Manager + team. | None. | |
AB Tasty | Only global. | CFO + team | None. | None. | |
AB Tasty | The structuration recently moved from a country level presence to a global presence only because of too much fragmented team across countries and a big hub in France. | VP People & Legal + team | None. | None. | |
AB Tasty | Each country has it owns marketing team structuration. Depending on country cultural habits, the focus is on events or content. | VP Marketing | Head of Marketing ZONE | Senior Marketing Manager + team | |
AB Tasty | Managed at a global level by VP BD and Alliances. | VP BD and Alliances | Head of Partnerships ZONE | None. But current open position for France. | |
AB Tasty | Only global. Product is not changing depending on the country. | VP Product + Team | None. | None. | |
AB Tasty | They are present at every level (country, zone, global) as the sales cycle is including close contact with customers. | VP BD and Alliances | Sales Director ZONE | Sales Team Leader + team | |
AB Tasty | Only global. | CTO + Chief Data Scientist | None. | None. | |
360Learning | There is no country manager because : US is considered as a ZONE and UK is too small to need one. The VP Zone EMEA is managing both France, UK & RoW. | CEO | VP ZONE | None. | |
360Learning | Each country localize the global CSM framework to the country level. | VP Customer Success | None. | Customer success Manager Country + team | |
360Learning | Only global. | CFO + team | None. | None. | |
360Learning | US and UK are big markets, that's why HR team needs to be at global and zone levels. To fulfill hiring needs, there is a Talent acquisition manager in every operating country. | VP People | Head of HR ZONE (only for US) + Head Talent Acquisition ZONE (only for US) | Talent Acquisition COUNTRY (for US & France) | |
360Learning | This company is marketing strategy is mostly relying on Demand Gen & content. Both are very specific to each country (culture & habits), that's why there is a dedicated team per country. | VP Marketing + Global Head of Demand Gen + Global Head of Content | None. | Head of Demand Gen Country Content Lead Country | |
360Learning | Partners are very localized. That's why, strategy is handled at a global level but ops are handled at country level. | VP Global Alliances | None. | Partner Success Manager | |
360Learning | Only global. Product is not changing depending on the country. | VP Product + team | None. | None. | |
360Learning | CRO is managing both VPs Revenue and VP Sales at zone level. | CRO | VP Revenue ZONE (handle by VP ZONE) | None. | |
360Learning | Sales strategy is handled at a zone level but managed by Revenues at a global level. | VP Sales ZONE + Head of BDR ZONE | Sales Director + team | ||
360Learning | Only global. | Head of Strategy & Ops + team | None. | None. | |
360Learning | Only global. | CTO + Team | None. | None. | |
Dynadmics | There is no "zone level" company management because there is almost the same number of countries and zones. Decision has been made to keep the management only at country level. | CEO | None. | Managing Director Country | |
Dynadmics | Customer Success is handled only at a zone level. | None. | Head of Customer Success | None. | |
Dynadmics | Only global. | CFO + team | None. | None. | |
Dynadmics | Only global. Team is reporting to CFO. | VP People + team | None. | None. | |
Dynadmics | Each country has it owns marketing team structuration depending on local market needs. | VP Marketing | None. | Marketing Manager + team | |
Dynadmics | Partners are very localized. That's why, Partnerships strategy is handled at Global level but ops are managed at a country level. | VP Global Partnerships | None. | Partnership Manager Country | |
Dynadmics | Product is specific to country because of local regulations, that's why product ops are managed at a zone level. Not at a country level because each zone has a dominant country driving the product localization. | VP Product | Head of Product ZONE + team | None. | |
Dynadmics | Head of Sales position at a ZONE level is sometimes endorsed by the managing director of the main country of the zone. | None. | Head of Sales ZONE (only for LATAM) | Senior Sales Team Lead + team | |
Dynadmics | Only global. | VP Global Ops + team | None. | None. | |
Dynadmics | Only global. | CTO + team | None. | None. | |
Prestashop | Country managers localize company value proposition in the country, making sure that all the key asset are properly translated for the local market, that the key players of the local ecommerce value chain are integrated and promotion & merchandising are properly adapted to the local market | VP International | None. | Country Manager | |
Prestashop | Prestashop has no proper customer success team. They deal with customer requests through a dedicated forum. The team is dealing with customers requests locally. | Head of Customer Engagement & Growth | None. | Team (Tech Evangelist, Ambassador) | |
Prestashop | Only global. | CFO + team | None. | None. | |
Prestashop | Only global. Report to CFO. | VP People + team | None. | None. | |
Prestashop | Each country has it owns marketing team structuration, depending on country cultural habits. Most of the team is localized at global level. | VP Marketing + team Head of Events | None. | Team (Digital Strategist, Event manager) | |
Prestashop | Partner managers at a zone level are dealing with top partners of the zone while manager agency at country level adopts a mass market approach. | VP Partnerships + Team | Partner Manager | Manager Agency | |
Prestashop | Only global. Product is not changing depending on the country. | VP Product + team | None. | None. | |
Prestashop | Only global. More info here on CRO role at Prestashop: https://medium.com/xangevc/tout-savoir-sur-le-chief-revenue-officer-d5678f2313db | CRO + team | None. | None. | |
Prestashop | No proper sales team as Prestashop product is sell through partnerships only or self buying. | N/A | N/A | N/A | |
Prestashop | Only global. | CTO + team | None. | None. | |
Odoo | There is no "country level" management but managing director zone are usually located in the biggest country of the zone. | CEO | Managing Director ZONE | None. | |
Odoo | Only at a zone level. The team is reporting to Managing Director Zone. | Managing Director ZONE | Head of Customer Success ZONE + team | None. | |
Odoo | To facilitate reporting, each zone has it owns head of finance, reporting to global finance team. | CFO + team | Head of Finance ZONE | None. | |
Odoo | HR topics are managed at global level but each zone gets its own talent acquisition team. | Head of People (attached to CFO) | Talent Acquisition ZONE | None. | |
Odoo | Marketing ops are managed at a zone level. Even if the most of the marketing efforts are focused on biggest region of the zone. | Head of Marketing | Marketing Team Leader ZONE + team (Campaign Specialists, Web Designers, Graphic Designers and Event Planners) | None. | |
Odoo | At every level (country, zone, global). | Chief Service Officer | Head of Services ZONE | Team (Business analyst) | |
Odoo | Partners are very country localized but not numerous enough to be handled at a country level. | VP Partnerships | Head of Partnerships ZONE + team | None. | |
Odoo | At Odoo, Product strategy is handled by the tech team. As ERP is a product with local legal specificities, Product owners are responsible for localizing the product. | CTO | CTO ZONE + team | Product Owner COUNTRY localizations | |
Odoo | They are present at every level (country, zone, global) as the sales cycle is including close contact with customers. | Chief Commercial Officer | VP Sales ZONE + Head of Channel Sales ZONE + Head of Direct Sales ZONE + Business advisor ZONE | Sales Team (analyst, KAM, SDR) | |
Odoo | As product is changing depending on operating countries, Tech function needs specific teams to address the product maintenance and update. | CTO | CTO ZONE + team | None. | |
Commanders Act | None. | ||||
Commanders Act | None. | Head of Consulting + team | |||
Commanders Act | None. | ||||
Commanders Act | None. | ||||
Commanders Act | None. | ||||
Commanders Act | None. | ||||
Commanders Act | None. | ||||
Commanders Act | None. |
