Activity CZ 372
How to Start a Web Portals Business in Dubai
Web portals are not a project with a launch date but a service with a shift pattern. The build is the cheap part, and the premises question is smaller than the question of where the data sits.
ConsultZone licensing desk
- Activity code
- CZ 372
- Category
- Digital Media & Portals
- Reviewed
- Read
- 8 min
Topic summary
How to Start a Web Portals Business in Dubai
Nobody launches a web portal. A portal is launched for about a week, and then it is operated, which is a different activity with a different cost structure and a shift pattern. The build has an end date and a budget; the operation has neither. Somebody has to approve new listings, remove the ones that have gone, answer the account that cannot upload, keep the search returning useful results as the inventory grows from four hundred items to forty thousand, and be awake when the site is not.
That is the honest framing of Web portals as a business, and it is worth putting first because the usual plan gets the proportions backwards. A founder budgets for development, launches, and then discovers that development was the small number. The recurring cost of a running portal is people, hosting and moderation, and it starts on the day the site goes live and never goes down again.
Who is this for?
This line suits an operator, not a builder. The distinction is worth drawing precisely, because it is the commonest mismatch between a licence and a business plan.
A development company builds websites for clients, bills a project, and moves on. It sells hours, it has no inventory and no audience, and its revenue is the sum of the projects it won this quarter. That is a different activity and a different business.
An operator owns the destination. It carries somebody's inventory or its own, it has an audience that returns, and its revenue is recurring — listing subscriptions, featured placement, lead fees, advertising, or a membership. The asset on the balance sheet is the audience and the supply side's habit of updating; the liability is that both have to be served continuously.
Four operator profiles work here.
The vertical operator runs one category deeply — property, motors, jobs, education, healthcare, travel — and competes on completeness and on knowing the category's own vocabulary. The strongest position and the hardest to start.
The aggregator pulls inventory from feeds and partners rather than from individual uploaders, which solves the cold start and makes the business dependent on access it does not control. Worth being clear-eyed about how long that access lasts.
The community operator has content rather than listings — forums, reviews, guides, user contributions — and monetises attention. The lightest supply side and the heaviest moderation burden, because here the content is the risk.
The service portal operator runs a booking or enquiry surface for a defined set of providers, often on behalf of an industry. Steady, unglamorous, and frequently the most profitable of the four because the supply side is contracted rather than courted.
| Listings portal | Content site | Marketplace | |
|---|---|---|---|
| Where the inventory comes from | Third parties who upload it | You, or your contributors | Sellers who also transact |
| Where the money comes from | Listing fees, placement, lead fees | Advertising, sponsorship, subscription | A share of the completed deal |
| What the operator is responsible for | Accuracy and removal of what has gone | What is published, including contributions | The transaction, and both parties' expectations |
| What moves it outside this line | Taking a commission on the deal | Producing regulated categories of content | It is already a different conversation |
| What breaks it | Stale listings and a drifting audience | Moderation failure, or losing a platform's traffic | A dispute nobody owns |
| What the recurring cost really is | Moderation and account support | Editorial and moderation | Support, payments and dispute handling |
The focus row is the one to take away. The three columns are not three licences — the first two are ordinary readings of this activity, and the third is the point at which the business has become something else. What moves a site across that boundary is never the software; it is a decision about where the money changes hands.

What you can and cannot do under this line
You can operate the destination and publish on it. Running the site, carrying third-party listings and user contributions, charging for placement and subscriptions, selling advertising, operating search and enquiry tools, and holding accounts for the people who supply the inventory are all the substance of the activity.
You can be paid for an introduction. A lead fee, a per-listing charge or a subscription for access to your audience is a publishing and advertising revenue, and it sits comfortably inside this line.
You cannot broker the deal. This is the boundary that matters most and the one crossed most casually. Negotiating between the parties, representing one of them, holding a deposit, or taking a percentage of a completed sale or lease are the destination activities — brokerage, agency, dealing — and each is licensed on its own terms. In Dubai property that is a particularly clear line, because brokerage sits with its own authority. A portal does not acquire any of those by displaying its customers' stock, and adding a "pay here" button to a listing page is a licensing decision wearing the clothes of a product decision.
You cannot hold other people's money. Collecting payment from a buyer and passing it to a seller is a payment and money-handling activity, supervised in its own right, and it is not something a portal licence confers. Portals solve this routinely by sending the payment to a licensed provider instead of through their own account, and that is the normal architecture rather than a workaround.
You cannot give advice that is licensed when given. A site may publish mortgage rates, insurance comparisons, medical information, legal templates or immigration guidance. The moment it recommends one to a named user on their facts, it is advising in a sector licensed on its own terms. The distinction between publishing information and giving advice is the single most useful one for a portal operator to hold in mind while designing features, because a recommendation engine is a very short step from the second.
And a portal does not inherit its listers' licences. If the activity being advertised requires a licence, the person doing it needs one; the portal's responsibility is not to misrepresent that, not to acquire it on their behalf.
Premises and practical conditions
The premises question is small and the data question is large. This is a desk business. The office is sized by headcount rather than by operations, and for most portals the licence's premises condition is satisfied by an ordinary office — which is why spending planning effort here is a waste of it.
Where the real conditions sit is the data.
Where the site is hosted matters, and where the users' data sits matters more. A portal holds personal information about the people who contact listers and about the listers themselves, and it accumulates behavioural data about everyone else. Obligations on handling that information follow the data and the people it describes rather than the location of a server, so hosting abroad does not move the question. What to collect, how long to keep it, what the site says it does with it and whether that statement is true are all ordinary operating decisions that are far cheaper to make before launch than after a complaint.
Content moderation is a staffed function, not a filter. Any site that accepts third-party submissions will receive material it should not publish. Automated tools reduce the volume and do not remove the responsibility, and a portal with no human in that loop and no documented takedown route is relying on luck. For a community site this is the single largest operating cost.
Availability is a commercial condition even where it is not a regulatory one. Users look at a portal at particular hours, suppliers upload at particular hours, and a site that is down during either is losing the habit that is its only asset. Monitoring, backups and somebody reachable are operating costs rather than optional engineering polish.
Intellectual property runs both ways. Your own content, data and brand are assets worth protecting through the intellectual property framework the Ministry of Economy administers; other people's photographs and descriptions arrive on your site every day, and a clear position on what a lister grants you by uploading — in your own terms of use — prevents the argument later.
What the licence costs to hold, which emirate and which route suit the model, what changes if the portal starts transacting or taking payments, and how listing, advertising and commission revenue are treated for tax all depend on the licensing authority and the revenue model. ConsultZone settles those against the actual feature roadmap, because in this line the feature that changes the licence is usually scheduled before anybody asks whether it does.
References
- Ministry of Economy — intellectual property, commercial agency and the company matters behind operating a site that carries third parties' material. Ministry of Economy
- UAE Government portal — the federal framework on online content and on the handling of personal data. UAE Government portal
- Federal Tax Authority — VAT enrolment and the treatment of subscription, advertising and lead-fee revenue. Federal Tax Authority
- Ministry of Human Resources and Emiratisation — work permits and labour contracts for moderation, support and engineering staff. MoHRE
Elsewhere in Digital Media & Portals
Activities that sit beside this one
Most licences carry more than one activity. Adding a neighbouring line at the application stage costs a fraction of amending the licence afterwards.
Begin with a clear conversation
Tell us what you intend to build.
A consultant will map the structure, jurisdiction, approvals and likely cost against what you actually described — not against a package.