About
An independent software team building the systems companies actually run on. We are judged not by what a system demonstrates, but by what it survives: an ordinary Tuesday, fifty people in it at once, and a delivery waiting on the number it returns.
Off-the-shelf software asks a company to change to suit it. We work the other way round. Before a single screen is drawn we sit with the people doing the job and write down how the work actually moves — that a chute is measured in buildings and floors, that the central store is the one control point for material, that quality is what allows material into the warehouse at all. The system is then built around that, in the company’s own vocabulary.
Our flagship is a full ERP for a manufacturer: thirteen departments, a hundred and ninety-one screens, built in about ten weeks and in daily production use since. It replaced paper, spreadsheets and a WhatsApp thread per project with one platform where a figure is calculated once and read everywhere, and every movement is recorded against the person who made it.
The systems on this site are not variations on one template. A manufacturer’s ERP. An instalment showroom where no step opens until the one before it is approved. A dress-rental atelier whose booking lifecycle is held in the database itself. An importer whose trade debt is measured in gold rather than pounds, so inflation does not eat it. A law firm’s public site with a private office panel behind it. None of them could have been bought.
Arabic is a first language in everything we build, never a translation layer added at the end. The flip to right-to-left is complete — navigation, tables, galleries and forms all mirror — while numbers, dates, currency and document codes keep their correct order. Arabic is never letter-spaced, and the line height opens to suit the script. Your people read the system in the language they think in.
We would rather say “not measured yet” than “it should work”. Every figure on this site traces back to something we built, ran and counted — and where there is no measurement, the page says so plainly.
How we work
Start from the process, not the screen
We sit with the people doing the job and write down how the work actually moves — not how the manual says it should. What gets built serves that, in your own vocabulary.
A feature is never delivered half-done
Every feature ships whole: interface, API endpoints, database, activity log, permissions, error handling, and both languages. Missing one of those means it is not finished, and it does not go out.
A guide that moves with the system
Every workspace carries a bilingual field guide, updated the moment the screen changes, so a new hire learns the system that exists rather than the one it used to be.
The build does not tolerate silent errors
Type checking, lint rules, tests and a translation-completeness check run before every deployment. Incomplete work never reaches the people using it.
Who we work with
- Factories and mid-size businesses replacing paper and Excel
- Retailers, traders and importers outgrowing their notebooks
- Law firms and professional practices
- Teams that need internal tooling built quickly and properly
- Agencies and consultancies subcontracting build work
A fully custom ERP for a manufacturer
From paper, Excel and WhatsApp to one platform covering 13 departments.
See the flagship, screen by screen →