product-lens-gcc

name	product-lens-gcc
description	Think before you build. Validate the "why," run product diagnostics, and pressure-test product direction for GCC tech companies. Specialized for Saudi Arabia, UAE, Kuwait, Qatar, Bahrain, and Oman. For product teams, leaders, and founders who want to validate before engineering starts.
origin	ECC + GCC Specialization
tier	professional
version	1

Product Lens for GCC Markets — Think Before You Build

This lane owns product diagnosis and validation, not implementation-ready specification writing.

If the user needs a durable PRD-to-SRS or capability-contract artifact, hand off to product-capability.

---

When to Use This (GCC Context)

Use this skill when:

• Before starting any feature — validate the "why" in your GCC context
• Weekly product review — are we building the right thing for our market?
• Stuck choosing between features in a GCC-specific decision
• Before a launch — sanity check the user journey for your market
• Converting vague idea into product brief before engineering planning
• Evaluating product-market fit signals in your GCC market
• Preparing pitch for GCC-focused investors
• Diagnosing why adoption is stalling in your specific market
• Comparing product strategy across different GCC markets
• Validating before pivoting to a new GCC country

Do NOT use when:

• You already have clear product-market fit signals
• You're writing a detailed PRD (use product-capability instead)
• You need engineering implementation specs
• The decision is already made (you need execution, not validation)

---

How It Works — Four Modes

Mode 1: Product Diagnostic (GCC Edition)

Like YC office hours for GCC founders. Asks hard questions tailored to your market:

CUSTOMER
1. Who is this for? (specific persona, not "businesses")
   GCC context: Saudi-first? UAE-first? Regional?
   Pain point: How is this pain GCC-specific vs. universal?

2. What's the pain? (quantify: how often, how bad, what do they do today?)
   GCC context: Is this a pain point in your specific GCC market?
   Willingness to pay: Can they afford a solution? (GCC often can)
   Regulatory: Does the pain relate to GCC regulation?

3. Why now? (what changed that makes this possible/necessary?)
   GCC context: Vision 2030 (Saudi)? UAE innovation? New regulation?
   Competitive: Are competitors moving? VC interest shifting?
   Technology: Can you solve this now that wasn't possible before?

PRODUCT
4. What's the 10-star version? (unlimited budget/time)
   GCC context: What would make this regional leader in your market?

5. What's the MVP? (smallest thing that proves the thesis)
   GCC context: Can you test with one city/country first?
   Validation: What's the minimum to get real usage signals?

6. What's the anti-goal? (what are you explicitly NOT building?)
   GCC context: What features might conflict with local regulation?
   Example: Feature that violates SAMA/DFSA/CBK rules

GO/NO-GO
7. How do you know it's working? (metric, not vibes)
   GCC context: DAU, retention, NPS, revenue/ARPU, regulatory compliance
   Timeline: What signals appear in week 1 vs. month 3?
   Threshold: At what point do we kill this if signals are weak?

Output: A PRODUCT-BRIEF.md with:

• Clear customer persona (GCC-specific)
• Quantified pain point
• Market size estimate (for your specific GCC market/countries)
• MVP definition
• Success metrics
• Go/no-go recommendation
• Top 3 risks (GCC-specific)
• Regulatory requirements (if any)

Example GO/NO-GO output:

# Product Brief: B2B Payroll Fintech for Saudi Arabia

## Customer
- Persona: HR managers at 50-500 person companies in Saudi Arabia
- Problem: Manual payroll processing takes 2 days/month, error-prone, no audit trail
- Market: Saudi Arabia (largest GCC market for this)

## Why Now
- SAMA modernizing fintech regulation (2024-2025)
- Vision 2030 creating demand for enterprise SaaS
- Competitors entering market (ADP, SAP Concur)
- No local solution optimized for Saudi regulation

## MVP
- Core: Payroll calculation, employee management, bank integration (SWIFT)
- NOT included: Time tracking, HR analytics, advanced reporting
- Scope: 4 weeks to build

## Success Metric
- 10+ paying customers (Saudi) in first 3 months
- 70%+ D30 retention
- $500+ MRR minimum

## Risks
1. SAMA regulatory approval timeline unknown
   - Mitigation: Engage SAMA in week 1
