How Long Does It Take to Build a Web Portal in UAE?

# How Long Does It Take to Build a Web Portal in UAE?

TL;DR: A mid-sized business or client portal in the UAE typically takes 10–16 weeks from kickoff to launch if requirements are locked early — but projects can easily stretch to 18–24 weeks because of Arabic content delays, multi-stakeholder sign-off, and payment-milestone gaps that are common in how UAE organizations operate.

If you've been quoted "8 weeks" by an agency in Dubai or Abu Dhabi, treat it as the development phase only, not the real calendar time. This guide breaks down an honest, phase-by-phase web portal development timeline, the UAE-specific reasons projects slip, and how to plan around them.

What Counts as a "Web Portal" Here

For this timeline, a web portal means a logged-in, role-based web application — a client portal, vendor/supplier portal, HR self-service portal, dealer portal, or B2B ordering system — not a marketing website or a simple brochure site. Portals involve authentication, dashboards, document workflows, and usually at least one third-party integration (payments, CRM, ERP, or a government/free-zone system). That extra complexity is exactly why timelines get compressed unrealistically in early sales conversations.

The Real Phased Gantt

Below is a realistic phase breakdown for a mid-complexity portal (custom login roles, a dashboard, document upload/approval workflows, and one payment or CRM integration). Weeks overlap slightly in practice — design usually starts before requirements are 100% frozen — but this is the sequence and typical duration:

For a straightforward portal this compresses to roughly 10–12 weeks. For one with multiple integrations (payment + CRM + a government or free-zone e-service) or multi-department approval, 16–24 weeks is more realistic. Enterprise-grade platforms with complex workflow engines and legacy system integration can run 6 months or longer — and cost scales with that complexity. Published UAE vendor price guides give a sense of the range but disagree with each other: Skyline Advanced Technology's 2026 guide puts its top tier of custom software at AED 50,000–500,000+, while Element8's 2026 Dubai pricing guide lists AED 12,000–55,000 for a 10–20 page multilingual corporate site with workflows and AED 50,000–275,000+ for custom web applications with bespoke workflows and API integrations — the category most portals fall into.

Why UAE Projects Slip: Three Recurring Bottlenecks

1. Content and Arabic translation arrive late

Development teams can build screens before final copy exists, but launch cannot happen without it. In the UAE, Arabic content is not a "nice to have" — for a portal serving government-adjacent, banking, or public-facing clients, Arabic (with correct RTL layout, not just translated strings) is often expected by end users and sometimes by regulators. A very common delay is a client agreeing to "send Arabic content next week" during discovery, and it arriving during week 10 instead. Build translation into the project plan as its own tracked workstream with its own deadline, not an afterthought bolted onto week 12.

2. Multi-stakeholder approval cycles

UAE organizations — especially government-linked entities, family-owned groups, and larger corporates — often route sign-off through several layers: a project lead, a department head, sometimes a group CEO or board member for anything customer-facing. A design or scope change that would take two days to approve at a smaller company can take two weeks when it has to be walked through four people, several of whom may be traveling or observing a public holiday (Eid, National Day, or the summer slowdown in July–August when many decision-makers are out of the country). Lock a single approver per phase in the kickoff meeting — it's the single highest-leverage thing a client can do to protect the timeline.

3. Payment cycles affect resourcing, not just cash flow

Many UAE development contracts are milestone-based (often a sizeable upfront payment, balance split across delivery milestones). When a milestone invoice sits unpaid for two or three weeks — easy to happen with 30/60-day supplier payment terms — an agency will often reassign that project's developers to paid work in the interim, and reassembling the same team adds real calendar time even after payment clears. If your organization's finance department works on a fixed monthly payment run rather than paying on receipt of invoice, flag that during contracting so milestones can be aligned to your payment calendar rather than fought against it.

A Realistic Planning Checklist

