Blog Overview
Our published band is SAR 10,000 to 25,000 over 8 to 14 weeks. This is what it covers, the six factors that push the number higher, and the five lines every proposal should share.
Corporate website quotes in Saudi Arabia can look identical and differ by a factor of two. The difference is rarely design quality. It is what the scope does not say: is there research? Is translation included? Do you own the CMS? Is there support after launch?
This article breaks down our published band, what pushes a project above it, and how to read two proposals against the same lines. The numbers are our published figures, not a market estimate.
What the band covers
A corporate site is not a homepage and nine pages. It is a content system, a digital identity, and a conversion path. The published band covers discovery and information architecture, eight to fifteen templates, a bilingual build, a CMS your team can operate, baseline analytics, an accessibility pass, and a launch with short post-delivery support.
The difference between a “page” and a “template” is the first thing to understand. Fifty pages built from eight templates is very different work from fifty unique pages. The second needs design, review, and testing for every page; the first needs a good system and structured content.
What pushes a project above the band
Six factors raise the number more than anything else. Each can be planned for, but its cost cannot be hidden.
| Factor | Effect | How to control it |
|---|---|---|
| Migration from an existing site | Needs a URL inventory, 301 map, and SEO loss testing | Inventory URLs before design, not after |
| Integrations | Ticketing, payments, CRM, or a client portal | Name them in discovery, and test interface contracts early |
| Content volume | Hundreds of pages need structure, writing, and Arabic review | Start with the core stories; defer the rest until after launch |
| Full bilingual delivery | Not translation: RTL layout, type, content, and testing | Design both directions from the first template |
| Approval layers | Every department reviews every page, and the rhythm stops | One owner, a weekly review slot, and written decisions |
| Sector requirements | Government, finance, or health adds documentation and compliance | Put the requirements into acceptance criteria from day one |
The five lines every proposal should share
Compare proposals on five lines, not the final number. First: the number of unique templates, not pages. Second: are research and information architecture included, and who does them? Third: is delivery fully bilingual, including RTL, typography, and content? Fourth: who owns the content, code, and hosting after handover? Fifth: what happens in the first ninety days after launch?
A proposal that omits these lines is not merely incomplete. It is a proposal that will cost you the difference later, usually at launch when you have no time to negotiate.
Why page count is a bad unit
From reading to shipping
Want this built, not just explained?
Bring us the problem behind the article. We will tell you what it takes, what it costs, and whether we are the right team.
A page is not a unit of measurement, because pages differ in complexity. A single service page may need a form, a pricing table, FAQs, and internal links. An “about” page may need text and a photo. If you price by page, you either overpay for the simple or underpay for the complex.
The better unit is the functional template: service, article, case study, contact. Each template has states, fields, and rules. Template count drives design and build; page count drives content only.
Corporate site, store, or platform?
A corporate site sells trust. A store sells product. A platform runs an operation. The three need different decisions, and the first mistake is ordering a “website” when the need is a platform. If the user returns weekly to manage an order, a file, or a portfolio, you are not building a corporate site. You are building a web application. The difference is not only visual: it sits in roles, permissions, data structure, and testing.
If the goal is to convince a government buyer or an institutional partner, the corporate site is the right tool. A small set of pages has to carry proof: case studies, documents, certificates, policies. That is what separates a corporate site from an online brochure, and it is worth designing the scope around. To compare the options, start from web platform development and read the published cost breakdown before you request a quote.
After launch
A site does not end on launch day. It needs security updates, backups, performance monitoring, link repairs, and content improvement. Ask before you sign: who updates the stack? Who owns the domain and hosting? How long is support included? What does a small change cost? If the answers are not written, you are buying a project with no maintenance.
Before you request a quote
Write the problem, not the page list. “We need a site” is not a problem. “We cannot convince government buyers” is.
Inventory existing content. What can be reused? What needs writing? Who owns the Arabic copy?
Name the one conversion. A contact form, a quote request, or a call booking. A site with no clear conversion is a brochure.
Know who decides. One person, not a committee. The committee reviews; the owner decides.
Ask for a previous site. Not a testimonial. Open it on your phone and confirm it is fast in Arabic.
Ask about code and content ownership. Get the answer in the contract, not in a conversation.
Ask for the launch plan. Who moves the domain? Who tests the forms? Who watches errors on day one?
Agree acceptance criteria. Speed, accessibility, two languages, security. Written before the build.
Frequently asked questions
Is SAR 10,000 enough for a full corporate site? It covers a focused site with eight to twelve templates in two languages. Larger projects are quoted after discovery.
Why does it take 8 to 14 weeks? Because content, reviews, and testing are part of the work, not additions to it.
Is translation included? Bilingual design is included. Writing or reviewing Arabic content is a separate line.
WordPress or Next.js? It depends on your editorial team, integrations, and security. We have an article comparing the two.
What if we need changes after launch? We agree a support window and a clear change rate, both written into the contract.
Sources
- web.dev: Web Vitals — the LCP, INP, and CLS thresholds we use as acceptance criteria.
- WCAG 2.2 — the accessibility criteria required at handover.
- Milliseconds make millions — the link between speed and conversion.
- Rasad's published price bands — the published figures for this service.
- UI/UX design cost — the difference between site design and product design.
