Skip to content
ALI HAITHAM·TECH·responds in <1h
  • Homestart here
  • Workcase studies, projects
  • Serviceswhat I will build for you
  • Writingessays, series
  • Traincourses, labs, cohorts
  • Aboutthe engineer behind this site
Sign inStart a project
ALI HAITHAM · TECH
  • Home↗
  • Work↗
  • Services↗
  • Writing↗
  • Train↗
  • About↗
Sign inStart a project
Online
ALI HAITHAM·TECH

Engineering studio. Damascus, GMT+3.

aliyosef.online

Studio

  • Work
  • Writing
  • Training
  • About
  • Contact me

Portal

  • Sign in
  • Open a ticket
  • Track project
  • My account

Resources

  • Docs
  • Status
  • Changelog
  • Brand kit
  • Privacy
  • Terms

Newsletter

Field notes and tech news. Weekly. No fluff.

Free. Unsubscribe anytime.

Find me elsewhere
© 2026 Ali Haitham Yosef. All rights reserved.Hand-built in React 19. No frameworks of frameworks.Last deployed · 2026-05-08All systems operational
  1. Home/
  2. Services
003 / What I do

I build the custom systems you decided not to outsource.

Five services for founders and CTOs in MENA and beyond: custom ERP, product builds, audits, rescues, and team training. Solo engineer, weekly demos, written specs, no surprises.

Currently accepting 2 new builds this quarter·I usually reply within 2 business days.

Summary

I offer five services: custom accounting and cloud systems, custom product builds, code and architecture audits, migration and rescue work, and team training. Engagements are scoped in writing before kickoff, billed at fixed-scope or block-hours, and delivered in weekly Friday demos on a real staging environment. No surprise invoices.

The shape of the work

At a glance

  1. 01Five services: custom accounting and cloud, custom build, audit and consulting, migration and rescue, team training.
  2. 02Sample stack: Laravel, Flutter, React, NestJS, Postgres, MySQL, Redis, Reverb.
  3. 03Solo engineer model: one engineer end-to-end, no handoffs between sub-teams, written specs in plain Markdown.
  4. 04Currently accepting two new builds per quarter. Inquiries answered within two business days.
  5. 05Working across Saudi Arabia, the UAE, Egypt, Turkey, Europe, and the Americas, remote-first from Damascus.
The catalog

Five things I build, audit, or teach.

Each service has its own intake form so you spell out exactly what you need before we get on a call. Less back and forth, faster proposal.

I build custom multi-tenant accounting, inventory, payroll, POS, and e-invoicing systems for SMBs in Saudi Arabia, the Levant, and the Gulf. The reference implementation is Mohaseb (500+ tenants in production), and most engagements are either a fork of that pattern or a from-scratch build using the same offline-first Flutter + Laravel + Reverb stack. ZATCA-compliant by default. Typical engagement is four to nine months.

01Flagship

Custom accounting and cloud systems

Multi-tenant accounting, inventory, payroll, POS, and e-invoicing built around how your business actually works. Not a generic ERP forced into your shape.

  • Multi-tenant by design (one codebase, many companies, full data isolation).
  • Offline-first Flutter app with conflict-safe sync to a Laravel + MySQL backend.
  • Tax engine modeled on Odoo for accuracy (inclusive, exclusive, ZATCA-ready).
  • Self-hosted by default. You own the data, the database, and the deploy.
Discovery call within the week

I take on greenfield product builds where the off-the-shelf SaaS does not fit. Web, mobile, internal tools, integrations. Single engineer through delivery, weekly Friday demos on real staging, plain Markdown specs, scope locked at week one. Stack is picked per project, with Laravel + React or NestJS + Flutter being the most common combinations. Typical engagement is three to nine months.

02

Custom build: web, mobile, ERP

Greenfield product builds where the off-the-shelf SaaS does not fit. Web, mobile, internal tools, integrations.

  • Single engineer through delivery so context never gets lost in handoffs.
  • Weekly Friday demo on a real staging environment, not slides.
  • Plain Markdown specs, fixed milestones, scope locked at week one.
  • Code, infra, and docs handed over in a way your next team can actually pick up.
ReactLaravelFlutterNestJSPostgresRedis
Sample stack, picked per project

I review codebases, sync systems, multi-tenant architectures, and the hires you are considering. Output is a written report with prioritised findings and effort estimates, not a slide deck. Common findings: N+1 queries, sync drift between mobile and backend, tenant isolation gaps. Two shapes: a one-week quick read (top ten findings), or a two-to-three-week deep audit (full-stack review).

03

Audit and consulting

A second pair of senior eyes on your codebase, your sync system, your architecture, your hire. Written report, prioritized fixes, no PowerPoint.

  • Code, performance, security, sync, architecture (pick the slices that matter).
  • Written deliverable you can hand to your team, not a slide deck.
  • Action items ranked by impact and risk, with rough effort estimates.
Typical findings
  1. 01N+1 queries hiding behind Eloquent collections, easy 10x wins.
  2. 02Sync drift between mobile and backend, silent data loss in flight.
  3. 03Tenant isolation gaps a security review will catch later, not now.
Reads like a doctor visit, not a sales pitch

I take the call when a previous developer disappeared, when a framework upgrade has been blocking you for half a year, or when sync corruption is suspected and nobody on the team can prove it. Triage first, fix second. Restore-from-backup runbooks before any destructive change. Full Git access from day one. Triage available within 24 hours for genuine emergencies.

04Triage available

Migration and rescue