2. Bank API integrations slow
   - Mitigation: Partner with Telr/2Checkout instead of direct
3. Competitors with global brand (ADP)
   - Mitigation: Focus on Saudi-specific compliance

## Recommendation
→ GO, contingent on SAMA regulatory clarity in 4 weeks
   If SAMA says "too risky" → Pivot to compliance tool first

---

Mode 2: Founder Review (GCC Edition)

Reviews your current product through a founder lens, GCC-focused:

CONTEXT
1. Read: README, current pitch, recent PRs, metrics dashboard
2. Infer: What are we building? For which GCC market?
3. Assess: Are we solving for GCC-specific needs or generic problem?

PRODUCT-MARKET FIT SIGNALS (0-10 score)
4. Usage growth trajectory
   GCC context: Monthly growth rate? Active retention?
   Segmentation: Which countries/segments growing fastest?

5. Retention indicators
   GCC context: D30 retention (30-day)? Weekly repeat usage?
   By country: Is retention strong in Saudi but weak in UAE?

6. Revenue signals (if applicable)
   GCC context: ARPU by country? Payment method success?
   Pricing: Is pricing optimized for GCC willingness to pay?

7. Competitive moat
   GCC context: What's hard to copy in YOUR market?
   Regulatory: Does regulation protect your position?
   Partnerships: Any exclusive deals (with banks, telecom)?

8. Investor appetite
   GCC context: Are GCC-focused funds interested?
   Signals: What's coming from recent fundraising conversations?

PRODUCT QUALITY
9. Onboarding friction
   GCC context: Is setup culturally appropriate for your market?
   Language: Is Arabic as smooth as English?
   Payment: Are local payment methods integrated?

10. Feature completeness
    GCC context: Are you building features GCC users want?
    Not Western features that don't fit your market?

STRATEGIC
11. The one thing that would 10x this
    GCC context: Is it a feature, a market, a partnership, a pivot?

12. Things you're building that don't matter
    GCC context: Features only Western users want?
    Overengineering for your actual usage patterns?

13. Market positioning
    GCC context: Competing on price, quality, local trust?
    Your defensible position in YOUR market?

Output: Diagnostic report with:

