FAQ — every question we hear, answered

A business website in Saudi Arabia is scoped after discovery. A 5–8 page bilingual brochure site, a content-heavy service site, and an e-commerce platform all need different levels of work. The scope-review floor covers Arabic-first RTL, Core Web Vitals, ZATCA-aware checkout where relevant, and a transparent CMS hand-off.

A business website in Jordan is scoped after discovery. A brochure site, content-heavy service-area site, e-commerce store, and custom platform each need a different delivery model. Scope differs from Saudi Arabia because local market needs, currencies, content depth, and integrations differ. We quote per market instead of converting one package.

Standard business websites ship in 4–6 weeks. Content-heavy or service-area sites run 6–10 weeks. E-commerce on a headless stack runs 10–16 weeks. Government and enterprise platforms run 12–24 weeks. We share weekly Vercel preview builds from week 2 — no surprise reveals.

Yes — typically 40% to start, 30% at design sign-off, 30% on launch. Larger engagements use milestone-based payment schedules tied to deliverables. We do not take 100% upfront and we do not invoice on hours-only models for production work.

Yes. Every Saudi and Jordan project is Arabic-first. RTL parity uses Tailwind logical properties; Arabic typography uses fonts tested for legibility (IBM Plex Sans Arabic, GE SS, or your brand-licensed face); numerals respect locale; Hijri date support is built in; bilingual switching keeps user state.

Next.js, React, TypeScript, and Tailwind by default. Headless CMS (Payload, Strapi, or WordPress headless) per engagement. Netlify or Vercel hosting for non-PDPL Tier-2 work; STC Cloud or Mobily for in-Kingdom hosting. The same stack that powers most modern Saudi government platforms.

Yes. URL inventory + canonical map before launch, 301 redirect manifest covering every legacy URL, schema parity audit, content parity audit, pre/post Core Web Vitals snapshots, and Search Console post-launch monitoring with weekly delta reports.

Mada (~95% Saudi card coverage), Apple Pay, STC Pay, SADAD. Tabby and Tamara for BNPL where retail conversion matters. HyperPay or Moyasar as the unified gateway for most engagements. ZATCA Phase 2 e-invoicing wired into checkout.

Shopify is great for quick launches under 50 products with standard features. Custom (Next.js + headless CMS) is better for complex product configurations, multi-vendor marketplaces, or deep ERP/inventory integration. We build both and recommend based on your roadmap, not a default.

Mandatory for any e-commerce site issuing B2B receipts, and we wire it into every Saudi e-commerce build by default. We integrate with FATOORAH, ZATCA SDK, or your existing ERP's ZATCA module — whichever is the lowest-friction path for your stack.

SEO retainers are scoped after discovery based on competition, content volume, technical issues, and number of target locations. Local SEO and Google Business Profile management are lighter than enterprise SEO, while multi-location Saudi campaigns need more content, reporting, and technical cleanup.

Every site we build ships with foundational SEO baked in (schema, sitemap, robots, Core Web Vitals, internal linking, hreflang). For active competition on commercial keywords, you need a dedicated SEO retainer on top of the build — content production, technical SEO, link building, and monthly reporting.

Yes — Arabic SEO is one of our specialisations. Saudi search behaviour is roughly 60% Arabic, 40% English at the head, with bigger Arabic shares in specific verticals. We do Arabic keyword research as a primary research pass (not as a translation of English keywords), Arabic on-page content, Arabic schema, and Arabic GBP posts.

Saudi mobile app development is scoped after discovery. A startup MVP, a production app with iOS, Android, payments, authentication, and admin tools, and a government-grade platform with Nafath, Tawakkalna, or PDPL controls all require different architecture and QA depth.

React Native fits 80% of Saudi business apps. Flutter is preferable for pixel-perfect UI or heavy animation. Native iOS/Android is the right call for AR, deep hardware integration, or apps extended for years by an in-house team.

Yes. AI prototyping is scoped after discovery for a 2–4 week proof-of-concept that validates an AI hypothesis with real users. ChatGPT, Claude, ALLaM, Falcon, and Jais integrations. PDPL data residency and SDAIA-aligned engineering by default.

Headquartered in Amman, Jordan. About 70% of work is for Saudi clients (Riyadh, Jeddah, Dammam, Mecca, Medina). We also serve Iraq (Baghdad, Erbil), Jordan (Amman, Irbid), and the GCC (UAE, Kuwait, Bahrain, Qatar, Oman). Standard delivery is fully remote; we travel for kickoffs and major reviews.

Zoom for meetings, Slack for daily comms, project management tools (Linear / Notion / Trello per engagement) for task tracking, weekly Vercel preview builds for transparency. English or Arabic — we work in both.

Government-scale engineering muscle (20+ digital products including national-scale platforms across 10+ Saudi ministries) plus SME-grade scope and timelines. Most buyers either accept enterprise overhead for enterprise quality or accept template quality for a lower scope. We sit between those.

Yes — every figure is verifiable, but client names are withheld under NDA. Reviews and case studies use anonymized format (role + city). The metrics, sectors, and outcomes are real.