Web systems and internal platforms
Request, committee and disbursement approval workflows in the browser — with permissions for every role and a full audit trail. This includes the public-facing site, payment portals and stores tied to the same route.
We build both in the browser — website design and development on one side, and the internal platform that runs the requests on the other. And we start with neither the design nor the code, but with a sheet of paper on which we map your procedure as it is actually practised, not as the regulations describe it.
What we build
- Corporate website design: pages that read well on mobile, update from one place, and can be found by anyone searching for you by name.
- An internal platform: the request approval workflow with its roles — who submits, who reviews, who approves, who disburses.
- A payment portal or store tied to the same route, so no amount is recorded twice and nothing is reconciled by hand at month end.
- A dashboard showing where each request stands, how many are sitting with each role, and which have passed their deadline.
- An audit trail recording every transition with its time and its actor.
- Web applications that run on mobile with no download: the same screens open in the browser, and if you need an app in the stores we'll tell you when it's worth it and when it isn't.
For
An organisation with a recurring approval or disbursement route: requests, committees, contractor claims, procurement.
What you get
- A route with defined roles and permissions
- An audit trail recording every transition with its time and actor
- A dashboard showing where each request stands — and we have a ready system to tailor if that is faster for you than building from scratch.
We start on paper, before the code
- We understand the procedure
- We document it
- We build
- We hand over and run a trial
- We support and operate
Questions about this service
How long does it take to build the system?
It varies with the size of the system and the number of workflows, and it is set out in the proposal for each project. What actually shortens it is clarity about the procedure before we start: one settled route is faster than two that are still disputed.
Do we start from scratch or from a ready system?
If your route resembles everyone else's, ready is cheaper and faster, and we'll say so without flattery. We have a management system running at a client organisation today that gets tailored to your procedures. The test is practical: if you're going to buy something ready and then work around it with side spreadsheets, you've paid twice.
Who owns the code and the data?
Your organisation alone. The repository, the hosting and the database are in your name from day one, handed over complete and self-contained when the contract ends, and the documentation is written so another team can pick it up without coming back to us.
We work with organisations across all regions of Saudi Arabia and the Gulf — remotely, with site visits when needed.