Most Dubai web design agency horror stories trace back to four ungated checks at the procurement stage: who owns the code, what's the launch performance target, who you can call as a reference, and how the billing actually works after the deposit. Get firm written answers to those four questions and you've already filtered out about 70% of the market. The rest of this guide is the long form of those questions and nine more, written for SME founders, marketing managers and procurement leads who are about to sign a contract for AED 5,000 to AED 100,000 worth of work.
We've audited 40+ Dubai agency contracts over the past four years — for clients before they signed, and as a forensic post-mortem after things broke. The patterns are remarkably consistent.
Why agency selection in Dubai is harder than it looks
The UAE has roughly 1,800 registered web design / web development companies as of 2026, plus a much larger informal market of freelancers and overseas contractors operating under UAE-licensed front-companies. Quality, ownership transparency, and post-launch reliability vary by an order of magnitude. The price you pay does not reliably predict where on that distribution an agency sits.
Three structural reasons this is uniquely difficult here:
- Trade-license proliferation. Setting up a "web design" trade license in a Dubai free zone takes about a week and costs less than the average freelancer's monthly retainer. The brand on the invoice doesn't tell you who is actually building your site.
- White-labelled offshore delivery. A significant percentage of Dubai agencies subcontract delivery to teams in South Asia, Eastern Europe, or the Philippines. The English-speaking sales person you met never touches the codebase.
- Retainer-as-default. Most agencies will quote you a "starter project" and quickly funnel you into a monthly retainer. Once you're on the retainer, switching becomes painful because they hold the credentials, the hosting, and the institutional knowledge of what's actually deployed.
None of those patterns are inherently bad — plenty of subcontracted, retainer-based agencies do excellent work. But you need to know which model you're buying into before you sign.
The 12 vetting questions
1. "Who owns the source code, design files, and hosting accounts on the day after final payment?"
The only acceptable answer is you, in full, with no licence fees. If the agency owns the code and licenses it back to you on a SaaS-style monthly fee, you're trapped — you cannot move to another developer, you cannot self-host, and you cannot fully audit security. Ask for the IP-transfer clause in writing as part of the proposal, not as a verbal "of course."
Red flags: "we keep the rights but you have a perpetual licence," "the framework licence is separate," or "we host on our infrastructure as part of the package" with no migration option spelled out.
2. "What Lighthouse / Core Web Vitals target are you committing to at launch?"
A serious agency will quote you a specific number: a Lighthouse Performance score of 90+ on mobile, LCP under 2.5 seconds, CLS under 0.1, INP under 200 ms. If they shrug, say "Lighthouse is just one tool," or quote a desktop-only score, they are either inexperienced or planning to ship something slow.
Performance is not a finishing-touch upsell. It is a baseline.
3. "Can I speak to three clients you launched in the last six months?"
Past clients from three years ago tell you nothing about current delivery. Ask specifically for recent launches — projects that finished in the last two quarters. Then actually call them. Ask: did the project finish on budget, did the team change mid-flight, who owns the site now, and would they hire the agency again for a different scope.
If the agency hesitates, names only their flagship-flagship case study from 2022, or cannot produce three recent references, walk.
4. "Who specifically will be building my site, and will they change?"
Many agencies use the pre-sale meeting to put their most senior person in the room, then hand the actual build to junior staff or offshore contractors. Ask for named individuals on the proposal: the project lead, the designer, the developer. Ask whether they are full-time employees of the agency. Get assurance in writing that those individuals stay on the project unless you approve a swap.
5. "How is the billing milestone-structured, and what happens if I want to pause?"
The standard healthy structure is 50% on kick-off, 50% on delivery, with a clear written "delivery" definition (live URL, passing a Lighthouse audit, all features in the SOW demonstrably working). Some agencies do 30/40/30. Anything more than 50% upfront, or front-loaded with vague milestones, is a working-capital warning sign — they may be using your deposit to finish someone else's project.
Ask explicitly what happens if you need to pause for two months: do you forfeit the deposit, or does work resume on the original terms?
6. "What does month one of post-launch look like?"
If the answer is "we hand over and you're on your own," you're going to spend the first three weeks after launch in panic mode finding broken things in production. The right answer is some flavour of: 30 days of bug fixes included, weekly check-ins, and a clear escalation path for anything time-sensitive.
This is separate from a monthly retainer — it is what's already baked into the project price. If they want extra money for the first month of fixes, they don't believe in their own delivery quality.
7. "Will you ship with a real CMS that my team can actually use?"
A "custom-coded" site with no content management interface is fine for a 5-page brochure. For anything with a blog, services, locations, or evolving copy, you need a CMS — WordPress, Webflow, Statamic, Strapi, or a headless setup with a friendly admin. Ask to see a screen recording of a non-developer adding a blog post and editing a homepage hero. If they can't show that workflow, your team will be raising tickets for every typo.
8. "How do you handle Arabic / RTL if I need it later?"
You may not need Arabic on day one. You will likely need it within 18 months. Ask: is the framework you're using RTL-aware out of the box? Can a second language be added without rebuilding? What is the cost of adding Arabic in phase 2? Vague answers ("we'll figure it out then") indicate they haven't done a real bilingual build — and bolting Arabic onto a non-RTL design later costs 2-3× more than building for it from the start.
9. "What is your real average project length?"
Sales decks always say "two to four weeks." Ask the project manager (not the salesperson) what the actual average project length is, including the testing and revision phase. The honest answer for a serious business website is 6-10 weeks total. If they swear they always ship in three weeks regardless of scope, they're either flat-rate templating or they're going to deliver an unfinished product and ask for change-order budget to finish it.
10. "Who handles SEO setup, and what specifically is included?"
"SEO included" can mean anything from "we'll install Yoast" to "we'll run a 12-week technical and content programme." Get specifics: structured data (Schema.org), XML sitemap, robots.txt, canonical tags, Open Graph + Twitter cards, GA4 + Search Console setup, page-speed tuning. If they include all that without listing it as an upsell, they understand modern SEO. If they treat SEO as a separate phase-2 service, you're paying twice for what should be baseline.
11. "What's your security baseline?"
UAE-specific risk: ecommerce and lead-generation sites are scanned constantly for outdated WordPress plugins and exposed admin panels. A serious agency will list: HTTPS enforced, security headers (HSTS, CSP, X-Frame-Options), input validation on every form, rate-limiting on auth endpoints, secrets in env files (never in code), and a documented backup / restore plan. If they wave this off as "the host handles it," they are wrong.
12. "Show me the contract — specifically the change-order clause and the scope-change pricing."
Most disputes are scope disputes. Read the change-order clause before signing: how are new requirements priced, what's the minimum billable unit, is there a markup over the original hourly rate? A fair contract is transparent on this. An exploitative one charges 2× the project rate for any work after the SOW is signed, or has a vague "additional features billed at agency discretion" line.
Red flags that should end the conversation
Beyond the 12 questions, there are conversation-enders. Walk away — not "negotiate harder," walk away — if you see:
- A portfolio of "designs" that are clearly Dribbble mockups, not real launched sites. Click every project. If half of them don't have live URLs you can visit, the portfolio is staged.
- Vague answers about who owns the code, with the offer to "clarify in the contract." The contract will not clarify it.
- High-pressure deposit-now pricing ("this rate is only valid this week," "we have one slot left this month"). Real agencies have pipelines, not flash sales.
- No written scope of work attached to the proposal. "We'll figure out the details after kick-off" is the prelude to every horror story.
- A proposal under AED 3,000 for a "full custom website." It's a template install with your colours. Fine if that's what you want; not fine if you were promised custom.
- No technical lead in the sales meeting, only a salesperson who can't answer specific build questions. The technical team should be available before the contract.
- They won't let you talk to the developer who will actually build the site.
What a good agency proposal actually looks like
A defensible proposal for an SME website in Dubai includes, at minimum:
- Named project lead and named developer(s) — with LinkedIn URLs
- Written scope of work with page-by-page breakdown
- Specific technology choices (CMS, hosting, framework) with rationale
- Concrete launch performance targets (Lighthouse, LCP, CLS, INP)
- Milestone schedule with calendar dates, not just sprint counts
- Itemised cost breakdown — design, development, content migration, SEO setup, testing
- 30-day post-launch support clearly included
- IP-transfer clause on final payment
- Change-order pricing structure
- Two or three recent references with project URLs
If you ask for these and the agency cannot produce them in 48 hours, they're not set up to deliver a serious project — they're set up to sell one.
When to use a freelancer instead of an agency
Honest answer: a single experienced freelancer can outperform a mid-size agency on small projects (under AED 15,000 budget, simple scope, no integrations). You lose the bench-depth and the institutional process, but you also lose the account-management overhead. The right move depends on three factors:
- How critical is the website to revenue? If the website is your primary lead source, the redundancy of a team matters. If it's a credibility brochure, a freelancer is fine.
- How much project management can you absorb internally? A freelancer expects you to write specs and review work. An agency does that for you.
- Do you need ongoing iteration? Freelancers move on. If you'll need someone in 18 months, an agency with proper documentation handover is the safer bet.
A good freelancer in Dubai charges AED 250–600/hour. A mid-size agency charges AED 400–1,200/hour effective rate. The agency is more expensive but spreads risk across more people — that's what you're paying for.
Pricing sanity check
If you're a UAE SME with annual revenue between AED 1M and AED 20M, here's what a realistic website investment looks like in 2026:
- Brochure site (5-8 pages, no commerce): AED 4,400 – 12,000
- Content-rich service site with blog and basic CRM integration: AED 12,000 – 30,000
- E-commerce store (under 200 SKUs, single language): AED 9,000 – 35,000
- Bilingual content site: add 30-45% to the above
- Custom web application (booking, dashboards, integrations): AED 25,000 – 100,000+
Below AED 4,000 for a "full custom website" is templates with paint. Above AED 50,000 for an SME brochure site is usually agency overhead, not value.
For an honest cross-check on a specific scope, the free WebStackRank quote calculator gives an itemised AED estimate in under two minutes.
Frequently Asked Questions
How long should the agency selection process take? For a project over AED 20,000, plan for three to four weeks: a week of shortlisting (3-5 agencies), a week of proposal collection, a week of reference calls and negotiation. Rushing this stage is the most expensive mistake you can make.
Is it normal to pay for a discovery phase? For projects over AED 50,000, yes — a paid discovery (1-3 weeks, typically AED 3,000–8,000) is sensible. For SME projects, the proposal should be free.
Should I work with a UAE-licensed agency or is offshore acceptable? Both work. UAE-licensed is easier for invoicing, VAT, and dispute resolution. Offshore is often cheaper but harder to enforce a contract against. If you go offshore, use a structured payment processor (Wise, Payoneer) with milestone protection.
How do I verify code ownership before final payment? Ask for the Git repository URL and read access before the second invoice. If the agency refuses, that tells you everything.
What if the agency's portfolio looks great but the references underwhelm? The portfolio is curated. References are reality. Trust references.
Where WebStackRank fits
We're a Dubai-based studio working project-based with fixed scope and fixed pricing. Code ownership transfers on final payment, every site ships with Core Web Vitals targets hit at launch, and the developer building your site is in the sales meeting. If you'd like to see how we'd price your specific project, the quote calculator is free and instant. Or submit a brief and we'll come back within 24 hours with a written proposal.
You should still ask us the 12 questions above. If we don't have good answers, walk.