I take web products from an empty repo to a live URL — frontend, backend, and AI features. Book a 15-minute call and we will work out whether I am the right person for what you are building.
Available for workTop Rated on Upwork · 5.0 · 100% JSSUS / UK / CA / AU overlap
Next.js Development — Freelance Next.js and React development — greenfield builds, App Router migrations, SSR/ISR architecture, and Core Web Vitals optimization for startups and product teams.
Shopify App Development — Shopify app development — embedded admin apps with Remix and Polaris, webhook-driven backends, storefront widgets, and App Store submission support.
AI Integration — AI and LLM integration for production applications — RAG and vector search, multi-provider architecture, streaming interfaces, prompt evaluation, and cost control.
Codebase Takeover & Bug Fixing — Taking over abandoned or broken React, Next.js and Node.js codebases — architecture review, production bug fixing, and finishing the work without an unnecessary rewrite.
Figma to React — Figma to React and Next.js conversion — pixel-accurate component architecture, design-system tokens, and responsive implementation across desktop, tablet and mobile.
MVP Development — Freelance MVP development for founders — full-stack product builds from zero to deployed, including auth, user roles, subscriptions, Stripe payments, and admin dashboards.
How engagements usually work
Fixed-scope project
You know what you need built.
A defined deliverable with a written scope, milestones, and a fixed price. Best for a first version, a specific feature, or an app store launch. Typically 4–8 weeks.
Weekly retainer
The roadmap is still moving.
A set number of days per week against a shifting backlog. Best when you are pre-product-market-fit and priorities change faster than a scope document survives.
Paid audit or spike
You are not sure it is viable yet.
A short, cheap engagement that answers one question — will this AI feature work on your real data, or what will break in this codebase first. You get a written answer you can act on with or without me.
What happens after you book
The call (15 min). You describe the problem. I ask what it has to get right and what it is allowed to get wrong. If I am not the right fit, I say so on the call.
A written scope (2–3 days). Deliverables, sequence, timeline, and price. Short enough to read in one sitting.
Kickoff. Repo, CI, preview deploys, and analytics on day one — so you are looking at working software in week one.
Weekly demos. A live deployed link every week, not a status report.
Handover. You own the repo and the deployment accounts, with written documentation. Bringing it in-house afterwards is a fine outcome.
Useful things to bring
None of this is required, but the call goes further if you have a rough sense of:
What the product does, and who it is for
Whether anything exists yet — repo, designs, a running app
What “done” looks like for this first phase
Your rough timeline and budget range
Any hard constraints — a stack you must stay on, a compliance requirement, a launch date
Prefer to look around first?
Reasonable. The case studies show what I have shipped, and the blog shows how I think.