One front door for everyone who deals with you

A portal that stores its own copy of your data creates a second source of truth, and the two drift apart. We build the portal as a layer over your systems of record. It reads from your ERP, CRM or databases through APIs and writes back through the same channels, so a customer sees the same balance your finance team sees.

Where the source system is slow or has no usable API, we add a small synchronization service with a cache, and we show the user when data was last refreshed. Honest freshness is better than a screen that looks live and is not.

A first release covers one user group and its three or four most common tasks, which usually takes eight to fourteen weeks. Further groups and features follow in the same framework, each faster than the last, because identity, layout and permissions are already in place.

The hardest part of a portal is not the screens. It is deciding who can see what. We run a short workshop to define user groups, roles and data boundaries before design starts. For example, a customer user sees their company's invoices only, a finance clerk at the customer sees payments, and a supplier sees purchase orders addressed to them.

Sign-in uses single sign-on with your identity provider for staff, and email plus multi-factor authentication for external users. Sessions expire, sensitive actions need re-confirmation, and every view of a sensitive record and every change is written to an audit log your administrators can search.

These choices follow the OWASP Application Security Verification Standard, and for entities covered by the NCA Essential Cybersecurity Controls we align access management, logging and session handling with those controls. We do not claim approval by the regulator. We build to the requirements and give you the evidence your own auditors will ask for.

Arabic is a first-class language in the portal, not a translation layer. Layouts mirror correctly right to left, forms accept Arabic names and addresses, dates can show Hijri and Gregorian, and numbers display consistently. Content editors manage both languages from one admin screen.

A portal holds personal data about customers, suppliers and staff, so the Personal Data Protection Law applies. We design a clear consent and notice flow, support access and deletion requests as real features, and limit the fields each role can see. If your policy or your customers require data to stay in the Kingdom, we host the portal and its database in a local cloud region, taking the CST cloud computing framework into account.

Hosting, backups, monitoring and security patching can be run by us after launch or handed to your IT team with runbooks.