The Amazon Now race is won on launch speed.
I take programs from zero to live across a market, then build the mechanisms that make the next launch faster. That is the job this role describes.
Talabat, Noon and Careem already run neighbourhood dark stores. Coverage goes to whoever can permit, fit out and stock the next site fastest, safely and on budget. I have taken a venture from zero to ten physical locations, shipped digital products to market on schedule, and I build the tooling that turns each launch into a repeatable playbook.
I designed and built this page myself with the AI toolchain I would bring to the team, including Claude Code. The launch plan below runs live.
Launch Control: opening a new Amazon Now site
This is the plan I would bring to the first program review: the critical path for standing up a new micro-fulfilment site, and what I do when the plan gets hit. Toggle a real disruption and the schedule, the go-live date, and the confidence recompute. Every mitigation is the corrective action I would actually run.
Critical path 7 gated phases
Throw a disruption at it
These are the real ways a UAE quick-commerce launch slips. Select any combination.
Corrective actions I would run
Nothing to correct yet. Select a disruption to see the mitigation, the Amazon principle behind it, and where I would refuse the easy fix.
Turn each launch into a mechanism
The role asks for scalable tools, mechanisms and operating models for future expansion. A mechanism at Amazon is a process that makes the right thing happen reliably, not by good intentions. Here are four I would stand up, each one I have built a version of before.
A reusable site-launch playbook
One template every new site runs on: the gated path, standard permit and civil-defence packs per emirate, a pre-qualified contractor panel, and a launch-readiness checklist. Site two is faster than site one because site one wrote the playbook.
I built the go-to-market playbook that took WePractice from zero to ten locations.
A weekly launch narrative, not slides
A short written status read at the start of each review: milestones, dependencies, financials, risks and readiness, with the go/no-go call and the two-way-door decisions made that week. It forces clarity and gives senior leaders one honest source of truth.
I was the reporting bridge between UBS and Baloise stakeholders and delivery at Brixel.
Input metrics that predict the launch
Track the controllable inputs that move go-live, permit lead time, fit-out slip, hiring fill rate, equipment clearance, and the pick-to-door test time against the 15-minute promise, rather than waiting on the output to tell you it is late.
At Ifolor I lifted conversion +9% and checkout +15% by testing and reading the funnel inputs.
A risk register that drives action
Every risk carries an owner, a trigger, and a pre-agreed mitigation, so a slip meets a decision, not a discussion. The register is the memory: what hit site three is already de-risked for site four.
I took market MVPs to launch at Die Mobiliar, including Smide, now BOND Mobility.
The honest read: where I would be learning, and what I bring on day one
Where I would be learning
I have not launched a physical fulfilment facility, run construction, or held a PMP. My program discipline comes from venture and product delivery, not a formal certificate, and the facility-specific craft, municipality permits per emirate, cold-chain fit-out, materials handling equipment, is new to me. I would ramp on it fast, the way I have ramped into every unfamiliar model I have worked in.
What transfers directly
The program itself is the same job in any domain: end-to-end delivery, governance, risk, budget, launch readiness and stakeholder coordination across many functions. I have taken a venture to ten physical locations, owned a CHF 100M+ e-commerce P&L, and delivered launches on schedule with external agencies and vendors. And I build the tooling myself, so the mechanisms this role wants are things I make, not just manage.
I would rather name the gap than have you find it. If the physical-facility depth is the dealbreaker, that is a fair call. If launch judgment, ownership and the ability to build the machine that scales are what you need most, that is exactly where I am strong.