Market Entry & Geographic Expansion Questions

Approach summary: compute annual gross transaction value (GTV) as baseline TAM (everyone with smartphones uses the wallet), then narrow to realistic serviceable and obtainable markets (SAM, SOM). Show both top‑down (broad penetration assumptions) and bottom‑up (adoption cohorts / take‑rate) with assumptions and validation steps.

Top‑down (annual GTV basis)

• Population adults = 40,000,000
• Smartphones = 40M * 70% = 28,000,000
• Monthly tx per active user = 3, avg value = $25 → monthly spend/user = 3 * $25 = $75
• Annual spend/user = $75 * 12 = $900
• TAM (if all smartphone users are active) = 28,000,000 * $900 = $25,200,000,000 (~$25.2B)

Make realistic narrowing:

• SAM (share of payments that realistically become digital-wallet transactions) assume 50% of current spend shifts → SAM = 0.5 * TAM = $12.6B
• SOM (achievable in 3 years) assume 10% market share of SAM → SOM = 0.1 * $12.6B = $1.26B

Bottom‑up (adoption-driven)

• Assume Year 1 adoption = 20% of smartphone users active → users = 0.2 * 28M = 5.6M
• Year1 GTV = 5.6M * $900 = $5,040,000,000 ($5.04B)
• If you measure SOM as Year1 GTV → $5.04B; if you measure revenue, use take‑rate. Example take‑rate = 1% → Year1 revenue = $5.04B * 1% = $50.4M
• 3‑year projection: adoption rises to 50% → users = 14M → GTV = 14M * $900 = $12.6B (matches SAM above). With 1% take‑rate, revenue = $126M.

Key assumptions

• “Active user” = user making 3 wallet transactions/month
• All smartphone users are potential users for TAM
• 50% of total transaction volume can migrate to wallets (SAM)
• Adoption curve: 20% Year1, 50% Year3
• Take‑rate (fee) = 1% for revenue calcs

How to validate with market research

• Quantitative: central bank / payments network data for total national transaction volume and electronic payment penetration; telecom & smartphone usage reports; competitor transaction volumes.
• Primary research: representative consumer surveys on payment habits, willingness to adopt, frequency; merchant surveys on acceptance and fees.
• Experiments: run a pilot in a city/segment, measure activation, retention, frequency; A/B pricing on fees and incentives.
• Partner data: banks, telcos, PSPs can share transaction counts and merchant coverage.
• Cross‑checks: benchmark against similar countries’ wallet adoption rates, cohort retention, and take‑rates.

Use these inputs to iterate assumptions, produce sensitivity ranges (best/likely/worst) and present TAM/SAM/SOM as ranges rather than single points.

Definitions & formulas:

• Revenue R = ARPU * N
• Total variable cost V = v * N (v = variable cost per user)
• Contribution C = R - V = (ARPU - v) * N
• Contribution margin per user = m = ARPU - v
• Contribution margin ratio = m / ARPU
• Gross margin (%) = (R - V) / R = contribution margin ratio
• Profit (Net operating) = C - Fixed

Given: Fixed = $500,000/mo, v = $0.30, ARPU = $1.00

Break-even users:

• Solve m * N = Fixed → N_break = Fixed / (ARPU - v) = 500,000 / 0.70 ≈ 714,286 users

Compute key points:

1. N = 100,000

• R = $100,000; V = $30,000; C = $70,000
• Gross margin = 70%; Profit = 70,000 - 500,000 = -$430,000 (loss)

2. N = 500,000

• R = $500,000; V = $150,000; C = $350,000
• Gross margin = 70%; Profit = 350,000 - 500,000 = -$150,000

3. N = 714,286 (break-even)

• R ≈ $714,286; V ≈ $214,286; C ≈ $500,000; Profit ≈ $0

4. N = 1,000,000

• R = $1,000,000; V = $300,000; C = $700,000
• Gross margin = 70%; Profit = 700,000 - 500,000 = $200,000

Sensitivity analysis (examples):

• If ARPU falls to $0.90 (v still $0.30): m = $0.60 → N_break = 500,000 / 0.60 ≈ 833,333 users.
• If variable cost rises to $0.40 (ARPU = $1.00): m = $0.60 → N_break ≈ 833,333.
• If both happen (ARPU $0.90, v $0.40): m = $0.50 → N_break = 1,000,000.

Implications & recommendations:

• Gross margin ratio fixed at (ARPU - v)/ARPU; here 70% constant for base case—scales linearly with ARPU and v.
• Key levers: increase ARPU (pricing, monetization), reduce v (optimize infra, batching), or cut fixed costs. Prioritize actions with fastest impact on m to reduce break-even users. Track cohort ARPU and marginal cost per feature to ensure scalable unit economics.

As a PM evaluating channel partners quickly, I focus on five high-impact criteria and a compact 30-minute discovery checklist that surfaces fit, risk, and next steps.

1. Strategic fit

• Question: Which customer segments and use cases do you target?
• Capture: overlap with our ICP (%), verticals, win themes
• Red flag: no clear ICP or conflicting priorities

2. Market reach & performance

