Service
I build and ship production Next.js applications — App Router, server components, ISR, and the performance work that keeps them fast after launch.
Most teams that come to me for Next.js work want one of three things: a product built from an empty repo, an existing React app moved onto the App Router without a rewrite, or a site that already works but is slow enough to be losing users. I do all three, and I do them as the person writing the code — not as a layer between you and an offshore team.
Every engagement ships to a real URL. I set up the repo, the CI, the preview deploys, and the analytics on day one, so you are looking at working software in the first week rather than a design document. You keep the repo and the deployment account; there is no lock-in to me or to any agency tooling.
The App Router gives you a real choice about where each piece of your app runs, and most performance problems I get called in for come from that choice being made by accident. A dashboard that renders per-request when it could be static. A marketing page shipping 400KB of client JavaScript because one component needed a hover state. A data fetch that waterfalls three levels deep because it was written the way a client-side app would do it.
So the first thing I do on any Next.js codebase is map the rendering boundaries: what is static, what is revalidated, what is per-request, and what genuinely needs to be a client component. That map usually explains the performance numbers on its own, and fixing it is cheaper than the caching layer people reach for first.
On new builds I default to static-plus-revalidation and only move things to per-request rendering when the data actually demands it. It is easier to make a static page dynamic later than to claw back a codebase where every route is dynamic by default.
This site is a Next.js App Router build — statically generated across 270+ routes with generated per-post Open Graph images. Beyond it: HireOS runs Next.js 16 and React 19 against Cloudflare Workers for edge AI inference; Wavel serves a 10,000-entry searchable directory with ISR on the category pages and sub-200ms search; CodexGenAI is a full AI content studio built solo on Next.js and Supabase in six weeks.
I work remote-first from Lahore and overlap with US, UK, Canadian, and Australian teams. Engagements are usually either a fixed-scope project with a defined deliverable, or a weekly retainer when the roadmap is still moving. I am happy to start with a small paid scoping piece so you can see how I work before committing to the full build.
You get a repo you can read, commits that explain themselves, and a written handover at the end. If you would rather bring the work in-house afterwards, that is a fine outcome and I will document it accordingly.
It depends on scope, so I price per engagement rather than per hour on a rate card. Engagements are usually either a fixed-scope project with a defined deliverable, or a weekly retainer when the roadmap is still moving. If you would rather not commit up front, I am happy to start with a small paid scoping piece so you can see how I work first.
A focused production build is typically four to eight weeks from kickoff to a deployed, working app. The variable is rarely the frontend — it is how much of the backend, data model, and third-party integration work is already settled when we start.
Both. A good share of my work is joining an existing Next.js or React codebase — migrating from Pages Router to App Router, fixing Core Web Vitals, or untangling rendering decisions that made sense at prototype stage and stopped scaling. I read the repo before proposing anything.
I work remote-first from Lahore (PKT, UTC+5) and overlap daily with US, UK, Canadian, and Australian teams. In practice that means real overlap hours for standups and reviews, not async-only handoffs.
Yes, entirely. You get a repo you can read, commits that explain themselves, and a written handover at the end. You keep the repo and the deployment account — there is no lock-in to me or to any agency tooling. If you want to bring the work in-house afterwards, that is a fine outcome and I document it accordingly.
An AI resume-optimization platform — tailors resumes to target roles, renders clean PDFs, and ships with a Chrome extension.
Read the case study →An AI tools and agent marketplace — a searchable directory of 10,000+ tools with categories, rankings, and a live leaderboard. Built for scale and discovery.
Read the case study →An AI content studio for creators and teams: generate multi-slide carousels, schedule posts across platforms, and track engagement with sentiment analysis.
Read the case study →A 15-minute call is usually enough to scope it. If I am not the right fit, I will tell you on the call.