Skip to content
All articles
Founder

From a ₨25,000 Salary to Founding DanixSoft — My Story

May 28, 2026 7 min readBy Daniyal Alam
From a ₨25,000 Salary to Founding DanixSoft — My Story — article by Daniyal Alam

title: "From a ₨25,000 Salary to Founding DanixSoft — My Story" description: "How I went from earning ₨25,000 a month as a junior developer to leading a team of 15+ engineers and building DanixSoft into a real software studio." publishDate: 2026-06-24 tags: ["founder story", "Pakistan tech", "DanixSoft", "software development"]

I remember sitting at my desk in 2023, staring at a salary slip that read ₨25,000, and telling myself that this was just the beginning — not the ceiling. I was Daniyal Alam, a developer with more ambition than money, more hunger than experience. That gap between where I was and where I wanted to be is exactly what built everything that came after.

The ₨25,000 Starting Point

Twenty-five thousand rupees a month. For context, that barely covers rent in Lahore, let alone savings, upskilling resources, or the occasional coffee to get through a late night of code review. Most people look at a number like that and think about what they can't afford. I looked at it and started making a list of what I needed to learn.

The job itself was fine — typical junior developer work, ticket-driven, incremental, mostly frontend fixes and CRUD operations. But I knew the market was moving fast. AI was reshaping what software even looked like. MERN stacks were becoming the baseline, not the differentiator. And Python with frameworks like Django and FastAPI was opening entire categories of backend work that weren't accessible a few years earlier. I had a choice: wait for promotions that might never come, or build the skills that would make the promotions irrelevant.

I chose the second option.

Running Two Tracks at Once

For a significant stretch of time, I was working two jobs simultaneously. Not in the abstract hustle-culture sense where people say "two jobs" and mean one full-time role plus occasional freelancing. I mean two real commitments — deliverables, standups, client expectations — being managed in the same waking hours.

It was not glamorous. My sleep schedule was chaotic. My social life basically disappeared. I ate lunch while reading documentation and answered messages before I was properly awake in the morning. But here is what that period taught me that I could not have learned any other way: you find out very quickly what you are actually capable of when there is no slack in the system.

I was shipping features at a day job while simultaneously onboarding freelance clients who needed mobile apps in React Native or automation scripts in Python. Every new project was a forced upskilling event. You cannot fake your way through a FastAPI microservice when a client is waiting on it. You either build the thing or you don't.

That pressure became a teacher. A ruthless one, but a good one.

The Skills That Changed the Trajectory

I want to be specific here because vague advice about "keep learning" helps nobody.

The skills that actually moved the needle for me were:

  • Full-stack ownership — being able to take a product from database schema to deployed frontend without handing it off. Clients trust you differently when you can own the whole thing.
  • React Native — mobile was where a lot of the practical budgets were going. Learning it opened a category of projects I couldn't touch before.
  • AI and LLM integration — this one accelerated everything. When I started working seriously with large language models and building AI-powered features into products, the complexity of what I could offer to clients increased dramatically, and so did the rates.
  • Django and FastAPI — Python for backend work made me genuinely versatile. A client in one industry might need a Django monolith with a proper admin panel; another needs a FastAPI service that handles async jobs and talks to an ML model. Knowing both meant I stopped turning down work.

None of these happened in a classroom. Most of it happened at midnight, with documentation open in one tab and a half-working prototype in another.

Turning the Grind Into Something Bigger

At some point, the freelance work grew past what I could handle alone. I was turning down projects not because I wasn't qualified, but because I didn't have the hours. That is when the question shifted from "how do I do more work" to "how do I build something that can do more work."

That shift in thinking is where DanixSoft came from. Not a pitch deck moment, not a lightbulb epiphany — just a practical recognition that the demand was real, the skills were there, and the only missing piece was structure.

I turned that freelance operation into DanixSoft, a software development studio based in Lahore. Building a company, even a small one, is a completely different skill set from being a good developer. You have to learn how to hire people you can trust, how to scope projects so they don't collapse mid-delivery, how to have honest conversations with clients when something is going sideways, and how to maintain quality when you are not personally writing every line of code.

There were bad hires. There were projects that ran over budget. There were clients who needed more hand-holding than the contract implied. I made those mistakes, absorbed them, and adjusted.

Where DanixSoft Stands Now

Today DanixSoft is a team of 15+ engineers. We have served 50+ clients and shipped more than 80 projects across industries ranging from fintech to edtech to SaaS platforms. Our core stack — MERN, Python with Django and FastAPI, React Native, and AI/LLM integrations — reflects the same practical decisions I made early on about where real demand lives.

The work is genuinely interesting. We are building products that automate real workflows, not just CRUD apps with a fresh coat of paint. The AI component in particular has become a serious part of what we offer — teams come to us specifically because they want to embed intelligence into their products and don't know where to start.

Lahore is an underrated place to build a software company. The talent pool is serious, the appetite for good engineering culture is real, and the cost structure allows you to compete on quality rather than racing to the bottom on price. I am proud that DanixSoft is a Lahore company and I have no interest in pretending otherwise.

What I'd Tell Other Developers in Pakistan

If you are a developer in Pakistan right now sitting on a salary that feels like a ceiling, here is what I actually believe, not just what sounds good:

Do not wait for permission to be capable. The projects that teach you the most are the ones slightly outside your comfort zone. Take them. Figure it out. Charge accordingly once you have.

Two income streams early on is not a grind — it is a strategy. It compounds your exposure to different types of problems and clients faster than any single job can. The chaos is temporary; the skills stay.

Learn the AI layer. I don't care what your primary stack is. Developers who can integrate LLMs into real products are going to be the ones building the next decade of software. This is not optional anymore.

Build relationships, not just a portfolio. Most of DanixSoft's early clients came from referrals. Doing good work and treating people well is the most durable business development strategy that exists.

Pakistan is not a constraint. Remote work has made geography mostly irrelevant for software. Your location doesn't limit your clients; your skills do.

What I'd Tell My Younger Self

Stop calculating how long it will take. You don't know, and the estimate is going to be wrong anyway — probably in a good direction, but wrong. Just stay consistent.

The ₨25,000 salary was not an insult. It was data: data about where the market valued me at that moment, which told me exactly what I needed to change. Daniyal Alam, the person writing this, is not a different person from the one who stared at that slip in 2023. He just kept showing up, kept building, and refused to let a number on a piece of paper be the final word.

The rest is still being written — and I wouldn't have it any other way.