Personas — who buys PC parts in Lebanon¶
Reference for the audiences that shape 961tech's design, copy, and monetisation choices. Produced for Foundation: target audience + persona research (#36).
1. Scope & method¶
1.1 What this is / isn't¶
What this is. A reference for the six personas that shape 961tech's design, copy, and monetisation choices. Six structured profiles followed by cross-cutting analysis and ticket-level design implications. Format mirrors competitive-landscape.md so the two reference docs read as a coherent pair.
What this isn't. Not market sizing — covered in Specs → 2026-04-25 aggregator design §2.2. Not a feature spec — that lives in #28 page design. Not validated primary research — see §1.2 for method and §1.3 for honest limits. Personas land as defensible hypotheses with explicit post-launch validation paths in §7, not as survey-grade segmentation.
1.2 Method¶
Sources used. In order of weight:
competitive-landscape.md— already established Lebanese-context findings (§4.1-§4.6) including retailer-direct UX teardowns, FB / Steam / Discord community surface, SERP language analysis, Pricena's deliberate Lebanon skip, and "your guy" commerce patterns- Specs → 2026-04-25 aggregator design — original spec's Stream 1 Lebanese research and Stream 2 global benchmarking
- MASTER's first-hand knowledge as a Lebanese PC buyer and an areeba backend developer with daily exposure to Lebanese SMB tech behavior
- Public Lebanese retailer UX (PCAndParts, 961Souq, Macrotronics, GammaLB, plus the long-tail list in competitive §4.4) — directly observable
- Lebanese demographic baselines: 5.34M population, banking-crisis-era cash dominance, post-2019 lollar / fresh-USD bifurcation, ~89,500 LBP/USD rate, ~14M diaspora abroad
Sources deliberately not used.
- Surveys, polls, or outreach — out of scope for this pass; validation happens post-launch via telemetry (§7).
- Pricena's internal traffic data — not public.
- WhatsApp / Instagram retailer DMs — would require posing as a buyer; ethically thin.
- Retailer sales figures — confidential.
1.3 Honest limits + confidence taxonomy¶
Honest limits. Most claims in this doc are Hypothesis-grade — defensible from competitive precedent + Lebanese demographics + adjacent evidence, but not directly observed via interviews or telemetry. The §7 register captures every claim that should be probed post-launch.
Confidence taxonomy. Three buckets, applied consistently:
| Mark | Meaning | Bar |
|---|---|---|
| High | Directly evidenced by competitive-landscape, retailer UX teardown, SERP results, public Lebanese community signals, or first-hand observation | "I can point to the source line" |
| Hypothesis | Reasoned from competitive precedent + Lebanese demographics + adjacent evidence; defensible but not directly evidenced | "This is what I'd expect; I can't point to a Lebanese-specific source" |
| Untested | Assumption with no current evidence; included because the persona is incomplete without a value, but flagged | "I'm guessing" |
Inline within prose, claims that are Hypothesis or Untested end with an italic tag — (hypothesis) or (untested). High-confidence claims are unmarked; silence is the High signal, to keep the doc readable.
1.4 How to read this doc¶
- For a quick scan, read §2 (the personas-at-a-glance table) and §6 (design implications by ticket).
- For deep persona context, read §3 (primary) and §4 (secondary).
- For cross-cutting design pressure on a specific ticket (#28, #33, #37, #41, #43), jump to the matching subsection in §5 or §6.
- For "what should I probe post-launch?", read §7.
Each persona profile in §3-§4 ends with a Design implications block keyed to downstream tickets. §6 deduplicates these into ticket-level implication lists with persona attribution. If the same insight appears in both, §6 is the canonical statement.
2. Personas at a glance¶
A scannable map of the six personas. Primary personas (full profiles in §3) precede the separator; secondary (compressed profiles in §4) follow.
| Tier | Persona | Age | Budget | Languages | Device profile | Payment | Decision style | Primary channel today | Key pain |
|---|---|---|---|---|---|---|---|---|---|
| Primary | Karim the gamer | 18-26 | Tight ($600-1.5k builds) | English | Phone + family/own desktop | Cash, OMT, Whish | Specs-first (FPS/$) | PCAndParts + FB Lebanon PC Gamers | No price comparison; stock anxiety |
| Primary | First-time builder | 17-30 | Tight-Mid ($800-1.8k) | English | Phone-heavy; aspires to own desktop | Cash, OMT, Whish, family card | Trust-first → specs-first as confidence grows | YouTube tutorials + WhatsApp friend who builds | Compat anxiety, jargon overload |
| Primary | Casual parts customer | 20-50 | Variable ($100-2k) | English | Phone primary | Cash, card if available, Whish | Brand-first / price-first | PCAndParts + 961Souq (categories: laptops, monitors, peripherals) | Forced into builder UX they don't want |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Secondary | Office IT buyer | 30-55 | Mid-Comfortable ($5k-30k batch) | English (FR for older) | Desktop primary; phone for WhatsApp | Bank transfer, company card, COD | Trust-first + relationship-led | Direct retailer rep on WhatsApp | No batch quoting tool, manual reconciliation |
| Secondary | Layla the content creator | 24-35 | Mid ($1.5k-3k) | English (FR passive read) | Mac or aspiring Mac; phone for socials | Card, Whish, fresh-USD cash | Reliability-first; brand-aware | Macrotronics / 961Souq + Apple resellers + IG creator communities | Spec opacity, weak filtering on creator-relevant dims |
| Secondary | Diaspora buyer | 28-55 | Mid-Comfortable ($800-3k) | English | Desktop abroad + phone | Foreign card, Western Union, OMT to family | Trust-first + delegation | Direct retailer on WhatsApp + family middleman | Payment friction, delivery routing, currency anxiety |
Reading the table. Each cell is a hypothesis grounded in §3-§4. Where a cell looks crisp, the underlying profile flags any Hypothesis / Untested claims explicitly. Where a cell is ambiguous, the profile narrative resolves it.
3. Primary personas¶
3.1 Karim the gamer — the loud organized cohort¶
Lebanese-Lebanese male, 18-26, in university or first job, gaming-focused, tight budget, fluent English with French passive read. Lives on the PCAndParts product grid and Lebanon PC Gamers Facebook group. The most visible Lebanese PC-buyer cohort and the persona 961tech's M1 build flow most obviously serves.
| Dimension | Value |
|---|---|
| Age range | 18-26 |
| Income tier | Tight ($600-1,500 per build; $200-500 per upgrade cycle) |
| Languages | English (primary, default for everything tech). French (passive read for francophone subset; not load-bearing). |
| Device profile | Mid-range Android phone primary; family desktop or own previous-gen desktop for serious browse |
| Connection | Mobile data (3G/4G common, 5G in central Beirut); home fiber if Beirut and family can afford it; sketchy outside Mount Lebanon |
| Payment habits | Cash dominant; OMT for in-country transfers; Whish for friends-and-family P2P; rare card use post-2019 |
| Price tier they shop | $600-1,500 full build; \(200-500 GPU/CPU upgrade; <\)100 peripheral upgrade |
| Decision style | Specs-first, FPS-per-dollar oriented; brand-aware on GPU (NVIDIA over AMD by reputation, hypothesis) and PSU (Corsair / EVGA / Seasonic, hypothesis) |
| Where they shop today | PCAndParts (price leader, §4.4) → 961Souq (specs research) → FB Marketplace + Olx (used parts) → WhatsApp groups (informal price intel) |
| Confidence | Hypothesis (overall persona structure is well-grounded; specific behaviors per cell vary in confidence) |
Motivations. Karim's PC is identity, hobby, and one of the few Lebanese-affordable serious leisure goods. Post-2019 banking crisis collapsed disposable income, but a $1,000 build that runs Valorant at 240 FPS or Cyberpunk at 1440p is still achievable on local prices and lasts 4-5 years. Gaming is a social good — Lebanon PC Gamers and Lebanese Gamers Esports communities (competitive doc §4.3) are real cohorts with regular activity. Karim wants to win arguments about FPS-per-dollar in Discord and to not feel ripped off by retailer markups.
The price-comparison gap is felt acutely. PCAndParts is dominant + cheapest, but Karim has no fast way to verify that on a part-by-part basis — he checks 961Souq, Macrotronics, occasionally posts in FB groups asking "X price at Y store?" The work of cross-checking costs hours per build. (hypothesis — based on competitive §4.6 SERP gap + community-substituting-for-aggregator pattern in §4.3)
How they buy today. YouTube research → tentative PCPartPicker build using US/EU prices (knowing it's not Lebanese-accurate) → Lebanon PC Gamers FB post asking "is this build OK for Lebanon, where do I get parts" → WhatsApp messages to 2-3 friends who built recently → PCAndParts as default first stop → 961Souq if PCAndParts is out of stock → repeat per part, manually tracking running cost in Notes app or WhatsApp draft. Cash payment at PCAndParts pickup. Often a 2-4 week elapsed buying window for a single build.
Pain points (most painful first):
- No price comparison — verifying PCAndParts is cheapest takes 30+ minutes per part
- Stock anxiety — no real "in stock" signal across retailers; "Sold Out" without restock ETA is universal (§4.4)
- "Call For Price" listings on 961Souq with no inquiry mechanism (#3, §4.4) — wastes time
- Cross-store cart math is manual; mixed builds across 2-3 retailers are error-prone
- US/EU PCPartPicker prices mislead him on what's affordable in Lebanon; no Lebanese equivalent exists (high — competitive §4.6 confirms)
Triggers to use 961tech.
- New GPU launch he wants to scope (RTX 50 series, Radeon refresh)
- Friend posts a build URL in Discord/FB — Karim opens it to check / fork
- Black-Friday-shaped sale at PCAndParts (weeks where major restock + promo)
- Specific game release ("can my rig run X" → spec compare → upgrade path)
- Forum / Reddit thread on /r/lebanon or /r/buildapc mentioning Lebanese availability
Design implications.
- #28 page design. Build flow must default to all-slots-at-once (already locked in ADR-0002). Per-slot rows must show price across all listed retailers inline, not via click-through. Stock state visible in the build UI, not on the product page (Karim won't click out to check). FPS-per-dollar surfaceable as a sort key on GPU/CPU rows (hypothesis — Karim wants this; needs telemetry validation).
- #33 per-category criteria. GPU row shows benchmark FPS bands (e.g., "Cyberpunk 1440p ultra: 78 fps") (hypothesis — needs LLM-extracted benchmark data, M2); CPU shows gaming-relevant cores + clocks before workstation specs; PSU shows wattage with margin calc, not just rated wattage; case shows GPU clearance.
- #41 monetisation. Karim is high-volume, low-margin per outbound click. Affiliate (CPS 1.5%) fits well; CPC less so given he click-shops 6-10 times per build. Price-drop alerts (#14) tap directly into Karim's stock-anxiety pain point — strong retention hook.
Confidence markers.
- Hypothesis: brand preferences (NVIDIA, Corsair) — based on global PC-builder norms, not Lebanese-specific data.
- Hypothesis: 30+ minutes per-part verification time — felt-experience claim, not measured.
- Untested: Karim's responsiveness to a "tier ladder" UI (#22 / Logical Increments pattern). Could go either way.
Validate via (post-launch):
- Telemetry: % of sessions tagged "Karim-shaped" (gaming-categories build, $600-1,500 total, completed compat-warning step) that complete a build and click out to ≥1 retailer. Target ≥40% click-through rate per build session.
- Telemetry: average parts-per-build for Karim sessions. Target 6-9 (full builds, not single upgrades).
- Manual: post a feature poll in Lebanon PC Gamers FB group after M2 launch — "what would make 961tech replace your current process?"
3.2 First-time builder — the anxiety-driven newcomer¶
Lebanese, 17-30, often a high-schooler with a small freelance gig, a university student starting a degree that needs more compute, or a young professional staring at a first paycheck. Same demographic spine as Karim, two steps earlier in the journey — and could become Karim once the first build is sitting on a desk and works. The design pressure is anxiety, not price-mining.
| Dimension | Value |
|---|---|
| Age range | 17-30 |
| Income tier | Tight-Mid ($800-1,800 per first build; often family-supplemented for students) |
| Languages | English (primary, default for everything tech). Same English-only scope as Karim. |
| Device profile | Phone-heavy; aspires to own desktop. Their current "PC" is a school laptop or the family desktop. |
| Connection | Mobile data dominant; home fiber if family-supported and Beirut-based; otherwise patchy |
| Payment habits | Cash, OMT, Whish; family card occasionally for parental approval; rare own card |
| Price tier they shop | $800-1,800 for the first build; $0-200 for a small initial peripheral while they save |
| Decision style | Trust-first initially (YouTubers, the friend who already built one); shifts to specs-first as confidence grows. Migrates across the journey. |
| Where they shop today | YouTube tutorials → Lebanon PC Gamers FB advice posts → WhatsApp friend who built last year → reluctant first walk-in to PCAndParts |
| Confidence | Hypothesis (cohort exists for sure; specific behaviors per cell vary) |
Motivations. The first proper paycheck or a family-funded build budget is the trigger that makes this persona exist at all. Until that moment they are not in the market — they are watching builds on YouTube and noting parts. When the money lands, what they are buying is identity as much as hardware: the transition from "I use my parents' computer" or "I have a school laptop" to "I have a PC I built." Karim is optimizing FPS-per-dollar; the first-time builder is optimizing for not screwing up something they have been waiting on for a year.
The learning curve is part of the appeal — the persona genuinely wants to understand what AM5 means and why DDR5 matters — but it is also the source of the dominant feeling, which is fear of looking stupid. This is often the first big tech purchase they are personally responsible for, and a wrong-RAM call costs a quarter of the budget. (hypothesis — grounded in adjacent first-purchase behavior, not Lebanese-specific telemetry)
How they buy today. Months of YouTube research first — "$1000 build in 2026"-style videos that quote US prices. Then a tentative PCPartPicker draft using US/EU listings, which they know is wrong for Lebanon but use as a scaffold. Then a long advice post in Lebanon PC Gamers FB group: "First build, $1,200, mostly Valorant and Counter-Strike, please critique." WhatsApp messages to the one friend who built a rig last year asking which store to actually visit. Then a reluctant walk-in to PCAndParts, parts list on a phone screen, asking the counter staff questions they hope are not stupid. Cash payment. The whole sequence takes 4-8 weeks of elapsed time.
Pain points (most painful first):
- Compat anxiety — "what if the parts don't fit, don't post, don't run together?" Acute enough that it delays the purchase by weeks.
- Jargon overload — DDR4 vs DDR5, AM5 vs LGA1700, what a chipset is, what TDP means, why the GPU advertises 12GB and the RAM also advertises 12GB and these are different things.
- Fear of wasting the first build's budget on the wrong part — there is no second paycheck queued behind this one.
- No cheap way to ask a question — the WhatsApp friend isn't on call, FB group answers come hours or days later, YouTube comments are noise.
- Buying from multiple retailers feels riskier than buying from one — trust does not transfer across shops, and they would rather pay more to one retailer than less to three.
Triggers to use 961tech.
- First proper paycheck lands, or family signs off on a build budget
- Upcoming semester or freelance gig forces it ("I need a real PC for this internship")
- Friend's build photos in a WhatsApp group ("I want one of those")
- Steam sale on Cyberpunk 2077 plus the realization the family laptop won't run it
- A YouTube "build for $X" video that matches their budget tier and convinces them it's possible
Design implications.
- #28 page design. Compat warnings must explain why in plain language — "PSU 450W is below recommended 600W for this GPU at 30% headroom" rather than "PSU mismatch." Show rule provenance so power users can override and first-timers learn from the override. "Why this matters" inline tooltips on each spec dimension. Empty-state on the build page should offer "Not sure where to start? Try a tier preset" — a Logical Increments-style on-ramp (competitive §3.3).
- #33 per-category criteria. Each category's filter UI needs an "I just want a working PC" mode that hides advanced filters (memory bandwidth, NVMe gen, sub-timings) until the user opts in. Glossary tooltips on every term, inline education over dense spec tables. The first-timer reads the filter labels before they read the values.
- #41 monetisation. First-timer is one-build-then-lurks; LTV is moderate and their session count is low. Affiliate fits because they do click "Buy" once the build is decided, and conversion-per-session is high (they finish what they start). Don't optimize for first-timer LTV directly — optimize for first-timer trust, because the same user becomes a Karim-shaped upgrade-cycle buyer 18 months later.
Confidence markers.
- Hypothesis: first-timer is meaningfully distinct from Karim rather than simply Karim earlier in the journey; treated as distinct because the design pressure (anxiety mitigation) is structurally different from price-mining.
- Hypothesis: tier-preset is the right on-ramp. Could be too hand-holdy for the subset that wants to learn the parts themselves.
- Untested: how much guided-explanation copy is too much vs. not enough.
Validate via (post-launch):
- Telemetry: compat-warning view → next-slot-pick funnel rate. Target 65%+ (vs Karim's likely 85%+). If <50%, the warnings are scaring people off rather than guiding them.
- Telemetry: "tier preset" click-through rate on new-session builds, if shipped. Target 20% of new sessions starting from a preset.
- Manual: post a feature poll asking "did anything intimidate you about your first build?" in Lebanon PC Gamers FB group and the lebanese-gamers Discord after M2 launch.
3.3 Casual parts customer — the missing-flow primary¶
Lebanese, 20-50, wants to buy a thing — a laptop, a prebuilt PC, a gaming chair, a monitor, a Logitech mouse — without going through a build flow. The persona that exposes 961tech's missing path: the current use-cases.md framework routes them through UC-1 → UC-A → UC-2 with no path-specific UX, and the categories they care about are mostly M3-deferred. Their existence is the design pressure that justifies a casual landing alongside the build flow.
| Dimension | Value |
|---|---|
| Age range | 20-50 |
| Income tier | Variable ($100-2,000 — peripheral upgrade up to laptop replacement) |
| Languages | English (primary, default for everything tech). French passive read for francophone subset; not load-bearing. |
| Device profile | Phone primary; arrives via Google search or Instagram ad |
| Connection | Typical Lebanese mobile data; home fiber if Beirut-based |
| Payment habits | Cash dominant; card if the retailer accepts it (post-2019 SMBs sometimes do); Whish; rare OMT (one-shot, not P2P) |
| Price tier they shop | \(100-2,000, highly variable: gift purchases often <\)300, laptop replacements $800-1,500 |
| Decision style | Brand-first or price-first; rarely specs-first. Trust-first as a secondary filter on bigger spend. |
| Where they shop today | PCAndParts (laptops, monitors, peripherals — homepage stacks these grids prominently, §4.4); 961Souq (peripherals); Macrotronics (laptops, prebuilts, VAT-inclusive); occasional physical-retailer walk-in |
| Confidence | Hypothesis (cohort exists — PCAndParts homepage devotes prime real estate to Laptops / Monitors / Gaming Gear grids; specific behaviors per cell vary) |
Motivations. The casual customer is shopping for a discrete object. A laptop because the old one died or a sibling got accepted to university. A monitor because the work-from-home setup needs a second screen. A gaming chair as a birthday gift. A Logitech mouse to replace one that's started double-clicking. They are not building anything, not optimizing FPS-per-dollar, not researching for weeks. The job is "find the thing, confirm a fair price, confirm a Lebanese retailer has it, buy it." Often a one-shot transaction — they will not come back to 961tech for months unless another need shows up.
Brand familiarity does the heavy lifting. The decision tends to start at "I want a Logitech mouse" or "I want a Lenovo ThinkPad" rather than at a spec sheet — brand IS the spec here. Price tier is the second filter ("cheapest gaming chair under \(200"), and trust matters mainly on bigger spend (\)800+ laptop, prebuilt PC). Not anxious like the first-time builder, not specs-fluent like Karim; decisive on what they want by name, and want the buy to be fast.
How they buy today. Phone search like "best laptop under $500 lebanon" → Google ad or organic → PCAndParts or Macrotronics → scroll the laptop grid, narrow by brand and price → tap into 2-3 listings, glance at the spec block, compare → cart at whichever retailer is cheaper or in stock → cash on pickup, or card if the retailer takes one, or Whish if offered. Delivery is confirmed by WhatsApp from the retailer's number, not an order-status page. Hours to a couple of days from search to checkout, not weeks.
Pain points (most painful first):
- Forced into builder UX they don't want — landing on a "build a PC" site when the goal is to buy a thing. The structural pain that makes this persona primary.
- Categories they care about are M3-deferred today — laptops (#24), prebuilts (#25), and peripherals are not shipped yet. Even if 961tech served the casual flow well in copy, there is no catalog under it.
- Brand-first browse is poorly supported on Lebanese retailers — no Lenovo brand page that compares ThinkPad vs IdeaPad vs Legion lines side-by-side.
- Spec opacity on laptops and prebuilts makes price comparison hard — laptop A on PCAndParts and laptop B on Macrotronics differ on RAM, storage, screen, and warranty, so the price delta isn't apples-to-apples.
- Stock state for a single item is what they need, not multi-retailer cart math — "is this Logitech G502 in stock at any retailer" beats "how do I split a cart across three."
Triggers to use 961tech.
- Laptop dies or a family member needs a new one — student gets a university acceptance, parent's machine gives up
- Cheap monitor on a Black Friday banner (impulsive, price-anchored)
- Gift purchase — gaming chair for a sibling, mechanical keyboard, headset
- Office work-from-home setup — peripheral upgrade post-COVID, lasting trend in Lebanon
- Phone search like "best laptop under $500 lebanon" → ad or organic → retailer site
Design implications.
- #28 page design. Casual landing must be distinct from builder landing — brand-first nav with category cards for laptops, prebuilts, peripherals. Filter UX for laptops emphasizes brand + screen size + price tier, not internals (CPU model, memory bandwidth, NVMe gen). Single-item buy flow must NOT show compat warnings or build affordances — compat is irrelevant for a laptop or chair. Tax-toggle and three-state stock signal still apply.
- #33 per-category criteria. Laptops and prebuilts need their own spec dictionary — screen size, battery life, warranty length, not CPU socket and RAM speed. Peripherals need brand-line awareness, not just SKU comparison: "Logitech MX series vs G series" matters more here than "M720 vs G502."
- #41 monetisation. Casual buyers are highest-volume, lowest-engagement — short sessions, one-shot conversion. CPC and affiliate both work. Featured listings on category pages are the natural surface and most acceptable here because the buyer is in browse mode, not deep planning — brand-promoted options read as helpful rather than intrusive. Highest receptivity to sponsored content of any persona.
Confidence markers.
- Hypothesis: this persona is a sizable share of Lebanese PC retail traffic. Evidence: PCAndParts homepage stacks Laptops / Monitors / Gaming Gear grids prominently (§4.4) — if these didn't sell, they wouldn't anchor the homepage. Cohort is real; share is unmeasured.
- Hypothesis: session shape is single-item and short. Could be wrong if Lebanese casuals also browse comparatively before bigger purchases ("compare top 5 laptops under $1k for student") and look more like first-time builders on the laptop subset.
- Untested: whether they'd use 961tech at all over Google → retailer-direct. The aggregator value-add is "all retailers' prices for this Logitech mouse on one page" — but Google plus a couple of retailer tabs may already be enough.
Validate via (post-launch):
- Telemetry: % of sessions that touch only non-builder categories (laptops, prebuilts, peripherals once shipped) and click out to one retailer. If <5%, the casual flow is over-invested in.
- Telemetry: time-on-page for single-item product pages vs build-flow pages. Casual flow should average shorter per page; if it doesn't, the page is doing too much.
- Manual: post-launch monitoring of PCAndParts and Macrotronics — do they add price-comparison features? If yes, validates demand. If no, the casual cohort may not be vocal enough to force retailer change, and our wedge holds longer.
4. Secondary personas¶
4.1 Office IT buyer — the B2B / batch buyer¶
Lebanese SMB IT manager or owner-operator, 30-55, responsible for fitting tech into a P&L line for a 5-50 person company. Buys in batches — 5-15 employee laptops at a time, replacement parts, peripherals — and almost always through a single retailer rep on WhatsApp. The high-LTV outlier among 961tech personas: per-batch GMV can be $30k against Karim's $1.5k.
| Dimension | Value |
|---|---|
| Age range | 30-55 |
| Income tier | Mid-Comfortable (per-batch spend $5,000-30,000) |
| Languages | English (primary). French passive read for older buyers (>45); not load-bearing. |
| Device profile | Desktop or business laptop primary; phone for WhatsApp coordination with the retailer rep |
| Connection | Office fiber during work hours; mobile data off-hours |
| Payment habits | Bank transfer dominant; company card for SMBs that have one post-2019; sometimes COD on smaller items |
| Price tier they shop | $5,000-30,000 per batch (employee-laptop refresh, replacement parts, office peripherals) |
| Decision style | Trust-first + relationship-led ("I have a guy at PCAndParts") |
| Where they shop today | Direct retailer rep on WhatsApp (primary); occasionally Macrotronics for VAT-inclusive pricing; rarely browses aggregators |
| Confidence | Hypothesis (cohort exists; specific channel preferences vary) |
Motivations. Cost-of-time-vs-cost-of-money. Office IT buyers want to spend 30 minutes setting up an order and have it delivered next day, not 3 hours comparison-shopping for $20 savings per laptop. The job is fitting tech into a budget line, not building the perfect rig. Relationships with retailer reps are load-bearing — same rep year over year, the "my guy at PCAndParts" pattern that makes switching costs material.
How they buy today. WhatsApp message to known retailer rep with line items → rep replies with prices and delivery timeline → bank transfer or company card or COD → rep coordinates delivery to office → done. Often a single retailer for the whole batch, even when a competing retailer is cheaper on a few SKUs, because the relationship simplifies invoicing and accountability.
Pain points (most painful first):
- No batch quoting tool — has to build the order line-by-line via WhatsApp message; manual reconciliation between quote and final invoice
- No way to request quotes from multiple retailers in parallel — each retailer needs a separate WhatsApp conversation, so cross-shop comparison costs hours
- Tax-inclusive vs exclusive opacity — needs both views (tax-inclusive for budget approval; tax-exclusive for VAT reclaim)
- No aggregated invoice across retailers — buying from 2 retailers means 2 separate invoices and 2 payment processes
- Stock confirmation friction — "is this 15-unit Dell laptop available?" requires WhatsApp ping; aggregator helps if it shows real stock state per retailer
Design implications.
- #28 page design. A "quote mode" affordance on builds and casual carts — a toggle that switches outbound from "Buy" to "Request quote with line items prefilled." Tax-inclusive view default ON in this mode. Quote-export as PDF or CSV for procurement workflow.
- #33 per-category criteria. Business laptops need warranty terms, on-site service availability, and procurement-friendly fields (model number, BOM-friendly export). Spec dictionary should include B2B-relevant dimensions, not just consumer.
- #41 monetisation. Office IT is the high-LTV outlier — per-batch GMV reaches $30k. Featured-listing receptivity is high (their suppliers want to be featured to B2B buyers). CPS at 1.5% works; per-converted-session affiliate revenue can be 10-50× a Karim session. Worth investigating B2B-tier listings as a Stage-4 partner offering.
Confidence markers.
- Hypothesis: Office IT volume is meaningful at Lebanese scale. Lebanese SMBs do refresh employee laptops; cohort is real. Share of total Lebanese tech-aggregator demand is unmeasured.
- Hypothesis: WhatsApp-rep workflow is the dominant Office IT pattern. Could be wrong if some segments use direct retailer-website B2B portals (rare in Lebanon, hypothesis).
- Untested: would Office IT buyers actually use 961tech, or continue WhatsApp-rep workflow? Aggregator value-add (parallel-quote, batch-export) needs to be high enough to disrupt the relationship-led status quo.
4.2 Layla the content creator — the reliability-first creator¶
Lebanese woman, 24-35, working in video, photo, music, or design — freelance or in a small studio. Mid-budget at $1,500-3,000 a build, aspiring to a Mac if affordable. Her PC is a tool that has to not crash during a 3-hour Premiere render; reliability over peak FPS, brand-aware on the dimensions creators actually feel.
| Dimension | Value |
|---|---|
| Age range | 24-35 |
| Income tier | Mid ($1,500-3,000 PC build budget; aspires to Mac if affordable) |
| Languages | English (primary). French passive read for francophone subset; not load-bearing. |
| Device profile | Mac if achievable, otherwise high-RAM Windows desktop; phone for socials and spec checking |
| Connection | Home fiber if Beirut-based; mobile data backup |
| Payment habits | Card (Whish-linked debit, fresh-USD card if held); cash for cash-only retailers; sometimes Western Union via diaspora middleman |
| Price tier they shop | $1,500-3,000 build; $500-1,500 for upgrades |
| Decision style | Reliability-first; brand-aware (Apple over Asus / Lenovo for laptops; Samsung / LG for monitors); creator-dimension-aware (RAM, color accuracy, sustained writes) |
| Where they shop today | Macrotronics (Apple-tier and tax-inclusive — primary for Mac), Apple resellers, 961Souq, IG creator communities for recommendations |
| Confidence | Hypothesis (cohort exists; the "Mac vs Windows for creators" decision pattern is hypothesis-grade) |
Motivations. Creator workflows are the optimization. Layla edits video, takes photos, mixes music, or designs. Her PC is a tool that has to not crash during a 3-hour Premiere render — reliability over peak FPS, brand-aware (Apple silicon for the M-series memory bandwidth advantage). Mid-budget sustaining a creator workflow at studio quality is the optimization, not benchmark scores.
How they buy today. IG creator-community recommendations or YouTube creator-build videos → spec-check on retailer pages → Macrotronics or Apple reseller for the Mac path; 961Souq or PCAndParts for the Windows path → card or cash payment → 1-3 week elapsed window. The Mac path dominates if she can afford it, with the Windows fallback if budget forces the call.
Pain points (most painful first):
- Spec opacity on creator-relevant dimensions — RAM headroom for editing, screen color accuracy (sRGB / DCI-P3 / AdobeRGB %), NVMe gen for video scratch disk, sustained-write throughput vs rated speed
- Weak filtering on creator-relevant dimensions on Lebanese retailers — can't filter monitors by color gamut, can't filter SSDs by sustained write
- No comparison between PC and Mac options — even though both serve the same creator workflow, no Lebanese tool surfaces them side-by-side
- Apple-tier pricing opacity — Apple resellers sometimes have unclear authorized-vs-grey-import pricing, and the price gap is large enough to matter
- Cash vs card payment friction at high price points — $2k+ purchases via cash are uncomfortable; card-accepting retailers are limited
Design implications.
- #28 page design. Spec-display blocks should highlight creator-relevant dimensions when category is GPU / RAM / storage on a creator-tagged build (M2+). Color-accurate monitor filtering as an M2 surface. Mac-comparison mode in M3 (after #24 laptops ships) lets her compare a Mac to a Windows alternative on the same dimensions.
- #33 per-category criteria. GPU spec dictionary needs CUDA-cores plus VRAM-for-creators view. RAM dictionary needs ECC vs non-ECC and capacity ranges suited for video work. Storage dictionary needs sustained-write benchmarks, not just rated speed. Monitors need color-gamut % across sRGB / DCI-P3 / AdobeRGB.
- #41 monetisation. Layla is mid-volume mid-margin. Featured-listing receptivity is moderate. Affiliate fits. Deferred opportunity: partner content (creator build guides, "best Mac vs PC for video editing in Lebanon") drives long-tail SEO.
Confidence markers.
- Hypothesis: Lebanese creator cohort is real. IG creator communities exist; freelance video and photo work happens in Beirut. Specific behaviors per cell vary.
- Hypothesis: Mac-path-when-affordable is dominant. Could be wrong — some creators are Windows-pipeline locked and stay there.
- Untested: how much creator-dimension UX surfacing is enough to compete with creator-community recommendations as the decision substrate. Layla might still default to "I asked Mona on IG, she said get the Asus ProArt" regardless of what 961tech surfaces.
4.3 Diaspora buyer — the gift-from-abroad buyer¶
Lebanese living abroad — Gulf, Europe, North America, West Africa — 28-55, buying tech for a family member back in Lebanon. Often a one-shot purchase tied to a specific event (university acceptance, birthday, graduation). The diaspora buyer never physically visits the retailer; the family member in Lebanon does the pickup or coordinates delivery.
| Dimension | Value |
|---|---|
| Age range | 28-55 |
| Income tier | Mid-Comfortable ($800-3,000 per gift purchase) |
| Languages | English (primary) |
| Device profile | Desktop or laptop primary (browsing on a stable connection abroad); phone for WhatsApp with family in Lebanon |
| Connection | Stable abroad; family in Lebanon on whatever Lebanese connection they have |
| Payment habits | Foreign card (primary); Western Union to family for cash purchase; sometimes OMT to family |
| Price tier they shop | $800-3,000 per gift (laptop, prebuilt, peripheral); occasional smaller spends |
| Decision style | Trust-first + delegation ("I'll buy what my brother says he needs") |
| Where they shop today | Direct retailer on WhatsApp (paid by foreign card or Western Union); family middleman who picks up the part; occasional direct international shipping if a retailer offers it (rare in Lebanon) |
| Confidence | Hypothesis (cohort exists — Lebanese diaspora ~14M abroad; gift-shaped tech purchases are common; specific behaviors vary) |
Motivations. Buying for family in Lebanon — laptop for a student sibling, phone or PC for parents, gaming gear for a teenage relative. Often a one-shot transaction tied to a specific family event (university acceptance, birthday, graduation). The diaspora buyer doesn't visit the retailer; the family member in Lebanon handles pickup or delivery, and trust passes through that relationship.
How they buy today. Family member in Lebanon WhatsApps "I need X" → diaspora buyer Googles → arrives at a retailer site → contacts the retailer via WhatsApp to ask about foreign-card payment or shipping to a Lebanese address → if accepted, pays with foreign card; if not, sends Western Union to the family member who pays cash on pickup → family confirms delivery via WhatsApp. The buyer is rarely on the same continent as the box.
Pain points (most painful first):
- Payment friction — many Lebanese retailers don't accept foreign cards; Western Union via family is the workaround but adds 1-3 days
- Delivery routing — the buying-from-abroad-shipping-to-Lebanon flow is not native to most Lebanese retailers; relies on family pickup
- Currency anxiety — USD vs lollar vs LBP confusion; needs USD-anchored pricing with confidence the displayed rate is current
- No "buy and ship to family" affordance — every retailer's checkout assumes the buyer is the recipient
- Stock confirmation lag — diaspora buyer can't visit the retailer to confirm "is this in stock"; depends on family member or WhatsApp ping
Design implications.
- #28 page design. Explicit "I'm buying for someone in Lebanon" toggle that switches delivery-address UX to a "Lebanese family member" mode. Currency display always USD with LBP secondary; rate-freshness signal mandatory. Foreign-card-payment flag on retailer profiles (which retailers accept foreign cards out-of-the-box).
- #33 per-category criteria. Laptop and prebuilt categories matter most to diaspora — gift-shaped purchases skew laptop / prebuilt / peripheral, rarely DIY components. Reinforces #24 / #25 priority.
- #41 monetisation. Diaspora is high-LTV per session (per-purchase value $800-3,000) but low-frequency. Affiliate fits well — the diaspora buyer is not interested in featured listings, just trust signals. Monetisation opportunity: foreign-card-payment partner integration as a paid retailer service. Rare enough that being the platform with this affordance is a defensive moat.
Confidence markers.
- Hypothesis: Lebanese diaspora gift-tech-purchases are a meaningful share. Diaspora ~14M abroad with strong family ties; tech gifts are a real flow. Share of 961tech traffic is unmeasured.
- Hypothesis: foreign-card-payment friction is the dominant pain. Could be wrong — the Western Union workaround may be acceptable enough that diaspora buyers don't feel the friction acutely.
- Untested: whether 961tech is the right surface for diaspora vs sending family the WhatsApp number directly. Aggregator value-add is "see prices across all Lebanese retailers in one trip"; for one-off gifts, the family-rep workflow may already work.
5. Cross-cutting analysis¶
5.1 Language scope: English-only justification¶
961tech ships in English only. This subsection documents the decision so #37 can defer cleanly.
Why English. Every Lebanese PC retailer profiled in competitive §4.4 ships English-only UI — PCAndParts, 961Souq, Macrotronics, and the long-tail list. The Lebanese tech-savvy cohort, across all six personas in this doc, defaults to English for technical content. Tech specs, build communities, YouTube tutorials, and Discord servers are English-first globally; Lebanese buyers consume this content directly without friction.
Why not Arabic. Competitive §4.6 found Lebanese-Arabic SERP queries collapsing into classifieds (OpenSooq, Olx Lebanon Arabic interface) and cross-ranking Saudi retailers (PCD, La3eb, PCPalace), not into a Lebanese-Arabic aggregator audience. There is no observable Lebanese-Arabic PC-buyer cohort that 961tech would capture by translating. Arabic is deferred until evidence of demand emerges — most likely via post-launch Casual-customer telemetry (§7).
Why not French. Francophone Lebanese (Lycée Verdun / Saint Joseph cohort, ~30-40% of the Beirut-educated population (hypothesis)) read English tech content fluently. They do read French retailer content (LDLC, Cowcotland) but not in a way that creates a Lebanese-French aggregator opening. French passive-read habit is noted per persona where relevant; it does not justify a French UI.
Implication for #37. #37 i18n strategy becomes a deferred no-op until Casual telemetry surfaces demand or a Lebanese-Arabic cohort emerges. The active scope of #37 collapses to "we ship English, here's the trigger for revisiting." No translation work, no RTL handling, no per-language SEO planning needed in M1-M2.
5.2 Device & connection profile¶
| Persona | Primary device | Secondary device | Connection | Implication |
|---|---|---|---|---|
| Karim | Mid-range Android phone | Family / own desktop for serious browse | Mobile data primary; home fiber if Beirut | Mobile-first build flow; cross-device persistence (cookie + sign-in claim per ADR-0003) is load-bearing |
| First-time builder | Phone | Aspires to own desktop | Mobile data; home fiber if family-supported | Onboarding copy must read on a 6" screen; tooltips need touch-friendly affordances |
| Casual parts customer | Phone | Occasionally a borrowed desktop | Mobile data | Single-item product pages must be perfectly mobile-first; gallery, specs, three-state stock all visible without scrolling overhead |
| Office IT buyer | Desktop / business laptop | Phone for WhatsApp | Office fiber; mobile data for off-hours | Quote-export flow must be desktop-friendly; phone is for coordination only |
| Layla | Mac (or aspiring Mac) | Phone for socials | Home fiber | Color-accuracy and design-craft become legible to her; rough UI loses her |
| Diaspora buyer | Desktop / laptop abroad | Phone for WhatsApp coordination | Stable abroad; family on whatever they have | Payment + delivery flow must work on a Beirut family member's mid-range phone too |
Cross-cutting implications.
- Mobile-first is non-negotiable for primary personas (Karim, First-timer, Casual). #43 perf budget + observability needs to set explicit weight budgets per page, especially for image-heavy pages (the build flow, category browse).
- Cross-device session persistence matters for Karim and First-timer (research on phone, finalize on desktop) — ADR-0003 handles this for builds; #11 Auth.js extends to saved-build claim.
- Image weight budget must accommodate Lebanese mobile-data realities. Lazy-load below the fold; serve WebP with AVIF where possible; cap per-product hero at 200KB.
- Connection robustness: any flow that depends on >1 sequential network round-trip (search-then-filter-then-add-to-build) must work over a 3G simulation. M1 Vitest doesn't cover this; M2 should add a Lighthouse mobile budget check in CI.
5.3 Payment habits & financial trust¶
The post-2019 banking crisis reshaped Lebanese payment habits. Lollar (in-bank USD, devalued) and fresh-USD (cash USD) are non-fungible; card payments are rare; cash, OMT, Whish, and Western Union are the working payment rails for most personas.
| Persona | Cash | OMT | Whish | Card (local) | Card (foreign) | Bank transfer | Western Union |
|---|---|---|---|---|---|---|---|
| Karim | Primary | Common | Friends/family P2P | Rare | — | — | — |
| First-time builder | Primary (often family-supplied) | Common | P2P | Rare | — | — | — |
| Casual parts customer | Primary | Common | Common | Sometimes | — | — | — |
| Office IT buyer | Sometimes | Sometimes | — | Company card (post-banking-crisis SMBs) | — | Primary | — |
| Layla | Common | Common | Common | Sometimes (fresh-USD card if held) | — | Sometimes | — |
| Diaspora buyer | — | — | — | — | Primary | Sometimes | Common |
Cross-cutting implications.
- Card-required signup is a non-starter. Auth.js integration (#11) must support email-only signup; no card-on-file even when payments-in-flow ship later.
- WhatsApp deep-links and "Confirm with retailer" affordances are mandatory (#28). Most outbound conversions are WhatsApp + cash + COD, not card. Outbound CTAs must default to "Confirm with retailer" not "Buy now" for retailers that don't ship card-online.
- Currency-dual display (USD primary, LBP secondary, with rate) is universal. Stale-rate warning when displayed rate diverges from a fresh source (per competitive §5.3 #3). #41 monetisation treats lollar / fresh-USD as out-of-scope for in-flow payments — affiliate clickout sidesteps the issue.
- Foreign-card support is the diaspora unlock. Listed as #41 monetisation candidate (paid retailer service). Not M2.
- Tax-inclusive toggle (per competitive §5.3 #1) is multi-persona — not just Office IT. Casual buyers compare prices including tax; Diaspora buyers verify totals before sending money. Default toggle state is per-flow (see §6.1.4): OFF for Builder, ON for Casual + Quote mode.
5.4 Decision-style spectrum¶
Personas placed on a four-axis decision-style spectrum. A persona can sit on multiple axes — the dominant axis drives default UX; secondary axes drive optional affordances.
| Persona | Specs-first | Brand-first | Price-first | Trust-first |
|---|---|---|---|---|
| Karim | Primary | Secondary (GPU + PSU) | Strong secondary | Tertiary |
| First-time builder | Tertiary (becomes primary as confidence grows) | Tertiary | Tertiary | Primary |
| Casual parts customer | Tertiary | Primary | Strong secondary | Secondary |
| Office IT buyer | Secondary | Secondary (vendor stability) | Tertiary | Primary (relationship-led) |
| Layla | Secondary (creator dims) | Primary (Apple, Samsung, LG) | Tertiary | Secondary |
| Diaspora buyer | Tertiary | Secondary | Tertiary | Primary (delegation-led) |
Cross-cutting implications.
- Specs-first UI is the default Builder flow (Karim, eventually First-timer). All-slots-at-once layout (ADR-0002) presupposes specs-first navigation.
- Brand-first affordances are the Casual-flow primary. Category pages must surface brand families prominently — "Lenovo ThinkPad," "Apple MacBook," "Logitech MX Master" — not just SKU lists. This is the missing-flow gap (spec §10) made concrete.
- Trust signals carry First-timer, Office IT, and Diaspora. Trust badges above the fold (per competitive §3.3 #6), retailer ratings, last-updated timestamps, "real Lebanese stock" + WhatsApp + COD badges. Three of six personas list trust as primary.
- Price-first is everywhere strong but never primary. Pure-price ranking with explicit tiebreaker chain (Geizhals pattern, competitive §3.3 #3) is the default sort, but design must not collapse to "cheapest only" — three of six personas weight trust above price.
- #33 spec dictionaries must support both specs-first and brand-first browse. The same dataset, surfaced two ways.
5.5 Where they shop today¶
| Persona | PCAndParts | 961Souq | Macrotronics | Olx LB | FB groups | IG creators | WhatsApp retailer | Apple resellers | Diaspora middleman |
|---|---|---|---|---|---|---|---|---|---|
| Karim | Primary | Secondary | Tertiary | Used parts | Primary advice | — | Sometimes | — | — |
| First-time builder | Eventual | Sometimes | — | — | Primary advice | — | Friend's contact | — | — |
| Casual parts customer | Primary | Strong secondary | Strong secondary | Sometimes | — | — | Sometimes | — | — |
| Office IT buyer | Direct rep | — | Direct rep (VAT-inclusive) | — | — | — | Primary | — | — |
| Layla | Sometimes | Sometimes | Strong secondary | — | — | Recommendations | Sometimes | Primary | — |
| Diaspora buyer | Indirect via family | Indirect via family | Indirect via family | — | — | — | Primary (paid by foreign card or WU) | — | Strong secondary |
Cross-cutting implications.
- PCAndParts dominance is structural for primary personas. Competitive §4.4 confirms — price leader since 1998. Don't pitch 961tech as "cheaper than PCAndParts" — pitch as "compat-checked + multi-retailer view that includes PCAndParts."
- WhatsApp is the dominant retailer channel for high-trust personas (Office IT, Diaspora). #28 page design must integrate WhatsApp deep-links as a first-class outbound (per competitive §4.5). Not "View on retailer" — "View on retailer + WhatsApp this listing."
- FB groups + IG are advice substrates for Karim and First-timer (advice) and Layla (recommendations). Build-share via URL (#13) and completed-build gallery (#9) tap into this — Lebanese PC Gamers FB group becomes a 961tech share-target naturally.
- Olx is used-parts-only for Karim. Out of M1-M2 scope; revisit in v3 for used-market integration (competitive §4.2).
- Apple-retailer track is Layla-specific and needs the #24 laptops work to surface in 961tech at all. M3.
- Diaspora middleman is informal but real — a brother/cousin in Beirut who picks up parts paid by foreign card. The "I'm buying for someone in Lebanon" flow (§4.3) must accommodate this. Not M2.
5.6 Pain-point matrix¶
Severity 0-3 per persona per pain point. 3 = acute, drives current behavior; 2 = significant; 1 = mild; 0 = not felt by this persona. Universal pains (≥2 across most personas) are the wedge; persona-specific 3s are the differentiation surface.
| Pain point | Karim | First-timer | Casual | Office IT | Layla | Diaspora | Universal? |
|---|---|---|---|---|---|---|---|
| No multi-retailer price comparison | 3 | 2 | 2 | 1 | 2 | 1 | Universal-2.5 |
| No real-time stock signal across retailers | 3 | 2 | 3 | 3 | 2 | 2 | Universal-2.5 |
| "Call For Price" with no inquiry mechanism | 2 | 1 | 2 | 1 | 1 | 1 | Universal-1.3 |
| No compatibility checking | 2 | 3 | 0 | 1 | 1 | 1 | First-timer-driven |
| Jargon overload / spec opacity | 1 | 3 | 2 | 1 | 2 | 2 | First-timer + Casual |
| Forced into builder UX (no casual flow) | 0 | 0 | 3 | 1 | 1 | 1 | Casual-only acute |
| No batch quoting / line-item exporting | 0 | 0 | 0 | 3 | 0 | 0 | Office-IT-only acute |
| Foreign card / payment friction | 0 | 0 | 0 | 0 | 0 | 3 | Diaspora-only acute |
| Currency confusion (USD vs lollar vs LBP) | 1 | 1 | 1 | 2 | 2 | 2 | Universal-1.5 |
| Tax-inclusive vs exclusive opacity | 1 | 1 | 1 | 3 | 1 | 2 | Office-IT + Diaspora |
| Cross-store cart math is manual | 3 | 1 | 1 | 1 | 1 | 1 | Karim-driven |
| US/EU tools mislead on Lebanese prices | 3 | 2 | 1 | 0 | 1 | 0 | Builder-cohort |
| No spec-comparable laptop / prebuilt browse | 0 | 0 | 2 | 2 | 2 | 2 | Casual + creator + diaspora |
| Spec-dimensions weak for creator workflows | 0 | 0 | 0 | 0 | 3 | 0 | Layla-only acute |
| Color accuracy / monitor tier opacity | 0 | 0 | 1 | 0 | 3 | 0 | Layla-only acute |
| Delivery routing for in-Lebanon recipients | 0 | 0 | 0 | 0 | 0 | 3 | Diaspora-only acute |
Universal pains (≥2 across ≥4 personas).
- No multi-retailer price comparison. This is 961tech's reason for existing. Acute for Karim, significant for everyone else.
- No real-time stock signal across retailers. Three-state stock signal (Listed / Call For Price / Out + last-updated) is the response (per competitive §3.6).
- No compatibility checking — only acute for First-timer but felt by Karim and others. The compat-DB moat.
- Jargon overload / spec opacity — acute for First-timer, significant for Casual + Layla. "Why this matters" inline education.
Persona-specific acute pains (severity 3 in only one persona).
- Karim: cross-store cart math is manual → multi-merchant cart aggregator (#15) is the M2 wedge.
- First-timer: no compat checking + jargon overload → compat-warning panel with rule provenance + plain-language tooltips.
- Casual: forced into builder UX → adjacent ticket (§10) opens the casual flow.
- Office IT: no batch quoting + tax-inclusive opacity → "Quote mode" affordance with tax-inclusive default ON (#28 implications §6.1.4 + §6.1.6).
- Layla: spec opacity for creator workflows + color accuracy → #33 per-category criteria needs creator dimensions surfaced.
- Diaspora: foreign-card friction + delivery routing → mostly post-M2 ("buy for family" flow + payment partner integration).
Implication. The doc's design pressure on M2 features lines up cleanly with persona-specific acute pains. Each primary persona has one wedge feature in M2 scope:
- Karim → multi-merchant cart aggregator (#15)
- First-timer → compat-warning rule provenance (#28)
- Casual → casual flow (new ticket from §10)
Secondary personas have wedges that mostly land in M3 or later.
5.7 Anti-personas / cohorts we don't optimize for¶
961tech acknowledges these cohorts but does not design for them. Each profile ends with a drift signal — what telemetry would tell us we're mission-creeping toward this cohort instead of staying on the primary personas. If a drift signal trips, revisit scope; don't passively absorb the cohort.
Crypto / AI tinkerer¶
Niche. High spend per build ($3-10k for ML rigs, mining setups, multi-GPU stations); often sources from non-Lebanese channels (eBay, AliExpress, ASUS direct) because Lebanese retailers don't carry workstation tier. Ticket #36 originally listed them as a hypothesis persona; on review the cohort is too small and too out-of-distribution to drive design.
Drift signal. Telemetry shows >5% of build sessions configuring 4+ GPU slots, dual-CPU, or workstation chipsets. Revisit if so.
Wholesalers / large B2B accounts¶
Distinct from Office IT (5-15 unit batches). Wholesalers buy 50+ units per order, often as resale stock. They use direct retailer relationships, not aggregators. 961tech's UX would feel like a toy at this scale.
Drift signal. Telemetry shows sessions with cart values >$10k or part-counts >20 of the same SKU. Revisit if recurring.
Used-only buyers¶
Olx-LB primary cohort. Different segment than 961tech's new-parts focus; shop on price-from-stranger trust signals, not multi-retailer comparison. Used-market integration is a v3+ deferred (competitive §4.2).
Drift signal. Inbound traffic from Olx LB referrers >10% of sessions. Indicates demand for used-integration; revisit v3 priority.
Apple-only customers¶
Mac + iPhone + iPad buyers. Apple resellers (iStore, EnvyMyne, others) own this surface. 961tech can include Mac in laptop-comparison mode (#24 laptops M3) but Apple-product detail (RAM upgrade tiers, M-series chip differentiation, ecosystem accessories) is out of scope.
Drift signal. >20% of laptop-category sessions filter to "Apple only" once #24 ships. Revisit Apple-detail depth.
Phones-only buyers¶
The v3+ market in the original spec (§3.3 phased category roll-out). Different retailers (telco shops, Apple resellers, Khoury Home), different journey, different purchase frequency. Out of scope through v2.
Drift signal. Inbound search referrers asking for "phone Lebanon price compare" >5% of total. Validates v3 phone-category priority.
Arabic-only PC enthusiasts¶
Per competitive §4.6 the Lebanese-Arabic SERP collapses into classifieds + cross-ranked Saudi retailers — no observable Lebanese-Arabic PC-aggregator audience exists. Per §5.1 above, English-only is the active scope.
Drift signal. >5% of inbound sessions arrive from Arabic-language search referrers OR >5% of Casual-customer sessions originate from Arabic-region IPs (Lebanese-Saudi diaspora overlap). Revisit Arabic-UI priority — likely surfaces via Casual-customer telemetry rather than Builder telemetry.
6. Design implications by ticket¶
6.1 For #28 page design¶
Top 6 implications, each citing the personas that drive it. These are the canonical statements — per-persona profiles surface these, but #28's design conversation should happen against this list.
6.1.1 Compat warnings explain why in plain language with rule provenance¶
The compat-warning panel on the build page must show why a part is incompatible — "PSU 450W is below recommended 600W for this GPU at 30% headroom" — not "PSU mismatch." Show the rule that triggered and the threshold. Lets power users override; lets first-timers learn.
Driven by. First-time builder (acute compat anxiety, severity-3 pain), Karim (uses provenance to validate before accepting).
Touches. ADR-0002 (build UX), #28, #22 more compat rules, competitive §3.2 gold standard pattern.
6.1.2 Three-state stock signal with "Confirm with retailer" affordance¶
Stock state is Listed / Call For Price / Out — not binary. Each state has a dedicated affordance: Listed → "View on retailer + WhatsApp this listing"; Call For Price → "Get a quote" (WhatsApp deep-link with prefilled message + product reference); Out → "Notify when restocked" (#14 hook). Last-updated timestamp visible on every row.
Driven by. Karim (severity-3 stock anxiety), Casual customer (severity-3 stock anxiety), Office IT (severity-3 stock — needs to confirm bulk availability), Diaspora (needs confirmation before paying foreign card).
Touches. #28, #3 Call For Price, #14 price drop alerts, competitive §4.4 Lebanese context.
6.1.3 Casual flow distinct from Builder flow¶
A non-builder visitor to a category (laptops, prebuilts, peripherals) lands on a flow optimized for single-item purchase: brand-first navigation, product details over component-internals, no compat panel, no build-cart sidecar. Builder flow remains the default for component categories.
Driven by. Casual customer (severity-3 "forced into builder UX"), Layla (creator workflows wanting product-detail not build-flow), Diaspora (gift-shaped purchases).
Touches. #28, #24 laptops, #25 prebuilts, and the new use-case ticket created with this doc.
6.1.4 Tax-inclusive / tax-exclusive toggle as a session preference¶
Currency / tax display is sticky per session. Default OFF (tax-exclusive) for Builder flow (Karim doesn't think in tax-inclusive); default ON (tax-inclusive) for Casual flow (consistent with how Macrotronics displays — competitive §4.4). User preference overrides. Currency-dual display (USD primary, LBP secondary, with rate freshness signal) is universal regardless of toggle.
Driven by. Office IT (severity-3 tax-inclusive opacity), Diaspora (tax-inclusive opacity severity-2 + currency confusion severity-2 — both addressed by the toggle + currency-dual display), Karim (severity-1 but volume), all other personas (severity-1).
Touches. #28, competitive §5.3 #1 + #3.
6.1.5 Mobile-first with cross-device session persistence¶
Build flow, casual flow, and product detail must work cleanly on a 6" Android screen. ADR-0003 cookie persistence + #11 Auth.js sign-in claim cover the cross-device handoff (research on phone, finalize on desktop). Image weight budgeted; per-product hero capped at 200KB; below-the-fold lazy-loaded.
Driven by. Karim, First-timer, Casual customer (all primary, all phone-primary). Layla and Office IT also benefit indirectly.
Touches. #28, #43 KPIs / observability / perf budget, ADR-0003, #11 Auth.js.
6.1.6 Quote mode for batch-shaped sessions¶
A "Quote mode" affordance on builds and casual carts switches outbound from "Buy" to "Request quote with line items prefilled" and exports to PDF/CSV for procurement workflows. Default tax-inclusive view ON in this mode. Distinct from the per-row "Confirm with retailer" affordance (§6.1.2) — Quote mode is for whole-cart line-item handoff to a retailer rep, not per-product discovery.
Driven by. Office IT (severity-3 "no batch quoting tool" — the persona-specific wedge that justifies B2B-tier listing surfaces in §6.3).
Touches. #28, #15 multi-merchant cart aggregator (Quote mode is the B2B-shaped variant of cart aggregation), #41 monetisation Stage-4 partner tier.
6.2 For #33 per-category buyer criteria signals¶
Per category, which spec dimensions each primary persona ranks by. Tabular. Drives #33 per-category spec dictionary depth + filter UX prioritization.
| Category | Karim ranks by | First-timer ranks by | Casual customer ranks by | Layla ranks by | Office IT ranks by |
|---|---|---|---|---|---|
| CPU | FPS-per-dollar in target games; clocks > cores for gaming | "Will it run [game]?" + "Compatible with my motherboard?" | Brand (Intel familiar / AMD if recommended) | Cores + RAM channel support for editing | Vendor stability + warranty + per-socket consistency across batch |
| GPU | FPS at 1080p/1440p in target games; VRAM for future-proofing; brand (NVIDIA preference) | "Will it run [game]?" + "Does it fit?" + "Will my PSU handle it?" | Brand recognition; price tier | VRAM (creator workflows); CUDA cores; color-accurate output | Rarely needed in standard office desktop builds; if specified, prioritize warranty + vendor stability |
| RAM | Capacity (16GB → 32GB) + speed; brand if mentioned | "How much do I need?" + "DDR4 vs DDR5?" | Capacity (number-bigger-is-better) | Capacity (32GB+ for creators); ECC awareness | Capacity per-machine spec compliance |
| Storage | Capacity + NVMe gen for boot drive; brand for reliability | "How much space?" + "SSD vs HDD?" | Capacity; brand if known | Sustained write speeds (video editing); capacity tiers | Vendor stability + warranty |
| PSU | Wattage + 80+ rating (Gold/Platinum); brand (Corsair/Seasonic preferred) | "Is this enough watts?" — relies on compat panel | Often N/A (prebuilt) | Wattage adequacy for high-end GPU + redundancy | Wattage adequacy + warranty |
| Case | Form factor + GPU clearance + airflow; aesthetics secondary | "Will my parts fit?" — relies on compat panel | Often N/A (prebuilt) | Aesthetic + sound dampening | Form factor + accessibility for service |
| Cooler | TDP rating + clearance | "Is this enough cooling?" | N/A | TDP + acoustics | TDP + warranty |
| Motherboard | Socket + chipset + connectivity (M.2 slots, USB) | "Does it match my CPU + RAM?" — relies on compat panel | N/A | RAM channels + I/O for capture / external | Vendor stability |
| Laptop (M3) | N/A | N/A | Brand line + screen + price | Apple line + RAM + screen color accuracy | Vendor + warranty + on-site service + screen + battery |
| Prebuilt PC (M3) | N/A | "Is this a good build for [game]?" | Brand + price + spec sheet | Often N/A (DIY or Mac) | Vendor + warranty + standardization across batch |
| Peripherals (v2) | Performance-tier (mouse polling rate, keyboard switch type, monitor refresh rate); brand-aware (Logitech G, Razer, SteelSeries) | "Cheap good keyboard?" | Brand-led (Logitech, Razer) + price | Brand + ergonomics + connectivity | Brand + warranty + standardization |
Cross-category implications.
- Filter UX must support both specs-first and brand-first browse for the same dataset. Specs-first (Karim, First-timer) needs sliders + multi-select on numeric dims. Brand-first (Casual, Layla) needs prominent brand-family navigation.
- Compat-panel-driven reliance from First-timer means spec dictionaries don't need exhaustive depth for that persona — they offload spec interpretation to the compat engine. Karim and Office IT need depth.
- Creator dimensions (color accuracy, sustained write, CUDA cores) are Layla-only acute — secondary tier, but visible.
- Office IT consistently weights vendor stability + warranty — surface these per category, even though they're secondary for Karim/First-timer.
6.3 For #41 monetisation — LTV / willingness-to-pay signals¶
Per persona, LTV intuition + affiliate-vs-CPC fit + featured-listing receptivity. Surfaces the high-LTV outliers and the low-margin-but-high-volume cohorts.
| Persona | Per-session GMV (rough) | Sessions per year | Annual LTV (rough) | Affiliate (CPS 1.5%) | CPC ($0.15) | Featured listing receptivity |
|---|---|---|---|---|---|---|
| Karim | $600-1,500 (build) or $200-500 (upgrade) | 4-8 | $30-100 affiliate / $5-15 CPC | Strong fit | Moderate (multi-click per session) | Moderate (annoying to specs-first cohort if poorly labeled) |
| First-time builder | $800-1,800 (one-time then lurks) | 1-2 (then converts to Karim or lapses) | $15-30 affiliate / $2-5 CPC | Strong fit | Weak (single-build session) | Low (anti-pattern for trust-seeking cohort) |
| Casual customer | $100-2,000 highly variable | 2-6 | $10-50 affiliate / $5-20 CPC | Strong fit | Strong fit | Strong fit (browse mode is featured-listing-friendly) |
| Office IT buyer | $5,000-30,000 per batch | 4-12 batches | $300-2,000 affiliate / $20-50 CPC | Outlier — high | Moderate | Strong fit (B2B suppliers want featured) |
| Layla | $1,500-3,000 (build) or $500-1,500 (upgrades) | 1-3 | $25-90 affiliate / $5-15 CPC | Strong fit | Moderate | Moderate |
| Diaspora buyer | $800-3,000 per gift purchase | 1-3 | $15-90 affiliate / $3-10 CPC | Outlier — high per session | Weak | Low (trust-seeking; doesn't browse) |
Implications for #41.
- Spec'd CPS 1.5% primary (per competitive §3.5) holds. Right shape across all six personas.
- Office IT is the high-LTV outlier and justifies a B2B-tier listing surface. Suppliers serving SMB IT buyers (Lenovo distributor, Dell partner, etc.) are willing to pay for featured placement. Stage-4 partner offering (competitive §3.5).
- Featured listings work cleanly for Casual and Office IT, are noise for First-timer and Diaspora. #28 must label
Sponsoredclearly (per competitive §3.4 #3) and keep them out of trust-seeking flows. - Diaspora is high per-session value but low frequency + zero featured-listing receptivity. Their unlock is a foreign-card-payment partner integration as a paid retailer service — not display monetisation.
- Affiliate (CPS) is universally a stronger fit than CPC for primary personas. CPC is a tail-tier fallback per the spec.
- First-timer's session is one-and-done — they convert to Karim (graduates) or lapse. Don't optimize for First-timer LTV; optimize for First-timer trust to drive Karim-conversion later.
7. Open questions for follow-up validation¶
The validation register. Each entry is a claim the doc makes that should be probed post-launch. Drives M2 telemetry events and any future outreach.
Persona-specific¶
- What % of Lebanese Karim-shaped sessions click out to ≥1 retailer? — Karim — Validate via: post-launch funnel telemetry. Target ≥40%.
- Average parts-per-build for Karim sessions — Karim — Validate via: build-completion telemetry. Target 6-9 (full builds).
- Compat-warning view → next-slot-pick funnel rate for first-timer-shaped sessions — First-time builder — Validate via: per-session funnel telemetry. Target ≥65%; <50% means warnings are scaring people off.
- Tier-preset click-through rate — First-time builder — Validate via: post-launch click telemetry once preset feature ships. Target 20% of new-session builds.
- Casual-flow detection threshold — Casual parts customer — Validate via: % of sessions touching only non-builder categories. Target detection — if <5%, casual flow is over-invested in.
- Time-on-page for single-item product pages vs build-flow pages — Casual parts customer — Validate via: telemetry. Casual flow should average shorter.
- Office IT batch-quote tool usage rate — Office IT buyer — Validate via: ask 2-3 areeba IT colleagues about workflow; observe whether B2B traffic patterns emerge in M2.
- Layla creator-dimension filter usage — Layla — Validate via: telemetry on creator-tagged filter applications once #33 ships creator dims.
- Diaspora "buy for someone in Lebanon" demand — Diaspora buyer — Validate via: 5-message DM survey to MASTER's Lebanese-abroad contacts; or post-launch session geo-distribution.
Cross-cutting¶
- Lebanese-Arabic cohort emergence — §5.1, §5.7 — Validate via: % of inbound traffic from Arabic-language SERPs and/or Casual-customer Arabic-region IPs. Trigger Arabic-UI revisit at >5%.
- PCAndParts dominance erosion — §5.5 — Validate via: outbound-click distribution across retailers. If PCAndParts share drops below 50%, market is fragmenting and aggregator value increases.
- WhatsApp-deep-link click rate — §5.3, §5.5 — Validate via: outbound channel telemetry. Target ≥20% of outbound clicks go to WhatsApp deep-link rather than direct retailer URL.
- Tax-toggle preference distribution per session type — §5.3, §6.1.4 — Validate via: toggle-state telemetry. Informs default per-flow.
- Brand-first vs specs-first navigation distribution — §5.4 — Validate via: filter-usage telemetry on category pages. Informs whether casual-flow brand-family nav investment is paying off.
Anti-persona drift signals (from §5.7)¶
- Crypto / AI tinkerer drift — >5% sessions configuring 4+ GPU slots, dual-CPU, or workstation chipsets
- Wholesaler drift — sessions with cart values >$10k or >20× same SKU
- Used-only buyer drift — Olx LB referrer share >10%
- Apple-only drift — laptop "Apple only" filter share >20% post-#24
- Phones drift — phone-comparison search referrers >5%
If any drift signal trips, revisit scope before passively absorbing the cohort.
8. See also¶
- #36 ticket — driver
competitive-landscape.md— format peer; substantive substrate this doc reuses heavily- Specs → 2026-04-25 aggregator design — original spec defining the dual-track Builder / Browse vision (§2)
- Architecture → use-cases.md — current use-case model where the Casual-flow gap lives
postmortems/2026-04-26-v01-prototype-rejected.md— the AI-slop UI rejection that made this kind of foundation work necessary
Downstream consumers (active): - #15 multi-merchant cart aggregator — consumer of §6.1.6 Quote mode + Karim's cross-store cart wedge in §5.6 - #28 page design — primary consumer of §6.1 - #33 per-category buyer criteria — primary consumer of §6.2 - #41 monetisation — primary consumer of §6.3 - #43 KPIs / observability / perf budget — consumer of §5.2 device + §7 telemetry list
Downstream consumers (deferred): - #37 i18n — deferred no-op per §5.1; revisit on §5.7 Arabic drift signal
Surfaced from this work: - New issue: feat(use-cases): add casual Browse & Buy flow distinct from Builder — created with this doc; addresses the gap that #28 cannot resolve without it