Skip to content
العربيةLet’s talk

Practical guide

How to compare website design quotes in Jordan

Specify templates, bilingual content, forms and ownership before asking for a website quote. Work through a Jordanian buyer’s example and compare first-year costs.

Lava Solutions · · 3 minute read

Hand-drawn website layouts on paper, with blue, purple and green watercolor sections.
Illustrative stock photo. Photo: Hal Gatewood / Unsplash.

One supplier quotes for a bilingual website. Another quotes for designing its English pages and installing a language switch. Both descriptions might say “Arabic and English website”, yet your team would inherit different amounts of work. Before comparing prices, give each supplier the same list of pages, content responsibilities, working features and handover items. Ask for the proposal in Jordanian dinars or have each supplier state its currency.

Count layouts, published pages and content separately

Fictional example. An Amman maintenance company wants a home page, an about page, a contact page and four service pages using a single layout. That is four distinct layouts and seven pages in one language. Publishing all seven in Arabic and English means fourteen page versions. It still leaves a question that can change both quotes: who writes, translates, enters and approves those fourteen versions?

Send suppliers one representative service description, a sample photo and the page list. Identify what already exists, what needs rewriting and what is missing. Ask them to separate designing a reusable layout from loading content into each page. If staff will add services later, include an editor handover and a demonstration of publishing one new service in both languages.

Give suppliers a short pricing sheet they can return

  • Design and build. Name the four layouts, the review rounds included, who consolidates feedback, and the devices or widths to review. Ask which items are fixed-price and which are estimates.
  • Content. Give quantities by language. Name the owner of copy, translation, photography and entry. Ask each bidder to mark a responsibility as included, optional or supplied by the buyer.
  • Working features. Describe where the enquiry goes, what confirmation the visitor sees, who receives a test enquiry and whether a CRM connection is included. For existing sites, list the content and addresses to retain.
  • Handover and renewals. Ask who controls the domain, hosting account, website administration and backups. List the billing frequency, any required licences, support period, renewal basis and what happens when support ends.

Turn one feature into an acceptance test

Replace “contact form included” with a visitor task. For the example company, an Arabic-speaking facilities manager should be able to select the relevant service, enter contact details, correct a missing required field and receive a confirmation. A named test recipient should be able to find the request and see which service was selected. Ask the supplier what is included to build and demonstrate that journey.

The GOV.UK Service Manual describes acceptance criteria as observable outcomes for a user need. W3C's Easy Checks provide starting points for keyboard use, field labels and errors. Ask the supplier to show how the form deals with each of these. If you require a full accessibility evaluation, specify its scope, reviewer and deliverable on a separate line. A short demonstration covers only the agreed checks.

Compare the first year and price one change

Add the one-off build, required setup fees and charges for the first twelve months on the same basis for each quote. Count an annual licence once. Keep optional features in their own subtotal. Ask each supplier to state how taxes are shown, which costs the buyer pays directly and when charges start. A blank line needs a written answer before you use the total to select a supplier.

Give both bidders one change request: “After approving the designs, we add a fifth service using the approved layout, with final Arabic and English text supplied.” Ask whether that creates two content-entry items, a new design charge or a task your trained editor can complete. Then ask what changes if the service needs a booking calendar. The answers expose the boundary between repeating a page and building a feature.

Once you have the scope, use the bilingual launch checklist to plan handover. To request a website design proposal from Lava, send the page list, one sample service and the features your first release must include.

Sources & further reading

A useful next step

Bring one real workflow.

Share the process you want to improve, the systems involved and the decision you need to make.

Talk to Lava ↗