Country Manager

Country Manager

When to Use

• Lead market entry or scale-up for a country or regional operating unit
• Build or refresh country P&L, business plan, and territory KPIs / QBR cadence
• Localize go-to-market, pricing, product packaging, support, and brand for in-market fit
• Stand up or reshape the local leadership team and matrix interfaces to global HQ
• Coordinate regulatory and compliance workstreams with local counsel and global functions (not legal advice)
• Design partnerships, channels, and distributors for the territory
• Manage government and stakeholder relations at executive level (not lobbying counsel)
• Respond to in-country crisis, reputation, or operational escalation
• Run competitive intelligence and positioning for the local market
• Hire and onboard country leadership; adapt culture and ways of working locally
• Prepare matrix reporting packages for regional/global leadership and board subsets

When NOT to Use

• Global corporate strategy, portfolio, or board-level where-to-play only → enterprise-strategist, ceo-advisor
• International expansion market selection without in-country operating plan → intl-expansion (pair with this skill for execution)
• Immigration, work permits, or employment law opinions → legal counsel (not this skill)
• Tax structuring, transfer pricing, or treasury policy → cfo-advisor
• Product roadmap, backlog, or feature prioritization → cpo-advisor (or product roles in repo)
• Engineering delivery, architecture, or sprint execution → cto-advisor (or engineering roles in repo)
• Hands-on audit evidence, control mapping, or SOC 2 pipelines → compliance-engineer
• Consulting workshops and issue trees without country P&L ownership → business-consultant
• Recruiting process design without country GM accountability → talent-acquisition (supporting role)

Related skills

Core Workflows

1. Scope the country mandate

Clarify entity structure, P&L ownership, decision rights, and reporting line to HQ.

See `references/country_manager_scope.md`.

2. Market entry and localization

Define entry mode, localization priorities, and 12–24 month market thesis.

See `references/market_entry_and_localization.md`.

3. Country P&L and business planning

Build revenue/margin plan, investment case, and quarterly operating rhythm.

See `references/in_country_pnl_and_business_planning.md`.

4. Local org and matrix governance

Design leadership team, RACI with global functions, and escalation paths.

See `references/local_org_build_and_matrix_governance.md`.

5. Regulatory, partnerships, and stakeholders

Coordinate licenses, partners, and government/stakeholder map (high level).

See `references/regulatory_partnerships_and_stakeholders.md`.

6. In-country operations and crisis

Run territory operations reviews; manage local incidents and reputation.

See `references/in_country_operations_and_crisis.md`.

When to load references

• Role scope, deliverables, boundaries → references/country_manager_scope.md
• Entry mode and localization → references/market_entry_and_localization.md
• P&L, plan, QBR → references/in_country_pnl_and_business_planning.md
• Org, matrix, hiring → references/local_org_build_and_matrix_governance.md
• Regulatory coordination, partners, GR → references/regulatory_partnerships_and_stakeholders.md
• Ops cadence, crisis, reputation → references/in_country_operations_and_crisis.md

Country manager scope

Table of contents

1. Role definition 2. Operating unit types 3. Typical deliverables 4. Decision rights and accountability 5. Inputs and stakeholders 6. Boundaries vs adjacent roles 7. Quality bar

Role definition

The country manager (CM) or in-country general manager / managing director owns results in a defined geography—revenue, margin, market share, customer outcomes, local compliance posture, and team health—within constraints set by global HQ. The CM translates global strategy into executable territory plans, builds the local leadership team, and runs matrix interfaces so product, engineering, finance, legal, and HR enable rather than block the market.

Work is P&L- and stakeholder-oriented for regional presidents, global functional leaders, and sometimes board subsets—not enterprise portfolio design (enterprise-strategist) or expansion market screening alone (intl-expansion).

Operating unit types

Clarify legal entity, P&L boundary (what costs sit in-country vs allocated), and brand (global vs local) before deep planning.

Typical deliverables

• Country business plan (12–36 months): thesis, targets, investments, risks
• Quarterly business review (QBR) pack: actuals vs plan, initiatives, asks to HQ
• Market entry or scale-up plan with milestones and capital ask
• Localization priority list (product, pricing, support, marketing, payments)
• Org chart and leadership profile gaps with hiring plan
• Matrix RACI with global product, engineering, finance, legal, HR
• Partner and channel strategy with target list and economics
• Stakeholder map (regulators, industry bodies, key accounts, media)
• Crisis playbook outline and comms escalation tree (local + global)
• Competitive landscape brief with implications for positioning and pricing

