Nawabshah to Karachi. Computers were never tools — they were puzzles. The question that started all of it: could I build one myself?
Most bugs in business systems are UX decisions, not code errors. So the work starts before the editor is open.
I focus on how teams actually work, so the software supports real operations rather than fighting them. Most bugs in business systems are UX decisions, not code errors.
Data models, permissions and growth paths get mapped on paper first. The decisions that matter most are made in the first hour, not the last sprint.
Backups before every deploy, deadline risks flagged a week early, and ownership when something breaks. Steady communication is part of the build.
Software agency — SaaS & business systems. Building and shipping production SaaS platforms and business systems for real estate and operations clients. Own full-stack architecture and delivery — from data modelling and API design through to frontend implementation and cloud deployment.
Award-winning global IT firm (201–500 people) — clients across North America, Europe & Asia. Joined as an intern and converted to a full-time MERN Stack Developer after 6 months — based on project output, not tenure. Shipped production work on a live e-commerce platform and multiple client projects across the full stack.
Research division of HBL — Pakistan's largest commercial bank · Conducted at GIKI. Short-term research internship at GIKI within the applied research arm of Pakistan's largest commercial bank. Focused on blockchain integration patterns in financial systems and contributed to prototype development alongside domain researchers and engineers.
Both had to be reasoned out rather than looked up. That is the part worth showing.
The first background job system I architected from scratch. Scheduling, custom intervals, per-user SMTP configs, retry logic and failure tracking — with one hard constraint: never send the same person the same campaign twice.
Allocation rules cascading from category to subcategory to individual product, across user groups and individuals. Deducting one person's limit could not affect anyone else's. No good tutorials exist for this — the logic came from first principles.
Building scalable SaaS platforms and admin dashboards
Designing backend architecture for business workflows
Turning product and operational requirements into production-ready systems
Balancing technical depth with clear communication for clients and teams
Clarify business goals, users, workflows, and success signals before architecture starts taking shape.
Map roles, permissions, data flow, integrations, and operational constraints so the product can grow cleanly.
Build in small, visible milestones that make collaboration easier for both technical and non-technical stakeholders.
Ship with a stable baseline, monitor usage, then refine the product around real feedback and edge cases.
Most developers build forthe ticket in front of them.I build for the systemthat ticket belongs to.
I also play chess. Both disciplines share the same logic — read the whole board before you move, not just the piece in front of you.
Three years out I want to be running my own software house or shipping my own SaaS. Every production system I build now is practice for that — not just code that ships, but decisions that still hold up six months later.
The things that come up in almost every first conversation — answered here so the first message can be about your project instead.
Bring the rough idea, the existing workflow, or the messy process. I’ll help shape it into something worth building — and worth maintaining after launch.
Book a Strategy Call