Selected work
Results, not screenshots
Client names are withheld. The numbers are not — every one comes from a system I can open.
-
Staff had accepted the system was slow. It wasn't — it was fixable.
Screens that took about a second now open instantly. A page that froze for nine seconds loads immediately. Fixed on the live system during working hours.
Retail group, dozens of branches
- Odoo
- PostgreSQL
- Python
-
Three versions forward, on a live business, without losing a record
One of the largest custom Odoo systems I have worked on, brought up to date without a shutdown — including the parts the vendor rewrote twice underneath us.
Retail group, dozens of branches
- Odoo
- Python
- PostgreSQL
- Git
-
Customers pay the way they expect to — and the books still balance
Local card payments and buy-now-pay-later, wired end to end. Five platforms, each reconciling correctly against the accounts.
Retail and e-commerce, GCC
- Odoo
- Python
- UPayments
- Tamara
- Tabby
-
A hotel booking platform built for real traffic, in Arabic and English
Search, availability, checkout and payment — on cloud infrastructure defined in code, so it can be rebuilt from scratch on demand.
Travel technology
- Next.js
- React
- TypeScript
- Tailwind
- Terraform
- AWS
No cost, no pitch
Book a free 30-minute call
Bring the problem you keep postponing. We will work out whether it is worth fixing, what it would take, and whether I am the right person for it.
- A slow system, and nobody can say why
- An upgrade that has stalled
- A build about to start, and you want a second opinion
