Ecommerce developer for hire.
One developer accountable for the whole stack — architecture, storefront, backend, deploy — instead of an agency handoff. Most projects start from one of three places: a migration that cannot lose traffic, a store that has grown too slow, or a catalogue the theme was never built for.
What I build
Shopify and headless storefronts
Custom Shopify themes, and Next.js storefronts on the Storefront API when the theme layer stops being enough. Built against the catalogue you actually run, not a demo of twelve products.
Ecommerce migrations
OpenCart, WooCommerce and Magento to Shopify. Redirect maps, structured data and metafields move with the products, so the rankings survive the switch — 3,000 products migrated with zero lost positions.
Speed and Core Web Vitals
Render-blocking assets, image pipelines, third-party scripts, server rendering. Measured before and after on real devices, not on a staging URL — one storefront went from 4.8s to 1.2s LCP.
Integrations and automation
Payments, CRM, ERP, warehouse and marketplace syncs. Multi-currency payout engines, catalogue pipelines, and the admin tooling that keeps the data straight without someone editing spreadsheets.
How it runs
A call
Thirty minutes on the actual problem. You leave with an opinion on it whether or not we work together.
A scope and a number
Written scope, fixed price where the work is knowable, weekly rate where it is not. No discovery phase to pay for.
Weekly builds
Deployed increments you can click, every week. You see the thing working long before the invoice.
Working together
Project
A defined build — a migration, a storefront, an integration. Fixed scope, fixed price.
Retainer
Ongoing development and fixes for a store already live. Monthly, cancel any time.
Audit
One week on an existing store: performance, architecture, what is costing you conversions. A written report and a call.
Tell me what is broken.
A short description of the store and the problem is enough to start. Replies within a day.
Start a project