Practice 02 · Websites & Digital Experience

Fast, mobile-first bilingual sites engineered for how Saudis actually buy.

Real /ar routes — not Google Translate toggles. Lighthouse-graded performance. WhatsApp-first conversion architecture. Built for the device 92% of your Saudi traffic uses.

Bilingual homeEN · /
Get a bilingual audit →

Brand

Web

Growth

9:41
/ar gated

Arabic route under native review

WhatsApp

Lighthouse

96

/ 100 mobile

Bilingual website rendered across three devices with a Lighthouse mobile score of 96.

Two real routes. Same architecture. Mirrored, not overlaid.

Decision console

Pick the route before the scope.

Use this room before a proposal call: confirm the pressure, inspect what must be credible, and see the first handoff before a scope is agreed.

Buyer fit

Decide if this is the right route.

Saudi SMEs with weak or no digital presence

Websites & Digital Experience

Site is 2018 or older
No Arabic version, or auto-translated
Mobile experience is broken
Book this route

Device studio

Prove the bilingual path on screen.

The page needs a sharper RTL/LTR proof moment that connects devices, routing, QA, and release gates.

Device QA

Websites & Digital Experience

LTR desktop

QA route visible.

RTL mobile

QA route visible.

MobileDesktopRTLTrack

Editable route report

Pressure

85

Two real routes. Same architecture. Mirrored, not overlaid.

Proof

77

LCP target

Handoff

80

Build gate

1

Buyer scene

Mobile route

Two real routes. Same architecture. Mirrored, not overlaid.

2

Pressure cue

Real /ar routes

WCAG 2.1 AA target

3

Decision cue

WhatsApp-first conversion

The page should make the first buyer decision visible before proposal scope.

Acceptance gates

LCP target< 2.5s
AccessibilityWCAG 2.1 AA
Bilingual modelReal /ar

Route proof

01

EN

Largest contentful paint, mobile

02

AR

axe-core verified

03

WhatsApp

Separate routes, mirrored layout

04

Analytics

Largest contentful paint, mobile

What ships

What's actually shipped.

Six categories of work, every one with a measurable acceptance gate. No 'design + dev + magic' line items.

01

Bilingual website (EN + AR, RTL-native)

Acceptance · axe-core scan + native AR review pass

Real /ar routes, not toggles

02

UI/UX system + component library

Acceptance · component inventory + storybook-style preview

Reusable React component set

03

Performance hardening

Acceptance · published Lighthouse report

Image optimization (AVIF + WebP)

04

Accessibility audit

Acceptance · axe-core zero-violation report

Keyboard-nav across all interactive areas

05

Conversion + WhatsApp routing

Acceptance · 4-path conversion map signed

WhatsApp deep links with presets

06

Analytics + attribution

Acceptance · live dashboard handover

GA4 or Plausible setup

The bilingual difference

Two real routes. Same architecture. Mirrored, not overlaid.

Auto-translated toggles fail Saudi buyers in two seconds — broken hierarchy, wrong directional arrows, English idioms in Arabic clothing. We build separate /ar/ routes that share one component layer but render in true RTL with native typography line-heights. The buyer never knows the EN route exists.

Live demo · Scroll either pane

Mirrored sync
/EN · LTR

Hero

Bilingual digital growth.

Read more →

Practice

Brand & Presence Launch.

Read more →

Practice

Websites & Digital Experience.

Read more →

Practice

Growth & Visibility.

Read more →

Vertical

Engineering Firms.

Read more →

Process

Six-step operating system.

Read more →
AR · gated/ar review

Hero review

Arabic copy gated for native approval.

Native review →

Practice review

Arabic copy gated for native approval.

Native review →

Practice review

Arabic copy gated for native approval.

Native review →

Practice review

Arabic copy gated for native approval.

Native review →

Vertical review

Arabic copy gated for native approval.

Native review →

Process review

Arabic copy gated for native approval.

Native review →

Two real routes. Same architecture. Mirrored, not overlaid.

Process

Six phases. Performance + accessibility gated, every one.

From audit to live. Each phase ends with a published acceptance test the founder can read.

Phase 01Lead strategist

Audit + IA

Sitemap + IA approved by founder

IA + content map

Phase 02Design lead

Design system

Component library reviewed in browser preview

Storybook-style preview link

Phase 03Web lead

Build

All EN routes pass component QA

Staging URL + component inventory

Phase 04Arabic reviewer

Localize

All AR routes pass native review + RTL QA

AR staging URL + reviewer audit log

Phase 05Web lead

Performance + a11y

Lighthouse 90+ mobile · axe-core 0 violations

Performance + a11y report (PDF)

Phase 06Founder + analytics lead

Launch + handover

Analytics live · WhatsApp routing tested · DNS cut

Handover doc + dashboard access

Pricing

Pricing in SAR. Two engagement models.

Setup is for SMEs needing a fast, credible bilingual presence. Full bundle is for growth-stage and engineering buyers needing depth.

One-off project

Digital Presence Setup

SAR 7,000–14,000

50% start · 50% on launch3–5 weeks
One-off projectChosen

Full bilingual build

SAR 12,000–24,000

40% start · 30% mid · 30% on launch6–9 weeks

Hosting (Vercel/cPanel) and ongoing maintenance quoted separately. SAR-only invoicing. ZATCA-ready.

Ready when you are

See how a real bilingual site performs.

Send us your current site or a brief. We'll come back with a Lighthouse audit + a working range inside 2 business days.

One Saudi business day · Founder-led · NDA-ready