Custom Software
A portal your clients actually use, not one they forget the password to
Your clients call you for order status, invoice copies, and document requests because there is nowhere else for them to look. A portal gives them a login. It gives your team fewer calls and a paper trail for every request.
4 to 8
weeks to a working first version
2
languages, Arabic and English, from day one
24/7
access for your clients, no waiting on office hours
The direct answer
A client portal is a secure website where your customers log in to see their own data: order status, invoices, quotes, documents, and a way to message your team. It replaces phone calls and email threads with a single place both sides can check. Built for Saudi companies that deal with distributors, contractors, or repeat B2B buyers who need self-service access without you building a whole new department.
What this removes.
Your team answers the same questions
Today
Staff spend hours a week on "where is my order" and "send me the invoice again" calls and emails.
With the system
Clients check the portal themselves. Your team handles the exceptions, not the routine lookups.
Documents live in scattered email threads
Today
Invoices, PO confirmations, and delivery notes sit buried across dozens of email chains nobody can search.
With the system
Every document tied to a client sits in one place, timestamped, searchable, and downloadable on demand.
No record of what was promised
Today
A price, a delivery date, or a change gets agreed by phone or WhatsApp and nobody writes it down.
With the system
Requests and responses live in a thread attached to the client account, visible to anyone on your team.
Arabic clients get an English-only experience
Today
Your only client-facing tool is an English spreadsheet or a system nobody localized.
With the system
Clients switch to Arabic with one tap. Numbers, dates, and invoice PDFs render correctly either way.
What lands in your hands.
Client accounts and roles
Login, password reset, and per-client permissions so users only see their own data.
Order and status tracking
A live view of where each order or project stands, pulled from your existing system.
Invoice and document center
Searchable archive of invoices, statements, and files with PDF download.
Request and message threads
Clients raise a request or question, your team replies, everything stays on record.
Admin dashboard
Your internal view to manage client accounts, permissions, and content without a developer.
Bilingual interface
Full Arabic and English UI with correct RTL layout, not a machine-translated afterthought.
Systems and platforms we work with
- App Store
- Google Play
- Apple
- Android
- iOS
- macOS
- Windows
- Web
Systems and platforms we work with
- React
- Next.js
- TypeScript
- Node.js
- Python
- Flutter
- PostgreSQL
- Supabase
- Tailwind CSS
- Docker
- GitHub
- Google Cloud
- Figma
Five stages. You sign off every one.
Read each stage as a small contract: what we need from you, what lands in your hands, and the sentence that has to be true before we move on.
- Scope and data mapping1 to 2 weeks
- Design1 to 2 weeks
- Build2 to 4 weeks
- Testing and hardening1 to 2 weeks
- Launch and supportongoing
Scope and data mapping
1 to 2 weeks
We map what your clients actually ask for, what data already exists in your systems, and what a first version needs to cover.
- Share current client requests and pain points
- Give access to existing systems and data
- A scoped feature list with priorities
- A data map showing what connects to what
We move on when the scope and data sources are agreed in writing before any build starts.
Design
1 to 2 weeks
We design the portal screens in both languages, focused on the handful of tasks clients do most often.
- Review screen designs and give direction
- Confirm branding and terminology
- Clickable design for every core screen
- Arabic and English versions side by side
We move on when you sign off on the design before we write a line of production code.
Build
2 to 4 weeks
We build the portal against the agreed scope, connecting it to your existing data where needed.
- Answer questions as edge cases come up
- Test each feature as it lands
- Working features delivered in stages, not one big drop
- A staging environment you can log into
We move on when every feature in scope is built, connected, and testable by you.
Testing and hardening
1 to 2 weeks
We test with real client data, check both languages under load, and fix what breaks before anyone outside your team sees it.
- Run the portal with a small group of real users
- Flag anything that feels off
- A bug-fixed, load-tested build
- Access control tested so clients only see their own data
We move on when the portal passes real-user testing with no open critical issues.
Launch and support
ongoing
We go live, hand over documentation, and stay on for fixes and small changes as your client base uses it.
- Roll out access to your clients
- Send us issues or new requests as they come up
- Production deployment and monitoring
- A support window for fixes and adjustments
We move on when the portal is live, your team can operate it day to day, and a support plan is in place.
Asked before signing.
How is the price set?
Fixed scope, fixed price, agreed after the scoping stage. We map your actual client requests first so the quote reflects what you need, not a generic package. Changes after sign-off are priced separately, not folded in silently.
Can it connect to our existing ERP or CRM?
Usually, yes. We connect to systems like Odoo, SAP, or a custom database through their existing APIs, so the portal reflects live data rather than a manual copy. If a system has no API, we scope a workaround during the first stage.
Is our client data handled in line with PDPL?
Yes. We build access controls so each client sees only their own data, minimize what personal data we collect, and can host inside Saudi Arabia if your compliance requirements call for it. We will walk through your specific PDPL obligations before build starts.
Do you support Arabic properly, not just translated labels?
Yes. Right-to-left layout, Arabic-Indic or Latin numerals per your preference, and Arabic invoice PDFs are built in from the start, not bolted on after. We test both languages at every stage, not just at the end.
Give your clients a place to look instead of a number to call
Tell us how your clients currently reach you and what they ask for most. We will scope a portal around that, not a generic template.