Available for select work. Systems Architect — Dubai
The software that runs the company after everyone goes home.
The systems I built are running — around the clock.
Process automation · AI/ML · Full-stack Available for select work
Fig. 02 — After hours
Every company has a closing time.
The spreadsheets stop reconciling.
Approvals wait for morning.
And the one person who knows how it all works — goes home.
The businesses running my systems don’t stop.
Quotes go out. Sessions seal themselves. The books close.
I build the night shift.
Fig. 03 — The ledger
Meet the night shift.
Six working systems across consulting, agency ops, healthcare, manufacturing, finance, and developer tooling. Some run operations; others prove a product or architecture under real gates.
Every cell opens a recorded bench test grounded in the source product. Hover one to see its 3 A.M.The one mid-screen is on its 3 A.M.
ProcessOS
Five minutes of intake; a consulting-grade document before the meeting ends — grounded in an industry corpus, quality-gated before a client ever sees it.
KorCRM
Hunt finds the fit; three drafts face five deterministic checks and an eight-part judge. Weak work is refined before a human sees it.
EHR Behavioral
A clinician corrects the diarized draft, signs once, and the transcript locks. Finalization and signature land as linked audit events.
Afterwit
Resolved fixes enter a review queue before future agents can see them. Relevant history returns cited and bounded; unrelated work gets silence.
Ducts Manufacturing Ops
Consumption closes; margin recomputes from the material snapshot. Approval appends a new version and queues the dispatch hand-off.
Financial Modelling OS
Rules route every source row with provenance; allocation slices reconcile exactly before the Revenue and GM meeting view opens.
Fig. 04 — Method
Trust is a deliverable.
Every engagement starts in your operation, not in code — the real process, its failure modes, the numbers that will define success. Those numbers are agreed before the build begins. Where AI helps, it assists inside deterministic guardrails: rules enforce the process, people keep the final call, and your data stays where you govern it. The work ends with a handover, not a dependency — runbooks, training, and a system your team runs.
See the methodology →- Understand Leaves you with Process map
- Contract Leaves you with Success metric
- Build Leaves you with Working increment
- Prove Leaves you with Acceptance evidence
- Handover Leaves you with Runbook + training
Fig. 05 — Correspondence
Let's build your night shift.
I'm a systems architect in Dubai (UTC+4), available for select work. Tell me what should keep running after your company goes home.
Wherever you are — the systems are still running.
[email protected]