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. Custom accounting and cloud systems
003 / What I do

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.

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
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.
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
Selected case studies

Recent work, end to end.

01MohasebLead EngineerView case study→
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