• Product-market fit score (0-10)
• Growth trajectory assessment
• Retention health by country
• Revenue optimization opportunities (if applicable)
• Competitive analysis (who's winning in your GCC market?)
• Top 3 quick wins
• Top 3 strategic bets
• Red flags to address immediately
• "One thing that would 10x this" recommendation

---

Mode 3: User Journey Audit (GCC Edition)

Maps the actual user experience, optimized for GCC context:

ONBOARDING
1. Clone/install/signup as a new user
   GCC context: Does onboarding work on Middle Eastern networks?
   Language: Is Arabic copy correct? (not machine-translated)
   Cultural: Are screenshots/examples culturally appropriate?

2. Document every friction point
   GCC context: Errors, confusing steps, missing docs, payment issues
   Language: Confusing because of translation vs. UX?
   Localization: Phone numbers, addresses, payment methods

3. Time each step
   GCC context: How long until first "aha" moment?
   Compare: How does this compare to competitors in your market?

4. Cultural appropriateness
   GCC context: Is the tone/imagery respectful?
   Payment: Are Aramex, 2Checkout, local banks supported?
   Privacy: Does copy address GCC data privacy concerns?

5. Compare to competitors
   GCC context: Is competitor onboarding faster?
   Regional players: What do successful local products do?

6. Score: Time-to-value
   GCC context: Minutes until first win? Hours?
   Benchmark: Is this industry-standard for GCC users?

7. Recommend: Top 3 onboarding fixes
   GCC context: What's the highest-leverage fix?
   Quick wins: Can you implement in 1 sprint?

Output:

• Friction map (step by step with screenshots)
• Time-to-value assessment
• Competitive comparison (by country)
• Top 3 onboarding fixes (with effort + impact estimate)
• Cultural appropriateness score
• Localization gaps (Arabic, payments, etc.)

---

Mode 4: Feature Prioritization (GCC Edition)

When you have 10 ideas and need to pick 2:

EVALUATION
1. List all candidate features
   GCC context: Which solve GCC-specific problems?
   Which are "Western users asked for them"?

2. Score each on:
   Impact (1-5): How much does this move the needle?
   GCC context: Is impact different across Saudi vs. UAE?
   
   Confidence (1-5): How sure are you this is the right solution?
   GCC context: Have GCC users actually asked for this?
   
   Effort (1-5): How long to build?
   GCC context: Does localization add effort?

3. Calculate: ICE score = (Impact × Confidence) ÷ Effort

4. Apply constraints:
   Runway: How many sprints until we need revenue?
   Team: Do we have the skills to build this?
   Dependencies: Does this block other work?
   Regulatory: Any GCC compliance requirements?
   Strategic: Moves toward our vision?

5. GCC-specific factors:
   Which feature matters in Saudi but not UAE?
   Do we need different features per country?
   Is this a competitive blocker in our market?

6. Output: Prioritized roadmap with rationale

Output:

• ICE scores for each feature
• Prioritized roadmap (next 3 quarters)
• Rationale per feature
• GCC market considerations
• Dependencies flagged
• Effort estimates

Example:

# Feature Prioritization: Q2 2025

## Priority 1: Arabic Localization ✅
- ICE Score: 12.5 (Impact 5, Confidence 5, Effort 2)
- GCC impact: +3 Saudi, +3 UAE, +2 Kuwait, +2 Qatar, +2 Bahrain
- Why: Users constantly request Arabic-first experience
- Start: Week 1 | Owner: Product lead
- Block: Cannot launch in these markets without this

## Priority 2: Payment Method Integration 🎯
- ICE Score: 10.0 (Impact 4, Confidence 5, Effort 2)
- GCC impact: +3 Saudi, +3 UAE, +2 Kuwait
- Why: 40% users abandon at payment (only CC supported)
- Add: Apple Pay, Samsung Pay, local debit cards
- Start: Week 2 | Owner: Backend lead

## Priority 3: User Reviews System 📊
- ICE Score: 7.5 (Impact 4, Confidence 4, Effort 2.5)
- GCC impact: +3 Saudi, +2 UAE (trust-driven markets)
- Why: Competitors all have reviews; conversion increases
- Start: Week 4 | Owner: Frontend lead

## Rejected This Quarter (Why)
- Chat/Messaging: ICE 1.5 (users haven't asked for it)
- Advanced Reporting: ICE 2.0 (can wait; focusing on core)
- Referral Program: ICE 3.0 (growth not the bottleneck)

## Dependencies
- Payment integration → Localization
  (Need payment methods before making Arabic version)
- Localization → Regional expansion
  (Can't launch in new countries without Arabic)

---

GCC-Specific Product Standards

Standard 1: Market Entry Checklist

If you're entering a new GCC market:

□ Have you researched the regulatory environment?
  - Saudi: SAMA (payments), CMA (capital markets), SFDA (food/pharma)
  - UAE: DFSA (fintech), SCA (securities), ADAGM (ADM businesses)
  - Kuwait: CBK (payments), CMA (fintech), fast-moving
  - Qatar: Qatar Central Bank, Ministry of Commerce
  - Bahrain: CBB (fintech hub), BAPCO (innovative regulator)
  - Oman: State Bank, modern/less restrictive

□ Do you know which payment methods work in this market?
  - Credit cards? Apple Pay? Samsung Pay? Local cards?
  - Cash on delivery? Bank transfer? E-wallet preferences?

□ Have you identified the gatekeeper in this market?
  - Is it government procurement? Telecom partnerships?
  - Marketplace (Noon, Amazon)? Direct sales?

□ Do you have local hiring plan?
  - Can you launch day 1 or do you need local team first?

□ What's the regulatory timeline?
  - Approval needed? How long? Can you operate conditionally?

□ What's different about this market vs. your current one?
  - Customer behavior? Pricing expectations? Competition?
  - Government support? VC interest?

Standard 2: GCC Product-Market Fit Signals

Track these metrics by country:

USAGE (by country)
- DAU/MAU by country (Saudi, UAE, Kuwait, Qatar, Bahrain, Oman)
- Cohort retention by country (D7, D30, D90)
- Feature adoption by country (is feature X used only in Saudi?)

REVENUE (by country, if applicable)
- ARPU by country (are Saudi customers worth more?)
- Payment method success rate by country
- Churn by payment method
- Willingness to pay (Saudi willingness > Kuwait willingness?)

ENGAGEMENT (by country)
- NPS by country (do GCC users love this?)
- Support ticket volume (is support quality valued?)
- Review sentiment (app store reviews, Twitter sentiment)

COMPETITIVE
- Share of voice in each market
- Customer acquisition cost by country
- Incumbent threat level per market

REGULATORY
- Compliance incidents
- Regulatory feedback from CBK, SAMA, DFSA, etc.
- Approval timelines for new features

Standard 3: GCC Country Profiles

Reference this when thinking about market dynamics:

Saudi Arabia (KSA)

• Largest market by size and willingness to pay
• Heavy government regulation (SAMA, CMA)
• Vision 2030 creates innovation tailwinds
• Highly competitive (VC abundant)
• Expect: Government relationships matter
• Risk: Regulation changes quickly
• Product implication: Compliance-first approach

United Arab Emirates (UAE)

• Hub for regional expansion
• Advanced regulatory framework (DFSA, SCA, ADAGM)
• Fast-moving competition
• Strong talent and partnership ecosystem
• Expect: Sophisticated customers, high standards
• Risk: High CAC (Dubai density = high cost)
• Product implication: Quality and polish matter

Kuwait

• Government-driven market (procurement, Vision 2035)
• Strong banking sector
• Growing startup interest
• Smaller but loyal customer base
• Expect: Longer sales cycles for B2B
• Risk: Market size limitations
• Product implication: B2B focus, government relationships

Qatar

• Doha-centric market (80% of economy)
• Government planning focus
• Strong sovereign wealth (Qatar Investment Authority)
• Emerging tech ecosystem
• Expect: Government backing if aligned
• Risk: Smaller talent pool
• Product implication: Government partnerships valuable

Bahrain

• Regional fintech hub
• Regulatory innovation leader (BAPCO)
• Strong B2B finance sector
• Growing e-commerce
• Expect: Fintech focus, regulatory openness
• Risk: Consumer market is small
• Product implication: B2B focus, fintech specialization

Oman

• Emerging market (lower competition)
• Government modernization efforts (Vision 2040)
• Growing e-commerce adoption
• Smaller investor base
• Expect: Less crowded, more opportunity
• Risk: Slower growth rate
• Product implication: Growth opportunity, patient capital

---

Output Templates

Template 1: PRODUCT-BRIEF.md

# Product Brief: [Feature/Product Name]

## Customer
- Persona: [Specific person, not generic]
- GCC Market(s): [Saudi/UAE/Kuwait/etc.]
- Problem: [Quantified: how often, how bad, what do they do today?]

## Why Now
- Market signal: [Vision 2030 / Regulation / Competition / Technology]
- Timing: [Why now vs. 1 year ago?]

## MVP
- Definition: [Smallest thing that proves thesis]
- Scope: [What's included / not included]
- Success metric: [Specific KPI, not "users will like it"]
- Timeline: [Weeks to build]

## Risks (GCC-specific)
1. [Risk type]: [Description] → Mitigation: [Action]
2. [Risk type]: [Description] → Mitigation: [Action]
3. [Risk type]: [Description] → Mitigation: [Action]

## Recommendation
- GO / NO-GO / PIVOT
- Rationale: [Why this recommendation?]
- Next steps: [If GO, what's the very first task?]

Template 2: FOUNDER-REVIEW.md

# Product Review: [Your Product]

## Product-Market Fit Score: [X/10]

### Growth
- Trajectory: [Monthly growth rate]
- By country: [Saudi, UAE, Kuwait rankings]
- Comparison: [How does this compare to benchmarks?]

### Retention
- D30: [Percentage]
- By country: [Which country sticks best?]
- By segment: [Which user type sticks?]

### Revenue (if applicable)
- MRR: [$]
- ARPU: [$]
- By country: [Which pays more?]
- Growth: [MoM growth %]

### Competitive Moat
- What's hard to copy: [Specific advantage]
- Regulatory protection: [Are rules helping us?]
- Partnerships: [Any exclusive deals?]

### GCC-Specific Insights
- Best performing market: [Country name]
- Worst performing market: [Country name]
- Why the difference: [Analysis]
- Language impact: [Arabic vs. English adoption?]
- Payment method impact: [Which methods converting?]

### Top 3 Opportunities
1. [Specific action] — Impact: [High/Medium/Low] — Effort: [High/Medium/Low]
2. [Specific action] — Impact: [High/Medium/Low] — Effort: [High/Medium/Low]
3. [Specific action] — Impact: [High/Medium/Low] — Effort: [High/Medium/Low]

### Top 3 Red Flags
1. [Concern] — Urgency: [High/Medium/Low] — Fix: [Action]
2. [Concern] — Urgency: [High/Medium/Low] — Fix: [Action]
3. [Concern] — Urgency: [High/Medium/Low] — Fix: [Action]

### One Thing That Would 10x This
- Insight: [Specific idea]
- Why: [Rationale]
- Timeline: [When?]
- Resources: [What do we need?]

Template 3: USER-JOURNEY-AUDIT.md

# Onboarding Audit: [Product Name]

## Time-to-Value
- Signup to first win: [X minutes]
- Competitive benchmark: [Y minutes]
- Assessment: [Is this good?]

## Friction Points (Step-by-Step)
1. [Step name] → [Friction] → [Impact on users]
2. [Step name] → [Friction] → [Impact on users]
3. [Step name] → [Friction] → [Impact on users]

## Localization Assessment
- Language: [What's broken in Arabic?]
- Payment: [Missing payment methods?]
- Cultural: [Anything tone-deaf?]
- Accessibility: [RTL layout issues?]
- Compliance: [GCC privacy/data rules?]

## Competitive Comparison
| Step | Your Product | Competitor A | Competitor B |
|------|--------------|--------------|--------------|
| Signup | 2 min | 1 min | 2 min |
| Setup | 3 min | 2 min | 4 min |
| First action | 5 min | 3 min | 4 min |
| **Total** | **10 min** | **6 min** | **10 min** |

## Top 3 Fixes (Prioritized)
1. [Fix description]
   - Effort: [Days/weeks]
   - Impact: [High/Medium/Low]
   - Owner: [Name]
   
2. [Fix description]
   - Effort: [Days/weeks]
   - Impact: [High/Medium/Low]
   - Owner: [Name]
   
3. [Fix description]
   - Effort: [Days/weeks]
   - Impact: [High/Medium/Low]
   - Owner: [Name]

Template 4: PRIORITIZATION.md

# Feature Prioritization: [Q1/Q2/Q3]

## Roadmap

### Priority 1: [Feature Name]
- ICE Score: [X]
- Impact in GCC: [Which countries benefit most?]
- Timeline: Start [Week X], Duration [Y weeks]
- Owner: [Name]
- Why: [One sentence rationale]

### Priority 2: [Feature Name]
- ICE Score: [X]
- Impact in GCC: [Which countries benefit most?]
- Timeline: Start [Week X], Duration [Y weeks]
- Owner: [Name]
- Why: [One sentence rationale]

### Priority 3: [Feature Name]
- ICE Score: [X]
- Impact in GCC: [Which countries benefit most?]
- Timeline: Start [Week X], Duration [Y weeks]
- Owner: [Name]
- Why: [One sentence rationale]

## Rejected This Quarter (Why)
- [Feature]: ICE [X] — Reason: [Not GCC priority / Can wait / Dep missing]
- [Feature]: ICE [X] — Reason: [Engineering too complex / VC not asking]

## Dependencies
- [Feature X] blocks [Feature Y]
- [Regulatory approval] needed before [Launch Z]
- [Partnership deal] needed before [Feature W]

---

Quality Gate Checklist

Before recommending "GO" on a product initiative:

CUSTOMER CLARITY
□ Can you describe your customer in one sentence?
□ Have 5+ GCC customers told you they have this problem?
□ What do they currently do (before your product)?
□ How often do they experience this pain?

MARKET UNDERSTANDING
□ Do you understand which GCC market(s) this matters in?
□ Have you researched regulations for this market?
□ What payment methods do your customers use?
□ Is there a competitor already doing this?

MVP CLARITY
□ Can you build this in 4 weeks or less?
□ Is the MVP defensible (something works you can't break)?
□ Is there a specific metric that proves success?
□ What happens if you're wrong about this?

RESOURCE CLARITY
□ Do you have the team to build this?
□ Is this aligned with your company strategy?
□ What else would this delay?
□ Is there a GCC-specific blocker?
  (regulatory, payment, partnership, government)

STRATEGIC CLARITY
□ Why this feature now vs. later?
□ If this works in Saudi, can it work in UAE?
□ What's the next feature after this?
□ What's the off-ramp if this doesn't work?

---

Common GCC Product Mistakes (Avoid These)

Mistake 1: Building Western features without GCC adaptation

• Problem: "Payment is USD-only" in a SAR market
• Fix: Localize payment before launch, not after

Mistake 2: Not understanding regulatory differences

• Problem: Feature works in UAE, illegal in Saudi
• Fix: Research SAMA, DFSA, CBK rules per market BEFORE building

Mistake 3: Assuming all GCC markets are the same

• Problem: Saudi pricing = UAE pricing = Kuwait pricing
• Fix: Segment by country; willingness to pay differs

Mistake 4: Slow onboarding (>5 minutes to first value)

• Problem: Takes 15 minutes to get first value
• Fix: GCC users want instant gratification; optimize to <5 min

Mistake 5: Missing payment methods

• Problem: Only credit card; users want Apple Pay / local methods
• Fix: Research payment methods per country BEFORE launch

Mistake 6: Ignoring regulatory feedback early

• Problem: Build for 6 months, then regulator says "not allowed"
• Fix: Engage with CBK/SAMA/DFSA in MONTH 1, not month 6

Mistake 7: Not understanding GCC-specific job-to-be-done

• Problem: Solving US problem; GCC customer has different job
• Fix: User research in your market, not Western playbooks

Mistake 8: Language is not just translation

• Problem: Machine-translated Arabic copy feels wrong
• Fix: Native Arabic speaker reviews ALL copy before launch

---

When to Say "No, Don't Build This"

Product Lens recommends NO-GO when:

1. Customer pain is not quantified
   (Vibes ≠ evidence)

2. Regulatory blockers exist
   (SAMA says no → You can't build this)

3. No clear MVP
   (Project scope creeps to 6 months; too risky)

4. Competitive moat is unclear
   (Why can't someone copy this in 4 weeks?)

5. Success metric is unmeasurable
   ("Users will love it" ≠ metric)

6. Market is wrong timing
   (Good idea, wrong year for this market)

7. You're wrong customer/market
   (Built for Western users; GCC users have different need)

8. Regulatory timeline too uncertain
   (SAMA approval could take 12 months; can't wait)

When you get a NO-GO, the recommendation is:

• Pivot: Different market / customer / solution
• Research: Do more user research before building
• Wait: Right idea, wrong timing
• Kill: Not worth pursuing right now

---

Integration with Other Skills

Pair with:

• Product Capability — When product brief becomes implementation-ready spec
• Token Budget Advisor — Control diagnostic depth (quick vs. exhaustive)
• Market Research GCC — When you need deep market data to inform decisions
• Knowledge Ops — Store product decisions for quarterly review
• Research Ops — Validate competitive positioning before launch

---

Summary: Product Lens for GCC

What: Product diagnosis and validation for GCC tech companies
When: Before building, weekly reviews, before launch, before pivoting
How: 4 modes (diagnostic, founder review, journey audit, prioritization)
Output: Actionable briefs with clear go/no-go and next steps
GCC Context: Every recommendation factors in market dynamics, regulation, customer behavior

Use this to validate before you build, not to write PRDs.

Once Product Lens says "GO," hand off to product-capability for the detailed specification.

---

Reference: GCC Markets at a Glance

Market	TAM	Growth	Competition	Regulation	Best For
Saudi	Largest	22%	High	Strict (SAMA)	Enterprise, Fintech
UAE	#2	18%	Very High	Advanced (DFSA)	B2C, Regional
Kuwait	#3	19%	Medium	Traditional	Gov, B2B
Qatar	Smaller	15%	Low	Modern	Enterprise, Gov
Bahrain	Fintech hub	17%	Low	Progressive	Fintech
Oman	Emerging	16%	Very Low	Modern	Growth opp.