HomeCompanyPortfolioServicesSoftware & AIMobile AppsIndustriesLocationsPricingBlogContact
Englishالعربية
Home  /  Blog  /  Design
DesignApr 10, 2026·10 min read

How to Write a Web Design Brief That Gets Accurate Quotes

IW
IITWares Editorial Team
Digital Strategy & Search
How to Write a Web Design Brief That Gets Accurate Quotes

A working guide to web design brief for companies operating in Saudi Arabia — grounded in local search behaviour, local regulation and what we see across client accounts.

Most website problems presented as design problems are actually structure, speed or trust problems. Getting those three right does more for enquiry volume than any amount of visual refinement applied afterwards.

Framing the problem properly

Most teams arrive at web design brief after something stopped working: enquiries fell, a competitor became visible, or a target was missed. That context matters, because the right first move differs depending on whether you are fixing a decline or building from a standing start. Diagnose which situation you are in before applying anything below — the sequence changes completely, and applying a growth playbook to a decline problem wastes a quarter.

The language switch is a conversion element

Put it top-right in the English view, top-left in Arabic, label it in the target language, and preserve the current page rather than dumping users on the homepage. Remember the choice. Default by browser preference on first visit but never trap: a visitor who wants English must always be one click away from it. This small component is one of the most frequently mishandled details on bilingual Saudi sites.

Performance budgets prevent slow decay

Agree a maximum page weight, a maximum number of third-party scripts and a target for Interaction to Next Paint before development begins, then enforce them in review. Sites do not become slow in one release; they accumulate a chat widget here and a tracking pixel there until a fast build is a slow site two years later. A written budget is what stops that drift.

Arabic typography deserves its own scale

Arabic script has no capital letters, taller ascenders and connected letterforms, so it needs roughly 10–15% more line height and often a slightly larger optical size than Latin text at the same nominal point size. Choose a family with a genuine Arabic cut rather than a Latin face with bolted-on glyphs. Test with real content at real lengths — Arabic translations commonly run shorter than English, which breaks layouts tuned to the wrong measure.

Trust signals Saudi buyers look for

A visible commercial registration number, a national address, a landline in addition to mobile, a Maroof badge for ecommerce, named team members with photographs, real client logos with permission, and a WhatsApp route to a human. Saudi buyers verify before they enquire, and the absence of these elements costs more conversions than any amount of aesthetic refinement recovers.

Design for a mid-range Android on a moving connection

Internet penetration reached roughly 99% of the population at the end of 2025 and around three-quarters of people can reach a 5G device, but the median handset is not a flagship and a large share of sessions happen in transit. Design to that reality: generous tap targets, minimal script, images sized for the viewport actually served, no layout dependent on hover, and a first meaningful paint under two seconds. Test on a throttled mid-range device before signing off, not on the designer's laptop.

The businesses that win in Saudi search are rarely the biggest. They are the ones that did the unglamorous work consistently for four quarters.

RTL is a layout system, not a text direction

Setting dir="rtl" flips text and starts the argument. Navigation order, breadcrumbs, progress steps, sliders, form alignment, icon direction, chart axes and animation origin all need deliberate decisions. Meanwhile numerals, telephone numbers, email addresses, currency codes and Latin brand names stay left-to-right inside a right-to-left sentence. Use logical CSS properties — inline-start and inline-end rather than left and right — and the two directions can share one stylesheet honestly.

Speed is a conversion variable

Every additional second before content appears removes a measurable slice of conversions, and the effect is sharper on mobile connections. Before commissioning a redesign to fix conversion, check whether the current site simply loads too slowly. Performance work is cheaper, faster to deploy and more reliable in its effect than most creative changes.

Core Web Vitals, honestly