Decision rights and accountability

Document explicitly:

Escalate when decisions cross entity, tax, or sanctions boundaries—coordinate with cfo-advisor and counsel, do not improvise.

Inputs and stakeholders

Gather or state assumptions for:

• Global strategy pillars and non-negotiables from enterprise-strategist / ceo-advisor
• Financial baseline and allocation rules from finance / cfo-advisor
• Regulatory and licensing status from legal and compliance-engineer
• Product availability and roadmap constraints from product leadership
• HR policies, grading, and compensation bands from chro-advisor
• Competitive and market data (size, growth, share, regulation)

Stakeholders: regional president, global functional EVPs, local leadership team, key customers, regulators (via counsel), partners, local employees.

Boundaries vs adjacent roles

Quality bar

• Numbers-backed plans with explicit assumptions and sensitivity
• Decision-ready QBR slides: status, variance drivers, asks, risks
• Matrix-clear RACI—no ambiguous “support” rows without owner
• Localization with rationale—not blanket translation; tie to revenue or risk
• Label unknowns and dependencies on HQ; avoid hero narratives without resourcing

In-country operations and crisis

Table of contents

1. Operational cadence 2. Competitive dynamics in-market 3. Reputation and brand locally 4. Crisis types and severity 5. Crisis response workflow 6. Communications escalation 7. Post-incident review 8. Handoffs

Operational cadence

Run the country as an operating system, not only a sales plan:

Integrate customer incidents, regulatory touchpoints, and HR signals into one risk view for QBR.

Competitive dynamics in-market

Maintain a living competitive brief:

• Share shifts and new entrants (local and global players)
• Pricing and packaging moves
• Win/loss themes from sales and partners
• Product gaps vs local requirements

Translate intel into actions: positioning, localization asks, partner bets, pricing within policy—not generic SWOT slides.

Reputation and brand locally

• Align local campaigns to global brand standards
• Monitor social and media for emerging issues (comms-led)
• Employee advocacy and local executive visibility where appropriate
• Avoid country-only promises that global cannot support

Escalate reputational threats early—speed matters more than perfect information.

Crisis types and severity

Define what triggers S1 in advance with legal and comms.

Crisis response workflow

1. Detect and classify — assign severity; do not under-classify to avoid HQ attention 2. Activate cell — CM, legal, comms, relevant functional lead; secure channel 3. Facts only — separate confirmed facts from assumptions; timestamp updates 4. Stakeholder map — who must know (regulators, customers, employees, media) 5. Action owners — remediation, customer comms, technical fix, regulatory response 6. HQ alignment — regional president and global exec sponsor informed per playbook 7. Stand down — explicit criteria; transition to recovery mode

CM does not draft legal filings or privileged strategy—business coordination only.

Communications escalation

One voice policy—no improvised statements on legal or security incidents.

Post-incident review

Within 2 weeks of stand-down:

• Timeline of decisions
• Root cause (technical, process, human, external)
• Control gaps and owners
• Update to crisis playbook and training
• Customer/partner retention actions

Share learnings with global ops (coo-advisor) and compliance where controls failed.

Handoffs

• Security incident technical response → cybersecurity roles
• Audit and control remediation evidence → compliance-engineer
• Global crisis comms strategy → communication-lead / ceo-advisor for board
• Business continuity and DR → BCM roles if present

In-country P&L and business planning

Table of contents

1. P&L ownership model 2. Planning horizons 3. Building the country business plan 4. Revenue and pipeline mechanics 5. Cost structure and investments 6. QBR cadence and pack structure 7. Variance management 8. Handoffs

P&L ownership model

Clarify what the country P&L includes:

Document allocation rules and transfer pricing assumptions with finance—do not invent (cfo-advisor).

Planning horizons

Align country plan to global strategic pillars without duplicating enterprise portfolio work (enterprise-strategist).

Building the country business plan

Minimum sections:

