Your firm needs a portal — somewhere customers, partners or distributors log in to check orders, download documents and see their account. The choice looks like a pricing question: subscribe to a ready-made SaaS portal, or commission a custom portal built around your workflow. It is really a fit question, and portals punish the wrong answer: most people logging in are outside your company, so per-seat pricing and rigid workflows behave differently here than for internal tools.
The short answer: score the fit gap before you compare prices
List the jobs your portal must do, and mark each standard or genuinely yours. If almost all are standard — login, document download, order history, password resets — a SaaS portal will serve you well, and a custom build would reinvent a solved problem. If several core jobs follow rules only your business has — customer-specific pricing, approval chains that mirror your contracts, documents in your exact formats — the fit gap is real, and SaaS workarounds will cost staff time every month. Price comes second, over several years, not from the first invoice.
The problem: paying per seat for a portal that does not fit — or building one you did not need
Portals fail in two opposite ways. In the first, a firm subscribes to a polished SaaS portal, discovers its workflow does not match how customers actually buy, and starts running the real process in spreadsheets beside the portal it pays for. In the second, a firm commissions a custom portal for entirely standard jobs, then owns the hosting, patching and maintenance of a system a vendor would have run for a modest fee. Both failures come from the same shortcut: deciding on first-year price instead of fit and user economics.
What each route actually gives you: SaaS portal, custom portal, and the hybrid middle
A SaaS portal gives you speed and a landlord. You configure branding, roles and the workflows the vendor exposes; the vendor hosts, patches and updates it. You cannot change behaviour the vendor has not built — you rent it per seat, for as long as you use it.
A custom portal gives you ownership and exact fit. Workflow, data model and integrations are designed around your process, and the code and data are yours — with WebStackRank builds, ownership of IP and code transfers in full on final payment. You also own the upkeep: hosting, security updates and every later change. Our custom web application development overview places portals in that wider category.
The hybrid middle puts a custom layer where the fit gap lives and SaaS everywhere else: a tailored front-end over a standard accounting or CRM system, or a SaaS portal extended with the one module your contracts require. For many UAE firms this is where the decision lands.
The fit-gap test: which portal jobs are standard, and which are genuinely yours?
Write down every job the portal must do, then score each: 0 if any mature product does it the standard way, 1 if products do it but not in your sequence or format, 2 if the job exists because of how your business works. Be strict — a job is not a 2 because you prefer it your way; it is a 2 when a customer, contract or regulator requires it.
- Login, roles and password management: almost always 0.
- Order and invoice history from your accounting system: usually 0 to 1.
- Document downloads in standard formats: 0; in customer-specific formats: 2.
- Pricing shown per customer from your own agreements: usually 2.
- Approval chains mirroring your delegation rules: 1 to 2.
- Arabic interface with right-to-left layout: 0 if the vendor genuinely supports it, 2 if it does not and your users need it.
Add the scores. A total dominated by 0s means buy. Several 2s among daily customer jobs means the gap is structural: you are choosing between custom and hybrid, not SaaS.
The multi-year economics: per-seat growth vs build + maintenance (worked comparison table)
Portal economics turn on one fact: most of your users are external. A per-seat fee trivial for twenty staff becomes a serious line when 400 customers, or 4,000, log in — and some vendors count every registered user as a seat. Run both routes over three years, using your own quotes.
| Cost line over 3 years | SaaS portal | Custom portal |
|---|---|---|
| Getting live | Setup and configuration | Build cost (your scoped quote) |
| Recurring licence | Per-seat fee × all users × 36 months | None |
| User growth effect | Rises with every added user or tier | Hosting rises slowly; no per-user fee |
| Running costs | Included in subscription | Hosting, monitoring, updates |
| Change requests | Vendor roadmap or paid add-ons | Maintenance you control |
| Workaround cost | Staff hours where the fit gap bites | Near zero on 2-scored jobs |
| Leaving cost | Data export, retraining, rebuilt habits | Handover of code and data you own |
Do the arithmetic with your growth assumption, not today's headcount: if your customer base doubles in three years, the SaaS licence line roughly doubles with it, while the custom line barely moves — but it starts far higher and includes maintenance you must fund. Once you have chosen, our guide to client portal development costs in the UAE breaks down the build side, and our web development packages page shows how scoped packages are structured.
Integration, data location and Arabic: the UAE factors that can decide it alone
Three local factors can override the scorecard. First, integration depth: list every system it must touch — accounting, ERP, CRM, document store — and check whether the SaaS product's API reaches all of them, or whether you would be building middleware anyway. If you are building the hard part regardless, the comparison changes.
Second, data location and the UAE Personal Data Protection Law (Federal Decree-Law No. 45 of 2021). The PDPL does not impose a blanket rule that personal data must be stored inside the UAE; it sets conditions for transferring personal data abroad, and free zones such as DIFC and ADGM run their own regimes. Ask any vendor, in writing: where is portal data processed, and how are those conditions met for our case? A custom build lets you choose the hosting region directly; with SaaS you rely on the vendor's answer — get it before signing, and check your sector too, since some regulated activities carry stricter rules.
Third, Arabic. Many global SaaS portals translate menus but not documents, search or right-to-left layouts. If your customers will use the portal in Arabic, test it with real users during the trial — not from the vendor's feature list.
Exit and ownership: what leaving each route really costs
Decide how you would leave before joining. Leaving a SaaS portal means exporting your data — ask in what formats, and whether documents and history come out or only headline records — then retraining every external user, the part firms underestimate. Leaving a custom build is an engineering handover: code, documentation and data pass to a new maintainer — painful if documentation was never funded, routine if it was. With a WebStackRank build, ownership of IP, code and domain transfers in full on final payment. Either way, write exit terms into the initial agreement, when you still have leverage.
Decision criteria: match your score to a route
If your scores are mostly 0s and your user count is modest and stable, subscribe. If you scored several 2s on daily customer jobs, or your external users will grow into the thousands, commission custom or hybrid and model the build against three years of seat fees. If one UAE factor — a non-negotiable integration, a data-location answer a vendor cannot give, or Arabic your users need — fails on the SaaS side, that factor decides it alone. If the evidence is mixed, run the hybrid: buy the commodity core, build only the layer where your business differs.
Common mistakes
The first is comparing first-year prices: SaaS is priced to win that comparison. The second is counting only staff seats and forgetting that external users may be billable — confirm the vendor's definition of a user before modelling. Third, trialling with internal staff instead of real customers, the users least able to work around a bad fit. Fourth, commissioning custom without funding maintenance, then blaming the build when an unmaintained system ages. Fifth, skipping the exit questions until renewal day, when answers cost most.
FAQ
When should a customer portal be custom instead of SaaS?
When daily customer jobs follow rules only your business has — customer-specific pricing, contract-based approvals, documents in your formats — or when external user numbers make per-seat pricing outgrow a build over three years.
Why does per-seat pricing break down for customer portals?
Because portal users are mostly external. A fee designed around employee headcount multiplies across hundreds or thousands of customers, and some vendors count every registered user as a seat — so success directly inflates the bill.
What is a hybrid portal?
One that buys the standard parts and builds the distinctive ones: a custom customer-facing layer over a standard accounting or CRM system, or a SaaS portal extended with one custom module. Spending targets the fit gap, not commodity functions.
Does UAE law require portal data to be hosted in the UAE?
Not as a blanket rule. The UAE PDPL (Federal Decree-Law No. 45 of 2021) sets conditions for transferring personal data abroad rather than mandating in-country storage; DIFC and ADGM run their own regimes, and some sectors are stricter. Ask each vendor where data is processed.
What should we check about leaving a SaaS portal before signing?
Ask what data you can export, in which formats, and whether full history and documents are included; what happens to your data after cancellation; and what notice the contract requires. Get the answers in the agreement, not in a sales call.
Get a portal recommendation scoped to your workflow (CTA)
Bring us your fit-gap list and your user numbers — today and in three years — and we will recommend SaaS, custom or hybrid in plain language, including when the honest answer is to subscribe and not build at all. WebStackRank provides an itemised proposal within 24 business hours once a build scope is agreed. Start with our web portal development services, bringing your job list, the systems the portal must connect to, and any data-location requirements.