• Freeze the requirements document before design starts. Every scope change after week 2 pushes the whole Gantt back, not just that one task.
• Assign a single content owner responsible for Arabic and English copy, with their own internal deadline that precedes the development deadline by at least two weeks.
• Name one approver per department in the kickoff, not a committee, for day-to-day sign-off.
• Align payment milestones to your internal payment run dates, agreed in the contract, not discovered mid-project.
• Decide your payment gateway early (Telr and PayTabs are common choices for UAE SMEs; Network International and Stripe/Checkout.com are more common for larger or omnichannel merchants) since gateway KYC and merchant account approval is its own process with its own lead time and should run in parallel with development, not after it.
• Budget compliance time, not just development time, for anything touching personal data.

Data Protection Adds a Fixed Compliance Step

Any UAE portal that collects personal data — names, Emirates ID numbers, contact details, payment information — falls under Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data (PDPL), which has been in force since 2 January 2022 (its executive regulations are still unpublished) and applies extraterritorially to any controller or processor handling the personal data of individuals in the UAE, with its own consent, data-subject-rights, and cross-border transfer requirements, per Securiti's overview of the law. In practice this means: a documented lawful basis for each type of data you collect, a real (not boilerplate) privacy policy reflecting what the portal actually does, and a plan for handling data subject access/deletion requests. Free-zone entities such as those in DIFC or ADGM operate under their own separate data protection regulations rather than the federal PDPL, which matters if your organization or your hosting/cloud provider sits inside one of those zones — confirm which regime applies before finalizing your data architecture, since it can affect where you're allowed to host data and what consent language your portal needs to show.

Separately, remember that UAE VAT remains at 5% as of 2026, administered by the Federal Tax Authority, per ClearTax's 2026 VAT guide — relevant if your portal issues invoices, processes payments, or generates tax-compliant receipts, since your invoicing module needs to reflect current FTA formatting requirements from day one rather than being retrofitted after launch.

When to Bring in a Specialist Partner

If your portal needs custom role-based permissions, a document approval workflow, or integration with an ERP/CRM system rather than an off-the-shelf plugin, it usually falls outside what a template-based website builder or a generalist freelancer can deliver reliably. Teams that specialize in custom software development typically scope the integration and workflow pieces first, precisely because those are the components most likely to blow the timeline if they're treated as an afterthought rather than planned from week one.

FAQ

Q: Can a web portal really be built in 4 weeks, as some agencies advertise?

A: Only for something extremely narrow — a single-role login area with static content and no real integrations. Anything with role-based access, a payment gateway, or CRM/ERP sync realistically needs 10+ weeks even in the best case, and "4 weeks" quotes usually exclude content, testing, and revisions.

Q: Does Ramadan or summer affect UAE project timelines?

A: Yes, noticeably. Working hours shorten during Ramadan and many decision-makers travel during the July–August summer period, which slows approval cycles more than it slows actual development work. Build 1–2 weeks of buffer into any project that spans either period.

Q: What's the single most common cause of delay on UAE portal projects?

A: There's no published data on this. In our view, late-arriving Arabic content and copy is the one to plan for first, because it is fully in the client's control and easy to underestimate; approval delays and integration issues are the other usual suspects.

Q: Do we need a UAE-based developer or agency, or can we work with an offshore team?

A: Either can work technically, but time-zone overlap for the approval and content cycles described above matters more than location. A team in a compatible time zone (or one that schedules synchronous check-ins during UAE business hours) will generally hit review and revision turnaround faster than a fully async offshore relationship.

Sources

• ClearTax: New VAT Rules in UAE 2026
• Daftra: VAT in UAE (2026): 5% Rate, Registration Threshold, Exemptions & Filing Rules
• Securiti: Overview of UAE's Federal Decree-Law No. (45) of 2021 on PDPL
• Element8: Website Development Cost in Dubai (2026 Price Guide)
• Skyline Advanced Technology: Custom Software Cost UAE 2026
• ScaleUpAlly: 15 Best Payment Gateways in the UAE