• Question: Typical deal size, monthly/quarterly pipeline, ARR influence?
• Capture: active accounts, geographies, sales motions (inside/field)
• Red flag: tiny pipeline, no traction in our target regions

3. Technical compatibility

• Question: Integration capabilities, API experience, SSO/SCIM needs?
• Capture: integration model, timeline estimate, support SLA expectations
• Red flag: closed/proprietary stack or no integration team

4. Operational capability & enablement

• Question: Sales/CS onboarding process, certifications, enablement cadence?
• Capture: enablement lead time, demo capability, marketing co-op
• Red flag: no training process or high churn in partner reps

5. Commercial & legal viability

• Question: Pricing expectations, discounting policy, compliance requirements?
• Capture: typical margins, contract term needs, data/privacy constraints
• Red flag: unrealistic margin demands or unresolved compliance gaps

30‑minute call structure (timebox):

• 0–3m: quick intros & objective of call
• 3–10m: strategic fit + market reach (questions above)
• 10–18m: technical compatibility deep-dive
• 18–25m: ops, enablement, commercial terms
• 25–30m: red flags, mutual next steps, timeline

Decision rule (pass/fail thresholds):

• Pass: ≥3 criteria strong, no major red flags on tech/compliance, clear pilot plan
• Conditional: 2 strong + one mitigatable concern (requires follow-up)
• Fail: major tech/compliance/legal blocker or no ICP overlap

Deliverable after call: 1‑page partner scorecard (criteria scores, top risks, recommended next step: pilot, legal review, or decline).

Recommendation: Hybrid with partner-first bias. Because resellers control ~60% share and sales cycles average six months, leaning on established channel partners accelerates market reach and credibility while preserving direct engagement for strategic accounts and product feedback.

Rationale and trade-offs:

• Time-to-market: Partner-first shortens reach—resellers already have relationships and distribution. Direct is slower (building team, trust). Hybrid lets partners drive broad adoption while direct team handles key strategic or complex deals to unblock partners.
• Margin: Partners take margins (lower net per seat). Direct sales capture full margin but incur higher fixed costs (sales salaries, ops). Hybrid balances by using partners for volume, direct for high-margin enterprise sales.
• Control: Direct gives strongest product/price/control. Partners reduce control over messaging and customer experience. Mitigate via clear SLAs, co-selling agreements, and certification.
• Enablement costs: Partner enablement (training, MDF, certification) is substantial but scalable. Direct sales requires higher per-deal support (SEs, pilots). Budget for both but front-load partner enablement for faster ROI.
• Brand: Partners can amplify brand quickly but risk inconsistent positioning. Invest in co-marketing assets, joint PR, and brand guidelines.
• Strategic alignment: Use partner tiers (Gold/Platinum) and incentives for priority behaviors (new-logo acquisition, upsell).

Operational plan (90–180 days):

1. Identify top 5–10 resellers covering 70% of channel reach; run a pilot with preferred incentives.
2. Build partner kit: playbooks, demo tenants, pricing, battlecards, and 1-day certification.
3. Establish co-sell model: handoff criteria, SLAs, and joint account plans.
4. Hire 2-3 channel account managers and a partner engineer to scale enablement.
5. Iterate based on pilot metrics; expand tiered program.

KPIs to track partner performance:

• Revenue and % of total revenue (monthly/quarterly)
• Pipeline generated by partner (value & velocity)
• Win rate and average deal size (partner vs direct)
• Time-to-close (deal cycle length)
• New logos acquired
• Product attach / upsell rate
• Partner enablement metrics: certifications completed, deal registration uptake, MDF utilization and ROI
• Customer satisfaction / NPS for partner-sourced accounts
• Churn rate of partner-sourced customers

Success criteria: within 6–12 months, partners should drive majority of new logos in target segments, maintain win rates within 10% of direct, and show positive MDF ROI. Use this data to recalibrate split between partner-led and direct motion.

1. Territory and Exclusivity

• Purpose: Defines the geographic scope (country, regions, channels) where the reseller may sell and whether they have exclusive rights. Prevents channel conflict, aligns GTM coverage, and sets expectations for market investments.

2. Pricing, Discounts and MAP (Minimum Advertised Price)

• Purpose: Specifies wholesale pricing, allowed discount structures, MAP policy and invoicing terms. Protects margins, brand positioning, and prevents price erosion that can harm product perception.

3. Performance SLAs and Sales Targets (KPIs)

• Purpose: Sets measurable targets (sales quotas, pipeline, onboarding milestones) and remediation for underperformance. Encourages partner commitment, enables performance review, and ties incentives or renewal to results.

4. Compliance, Data Protection and Regulatory Requirements

• Purpose: Ensures the reseller follows local laws (export controls, privacy, tax, labeling) and product compliance. Reduces legal risk and ensures data handling aligns with company policies and local regulation (e.g., GDPR-equivalents).

5. Term, Termination and IP/Licensing Rights

• Purpose: States contract length, renewal mechanics, termination rights (for cause/without cause), and clarifies IP ownership, branding, and permitted use of trademarks. Protects company IP, provides exit paths, and reduces post-termination disputes.

Optional add-on: Confidentiality & Liability limits — often included or referenced to protect sensitive info and cap exposure.