What white-label web development costs a Gulf agency in 2026
Retained white-label capacity starts at AED 8,800 (about USD 2,400) per month for 40 senior developer hours, and a dedicated full-time developer runs AED 19,100 (about USD 5,200) per month. Project by project you buy on the same ladder your clients pay: a business website at AED 5,900 (about USD 1,600), an ecommerce build at AED 11,800 (about USD 3,200), a web app or SaaS MVP at AED 27,500 (about USD 7,500).
Those are the numbers. The rest of this article covers what decides whether the arrangement earns you margin or costs you a client: how the work is structured, what belongs in the contract, and how your name stays the only name your client sees.
Codelith Lab builds white-label for agencies in the UAE, Saudi Arabia, Qatar and Bahrain. The team is in India, and that belongs in the first hundred words, because a partner who hides it has already shown you how they will behave when something goes wrong. You are buying senior people, a cost base far below a Dubai or Riyadh salary, and a working day that overlaps yours almost completely.
What white-label means in practice, and what it does not
White-label means the build team works inside your process, under your brand, and the end client never learns a second company exists. Your logo on the staging link. Your project manager in the client call. Your invoice, your margin, your relationship, your renewal.
Four things it does not mean, and each one has cost an agency real money:
- It is not template resale. A partner who cannot show you the repository, the commit history and a real code review is selling a themed page with your logo on the invoice.
- It is not infinite capacity. A retainer buys a specific number of hours from named people. Selling three builds in one week does not get them delivered in parallel.
- It is not account management. The partner writes code, tests, documents and reports. Chasing your client for content, approvals and payment stays yours, and that is where most delays actually happen.
- It is not cover for a vague scope. If you sold “a website” with no page count and no feature list, nobody can rescue that. Bad scope is the biggest destroyer of white-label margin.
The three engagement shapes and what each one costs
Almost every workable arrangement is one of three shapes, and growing agencies usually move from the first to the second within two quarters.
| Shape | Best when | Cost | You commit to |
|---|---|---|---|
| Per project | You close two to four builds a year and cannot predict the next one | AED 2,600 (USD 700) landing page up to AED 27,500 (USD 7,500) web app | Nothing beyond the signed project |
| Retained capacity, 40 hours | Steady flow: roughly one site a month plus edits across live clients | AED 8,800 (USD 2,400) per month | Three months, then rolling with 30 days notice |
| Retained capacity, 80 hours | Two builds in flight plus a support queue | AED 16,500 (USD 4,500) per month | Three months, unused hours roll one month |
| Dedicated developer | One named person inside your team, your stack, your standups | AED 19,100 (USD 5,200) per month, full time | Six months, 60 days notice either side |
Ongoing care for a live client site, meaning updates, backups, uptime and small edits, is AED 440 (about USD 120) per site per month, and most agencies resell it at three times that as their own retainer. Anything genuinely bespoke, an internal system, a booking engine, an ERP integration, is quoted as custom software rather than pulled from the ladder.
How communication is structured so you stay the single point of contact
This is the part agencies get wrong, and good intentions do not fix it. Structure does, by making the wrong thing hard to do.
The shared board and one written update a week
One board, visible to both sides, one card per deliverable, with status, owner and the date it is expected. No status by chat message. Chat is for questions, the board is for truth. Every Thursday a written update lands: what shipped, what is blocked, what needs your client to decide, and the hours consumed against the retainer. If a partner cannot produce that in writing every week, the reporting will collapse in month two.
Agency-branded staging and repositories
Staging sits on a subdomain of your domain, for example staging.youragency.ae, not on the partner’s. Emails from the staging environment carry your sender name. The repository is named for your agency and your client, and the partner’s brand appears nowhere in the code, the readme, the footer or the page source. Check the page source yourself before signing.
Reports written for you to forward
Progress notes, launch checklists and performance reports should be written in language you can paste straight into a client email, with no internal jargon and no reference to the partner. That habit saves an account manager two hours a week and prevents copy and paste accidents.
The rule underneath all of it: no direct contact with your client unless you invite it. When a technical call is genuinely needed, the partner joins as a named member of your team. That invitation stays yours to issue, in writing, per meeting.
The NDA and non-solicitation clauses to insist on
A mutual NDA is the floor, not the protection. The clause that matters stops the partner ever becoming your competitor at your own client.
The non-solicitation clause that actually holds
It should cover both directions and name the behaviour, not the intention. Insist on: no approach to any client introduced by you, direct or through an affiliate, for the term plus 24 months; no acceptance of unsolicited work from those clients without your written consent; no use of your client’s name, logo, screenshots or results in the partner’s portfolio, website, pitch decks or case studies, ever, unless you approve it in writing; and no hiring of your staff during the term plus 12 months. Add a clear breach remedy, because a clause with no consequence is decoration.
Why an unprompted offer is the signal
Any partner will sign these if you push. The one worth trusting hands you the mutual NDA and the non-solicitation clause before you ask, because they have built a business on agency volume and know that one poached client ends every referral they would otherwise receive. When you have to negotiate basic protection line by line, you are not looking at a partner, you are looking at a competitor who is currently short of work.
Revisions, scope changes and emergencies
Margin dies in the space between “small change” and “new feature”. Price that space in the statement of work.
| Request type | How it is handled | How it is billed | Response |
|---|---|---|---|
| Revision inside agreed scope | Two rounds included per milestone, consolidated into one list | Included | One to two working days |
| New scope mid-build | Written estimate in hours before a line is written, you approve or defer | Against retainer hours or at the agreed hourly rate | Estimate within four working hours |
| Design change after sign-off | Re-estimated as new scope, timeline moves and you are told by how much | Hourly, quoted first | Same day |
| Live site down or checkout broken | Emergency channel, one named engineer, you get a client-ready note within the hour | Covered by the care plan, otherwise hourly at 1.5x outside working hours | Under two hours in overlap, under four outside |
| Third-party breakage | Gateway, API or plugin changed on its own, diagnosis then fix | Diagnosis free, fix from the care plan or quoted | Same working day |
One discipline beats every clause here: revisions arrive as one consolidated list per milestone, not as fourteen chat messages over three days.
Quality control and who owns the code
The checks that run before anything reaches your client
Ask what happens between “developer says done” and “you send the link”. A serious partner names the steps: peer review of every change, a mobile pass at 390 pixels wide, a console with zero errors, Lighthouse performance above 90 on mobile, forms tested end to end including the confirmation email, right to left layout checked on bilingual sites, and a broken link sweep. If the answer is “we test it thoroughly”, you are the tester and your client is the audience.
Who owns the repository, and the escape hatch
The contract should state that all code, design files and content are yours on payment, with no licence back to the partner and no reuse of your client’s work. Hosting, domains and gateway accounts stay in your client’s name or yours. From day one you hold owner access to the repository, so a handover on 30 days notice is a link and a document, not a hostage negotiation. Ask what happens if they disappear tomorrow. The correct answer is that you already have everything.
Realistic capacity, turnaround and overlap hours
Honest delivery times with one senior developer on the job: a landing page in five to seven working days, a business website in three to four weeks, ecommerce in six to eight weeks, a web app or MVP in ten to fourteen weeks. Content and approvals from your client cause most slippage, not development.
How the India and Gulf working days line up
India Standard Time is 90 minutes ahead of Gulf Standard Time. A team working 9:30 to 18:30 in India is available 8:00 to 17:00 in Dubai, Doha, Manama and Riyadh, which is roughly eight hours of live overlap on every shared working day. In practice a question asked at 9am in Dubai gets an answer before lunch, not the next morning, which is the difference between this and outsourcing to Europe or North America.
The week matters too. The UAE runs Monday to Friday, so all five days overlap. Saudi Arabia, Qatar, Kuwait and Bahrain run Sunday to Thursday, which gives four fully shared days plus a Sunday that is covered by a duty rota and a Friday that is covered by yours. Get in writing who covers Sunday, because a Saudi client will ask on a Sunday.
Add a build team without adding headcount
Tell us the pipeline you are turning away and we will tell you which shape fits, what it costs per month, and what we can ship in the first 30 days. Mutual NDA and non-solicitation sent before the call.
The Gulf specifics your partner must already know
A partner who has never delivered into the region will learn these on your client’s project, at your cost. Test for them in the first conversation.
Tax first. You bill your client with 5 percent VAT in the UAE, and at the local standard rate elsewhere in the Gulf. The white-label invoice you receive from an Indian supplier is an import of services, so your side of the chain carries the local treatment and the reverse charge entry your accountant expects. Practical effect: decide deliberately whether your client quote is VAT inclusive, keep the supplier invoice in USD for a clean audit trail, and never let it reference your client’s name.
The rest is technical and non-negotiable: proper Arabic and right to left layout, meaning mirrored navigation, correct numerals and a font that renders Arabic properly rather than a Latin font with fallback glyphs; hosting in a UAE or Bahrain region when the client asks for data residency, with a written note on where backups live; correct handling of .ae, .sa and .qa domains, including the trade licence documents some registries demand; and payment gateways actually used here, such as Network International, Telr, PayTabs, Checkout.com, Tap and Stripe, plus Apple Pay, which converts strongly on mobile across the Gulf. The delivery detail behind all of this sits on our web development page.
How to trial a partner on one small paid project
Never start with your biggest client and never ask for free work, which gets the junior nobody else is using. Buy a small real project with a real deadline, a landing page at AED 2,600 (about USD 700) or a site migration, and grade five things.
- Day one behaviour. Did a scope document and a milestone plan arrive within 48 hours, or did you get enthusiasm and a start date?
- Do they push back? A senior partner tells you which part of your scope will cause trouble. A vendor agrees with everything and invoices the difference later.
- The branding test. Staging on your subdomain, your sender name, nothing of theirs in the page source, checked by you and not promised by them.
- The change request test. Ask for something mid-build that is clearly outside scope and see whether you get an estimate in hours or a shrug and a surprise on the invoice.
- The handover. Repository access, credentials and a written handover on the day of launch, without a reminder.
Two paid trials with two partners cost less than one bad build on a client who then leaves.
When you should hire in-house instead
For some agencies this model is the wrong answer.
Hire in-house when build work has been more than about 60 percent of your revenue for a year, because at that point development is your business and outsourcing your core is a strategic mistake. Hire when twelve months of visible, consistent load justifies a full salary. Hire when you are building a product of your own, because product work needs someone carrying the context for years. Hire when the work sits under a regime requiring cleared, locally resident staff or on-site presence, which happens with some government and banking work in Saudi Arabia and the UAE.
Run the numbers honestly. A capable mid-level developer in Dubai costs roughly AED 14,000 to 20,000 per month in salary, and with visa, insurance, gratuity, a desk and recruitment you are near AED 22,000 (about USD 6,000) fully loaded. That buys one person with one skill set, on leave sometimes, resigning eventually. Retained capacity at AED 8,800 (about USD 2,400) gives you a designer, a backend developer and a QA pass from the same budget line, and it scales down in a quiet month. Below roughly one build a month, the retainer wins clearly. Above three, a hybrid usually wins: one in-house lead who owns quality and client trust, with white-label capacity behind them for volume.
The failure case nobody mentions: if your team cannot write a clear brief and will not work asynchronously, no partner fixes that. Fix the brief first.
Also read: The full Gulf price ladder, the delivery process and the terms we publish before any call are all on the Codelith Lab global page, including what a first 30 days with a new agency partner looks like.
