If two Saudi website quotes for "the same" project differ threefold, do not compare the totals — they are almost certainly not pricing the same product. One bundles Arabic, hosting and support while the other silently excludes them; one prices a template setup, the other a custom build. The fix: build one scope sheet from the project you want, force both quotes onto it line by line, price the gaps in the cheaper document, and send both vendors the same questions in writing.
This article assumes you hold the documents. What a complete Saudi quote should contain is a separate standard — see what a Saudi website quote should include — applied here, not repeated.
The short answer: stop comparing totals — compare scopes first (method at a glance)
Five steps. One: write one scope sheet — the deliverables you are buying — before re-checking prices. Two: map every line of both quotes onto it, marking each present, vague or missing. Three: interrogate the Saudi lines: ZATCA e-invoicing, mada, Arabic, hosting. Four: price the gaps, using the other quote or a written vendor price. Five: compare the non-price lines — milestones, timeline, ownership, support — then run one clarification round, identical questions to both.
What should differ at the end is narrow: design depth, build method, seniority, support level. Everything else is a scope mismatch, not a price difference.
Why the totals differ threefold: the four honest reasons and the two dishonest ones
Four honest reasons explain most gaps. Build method: a configured template and a custom build are different products, both legitimate. Scope depth: one quote includes content writing and Arabic; the other assumes you supply everything. Process: discovery, staging reviews and testing appear in one, not the other. Support and ownership: one price carries post-launch support and full handover; the other ends at launch.
Two dishonest patterns explain the rest. Low-entry pricing quotes the visible build, moving essentials — Arabic, integrations, revisions — into later change requests. Padding inflates the expensive quote with vague lines ("advanced SEO setup", "complete digital solution") behind which no deliverable sits. Your sheet exposes both. Broader context: our guide to website costs and choosing a partner in Saudi Arabia.
Step 1 — Build one scope sheet and force both quotes onto it
Create a three-column table: scope line, Quote A, Quote B. Rows are your project, in your words: pages and templates, design, content and languages, store or booking functions, integrations, launch work, training and support. Keep rows concrete enough to price alone — "Arabic version of all pages, fully right-to-left" is a row.
Transcribe, do not summarise: copy each quote's promises against each row, including quantities — pages, revision rounds, languages, support period. Where a quote is silent, leave the cell empty; the empty cells hide your threefold difference.
Step 2 — Map every line: same work, different words; present, vague or missing
Classify every cell. Present: named in enough detail to hold the vendor to it. Vague: words exist, no deliverable does — "SEO friendly", "modern design", "full support" — vague counts as missing until defined in writing. Missing: the row is absent.
Expect translation work. One vendor's "CMS setup and configuration" and another's "website build" may be the same row; one quote's "design" line may hide what the other splits into discovery, concepts and templates. General anatomy sits in what a fixed-price website quote should include; stay on your two documents.
Step 3 — Interrogate the Saudi lines in both documents: ZATCA, mada, Arabic, hosting
Four rows decide many Saudi comparisons. ZATCA e-invoicing: if the site takes orders or payments, find its integration line. ZATCA describes e-invoicing (Fatoorah) as a structured electronic process implemented in phases — does each quote include connecting invoicing to it, exclude it, or omit it? Mada: SAMA describes mada as the national payment system spanning point-of-sale, ATMs and e-commerce; does each quote name mada acceptance through a gateway as included work, and who arranges the account? Arabic: is the full version — translation, right-to-left layout, quality checks — priced, an assumption you supply translations, or absent? Hosting and domain: where will the site live, in whose account, who renews it? A quote hosting everything with the vendor prices a different ownership product from one handing you the keys.
Step 4 — Price the gaps: what the cheaper quote will charge you later
A missing line is not a saving; it is a deferred invoice. For every missing or vague row in the cheaper quote, get a number: ask that vendor in writing what adding it costs, or use the other quote's line price. Add them to the cheap total — the adjusted figure is your first honest comparison.
Also price the assumptions: if one quote assumes you provide Arabic content, photography and product data, that cost has moved to your team — treat "client provides" as a price in time. Check revision rounds: a low quote with one round and paid changes can finish above a higher quote with a realistic allowance. Our quote calculator can sanity-check the total; your sheet remains the evidence.
Step 5 — Compare the non-price lines: milestones, timeline, ownership and support
With scopes aligned, compare the contract-shaped lines. Payment: how much is due upfront, what milestones trigger the rest, what "completion" means. Timeline: days or weeks, starting when — and what happens if the vendor slips? Ownership: do domain, hosting, licences and source files end in your name on final payment, or the vendor's? Support: what period is included, what counts as a defect fix versus a paid change, and what support costs afterwards?
This is where a better expensive quote proves itself — and padding hides. Record answers on the same sheet.
The clarification round: the same questions, sent to both vendors, in writing
Send both vendors one identical message listing every vague or missing row, asking for a defined line or price. Adapt questions like these: "Is the full Arabic version included, and if not, what does it cost?" "Does your price include ZATCA e-invoicing integration and mada gateway setup, or are they excluded?" "Whose account holds hosting and the domain, and what transfers to us at launch?" "How many revision rounds are included, and how are changes priced?" "What support follows launch, and for how long?"
Judge replies as part of the quote. See also our web development in Saudi Arabia overview. Precise answers amending the document are a quality signal; verbal answers, or a higher re-quote still ignoring your rows, tell you the gap was structural. Honest vendors welcome the sheet; vendors who relied on the fog resist it.
A worked example: two quotes, one scope sheet (illustrative)
The pair below is illustrative, constructed for this method — not a real vendor quote or market data. Quote A totals SAR 18,000; Quote B totals SAR 54,000. Mapped onto one scope sheet, the picture changes:
| Scope line | Quote A (illustrative) | Quote B (illustrative) |
|---|---|---|
| Design and build | Template setup | Custom design and build |
| Arabic version | Missing | Included, with RTL checks |
| Content writing | Missing — client provides | Included for main pages |
| ZATCA e-invoicing integration | Missing | Included |
| Mada gateway setup | Vague — "payments ready" | Named, included |
| Hosting and domain | Vendor's account, not stated | Client's account, handover included |
| Support after launch | Missing | Defined period |
Pricing A's gaps using B's line values adds substantially to A's total — and still leaves A on a template build with content to produce in-house. A real difference remains, but it is now explained; you can choose knowingly.
Common mistakes when comparing website quotes
The classic mistake is comparing totals alone — haggling the expensive vendor down or picking the cheap one — without discovering the documents price different products.
Other errors: accepting verbal answers instead of amended documents; letting each vendor re-quote in their own structure; ignoring the Saudi rows because both quotes "probably include them"; forgetting ownership until launch. One sheet, one question set, one written record prevents most.
FAQ
Why do two quotes for the same website differ so much in price?
Usually because they are not pricing the same product: build method, scope depth, process and support differ, and one quote often bundles Arabic, hosting and support the other excludes. Map both onto one scope sheet to break the gap into explained, missing and vague lines.
Should I just choose the cheaper quote if the totals are far apart?
Not before you price its gaps. Add written prices for every missing or vague line — Arabic, integrations, content, support — to the cheaper total. If it is still cheaper on an identical scope, it may be right; if the gap mostly closes, the original total was never the real price.
How do I compare quotes that use different words for the same work?
Map by deliverable, not wording. Write the scope sheet in your own words, transcribe what each quote promises against each row, and classify every cell present, vague or missing. Treat vague lines such as "full support" as missing until defined in writing.
What questions should I send back to both vendors?
Send identical written questions covering every vague or missing row: is Arabic included, and at what price if not? Are ZATCA e-invoicing integration and mada gateway setup included? Whose account holds hosting and the domain? How many revision rounds apply, and what support follows launch?
When is the more expensive quote actually the better value?
When its premium maps to deliverables you need — custom design over a template, included content and Arabic, integrations, staged payments, clean ownership and defined support. If the premium sits in vague lines the vendor cannot itemise, it is padding, not value.
Want one clean quote on the scope you actually normalised? (CTA)
If the forensic leaves both documents full of holes, have your scope sheet priced cleanly, line by line. WebStackRank provides an itemised proposal within 24 business hours, with 50% due to begin and 50% at launch. Start from how much a website costs and compare our lines against your sheet row by row.
