I build software and AI systems for companies that need them to run every day — then make sure the people who own them can actually operate them. Remote-first, working with clients across Europe, the US and MENA.
Multi-tenant e-commerce with real accounting behind it — orders, inventory, double-entry books, and the reports an owner actually opens on a Sunday morning.
If you sell into MENA, WhatsApp is the storefront. Ordering, notifications and recovery flows built for it — with the consent, rate limits and stop conditions that keep the number alive.
Not a wrapper around a public model. Systems grounded in your catalogue, your history and your rules — with a failure mode I can describe in one sentence.
Systems in production, carrying real money and real customers. Clients aren't named here without their permission — the specifics are.
Live merchant storefronts on one codebase: orders, inventory, double-entry accounting, P&L and balance sheet per store, bank reconciliation, expense OCR, deadstock and reorder scanning. Row-level security so no merchant can ever see another's data.
Catalogue, customers and history moved without downtime. The import threw 186 failures that traced to 14 products with line breaks in their descriptions — the kind of thing only real data finds. Then months on the storefront being right in Arabic, on a phone.
Holding funds safely between two parties who don't trust each other, with a compensating-rollback path for every step that touches both a database write and an irreversible external call.
Ordering and recovery flows on WhatsApp, including the detail most miss: a DM cart goes cold in 30 minutes where a web cart takes 60, so the follow-up cadence is different. Consent, rate limits and stop conditions throughout.
Not a translation layer — RTL that actually holds up: invoices, search, SMS, mixed Latin-in-Arabic runs that reorder if you get the bidi isolation wrong. Live in production, not a demo.
Self-hosted CI, automated backups with tested restores, alerting wired before launch, and a written rule for every failure so the same class of bug doesn't come back under a new ticket number.
Work you can read, not just claims you have to take on trust. All of it built solo, all of it public.
MAVLink telemetry, live map, mission planning and a headless AI copilot for drones and rovers. If you want to know whether I can build a real-time system against a hardware protocol, the code is right there.
Swift 6 menu-bar companion for Claude Code, with a signed release channel and auto-updates. Small, but it ships — which is a different skill from building.
Wake word, speech, tool access and persistent memory, running on your own machine across Windows and macOS. No cloud round-trip for the parts that don't need one.
4K video behind your desktop icons, AppKit and AVFoundation talking to the Mac directly. No subscription, no account, no telemetry.
I don't hand over a repo and leave.
The systems I've watched fail didn't fail technically. They were delivered, the one person who understood them moved on, the vendor stopped answering, and eighteen months later the business was afraid to touch the thing it paid for. The software was never the problem. The handover was.Nothing gets called done because a dashboard is green. Merged isn't deployed, deployed isn't live — done means someone opened the real page, on a real device.
A reported bug is a sample. I find the cause, then every other place that cause exists, and fix them in one pass — so you don't get the same bug back under four ticket numbers.
That's usually a more useful first conversation than a feature list. If it's a fit I'll say so quickly; if it isn't, I'll tell you that too.
WhatsApp +20 120 776 1882 · Based in Egypt · full overlap with the European day, mornings with US East
Whisky 11 is based in Egypt and works fully remotely — there is no physical office or walk-in location. Clients are across Europe, the United States and MENA, and working hours overlap the full European business day and the US East Coast morning.
Multi-tenant e-commerce platforms with real accounting behind them, WhatsApp as a sales channel for MENA markets, AI systems grounded in a client's own data rather than a wrapper around a public model, and bilingual Arabic/English storefronts where the right-to-left layout holds up in invoices, search and SMS.
The system is built and then run alongside the client until their own people can operate it without us. Backups are restored before launch rather than merely scheduled, alerting and log retention are wired before go-live, and the client keeps the keys, the data and the ability to leave at any point.
Yes. Four projects are public on GitHub, including Ghost GCS — a ground control station for ArduPilot drones with MAVLink telemetry, mission planning and an AI copilot — and Whisky Claude, a shipping native macOS app with a signed release channel.
Message +20 120 776 1882 on WhatsApp or email hello@whisky11.com. The most useful opening is what breaks today and who has to live with it, rather than a feature list. If it isn't a fit you'll be told quickly.