Abdullah J.

Slow storefronts lose sales, and a site your team can't update without a developer costs you every week. I build Next.js ecommerce, SaaS and headless CMS products that fix both. Proof first: for Rahva Raamat, Estonia's largest bookstore (its flagship was named the world's best bookshop at the 2022 London Book Fair), I cut load time from ~4s to under 1.5s and reached a 98/100 Lighthouse score on a high-traffic Next.js ecommerce site. Top Rated Plus, 3,600+ hours on Upwork. What I build with Next.js: • Fast ecommerce that converts: custom Next.js storefronts and headless commerce, Core Web Vitals and page speed optimization, checkout optimization and conversion rate optimization (CRO), with analytics and A/B testing wired in (GA4, GTM, PostHog). Most recent: checkout optimization for a peptide ecommerce brand, delivered on time, rated 5 stars. • Multi-tenant SaaS: one Next.js codebase serving multiple brands (the NOTA platform), Supabase and PostgreSQL with row-level security for tenant isolation, and new clients onboarded through config instead of code. • Headless CMS your team can edit: headless WordPress + Next.js, GrapesJS page builders, and custom CMS builds (donations, booking forms, parent portals) that non-technical staff run themselves. Completed a 248-hour headless WordPress project here on Upwork, rated 5 stars. Also: AI chatbots and workflow automations built into the product, the same way I shipped them in production on Rahva Raamat. Common concerns, answered: • Timezone: I'm in UTC+5 with 4+ hours of daily US overlap, and most of the working day for UK and EU clients. • Who does the work: me. I lead the build personally and stay your single point of contact. • Getting stuck after launch: you get clean TypeScript code (App Router, server components), handover notes, and a CMS your team can use without me. Stack: Next.js, React, TypeScript, Node.js, NestJS, PostgreSQL, Supabase, Tailwind CSS, Vercel, headless WordPress, GrapesJS, OpenAI and Claude APIs. Send me the outcome you want (a faster store, a launch date, fewer developer requests) and I'll reply with a short plan for how I'd hit it.