Your previous developer disappeared. Your framework is two majors behind. Your sync system corrupted production. I take the call.

  • Triage first, fix second. We map the actual state before touching anything.
  • Restore-from-backup runbook before any destructive change.
  • You get full Git access from day one, not at the end.
  • Documented handoff so you are never in this position again.
When to call
  • !Your codebase has nobody who fully understands it anymore.
  • !A framework upgrade has been blocking you for over six months.
  • !You suspect data corruption but cannot prove it without help.
Triage call within 24 hours

I run on-site or remote workshops and multi-week cohorts for engineering teams who want to ship faster without losing the rigour. Hands-on, not slide-driven. Topics include sync engines, multi-tenant Laravel, offline-first Flutter, AI-paired engineering, and the accounting domain. Format ranges from a one-day workshop to a multi-week cohort with a capstone on your real codebase.

05

Team training and workshops

On-site or remote workshops for engineering teams who want to ship faster without losing the rigour.

  • Hands-on, not slide-driven. Your team writes real code in real repos.
  • Curriculum tuned to your stack and your team seniority.
  • Recordings, exercises, and a follow-up Q&A window included.
Sync enginesMulti-tenantFlutter offlineAI-paired engineeringAccounting domainCode reviewArchitecture
See open cohorts on /train→
One day to a full week, on or off-site
How we work together

A small process that respects both of our time.

No long pitch decks, no surprise invoices. Five steps, in this order, every time.

  1. 01

    Discovery call

    Thirty minutes, free, no commitment. We figure out together whether this is a fit.

    Free, 30 min
  2. 02

    Written proposal

    Plain Markdown: scope, milestones, price, assumptions. You read it on your own time, not over a call.

    Within 5 working days
  3. 03

    Kickoff and scope lock

    Contract, deposit, repo access, kickoff call. Scope is locked here so neither of us drifts.

    Week 1
  4. 04

    Build with weekly demos

    Every Friday, a real demo on staging. You see progress, you flag issues, we adjust early.

    Every Friday
  5. 05

    Handover and 30-day support

    Code, docs, runbooks, and 30 days of support included. Your next engineer can take over.

    30 days included
Packages

Pick the shape that matches your stage.

No fake price anchors. Every engagement is quoted after the discovery call, with the tier you picked as the starting frame.

DiscoveryBest when you want a clear blueprint before committing.
  • +Two working sessions to map your business.
  • +Module-by-module recommendations.
  • +Effort and timeline estimates per module.
  • +Written architecture brief you can share internally.
BuildBest when you have a green-light budget and a deadline.
  • +Full custom system, deployed and integrated.
  • +Multi-tenant data isolation from day one.
  • +Offline-first mobile app with conflict-safe sync.
  • +Documentation, runbooks, and handover.
  • +30 days of post-launch support.
RetainerBest when the system is live and you need a senior on-call.
  • +Monthly block of hours.
  • +Priority on production issues.
  • +Quarterly architecture review.
  • +Direct line for technical decisions.
DiscoveryBest when you have an idea but not yet a spec.
  • +Clarifying sessions with you and your team.
  • +A written technical spec you actually agree with.
  • +Stack recommendation and effort estimate.
  • +A go or no-go call at the end.
BuildBest when the spec is ready and the clock is ticking.
  • +Single engineer through delivery.
  • +Weekly Friday demo on staging.
  • +Plain Markdown spec maintained as we build.
  • +Code review window for your team.
  • +30 days of post-launch support.
RetainerBest when the product is live and evolving.
  • +Monthly block of hours, your priority queue.
  • +Quarterly product or technical review.
  • +On-call for production incidents.
  • +Same engineer who built it.
Quick readBest when you need a sanity check before a hire or a release.
  • +One week of focused review.
  • +Written report with the top ten findings.
  • +A 60-minute walkthrough call.
Deep auditBest when something is genuinely wrong and you need a plan.
  • +Two to three weeks of full-stack review.
  • +Code, performance, security, sync, and architecture.
  • +Prioritized fix list with effort estimates.
  • +Written report and a 90-minute walkthrough.
  • +Optional follow-up retainer.
TriageBest when you do not yet know how bad it is.
  • +A 48-hour discovery sprint.
  • +Documented current state with risk ranking.
  • +Restore-from-backup runbook.
  • +A clear go-forward proposal.
RescueBest when something is broken and your team is stuck.
  • +Hands-on fix work, not just a report.
  • +Backups verified before any destructive change.
  • +Daily progress note, weekly demo.
  • +Knowledge transfer to your team or your next hire.
RebuildBest when the cheapest fix is to start over with the lessons learnt.
  • +Greenfield rebuild on a sane stack.
  • +Data migration from the old system.
  • +Full handover with documentation.
  • +30 days of post-launch support.
WorkshopBest when you want a concentrated upskill in one or two days.
  • +One or two day curriculum.
  • +Hands-on exercises in your stack.
  • +Recording and exercise repo retained by your team.
  • +A follow-up Q&A window.
Cohort programBest when a small group needs to level up over weeks, not days.
  • +Multi-week curriculum tailored to your team.
  • +Two live sessions per week, async support in between.
  • +Capstone project on your real codebase.
  • +Recordings and exercises included.
Mentoring retainerBest when you want senior mentorship for a junior or mid team.
  • +Weekly office hours.
  • +Code review on real PRs.
  • +Quarterly architecture session.
  • +Same engineer, every week.
Practical questions

Things you probably want to ask.

01How does pricing work?+

I 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.

02Do you sign NDAs?+

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.

03Who owns the IP?+

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.

04What is your timezone?+

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.

05What languages do you work in?+

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.

06What is your refund policy?+

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.

07Can I hire your team after delivery?+

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?

Send a quick message→
Service inquiry

responds in <1h