Legacy system modernization
Untangle a system that has become too risky to change, and make it safe to change again — without stopping the business while it happens.
For startups and SMEs that need more than a developer.
What I do
What differs is whether that means building, fixing, or training.
Business systems built around the way your operation actually works, for when the standard product would need the operation to change shape to fit it.
Read more →Multi-tenant SaaS platforms where tenancy, identity, and money are settled before the first feature — because those are the decisions you cannot reverse.
Read more →Untangle a system that has become too risky to change, and make it safe to change again — without stopping the business while it happens.
Practical multi-day training designed around what your team is actually stuck on — not a fixed curriculum, and delivered with a codebase they keep.
Read more →A company site held to the same standard as a product — fast on mobile data, native in Arabic and English, and usually the front of something larger.
Apps for work that happens away from a desk — offline-first, with the sync rules and the App Store release handled by the person who designed the system.
A store platform built for the market it actually sells in — local payment rails, local couriers, multi-currency, and Arabic as an architecture decision.
A booking and ticketing platform for travel agencies — supplier search, expiring fares, irreversible issuance, agency credit, and margin, in one system.
Read more →Selected work
A Syrian market e-commerce platform — an independent store for every merchant, with local payments and delivery built into the core. Founded, built, and still running it.
Digital menus for restaurants and hospitality in the Saudi market — a multi-tenant platform where the menu is a live system, not a PDF behind a QR code.
E-commerce for Arab businesses worldwide — a store platform built for merchants whose customers, currencies, and shipping routes cross borders.
About
Most contractors enter at "development," once the decisions that matter have already been made. I start earlier and stay later — across the technical system and the business it has to serve.
Ways to work together
Freelance projects · Fixed-scope contracts · Technical partnership · Consultation · Team training
Before you ask
By settling what the system is actually about before anything is designed: the order lifecycle, the sync rules, the awkward states. Once those are agreed, what to build and what can wait is a much smaller argument.
A defined outcome for a defined price, from idea to launch. It only works in that order: what "done" means gets settled first, then the price and the plan against it.
Consultation time is published: $200 an hour, $350 for two, and the first twenty minutes free. Project prices aren't, because the same feature list is a different project depending on what it integrates with.
The five models differ mainly in how much of the outcome I own, from delivering one feature to leading architecture as you grow. Describe the situation rather than picking a format.
Something new, something that needs fixing, or a team that needs leveling up — tell me what you're working on.