Custom client portal or off-the-shelf SaaS?

Most portal projects fail on this decision, not on the code. Here is the comparison we run with clients before quoting, including the cases where we tell them not to build.

Talk to us See delivered portals

The decision is about your workflow, not your budget

A licensed portal product is cheaper on day one and gets you live in weeks. A custom portal costs more up front and takes longer, but it fits the process your clients already expect from you. The mistake is choosing by price instead of by how much of your operation the portal has to carry.

We have shipped portals for a development bank, a government SME authority and a ministry. All three could have bought a product. None of them could have run their approval chain, their Arabic document workflow and their integration requirements through one without rebuilding most of it.

The eight criteria that decide it

Score your own case on each row. If more than three land in the right column, a licensed product will cost you more over three years than building once.

Time to first release

Off-the-shelf SaaS: Weeks. Configuration only, no engineering.
Custom build: One quarter for a focused first release, more for integrations and approvals.

Fit to your process

Off-the-shelf SaaS: You adapt to the product. Requests become feature votes.
Custom build: The portal follows your approval chain, terminology and exceptions.

Arabic, English and RTL

Off-the-shelf SaaS: Usually translated, rarely designed right-to-left. Arabic documents often break.
Custom build: Built in both directions from the first screen, including PDFs, forms and email.

Integrations

Off-the-shelf SaaS: A fixed list of connectors. Anything else is a paid extension or impossible.
Custom build: Direct integration with your ERP, CRM, SSO and ZATCA e-invoicing.

Cost over three years

Off-the-shelf SaaS: Per-seat or per-client licensing. Grows with every client you win.
Custom build: Build cost once, then hosting and maintenance. Flat as you grow.

Data and hosting

Off-the-shelf SaaS: Their cloud, their region, their retention rules.
Custom build: Your infrastructure or a region you choose, with your retention policy.

Change requests

Off-the-shelf SaaS: Roadmap-dependent. You wait, or you pay for a custom module.
Custom build: Scoped and priced per change, no dependency on someone else’s roadmap.

Exit cost

Off-the-shelf SaaS: Export is partial. Leaving means losing workflow history and integrations.
Custom build: You own the code and the database. Exit is a hosting decision, not a migration project.

Criterion	Off-the-shelf SaaS	Custom build
Time to first release	Weeks. Configuration only, no engineering.	One quarter for a focused first release, more for integrations and approvals.
Fit to your process	You adapt to the product. Requests become feature votes.	The portal follows your approval chain, terminology and exceptions.
Arabic, English and RTL	Usually translated, rarely designed right-to-left. Arabic documents often break.	Built in both directions from the first screen, including PDFs, forms and email.
Integrations	A fixed list of connectors. Anything else is a paid extension or impossible.	Direct integration with your ERP, CRM, SSO and ZATCA e-invoicing.
Cost over three years	Per-seat or per-client licensing. Grows with every client you win.	Build cost once, then hosting and maintenance. Flat as you grow.
Data and hosting	Their cloud, their region, their retention rules.	Your infrastructure or a region you choose, with your retention policy.
Change requests	Roadmap-dependent. You wait, or you pay for a custom module.	Scoped and priced per change, no dependency on someone else’s roadmap.
Exit cost	Export is partial. Leaving means losing workflow history and integrations.	You own the code and the database. Exit is a hosting decision, not a migration project.

This is a decision framework, not a sales page. If your answers sit in the left column, buy the product — we will say so.

Which side are you actually on?

Two honest profiles. Most buyers recognise themselves in one of them within a minute.

Buy the product when

You sell a standard service, your client count is modest, and the portal is a convenience rather than the product.

Fewer than roughly fifty active clients
One workflow, no exceptions worth coding
English-only or lightly translated interface
No ERP, SSO or e-invoicing requirement
You need it live this quarter

Build it when

The portal carries regulated or high-value work, and a mismatch between your process and the software becomes a business problem.

Approvals, document exchange or billing that must match your policy
Arabic-first users, including right-to-left documents
Regulated sector: government, finance, healthcare
Existing ERP, CRM, SSO or ZATCA integration
Client count and licensing cost both growing

What we bring to the comparison

We build portals, so read this section as a bias check. These are the numbers behind the work, and the reason the comparison above is specific rather than generic.

projects delivered: 45+
government entities: 3
years shipping bilingual systems: 5+

Questions buyers ask at this point

Can we start with a product and move to custom later?

Yes, and it is often sensible: run the product for a year, learn which parts of your process it cannot hold, then build those. The cost is that you pay twice and migrate data once. Budget for the migration from the beginning.

How long does a custom portal take?

A focused first release — authentication, document exchange, one approval chain, dashboards — takes about a quarter. Integrations with ERP, SSO or e-invoicing add scope in proportion to how many systems and how much of their data you need.

Do we need to replace our ERP?

No. The portal sits in front of it: it owns the client experience and calls your ERP for the records that already live there. Replacing an ERP to get a portal is the most expensive way to solve this.

What happens to the code if we stop working with you?

It is yours. The repository, the database schema and the deployment configuration are handed over, with documentation. A custom build you cannot leave is not custom.

Is a custom portal secure enough for government work?

Security is a build decision, not a product feature: authentication, authorization on every state-changing path, audit trails, encryption in transit and at rest, and dependency review. We build to that standard because our clients are audited.

Bring your case and we will score it with you

Send the workflow the portal has to hold and the systems it must talk to. We will tell you which column you land in, including when the answer is to buy a product.