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/
  3. Migration and rescue
003 / What I do

Migration and rescue

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

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

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

Services→
Service inquiry

responds in <1h