Custom Systems
ERPs, dashboards, internal tools. The system that runs the business — not a SaaS subscription that runs you.
Deep dive
Every Saudi mid-market business reaches the same crossroads. The Excel file becomes a system. The system becomes a SaaS subscription. The SaaS subscription becomes a ceiling — too rigid for how the business actually operates, too expensive per seat, too hard to integrate with anything else, too dependent on a roadmap you don't control. The exit is custom software, but it's expensive and slow when done badly.
We do it by modeling the business first. Two weeks of structured discovery before any schema is written: we sit with the people who run the operation, watch them work, map the flows that actually happen versus the flows the SaaS pretends are happening. The data model that comes out of that fits the company, not the framework.
From there we build a Postgres + Prisma backend with a TypeScript API (REST or GraphQL), bilingual at the schema layer (every label, every error message, every report column lives in AR and EN from day one), and a clean operator UI in Next.js. Saudi-specific concerns — Hijri/Gregorian dates, ZATCA invoicing, VAT rules, SAR-precise decimal handling, Asia/Riyadh timestamps — are part of the foundation.
The most important deliverable isn't the software. It's the discipline of building it: a clean migration path off your current SaaS, role-based access that matches your actual org chart, exports that match what your accountant or auditor needs, and documentation written in a language your team reads. Deqa ERP — 14 modules, fully bilingual, shipped end-to-end — is the reference for what "built right" looks like in this market.
Arabic-first
Every SaaS that promises Arabic support actually delivers right-aligned English with translated labels. The numbers are still Latin, the dates are still Gregorian-only, the reports still read left-to-right. We design the schema in Arabic first — column names, enum values, audit logs — and let the English fall out as the secondary view. The result is a system Saudi teams actually want to use.
Deliverables
- Discovery & data modeling
- API & backend
- Admin & operator UI
- Reports & exports
- Hosting & maintenance
What's not included
- Quick replacements for Salesforce / HubSpot / standard CRMs that just need configuration. If your needs fit the standard CRM box, hire a CRM consultant.
- Mobile-only apps without a backend. We build full-stack systems where mobile is one of several surfaces.
- White-label SaaS for resale. The systems we build are owned by you, not by us.
Process
-
01 Modeling
Map the business as it actually runs — not as a SaaS imagines it.
-
02 Schema & API
Postgres schema, REST/GraphQL API, role-based access.
-
03 UI
Operator and admin UIs designed for speed and clarity.
-
04 Deploy & Maintain
Hosted, monitored, and maintained — the system is yours, not ours.
Typical timeline
12–20 weeks
Timelines flex with project scope, team availability, and response time on your side. We give a precise schedule after the discovery call.
Common questions
Should we build custom or buy a CRM/ERP?
Almost always: buy first, build only what doesn't fit. We do a free 60-minute audit before recommending custom. If a standard CRM/ERP fits 90% of your workflow, we'll tell you to buy it and we'll integrate the missing 10%. Custom from scratch is the right answer for 1 in 10 inquiries.
How do you handle Saudi compliance (ZATCA, NPHIES, SAMA)?
For ZATCA Phase 2 we ship invoice signing, QR generation, CSID handling, and clearance/reporting flows as part of standard delivery. NPHIES and SAMA we handle on a project-by-project basis depending on which APIs your domain touches; we have shipped to both before. Auditor-friendly logs are non-negotiable in everything we ship.
Where will the data live? In the Kingdom?
Your choice. We deploy to Saudi-resident servers (we use Liquid Web KSA, Tonic, or AWS Bahrain) when data residency matters. For non-regulated data we use the closest cloud region (typically Bahrain or Frankfurt). We never store production data on our infrastructure.
What happens if we want to leave?
You take everything with you. Code repository, database dump, hosting credentials, documentation. We build software you own — there is no lock-in clause, no source-code escrow, no payment trigger to keep your platform running. If you decide to take the project in-house or hire another studio, we hand it over cleanly.