Right tool.
Proven in production.
Every tool below has carried real launches under real traffic. I pair two decades of engineering judgment with AI-accelerated workflows — Claude, Cursor, the Vercel AI SDK — so you get senior-quality code at vibe-coding speed. Click any technology for the full picture.
The daily drivers.
Next.jsv15
Next.js is my default for marketing sites, storefronts and web apps — server components, instant pages, green Core Web Vitals. It's the stack running NIO's regional EV platform in production today.
React Native+ Expo
One codebase for iOS and Android, with over-the-air updates that ship a fix the same day. It's what PropertyCheck and The Savvy Way run on.
Laravelv12
I build the back end with Laravel: APIs, booking engines, CRMs and event-driven services that hold up under real traffic. A decade in production — including the ordering flows behind ChatFood (now Deliverect).
Sanity
Sanity is my default CMS for sites where marketing teams need to move fast without a developer in the loop. I run it in production behind brands like NIO — structured content, live previews and trilingual localisation across a dozen builds.
And the
deep bench.
Reactv19
I build the hard front-end: payroll, billing, real-time dashboards, configurators. Lead-architect on large React codebases — including alfii's HR SaaS and NIO's regional EV platform.
Vercel AI SDK+ OpenAI
I use the Vercel AI SDK to ship AI features that earn their keep — streaming chat, content generation and intelligent search wired straight into Next.js, Sanity and commerce stacks. Not a bolted-on widget; part of the product, the way I built it for NIO.
MedusaJS
I build headless commerce on MedusaJS — custom carts, checkout, and B2B logic you fully own, wired to a Next.js storefront. It's the engine behind NIO's regional EV configurator and ordering flow across MENA.
ShopifyHydrogen
I build headless Shopify storefronts on Hydrogen — Shopify checkout and inventory behind a fast, custom React front end. Shipped for beauty brand Siella, who wanted a flagship store that didn't look like a theme.
Filament+ Laravel
I build admin panels, CRMs and ops dashboards on Filament — the back-office layer your team lives in every day. It's the control room behind my Laravel builds, including the order flows that powered ChatFood.
Umbraco+ C#
My go-to .NET CMS for enterprise and government-grade sites that have to be locked down, multilingual, and editor-friendly. I shipped it for Emarat, the UAE national fuel brand.
Vue.js
I work in Vue.js when a team or codebase is already on it — and I'm fully productive in it. I joined ChatFood's Vue front-end with zero Vue experience and was shipping the order catalog, cart, and Apple Pay checkout within weeks.
Learn more →Payments & checkout
I build payment and checkout flows that take money correctly: wallet checkout, Stripe, bank transfers — idempotent, webhook-driven, reconciled. Shipped on ChatFood and alfii.
Retoolinternal tools
I build internal tools, admin panels and ops automation on Retool — admin dashboards, campaign runners, data jobs that plug straight into your existing backend. Days instead of weeks, so your product engineers stay on the product.
And everything
around them.
languages & ui
data & payments
cloud & delivery
Stack decisions,
not stack fashion.
Your team can run it
A stack is wrong if your developers can't hire for it or your marketers can't edit in it. Handover-ability is a first-class requirement.
Boring where it counts
Databases, auth and payments get the proven option. The innovation budget is spent where users feel it — not in the plumbing.
New when it pays
I adopted server components, Hydrogen and the AI SDK early — because each one bought measurable speed or capability. New for new's sake doesn't ship.
Questions, answered
What tech stack do you build with?
My core stack is Next.js and React Native on the front end, Laravel for back-end services, and Sanity as the CMS. Around that I work with React, the Vercel AI SDK, Medusa, Shopify, TypeScript, PHP, Node.js, PostgreSQL, Stripe and Vercel — every tool proven in production.
How do you decide which technology to use for a project?
I optimize for handover-ability: a stack is wrong if your team can't hire for it or your marketers can't edit in it. I keep databases, auth and payments boringly proven, and spend the innovation budget only where users feel it.
Do you use AI tools in your development workflow?
Yes. I pair two decades of engineering judgment with AI-accelerated workflows — Claude, Cursor and the Vercel AI SDK — so you get senior-quality code at vibe-coding speed. The AI accelerates the work; the architecture decisions stay mine.
Can you build e-commerce stores?
Yes. I build commerce on Medusa and Shopify, with Stripe for payments and Next.js or React Native on the storefront. The platform choice depends on your catalog, your team and how custom the checkout needs to be.
How do you decide when to adopt a new technology?
New for new's sake doesn't ship. I adopted server components, Hydrogen and the AI SDK early — but only because each one bought measurable speed or capability. A technology earns its place when it pays for itself, not when it's fashionable.