Every agency in the Kingdom shows you a portfolio and a price. Neither tells you much. These twelve questions surface what actually determines whether a project succeeds.
Why portfolios mislead
A portfolio shows what an agency's best clients approved, often years ago, sometimes built by people who have since left. It tells you nothing about whether the project ran on time, whether the client got the source code, or whether the site still works today.
Ask questions that reveal process rather than output. The answers are harder to fake and far more predictive.
The twelve questions
1. Who specifically will work on this, and what else are they on?
Agencies sell with senior people and deliver with junior ones. Ask for names, roles and current allocation. A good answer is specific. A vague answer about "the team" means you will meet whoever is free.
2. Show me a project that went wrong and what you did.
Every agency has had a project overrun or a launch go badly. One that claims otherwise is either new or not being straight with you. A confident, specific answer about a failure and the remedy is one of the strongest signals available.
3. How do you handle Arabic — translation or native writing?
Ask directly whether Arabic copy is written by an Arabic writer or translated, and whether Arabic layouts are designed independently or mirrored from English. Ask to see an Arabic site they built and have an Arabic-speaking colleague read it. This single check eliminates a large share of candidates.
4. Who owns the code, designs and accounts at the end?
The answer should be "you do", unambiguously, in the contract. Some agencies retain hosting accounts, domain registrations or codebases as retention devices. Ask specifically about domain registrar access, hosting account ownership, repository access and design source files.
5. What is your performance standard, and is it in the contract?
A serious agency states a target — Core Web Vitals thresholds on mobile, for instance — and accepts it as a deliverable. An agency that has never thought about performance will treat the question as unusual.
6. What happens after launch?
Ask about the warranty period, what counts as a bug versus a change request, response times, and what maintenance costs monthly. Vagueness here reliably predicts an expensive month two.
7. How do you handle scope changes?
You will change your mind. The question is whether there is a defined process — written change request, quoted, scheduled — or whether it becomes an argument. Ask how many change requests their last three projects had. Zero is not a good sign; it means changes went unrecorded.
8. Can I speak to a client whose project did not go smoothly?
Any agency can produce three delighted references. Asking for a difficult one tests both their honesty and their client relationships. The reference call is where you learn how they behave under pressure.
9. What do you need from us, and by when?
Most delays are client-side. An experienced agency knows this and will hand you a dependency list at kickoff. If nobody mentions what you owe them, the timeline is fiction and the overrun will be blamed on you later.
10. How will we know if it worked?
A website is a business investment. Ask what they will measure and what a good outcome looks like at three and six months. Agencies that only discuss aesthetics will deliver something attractive that does not perform.
11. What is your handover?
Documentation, CMS training, credentials, deployment instructions and a walkthrough of how to make common changes. Handover is the deliverable clients most often forget to specify and most often need.
12. What would you talk us out of?
An agency that agrees with everything is selling, not advising. The best answer here is a specific thing they think you should not do, and why. It is the clearest indicator you are buying judgement rather than production capacity.
The best question is the one that has no marketing answer. "What would you talk us out of?" is the hardest to rehearse.
Warning signs
- A quote arriving within an hour of first contact. Nobody can scope your project that fast honestly.
- Guaranteed Google rankings. No one controls Google's results. This claim is disqualifying on its own.
- Unlimited revisions. Either untrue, or already priced in on the assumption you will not use them.
- Portfolio links that are dead or point to redesigned sites. Check them before the meeting.
- Pressure to sign before the end of the month. Urgency is a sales tactic, not a project reality.
- No written scope. Without one, every disagreement becomes your word against theirs.
- Reluctance to discuss what happens if you leave. The exit conversation reveals the relationship.
Local versus offshore
Offshore development is materially cheaper and can be excellent. The trade-offs in a Saudi context are real: time-zone overlap for decisions, native Arabic quality, understanding of local payments and regulation, and someone who can be in the room when a stakeholder needs convincing.
A common workable pattern is a Saudi-based lead for strategy, design and accountability with offshore capacity for build volume. What consistently does not work is buying purely on hourly rate and discovering that everything requiring local context has to be explained three times.
A sensible selection process
- Write a one-page brief covering objective, scope, languages, timeline and budget band
- Approach three or four agencies, not ten
- Give all of them the same brief and the same budget band
- Ask the twelve questions above in a live conversation, not by email
- Take at least two reference calls, including one you selected rather than one offered
- Compare proposals on scope and process, not on the headline number
- Choose the team you would want to be on a call with in week nine when something has gone wrong
Frequently asked questions
How do I choose a web design company in Saudi Arabia?+
Evaluate process rather than portfolio. Ask who specifically will work on the project, how Arabic content is produced, who owns the code and accounts, what the performance standard is, and what happens after launch. Take reference calls including one from a difficult project.
Should I hire a local Saudi agency or an offshore team?+
Offshore is cheaper but costs you time-zone overlap, native Arabic quality and local regulatory knowledge. A common workable pattern is a Saudi-based lead for strategy and accountability with offshore build capacity.
What are the warning signs of a bad web agency?+
Instant quotes before scoping, guaranteed Google rankings, unlimited revisions, dead portfolio links, artificial deadline pressure, no written scope, and reluctance to discuss what happens if you leave.
Should the agency own my domain and hosting?+
No. You should own your domain registration, hosting account, repositories and design files. Agencies that retain these are using them as a retention device rather than a service.
How many agencies should I approach?+
Three or four, given the same written brief and the same budget band. More than that produces proposals you will not read carefully and wastes everyone's time.
What should a written scope include?+
Deliverables, page or template count, languages, integrations, revision rounds, performance targets, timeline with dependencies on you, payment schedule, ownership terms and post-launch support.