Interaction to Next Paint is the metric that catches most Saudi sites out, because it punishes heavy third-party scripts — chat widgets, tag managers, multiple pixels, review carousels — that accumulate over years. Largest Contentful Paint is usually an image or web-font problem: serve modern formats, set explicit dimensions, preload the hero, and subset Arabic fonts rather than shipping the full glyph set. Cumulative Layout Shift is almost always ads or late-loading banners. Fix in that order and the field data follows within a month.

Typical project shape

StageTypical windowWhat you should see
Discovery and content2–3 weeksUsually the critical path, not development
Design system and key templates3–4 weeksBilingual from the first artboard
Build and integrations4–8 weeksVaries most with third-party systems
QA, RTL testing and launch1–2 weeksReal devices, throttled connections

Windows assume consistent execution and a market of ordinary competitiveness. Treat them as planning ranges, not commitments.

Duplicate content in a bilingual, multi-branch site

Faceted navigation, session parameters, printer views, and city pages that differ by two words all create near-duplicates. Set self-referencing canonicals, block parameter crawling deliberately, and give each city page genuinely distinct content — local pricing, local case work, local landmarks and directions. If two pages can be swapped without a reader noticing, Google will pick one and it may not be the one you want.

Logs tell the truth that reports do not

Server log analysis shows which URLs Googlebot actually fetches, how often, and where it wastes budget. On large Saudi catalogues the usual finding is that most crawl activity goes to filtered listing URLs while new product pages wait weeks. Fixing that with parameter handling, pagination discipline and a clean XML sitemap is often worth more than any content project running in parallel.

Redirects, migrations and the cost of getting it wrong

Map every old URL to its closest new equivalent one-to-one; never bulk-redirect to the homepage. Use 301s, not 302s. Keep the old sitemap live for a few weeks so the redirects are discovered. Preserve internal links, then update them. Watch Search Console coverage daily for the first fortnight. Migrations that lose traffic almost never lose it to bad content — they lose it to missing redirect mappings nobody checked.

The short audit

Crawl, render, index, rank — in that order

Every technical problem sits in one of four stages, and diagnosing the stage saves weeks. If the URL is not crawled, look at robots.txt, internal links and server response. If it is crawled but not rendered, look at JavaScript and blocked resources. If rendered but not indexed, look at quality, duplication and canonicals. Only when a page is indexed does ranking work apply. Teams that skip this order end up rewriting content for a page that Googlebot never fetched.

Where to start this week

Test your site on a throttled mid-range Android. Time it. Then check the Arabic version for mirrored layouts, correct typography and a language switch that preserves the page. Add the trust elements Saudi buyers look for — registration number, national address, real photographs, a WhatsApp route. Most sites gain more from that afternoon than from a full redesign.

The Saudi market is moving quickly enough that a decision deferred by two quarters is usually a decision made by a competitor instead. Choose the smallest useful version and start.

[ Key Takeaways ]
RTL is a layout system, not a text direction
Arabic typography deserves its own scale
Redirects, migrations and the cost of getting it wrong
The language switch is a conversion element
Share

Frequently asked questions

Do we need separate designs for Arabic and English?+

One design system, two directional treatments. Layouts mirror, typography scales differently, and some components need genuinely different behaviour — but it should be a single system, not two projects.

How long does a website project take?+

A focused business site typically runs eight to twelve weeks; a bilingual site with integrations and a CMS runs twelve to twenty. Content readiness is usually the critical path, not development.

WordPress or custom?+

WordPress where content changes often and requirements are standard. Custom where business logic is distinctive or integrations are heavy. The wrong answer is a heavily customised WordPress build imitating custom software.

What actually improves conversion most on Saudi sites?+

In our experience: page speed, visible trust signals, a WhatsApp route to a human, and shorter forms — usually in that order.

Do you work with businesses outside Jeddah and Riyadh?+

Yes. We work across the Kingdom including Makkah, Madinah, Taif and the Eastern Province, and much of the work runs remotely with on-site sessions at the points where they add value.

Keep Reading

All Articles →

Ready to put these ideas to work?

Start a Project →