7+ years building web applications, with a Software Engineering degree from COMSATS University Islamabad. Somewhere in the last few years the questions I enjoy most stopped being "how do I ship this feature" and became "what happens to this design under load, under concurrency, three years from now."
That shift shows up in how I build with Laravel: queued jobs and event listeners instead of synchronous side effects, tagged Redis caching with deliberate invalidation instead of guesswork, and policies and gates for authorization instead of ad-hoc checks scattered through controllers.
Based in Lahore, Pakistan, working with teams remotely to turn ambiguous requirements into systems that are still legible a year after everyone's forgotten why a decision was made.
Saad Ahsan Residency & Citizenship
Own the architecture of a multi-office CRM: geofenced login per office, role-based permissions instead of ad-hoc checks, and Facebook Lead Ads ingestion hardened against a real webhook race condition that was creating duplicate leads.
iSoft Technologies
Designed backend APIs around clear service boundaries, with cache invalidation and query optimization as first-class concerns rather than afterthoughts.
TeamsWork PK
Set architecture conventions for a cross-functional team, favoring event-driven workflows over tangled callbacks, and mentored engineers through the tradeoffs behind those decisions.
ZEREFLAB
Built web applications and Ethereum smart contracts, where every design decision had to be right before deployment. On-chain state gives you no runtime patches.
Multi-office CRM for a Caribbean citizenship-by-investment consultancy
Lead management, ticketing, and marketing automation across multiple offices, on a Laravel admin stack with 2,500+ commits since mid-2024.
Architecture
Facebook Lead Ads webhooks feed leads directly into the pipeline, including tracking down a real race condition that was creating duplicate leads under concurrent webhook delivery. Login is geofenced to each office’s location, and Caribbean CBI pricing-change campaigns run through an automated email/SMS sequencing engine, with queues and app performance monitored through Horizon and Pulse.
Internal system, not publicly viewable
AI-assisted citizenship-by-investment case processing
End-to-end case management for CBI applications, with native iOS and Android companion apps for staff and applicants.
Architecture
Uploaded documents (passports, bank statements, medical reports) run through a document-extraction pipeline that auto-fills specific government CBI forms: converting stated net worth and income to USD, cross-checking IBANs against the source document, and flagging low-confidence reads for staff review instead of guessing silently.
Immigration consultancy platform
Corporate site for residency and citizenship services, with multi-language, geo-targeted content across roughly 30 campaign pages.
Architecture
A self-built passport and visa-requirement ranking tool runs as its own plugin with a public API, separate from the marketing site’s page content. Campaign landing pages push leads out via webhook and generate PDFs automatically, rather than routing everything through one contact form.
Link-in-bio for the Saad Ahsan brand
Centralized link management and bio page, keeping every campaign’s outbound links in one place instead of scattered across social profiles.
Architecture
A separate Next.js app from the main marketing site, so link and campaign changes ship on their own release cycle instead of waiting on the CMS deploy.
Internal system, not publicly viewable
In-house sales platform with a built workflow-automation engine
Full CRM for AKSA Capital’s residency and investment programs: pipeline management, built-in calling, and a social inbox alongside lead capture.
Architecture
A Zapier-style workflow-automation engine (triggers, steps, field mappings) built from scratch rather than integrated from a third party, plus a phone-number-reveal-with-OTP gate that stops the lead list from being scraped in bulk.
Residency & investment marketing platform
Marketing site for AKSA Capital’s Portugal-focused residency-by-investment programs, in English and Arabic.
Architecture
Passport and country residency-requirement data is modeled as first-class content collections rather than hardcoded pages, so a new program or an additional language ships as content through the CMS, not as a code deploy.
Live link unconfirmed
Link-in-bio for AKSA Capital
Centralized link management for the AKSA Capital brand, with content and media pulled from a headless CMS.
Architecture
Built and iterated directly against Figma specs: spacing, embed sizing, and layout matched precisely rather than approximated, with media and OG content served from a headless CMS instead of hardcoded assets.
Legal practice management
Case management for a law firm’s practice, client intake through case resolution, built with subscription billing from the start.
Architecture
Cases are modeled through a structured taxonomy: type, stage, and status tracked separately and tied to specific courts and judges, rather than one freeform status field, so filtering and reporting stay accurate as case volume grows. Facebook Lead Ads feed client intake, and Stripe-backed subscription plans meter usage per feature instead of gating the whole product behind one price.
The frontend (Vue, Nuxt, React with Inertia, TypeScript throughout) is a client of the same architecture, not a separate concern with its own duplicated API layer. Earlier work also took me through Solidity and mainnet smart contract deployment, where the constraint of no runtime patches forces the same rigor applied earlier in the process.
Queued jobs and batching in Laravel, Celery for the same job in Python, so slow work never blocks the request.
Tagged Redis caching with deliberate invalidation instead of a blanket TTL.
Listeners and observers in Laravel, signals in Django, instead of side effects buried in controllers.
Policies and gates that stay correct as roles multiply, not ad-hoc checks scattered through controllers.
Laravel Echo and websockets over polling. Sanctum-backed APIs versioned from day one, because the frontend you ship first is rarely the only client.
If you're scaling a system, untangling one that's outgrown its architecture, or need a senior engineer who thinks in tradeoffs instead of tickets, I'd like to hear about it.
Lahore, PK · GMT+5
Available for remote work worldwide