Custom software & platforms
The system your business actually runs on.
Built around how your people work, not the other way round. Two of ours run inside Saudi businesses today: one across 30+ sites in four cities, one for three multi-site operators.
Works with
- ZATCA Phase 2
- E-signature
- Excel
- Odoo
- ERPNext
- n8n
The situation
The process lives in people, not systems
The same details are typed three times: a paper form, a government portal, an Excel sheet. One person knows how it all fits, and they are on leave next week. Every branch does it slightly differently. Off-the-shelf software covers half of it, and your team routes around the other half on WhatsApp.
What you get
Four things you can point at when it is done.
One screen, entered once
Intake, the mandatory report and the signed contract in a single pass. Details typed once, by one person.
Every branch on one platform
Head office sees every site live. Each branch sees only its own work, in Arabic or English.
Rules built in
Government reporting, approvals and e-signatures happen inside the flow, not as a step someone has to remember.
Source code you own
Repository, documentation and deployment handed over on client-owned builds. No vendor holds the keys.
How we work
Nothing moves to the next step until you have checked this one.
Discover and map
We time the current process on the floor, count its steps, and you sign the map.
Screens approved, then built
Every screen reviewed with you before code. Milestones arrive working, tested against what you approved.
Parallel run, then switch
The old system keeps running beside the new one on real work. You decide when it stops.
30+
Sites on one platform, four Saudi cities
A front-line process that took more than ten minutes now takes about one, across 30+ sites in Makkah, Madinah, Jeddah and Riyadh.
Questions
Asked before every project like this.
- Why not buy off-the-shelf software?
- Often you should, and we will say so in the assessment. Custom makes sense when the routine is repeated across branches, tied to rules you cannot change, and no product fits without workarounds.
- How long does a platform take?
- Scope decides it, and we give a written timeline after mapping, not before. For reference, the 30-site platform went from first screen to full production in six months.
- Who owns the code when it is done?
- On client-owned builds, you do: repository, documentation and deployment. Nothing about the handover depends on you staying with us.
Free 45-minute assessment
Show us the process that costs the most time.
We map it, count its steps, and tell you in writing what we would build and in what order. You keep the map either way.