1. Executive summary — thesis, targets, top 3 bets, top 3 risks 2. Market context — size, growth, share ambition, competition 3. Revenue plan — by segment/product/channel with drivers 4. Cost plan — fixed vs variable; hiring by quarter 5. Investment cases — entry, marketing, systems, partner MDF 6. Cash and capital — working capital, capex, HQ funding ask 7. Initiative roadmap — outcomes, owners, dependencies on HQ 8. Risk register — regulatory, FX, talent, partner, product 9. KPI tree — links country metrics to regional/global scorecard

Revenue and pipeline mechanics

Define leading indicators alongside lagging revenue:

Require forecast categories (commit / best / upside) with evidence rules—same discipline as global sales ops.

Cost structure and investments

• Separate run rate from one-time entry costs
• Tie headcount to revenue milestones (hire triggers, not vanity org)
• Cap fixed cost as % of revenue by maturity stage
• Investment cases need ROI or strategic must-do rationale

For detailed models, pair with cfo-advisor or financial-analyst if present in environment.

QBR cadence and pack structure

Standard 60–90 minute QBR agenda:

1. Results vs plan (revenue, margin, KPIs) 2. Market and competitive update 3. Initiative status (green/yellow/red) 4. People and org (hiring, attrition, culture signals) 5. Risks and escalations 6. Asks to HQ (decisions, resources, roadmap) 7. Next quarter priorities (max 5)

Slide discipline: one message per slide; appendix for detail.

Variance management

For each material variance vs plan:

Avoid blame narratives; focus on decisions and resources.

Handoffs

• Enterprise-wide capital allocation → enterprise-strategist
• Tax, treasury, transfer pricing → cfo-advisor
• Global sales comp and quota policy → sales leadership / cro-advisor if available
• Workforce planning philosophy → chro-advisor

Local org build and matrix governance

Table of contents

1. Target org design principles 2. Leadership team composition 3. Hiring and onboarding 4. Matrix RACI patterns 5. Governance forums 6. Culture localization 7. Performance and accountability 8. Handoffs

Target org design principles

• Minimum viable leadership at entry; add roles when revenue or risk justifies
• Clear P&L line for customer-facing functions; dotted line to global centers of excellence
• Avoid duplicate layers (country + regional + global) without decision rights
• Document span of control and succession for each direct report

Leadership team composition

Typical country leadership team (scale-dependent):

For greenfield, CM may wear multiple hats temporarily—time-box with hiring plan.

Hiring and onboarding

1. Profile — outcomes, language, network, regulatory fluency 2. Scorecard — align with talent-acquisition on structured interviews 3. Comp — within global bands; local market data via HR 4. Onboarding — HQ immersion, customer visits, compliance training 5. 90-day plan — measurable outcomes per leader

CM owns who and when; recruiting ops owns process.

Matrix RACI patterns

Use a single RACI per major process (example: launch new SKU in country):

R = responsible, A = accountable, C = consulted, I = informed.

Escalate A conflicts** in writing with options—do not let matrix stall revenue.

Governance forums

Publish decision logs for cross-border topics (pricing exceptions, partner approvals).

Culture localization

• Translate values into local behaviors—do not dilute non-negotiables (ethics, safety, compliance)
• Adapt rituals (meetings, recognition, holidays) without creating second-class global policies
• Listen for psychological safety and speak-up channels
• Address language barriers in documentation and all-hands

Partner with chro-advisor on sensitive ER topics; never provide legal employment advice.

Performance and accountability

• Country KPIs on LT scorecards aligned to P&L
• Forced clarity on matrix goals: split local vs global objectives where needed
• Underperformance: fact-based PIP with HR; avoid public blame in matrix forums
• Celebrate local wins that advance global strategy

Handoffs

• Enterprise operating model design → enterprise-strategist, coo-advisor
• Recruiting operations → talent-acquisition
• Compensation philosophy → chro-advisor
• Global engineering delivery → cto-advisor or engineering roles

Market entry and localization

Table of contents

1. Entry thesis 2. Entry modes 3. Localization dimensions 4. Phased entry playbook 5. Partners and channels at entry 6. Risks and kill criteria 7. Handoffs

Entry thesis

Before tactics, articulate a one-page country thesis:

