The site falls over every time marketing runs a campaign.
I reshape the critical path with queues and caching that absorb 10× the load.
I work with a small number of clients at a time, because systems that carry money and data do not get built with half your attention.
The four I hear most. Each has a known shape and a fix I have already run in production.
The site falls over every time marketing runs a campaign.
I reshape the critical path with queues and caching that absorb 10× the load.
The dashboard crawls and queries take seconds.
Measured diagnosis, real indexes, N+1 elimination — usually 5–20× in two weeks.
The previous developer left and nobody understands the code.
Full audit, documentation, and a prioritised rescue plan before any rewrite.
Multiple websites need consistent data from one backend.
I define clear API contracts and keep deployments and permissions within those boundaries.
Backend first, product-minded, and comfortable owning the frontend when it matters.
From first schema to launch: clear domain boundaries, clean migrations, tests that protect what you built.
REST contracts, versioning, queues, events, and service boundaries enforced by tooling — not good intentions.
Server-rendered, RTL-ready multilingual interfaces wired straight into the API.
N+1 hunts, real indexes, layered caching, and a before/after number for every change.
Stripe, Paymob, idempotent webhooks and reconciliation that never loses a cent.
Docker, CI/CD, monitoring and alerting — or a monthly retainer that keeps it all alive.
Three shapes of engagement. Scope decides which one fits — not the other way round.
Agreed scope, clear timeline, delivered in slices. Best for a new product or a rebuild.
Two weeks to diagnose the system and hand you an actionable report with the top ten moves.
Reserved days each month for maintenance, monitoring and continuous delivery.
Four stages, every one of them visible to you while it happens.
A week of hard questions: what breaks, who it hurts, and which number has to move.
Straight answers to the questions that come up on every first call.
I do not publish prices because price follows scope. After a 30-minute call you get a written proposal with a fixed scope and one number.
Yes — I join as a senior engineer inside your team, with code reviews and written standards.
You do. Everything lives in your repository from day one.
I build the Next.js side myself — Tatbeqy and Dranovo are both in production — or integrate with your team through clean API contracts.
Tell me the problem in two paragraphs. You get an honest read on scope, risk and whether I am the right person — within a day.