Capabilities
What I build*
Six kinds of work, and the tools behind each one. If your project sits across several of these, that is normal, and it is the reason one engineer owning the whole thing tends to go faster than a team splitting it.
Areas
6
Shipped
8 case studies
Rating
5.0 from 148
Based in
Islamabad, Pakistan
Full stack product build
One person owning the database, the API, the interface and the deploy. Fewer handoffs, fewer gaps, and a codebase that stays coherent because one head held the whole shape of it.
AI systems that do real work
Document parsing, retrieval, agents that take actions, and drafting tools that write in a client voice. Built with guardrails, fallbacks and cost control, because a demo and a product are not the same thing.
Data pipelines and scraping
Collection systems that keep running when a site changes its markup, blocks a request or throttles a range. Queued, retried, monitored and stored in a shape you can actually query later.
SaaS platforms end to end
Auth, roles, multi tenancy, subscription tiers, invoices, admin panels and the boring edges nobody demos. This is where most products stall and where I have shipped the most.
Interfaces with motion
Front ends that feel considered. Real typography, real spacing, scroll and pointer motion that carries meaning instead of decorating the page. Accessible and quick on a mid range phone.
Performance and search
Rendering strategy, Core Web Vitals, structured data and the migration work that makes a site legible to crawlers. I have taken client sites from client side rendering to server rendering and watched the numbers move.
01
Understand the problem
A short call, then a written scope in plain language. I would rather find the hard part in week one than in week six.
02
Design the system
Data model, service boundaries, third party pieces and the parts most likely to break. You see the architecture before any code exists.
03
Build in the open
Working builds you can click through, pushed regularly. No long silence followed by a surprise. Feedback lands while it is still cheap to act on.
04
Hand it over properly
Deployed, documented and explained. You get a repository your next developer can read, not a black box that only I understand.
A lot of what comes through the door is one specific job: an old WordPress site that has become slow and expensive to maintain.
I move those onto Next.js without losing the rankings they already have, and when the team wants to keep writing in WordPress I wire it up as a headless CMS so the editor never changes. That one has its own page with timelines and a written scope.
Open to new work
Tell me what you are trying to build.
If I am the right person you will get a scope and a number in writing. If I am not, I will say so and point you somewhere better.