• Why this market now (growth, regulation, competition, strategic account pull)
• Who buys (segments, use cases, willingness to pay)
• How we win (differentiation vs local and global competitors)
• What must be true (assumptions on regulation, product fit, CAC, sales cycle)
• Investment and payback horizon (link to country P&L—see in_country_pnl_and_business_planning.md)

Pair with intl-expansion when the user has not yet chosen markets; this reference assumes country is selected and execution is the task.

Entry modes

Document exit options and minimum scale to justify fixed cost of local entity.

Localization dimensions

Prioritize by revenue and risk impact—not everything at once.

Use a localization backlog ranked by ROI and regulatory must-haves; tie each item to a metric (conversion, churn, sales cycle, ticket volume).

Phased entry playbook

Phase 0 — Validate (0–3 months)

• Pilot customers or design partners; LOIs where possible
• Regulatory path confirmed with counsel (licenses, data, employment)
• Competitive win/loss patterns from comparable markets

Phase 1 — Launch (3–9 months)

• Minimum org: CM + sales/CS leads as needed
• First revenue milestone and reference customers
• Partner signed (if mode requires) with enablement plan

Phase 2 — Scale (9–24 months)

• Expand headcount against hiring plan
• Deepen localization backlog from Phase 1 learnings
• QBR rhythm stable; variance management mature

Each phase ends with a gate review: continue, pivot, or pause (see kill criteria).

Partners and channels at entry

• Define ideal partner profile (coverage, technical ability, brand fit, financial stability)
• Economic model: margin, MDF, exclusivity, termination
• Enablement: training, deal registration, co-marketing
• Audit rights and brand compliance for franchise/JV modes

Detailed partner governance continues in regulatory_partnerships_and_stakeholders.md.

Risks and kill criteria

Track leading indicators:

Kill or pause when assumptions break and HQ will not fund remediation—document factually for portfolio review.

Handoffs

• Market prioritization → intl-expansion
• Entity and tax structure → cfo-advisor + counsel
• Technical compliance implementation → compliance-engineer
• Executive narrative for HQ → ceo-advisor (when board-level)

Regulatory, partnerships, and stakeholders

Table of contents

1. Regulatory coordination (not legal advice) 2. Compliance interfaces 3. Partnership strategy 4. Channel economics and governance 5. Government and stakeholder relations 6. Industry bodies and standards 7. Documentation and audit trail 8. Handoffs

Regulatory coordination (not legal advice)

The CM coordinates regulatory work; counsel provides opinions.

Maintain a regulatory milestone tracker with owners and dates—flag slips in QBR.

Never state legal conclusions; summarize status and open questions for counsel.

Compliance interfaces

• Align country operations to global policies (security, privacy, AML if applicable)
• For technical control evidence and audits, engage compliance-engineer and compliance-specialist if in repo
• Local incidents with regulatory notification potential → escalate legal immediately
• Train country LT on speak-up, gifts, anti-bribery, and data handling

Partnership strategy

Define partnership thesis by type:

Selection criteria: capability, financial health, cultural fit, conflict risk, exit ease.

Channel economics and governance

Document for each major partner:

• Commercial terms (margin, rebates, exclusivity, territories)
• Deal registration and conflict rules
• Enablement obligations (training, certifications)
• Marketing fund use and proof-of-performance
• Termination and data return
• Audit rights (financial and brand)

Review partner performance in quarterly business reviews with clear improvement or exit paths.

Government and stakeholder relations

High-level stakeholder map:

CM sets tone and prioritization; specialized functions execute (comms, legal, GA).

For crises touching government or media, see in_country_operations_and_crisis.md.

Industry bodies and standards

• Membership in trade associations where credibility and intel justify cost
• Participate in standards working groups when product interoperability matters
• Capture competitive and regulatory intel for QBR—not lobbying without counsel

Documentation and audit trail

Keep decision records for:

• Partner approvals and exceptions
• Pricing and discount outside policy
• Regulatory submissions and responses (factual status)
• Stakeholder meetings (attendees, topics—not privileged legal strategy)

Supports audit, litigation hold, and HQ governance.

Handoffs

• Contract drafting and negotiation → commercial-counsel / legal
• Technical audit evidence → compliance-engineer
• Tax and intercompany → cfo-advisor
• Corporate development M&A → enterprise-strategist + transaction roles if present