Software house · Jeddah, Saudi Arabia
The system behind your systems.
Orders, stock, invoices and government reporting, entered once and carried everywhere they need to go. Built in Jeddah, delivered in milestones you verify, and yours at the end.
Free assessment · 45 minutes · you leave with the process map either way
Entered five times → entered once
- Spreadsheet
- WhatsApp threads
- Paper invoices
- Government portal
- Ledger
- Entry point
Same work. Entered once instead of five times.
- ZATCA Phase 2e-invoicing live in production
- 30+ sitesone platform, four Saudi cities
- Data in JeddahOracle data center · PDPL-aligned
- CR 7054975482registered with MISA, 2026
What we build
One partner for everything digital your business needs.
Seven kinds of work, each described by what it does for your operation, not by a category name.
Custom software & platformsCustom software & platforms
The system your business actually runs on.The system your business actually runs on, built around how you work. Two of ours are in production in Saudi businesses today.
Systems integrationSystems integration
ZATCA, payments and accounting in one flow.Your systems already exist. Our job is to make them talk. ZATCA e-invoicing runs in production for us today.
ERP for factoriesERP for factories & distributors
Odoo or ERPNext, shop floor to ledger.Odoo or ERPNext, wired to the shop floor and the ledger. Sized for the Future Factories digitisation track.
Web & mobile appsWeb & mobile apps
Arabic first, fast on a mid-range phone.Arabic first, right-to-left by default, quick on a mid-range phone over mobile data.
E-commerce & marketingE-commerce & marketing
Takes the payment, issues the invoice.A storefront that takes the payment, issues the invoice and tells you what actually sold. Salla, Zid or custom.
AI where it pays for itselfAI where it pays for itself
Ships only when it beats the manual way.Reading documents, sorting the inbox, flagging the exception. Ships only when it beats the manual way on your data.
Payments & fintechPayments & fintech engineering
Checkout, settlement and SAMA-licensed platform work.Mada, Apple Pay, STC Pay, Tamara and Tabby at checkout, settlements reconciled into the accounts, and platform work for SAMA-licensed partners.
Every one of the seven carries the same guarantee.
Screens approved before code. Milestones you verify. Your old system runs in parallel. You own the code. Your data stays in the Kingdom.
Read the guarantee
One rule under all seven: nothing moves to the next milestone until you have verified this one. See the guarantee
The guarantee
Five promises. Every one verifiable.Five promises. Every one of them verifiable.
You should not have to trust us. Each promise is something you can check yourself: before you approve the work, while we build it, and after we hand it over.
- 01
You approve the screens first
No code until you have seen every screen and signed it off.
- 02
You verify every milestone
Each one arrives working, in your hands, tested against what you approved.
- 03
Your old system keeps running
In parallel, until the new one proves itself on real work. You decide when it stops.
- 04
You own the source code
Repository, documentation, deployment. No vendor holding your keys.
- 05
Your data stays in the Kingdom
Oracle’s Jeddah data center, PDPL-aligned, exportable any time you ask.
Work in production
Both of these are running inside Saudi businesses right now.
Client names withheld under NDA. The work, the numbers and the timelines are exactly as delivered.
Work in production
Both are running inside Saudi businesses right now.
Live across 30+ sites in four citiesMulti-site operations platform
The front-line process took more than ten minutes: a paper form, the same details retyped into government portals, then a chase for a signature, while the customer waited. One platform replaced all of it: intake, government reporting, e-invoicing and the ledger from a single entry.
- ~1 min
- 30+ sites
- 6 months
- ~1 min
- front-line process, down from 10+
- 30+
- sites live in four cities
- 6 months
- first screen to full production
Three multi-site operators run on itRecurring-order operations platform
Standing orders are easy to take and hard to keep: quantities that shift weekly, several sites pulling from one production load, a schedule rebuilt by hand every morning. The whole cycle now lives on one screen: orders, production load and the daily schedule, generated instead of retyped.
- 3 operators
- 1 screen
- Daily
- 3
- multi-site operators live
- 1 screen
- orders, load and schedule together
- Daily
- schedules generated, not rebuilt
Your sector is not the point. The pattern is: a routine that costs minutes, repeated across every branch, tied to rules you cannot bend.
How we work
Nothing moves to the next step until you have checked this one.
No black box. Each step ends in something you can read, click, or test.
Discover
Map before a line of code.We sit with the people who do the work, time the current process, count its steps, and write down every form, spreadsheet and portal it passes through. You get the map before a line of code.
Design
Every screen approved by you.Every screen is drawn and reviewed with you before development starts. You walk the real flow and we fix it on the screen, not inside a finished system.
Build & migrate
Working milestones, reconciled data.Milestones, each delivered working. Your data moves in stages, reconciled against your own records. ZATCA wired in from the start, on infrastructure inside the Kingdom.
Go live & train
Old system runs in parallel.Your old system runs in parallel until the new one proves itself. We train your team on their own data, in Arabic and English, and stay on the line through the first cycles.
Questions
The five questions we are asked first.
Short answers here; the full ones live on their own pages. If yours is not here, ask. We would rather answer it now than in a proposal.
- What does it cost?
- No fixed price, because scope varies too much for one honest number. The free assessment is where the number comes from: we map the process and scope it in writing.
- How long does it take?
- A written timeline after the mapping step, not before. What is fixed is the shape: screens approved first, then milestones you verify one by one.
- What happens to our current system?
- It keeps running, in parallel, until the new one has proved itself on your real cycles. You decide when it stops.
- Who owns the code?
- On client-owned builds, you do: repository, documentation and deployment. Nothing about the handover is conditional on staying with us.
- Where does our data live?
- In the Kingdom: Oracle’s Jeddah data center, PDPL-aligned, exportable any time. The same rule applies to enquiries sent through this site.
Free assessment
Describe the process that costs your team the most time.
45 minutes. You keep the map either way.Forty-five minutes on a call or in Jeddah. 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.