On-site or remote workshops for engineering teams who want to ship faster without losing the rigour.
On-site or remote workshops for engineering teams who want to ship faster without losing the rigour.
No fake price anchors. Every engagement is quoted after the discovery call, with the tier you picked as the starting frame.
No long pitch decks, no surprise invoices. Five steps, in this order, every time.
Thirty minutes, free, no commitment. We figure out together whether this is a fit.
Free, 30 minPlain Markdown: scope, milestones, price, assumptions. You read it on your own time, not over a call.
Within 5 working daysContract, deposit, repo access, kickoff call. Scope is locked here so neither of us drifts.
Week 1Every Friday, a real demo on staging. You see progress, you flag issues, we adjust early.
Every FridayCode, docs, runbooks, and 30 days of support included. Your next engineer can take over.
30 days includedI quote fixed-scope when the work allows it, and block hours when it does not. Both are written down in plain Markdown before kickoff, with the scope, the milestones, the price, and the assumptions, so there are no surprise invoices later. Discovery calls are free; written proposals are delivered within five working days.
Yes. If confidentiality matters to you, I will sign your NDA before we discuss specifics. I have my own one-page mutual NDA on hand if you would prefer something light to start with. Beyond NDAs, I treat client identities and source code as private by default.
You do, on full payment. Source code, infrastructure, documentation, and runbooks are assigned to your company at handover. I keep the right to mention the work in my portfolio unless you ask otherwise, and I retain the right to reuse generic non-confidential patterns the way every engineer does.
GMT+3, Damascus. I work synchronously with teams across Saudi Arabia, the UAE, Egypt, Turkey, and Europe. For teams in the Americas, synchronous overlap is usually four to six hours per day, with written async documentation beyond that. I travel for kickoffs and major milestones when an engagement justifies it.
Arabic (native) and English (fluent). Documentation, code comments, commit messages, and demos can be in whichever language fits the team. Mixed is fine and is the norm for most MENA teams. End-user documentation is delivered in both Arabic and English with full RTL support, never auto-translated.
If we part ways within the first week of kickoff, you get a full refund minus the discovery cost. After that, we negotiate fairly based on what was delivered, what was paid, and what remains unspent. The default is a clean split, not a fight; I have never had a client take this clause to a dispute.
There is no team to hire. I work solo and only bring in trusted collaborators when the engagement specifically requires it. Everything I build is documented well enough that your next engineer, whoever you hire, can pick it up cleanly. The handover package includes architecture docs, runbooks, and a recorded walkthrough.
Still have questions?
Services