Real systems. Real production.
Thirteen flagship systems on this page. Six hundred more projects in the back catalogue, available on request. Each card opens what was actually built, not the pitch deck.
Summary
My work archive: thirteen flagship systems shipped since 2015, plus six hundred smaller projects. Multi-tenant ERPs, Flutter offline-first apps, Laravel backends, hospitality and e-commerce platforms across the GCC, the Levant, and the US.
At a glance
- Thirteen flagship systems documented in detail. Six hundred more delivered since 2015.
- Flagship: Mohaseb, a multi-tenant ERP serving 500+ small and mid-sized businesses.
- Stack across most projects: Laravel, Flutter, Postgres, MySQL, Redis, Reverb WebSocket.
- Clients across five countries: Saudi Arabia, Syria, UAE, Kuwait, the United States.
- Solo engagement. The same engineer who scopes the work also ships and supports it.
I build productionsystems for thewhole region.
Solo, end to end, billable from day one. No agencies in the middle, no handoffs between strangers, no nineteen-thread Slack negotiation before a single line of code gets written.
- Years
- 10
- Projects
- 600+
- Countries
- 5
- 01
Multi-tenant ERPs
One Laravel codebase, hundreds of isolated tenants, custom workflows per industry. Sync, audit logs, billing, the lot.
- 02
Real-time sync engines
WebSocket plus offline queue, conflict resolution that survives bad networks, idempotency on every write.
- 03
Cross-platform mobile
Flutter with Drift, offline-first by default, native-feel UI on iOS and Android. POS, field ops, inventory.
- 04
Hospitality and e-commerce
Bookings, ordering, POS, inventory. Wired to your accounting from the first invoice, not bolted on later.
- 05
Backoffice and integrations
Odoo customisation, custom Laravel, ZATCA e-invoicing, third-party APIs. The plumbing other vendors quietly avoid.
Sixteen projects and products.
Click any project for the live site or case study
142026Fadel
Multi-service travel app · interactive prototype
Product design, app development and identity
152026HAEIFIN
Financial notebook & account management
Product experience, application and platform
162026Adooar
Restaurant and hospitality operations
Product customization, integration and frontend development
012024–2026Mohaseb
Multi-tenant ERP
Lead Engineer
022023Ritz-Carlton Riyadh
Integrated digital platform · guest experience
Full-stack Engineer
032024Concetto Labs
Full-stack digital portal
Full-stack Engineer
042024–2025Kais Center
Odoo ERP, web platform, accounting training
Odoo Engineer + Trainer
052024–2025CyberV
Tech consulting · Corporate site
Full-stack Engineer
062024Caravan Cargo
International shipping · Corporate site
Full-stack Engineer
072021Suhail Restaurant
Restaurant site · WooCommerce ordering
WordPress Developer
082025Junada WhatsApp Suite
WhatsApp management & broadcast automation
Backend Engineer
092024Baloma
Saudi e-commerce · Custom Zid theme
Theme Engineer
102023Asl Evaluation
Saudi real estate valuation
WordPress Developer
112024–2025Ali Omuom
CEO personal site · CyberV
Designer + Developer
122019Yang's Kitchen
LA restaurant · Custom ordering
Front-end Developer- OS132023–now
Open Source
Various tools
Maintainer
Built with these.
Ten tools, in rough order of how often I reach for them.
- 01Laravel
- 02Flutter
- 03Postgres
- 04Redis
- 05WebSockets
- 06React
- 07Next.js
- 08TypeScript
- 09Odoo
- 10Reverb
Same stack across most projects. Less time picking tools, more time shipping. The boring stack is the productive stack, especially when you have to maintain it for five years.
Four steps. No surprises.
- 01
Scope
A three-day audit of your codebase, or a structured discovery on a greenfield brief. Output is a one-page document on what to build and what to skip.
- 02
Build
Weekly demos on a real environment. You see what shipped, what is next, what is blocked. No black boxes, no vapor screenshots.
- 03
Review
Every change reviewed against production standards: tests, migrations, security pass. QA on a staging environment that mirrors the production setup.
- 04
Ship
Production deploy with monitoring, backups, and a thirty-day post-ship support window. After that, ongoing retainer or clean handoff. Your call.
Working with Ali on the digital transformation for Mira Restaurants Group was a pleasure. He led the technical team skillfully and delivered integrated solutions that markedly improved bookings and order management.
What people ask before reaching out
01Are these all your own work?
Yes. Every system on this page was built by me directly, either solo or as the lead engineer with a small team I assembled. Where I worked inside a larger agency or platform, I have noted it in the role line. Nothing here is white-labeled from someone else, and I do not claim credit for systems where I only consulted briefly. If a card is here, I wrote a meaningful share of the production code.
02Can I see the source code?
For most cases, no. Mohaseb, Junada, Kais Center, and the hospitality projects are commercial codebases owned by the client or by my own studio. For open-source work, the repo links are on the cards directly. If you are evaluating me for a job or contract, I am happy to walk you through architecture diagrams, decision logs, and selected file-level snippets in a private call.
03Why are some clients not named?
A few clients have NDAs, or simply prefer not to be named publicly. In those cases I describe the system, the role, and the outcome without naming the brand. If you ask for references, I can usually arrange an introduction with prior consent. The thirteen cards on this page are the projects whose owners explicitly approved being shown.
04How recent is this work?
The newest projects, including Mohaseb and Junada WhatsApp Suite, are shipping right now in 2025 and 2026. The oldest case shown, Yang’s Kitchen, is from 2019 and is included because the build patterns are still relevant. I refresh this archive every quarter and retire stale cases. The year on each card is the year I shipped the production version, not the year the project started.
05Can I commission something similar?
Most likely yes, depending on capacity. I take on roughly two to four engagements per quarter, usually a mix of new builds, audits, and rescue projects. Use the form at the bottom of this page or the /services page to send a brief. I read every message and reply within twenty-four hours, even if the answer is "this is not a fit right now."
06How do you handle confidentiality?
NDAs are signed before any commercial discussion. Source access stays inside the client’s environment, with credentials rotated when I hand off. Architecture diagrams shown in pitches are anonymised. Nothing about a current engagement appears on this page until the client has signed off in writing.