BS Economist · Digital Builder · Research Analyst
There are two kinds of people who see something broken.
The first kind notes it, reports it, and moves on. The second kind goes home that evening, sits down, and builds the fix.
I found out which kind I am during my second week as an office clerk.
Eight people. One printer. One notebook to track who printed what. A reasonable system — until arguments started. Someone couldn't remember printing forty pages three weeks ago. Someone thought I was overcharging. I had all the data. They had none. A paper notebook wasn't going to fix that.
Two weeks later, PrintDesk was live. Each person had their own login, their own dashboard, their own balance visible on their phone. My manager saw it and said: "Positive step. Keep it simple." I've kept those words since.
I'm not a software engineer. I studied Economics at a government college in Toba Tek Singh, not because it was a calculated career move, but because it was what I had access to, and something about it genuinely caught. The way markets breathe. The way policy ripples into real lives. The way data, read correctly, tells you what's actually happening beneath the surface.
What I've learned — through the tools I've built, the research I've run, the roles I've taken, is that I don't do well with static. I need problems that evolve, questions that compound, work where showing up with a better idea is encouraged rather than just tolerated.
I'm twenty-three. From a small city. I built working software in a government office in my spare time, without being asked.
I'm just getting started.
Real tools. Real problems. Built in my own time, without being asked.
Eight people. One printer. One ledger. I was the only one holding all the data, and that made me the source of every dispute. So I replaced the notebook with a live, multi-user web application. Each person got their own login, their own dashboard, real-time balance visibility, and a monthly billing system. Arguments stopped. Workflow accelerated.
Staff were recording policy data by hand, in registers. I manually entered hundreds of records into Excel, then watched myself type the same five-digit prefix over and over. I built Policy Record to eliminate exactly that: smart auto-fill defaults, search by policy number, year and month filters, and print-ready formatted outputs. Hours became minutes.
"Have a broken process? I build tools for that."
I design and deploy custom web tools tailored to your workflow — fast, simple, and built to actually get used. Let's talk →
Hands-on roles across government administration, remote logistics, and digital operations.
🏅 Class Representative (CR) — Primary liaison between Economics faculty and 40+ students for two consecutive years; managed schedules, exam coordination, and official communications.
Pakistani firms that invest in R&D don't automatically innovate. I spent a year trying to understand why.
The answer turned out to be less about money and more about people.
R&D investment alone yields statistically insignificant innovation outcomes. Returns become significant only when moderated by employee training (β = 0.130, p < 0.01) and process upgrades (β = 0.230, p < 0.01) human capital and operational readiness are co-requisites, not optional additions.
Thoughts on economics, building digital tools, and how things actually work.
Open to corporate roles, banking, research, freelance projects, and building custom tools.