Websites
Editorial, fast, accessible. Designed in Arabic and English — not translated into them.
Deep dive
A website is the only marketing surface that has to work for everyone you've never met. It needs to load fast on a 4G connection in Jeddah, render correctly in Arabic on a Samsung phone in Dammam, and be readable to a procurement officer who has 90 seconds before their next call. Most agency-built sites in Saudi Arabia fail at least one of those tests — usually the Arabic one.
We build websites in Astro or Next.js depending on what the project needs. Static-first for content sites; React-first for product surfaces. Every page is designed bilingual from the wireframe up — same content density, same visual hierarchy, AR and EN side by side from the first sketch.
Performance is non-negotiable. Our sites target Lighthouse scores above 95, image-format negotiation (AVIF, WebP, JPEG fallback), and zero layout shift on Arabic content. The Arabic version is not a heavier copy — it's the same site, in the right language, with proper RTL handling baked into the layout primitives.
We integrate with the CMSs Saudi teams actually use — Sanity, Strapi, custom Postgres, or a quiet headless setup nobody has to think about. SEO and analytics are wired in at launch, not added in a 'phase 2' that never comes.
Arabic-first
Most CMS templates treat RTL as a CSS property to flip. We treat it as the layout direction the site was designed in. The result is content that breathes correctly in Arabic — line lengths, spacing, type pairing, and even number formatting — without the squeezed-and-stretched feel that haunts translated sites.
Deliverables
- Information architecture
- Bilingual UI design
- Astro/Next.js build
- CMS integration
- SEO + analytics
What's not included
- WordPress and PageBuilder rebuilds. We build static-first or React-first; if WordPress is the right answer for you, we'll say so and recommend a partner.
- Single-page 'business card' sites with a contact form. Not because they're bad, but because we're overkill for them.
- Sites without analytics, SEO, or accessibility built in. Those aren't optional in 2026.
Process
-
01 Strategy
Goals, audiences, content map, and the metrics that will define success.
-
02 Design
Bilingual design system, then page-level work in Arabic and English in parallel.
-
03 Build
Astro or Next.js, content modeled in Sanity, deployed to the edge.
-
04 Polish & Launch
Performance audit, accessibility check, SEO, then a quiet launch.
Typical timeline
6–10 weeks
Timelines flex with project scope, team availability, and response time on your side. We give a precise schedule after the discovery call.
Common questions
How does a custom Astro/Next site compare to Webflow or WordPress?
Webflow and WordPress are great for fast, template-led sites. Custom Astro/Next sites are right when you care about Arabic-first UX, sub-second load times, multi-locale routing, or eventually plugging the site into a custom system. We help you decide before signing — most clients spend less than they expected once we map what they actually need.
How long does a typical website project take?
8–14 weeks end-to-end for most editorial / marketing sites — strategy and IA in weeks 1–3, bilingual design in 4–7, build and integration in 8–12, polish and launch in 13–14. Larger sites with deep CMS work or custom integrations can run longer; we'll tell you in the first call.
Do you handle SEO?
Technical SEO yes — sitemaps, structured data, hreflang for AR/EN, meta architecture, performance, accessibility. Content SEO (keyword strategy, ongoing publishing) we set up the foundations and hand to your team or a content partner. We do not run monthly SEO retainers.
Will my team be able to update the site without us?
Yes — and we set this up explicitly. CMS-managed pages (journal, services, testimonials, work index) are fully editable from a clean admin. Code-level changes to layout or new templates are us. We send a Loom walkthrough at launch and stay reachable for ad-hoc questions.
Do you provide hosting?
We deploy to Vercel, Cloudflare Pages, or your own server depending on your stack and data-residency needs. For Saudi clients with KSA data-residency requirements we provision a dedicated server inside the Kingdom and handle ops.