Focused offerings, proven on real platforms.
No generic service menu. Each offering maps to a strength I've shipped across multiple production systems — with the projects to prove it.
Marketplace platforms
Complete multi-sided commerce — storefront, vendor & admin dashboards, payments, and the DevOps to run it. You launch a working business, not a demo.
What you get
- Storefront + vendor + admin surfaces
- Payments, RFQ flows, order routing
- Dockerized deploys with CI/CD
ERP & internal systems
ERPNext/Frappe implementations and custom internal platforms — procurement, inventory, contracts, and fund flows. The unglamorous systems an organisation actually runs on, built to survive audit and daily use by hundreds of staff.
What you get
- ERPNext / Frappe implementation & customisation
- Procurement, inventory & contract workflows
- Arabic-first RTL, built for government-scale use
Native mobile + web
Flutter iOS/Android apps and Next.js web on one shared backend — every customer reached without paying three teams.
Multi-tenant SaaS
Subscription products with Postgres Row-Level Security and tenant isolation — sell once, serve many, safely.
Premium landing pages
High-end, conversion-first landing pages — bilingual, animated, and wired to capture qualified leads. Built to make a brand look worth trusting and turn visits into enquiries, not just impressions.
What you get
From $200- Bilingual Arabic/English with full RTL
- Lead capture wired to your inbox or database
- Premium motion, SEO-ready — shipped fast
Start from the problem, not the technology.
Six focused build offerings, each written for a specific business situation. Every one links to the case studies that prove it.
Spare parts marketplace development
Parts commerce is not normal e-commerce. A wrong part is a returned part, a lost customer and a stranded vehicle. I build parts marketplaces where compatibility, quotation and multi-supplier fulfilment are first-class parts of the data model — not features bolted onto a generic store.
Proven onSee the detailAjzaMONTRA LiftsMulti-vendor marketplace development
A marketplace is three products wearing one brand: a place customers want to buy, a back office vendors will actually log into, and an operations console your team runs the business from. I build all three, on one backend, with the money handling done properly.
Proven onSee the detailAjzaMONTRA LiftsQootyERP software for procurement and operations
The systems an organisation actually runs on are rarely the exciting ones: purchase requests, approvals, stock movements, contracts, budgets and reconciliation. I build and implement those — Arabic-first, audit-ready, and designed for staff who will use them every day for years.
Proven onSee the detailMONTRA LiftsCashskeMulti-tenant SaaS development
Turning a working product into a product you can sell many times is mostly one hard question: how do you guarantee tenant A can never see tenant B's data? I answer it at the database level, then build billing, plan gating and onboarding on top of that guarantee.
Proven onSee the detailMudarrisQootyStravoFlutter + web product development
Most products in this region need a web presence for search and trust, and a mobile app because that is where people actually transact. Building those as separate projects doubles the cost and guarantees they drift apart. I build them as one product with one API.
Proven onSee the detailAjzaMudarrisQootyArabic RTL software development for MENA
Most “Arabic support” is an English product with the text swapped and the layout mirrored. Users notice within seconds and trust drops. I build products where Arabic is a first-class language in the data model, the interface, the search, the emails and the invoices.
Proven onSee the detailAjzaMONTRA LiftsQooty
Most projects land in one of these.
Rough shapes, not a price list. The first call is where yours gets named and cut down to something shippable.
- Multi-week
Focused MVP
One core workflow, one or two surfaces, and the unglamorous parts done properly — auth, data model, deploy. Built to be extended, not thrown away.
Typical scope1 workflow · 1–2 surfaces · production deploy - Several months
Full platform build
Multi-sided product with customer, vendor and admin surfaces, payments or ledgers, and native apps where they earn their place.
Typical scope3+ surfaces · payments · mobile + web - Weeks
Rescue & hardening
An existing product that works until it doesn't — data integrity, tenant isolation, performance, or a release process nobody trusts.
Typical scopeaudit · fix · handover - Monthly
Ongoing engineering partner
A retained senior engineer for a product that keeps evolving — roadmap work, production support, and someone who already knows your system.
Typical scoperetainer · agreed capacity
One senior engineer, or an agency?
Both are legitimate. This is where each one actually wins — including the cases where you should not hire me.
| One senior engineer | A typical agency | |
|---|---|---|
| Who writes the code | The person who scoped it | Usually a junior team, supervised |
| Decision speed | Same day — one person decides | Through account and project management |
| Parallel capacity | Limited — one project at a time | High — several tracks at once |
| Where the money goes | Engineering, almost entirely | Engineering plus overhead and management |
| Continuity | One point of failure — mitigated by full handover | Team absorbs turnover |
| Best for | Products where judgment matters more than headcount | Large parallel scope with fixed process needs |
Who writes the code
- One senior engineer
- The person who scoped it
- A typical agency
- Usually a junior team, supervised
Decision speed
- One senior engineer
- Same day — one person decides
- A typical agency
- Through account and project management
Parallel capacity
- One senior engineer
- Limited — one project at a time
- A typical agency
- High — several tracks at once
Where the money goes
- One senior engineer
- Engineering, almost entirely
- A typical agency
- Engineering plus overhead and management
Continuity
- One senior engineer
- One point of failure — mitigated by full handover
- A typical agency
- Team absorbs turnover
Best for
- One senior engineer
- Products where judgment matters more than headcount
- A typical agency
- Large parallel scope with fixed process needs
Discovery → Design → Build → Ship & Support.
A small, senior team means less ceremony and more signal. Here's the path from first call to live product.
- 01
Discovery
We scope the users, success metrics, and constraints. A free 15-minute intro call to confirm fit and direction before anything is committed.
- 02
Design
Architecture, data model, and UI direction agreed up front — so the build has no surprises and every decision has a reason.
- 03
Build
Iterative delivery with weekly previews. You see real, working software as it grows — not a black box that opens at the end.
- 04
Ship & support
Production deploy, monitoring, and a clean handover, plus an agreed support window so launch day isn't the end of the road.
Worth knowing before you write.
A short, honest filter. It saves both of us a call that was never going to work.
A good fit if
- You have a real business or a funded idea, and a decision-maker in the room
- The product has to handle money, roles, or operations correctly — not just look good
- You want one senior engineer accountable end to end, not a rotating team
- Arabic and English both matter to your market
- You can give a few hours a week to reviews and decisions
Not a fit if
- You need a team of ten starting Monday — that is an agency's job, not mine
- The budget is fixed before the scope exists and cannot move
- You are looking for the cheapest possible quote rather than the right build
- Nobody on your side can answer product questions within a few days
- You want equity-only work or an unpaid prototype
What you get in the first call
Fifteen minutes, free, no deck.- A straight answer on whether this is buildable the way you imagine it
- The two or three decisions that will drive most of your cost
- A rough shape: phases, surfaces, and where the risk sits
- An honest ballpark range — or a referral if I am not the right fit
What to prepare
None of it has to be polished.- One sentence on what the business does today
- The workflow that hurts most, described in plain language
- Who needs to log in, and what each of them does
- Any deadline that is real, and why it is real
- A budget range you are comfortable discussing openly
Questions, answered straight.
Still unsure? Ask the assistant in the corner, or message on WhatsApp.
Mahmoud Makhlouf — a senior full-stack engineer — handles the engineering directly, using modern tooling and AI for leverage. You get senior judgment on every line instead of work handed down to juniors.
// Let's build
Have a product in mind? Get a clear plan and a free 15-minute intro call.
Tell me what you're building. I'll come back with an approach, a rough timeline, and a ballpark — usually within 24 hours.