Code, Clients and Coffee: My Freelancing Story.

Over the last year, I've taken the plunge and gone freelance, and it's been as tough as it has been rewarding. This blog is a copy of an interview I conducted with ChatGPT, in which I gave insights into my experience as a freelancer. I explained to ChatGPT that I was blogging about my experience, and it thought it would be better if we were to tell this tale as an interview. In this discussion, we've touched on the highs and lows, what I have learned, and how this journey has made me the developer that I am today.

I started freelancing in October 2024, when I registered myself officially on Freelancer.com. I was pursuing an internship then and was interested in challenging my real abilities. I felt that I could do some more strenuous and fulfilling projects, and freelancing appeared to be the ideal chance to accomplish this. Not only was the aim to earn, but to challenge myself and demonstrate to myself that I was capable of dealing with the sophistication and accountability of client-initiated development.

I began by consistently bidding on projects—on Freelancer, these applications are known as "bids." I would make it a point to bid daily, looking especially for projects involving niche frameworks like Ionic React, which not many developers specialize in. This strategy paid off when, after about a month, I landed my first project from a Canadian client. It was an Ionic React app. Because the project had fewer bids and aligned with my niche skills, I was able to deliver it successfully and quickly. That first delivery—accompanied by a happy client and a glowing review—opened the door to future work and gave me a massive confidence boost.

Initially, I tried balancing my internship work with freelance work but quickly discovered it could not be done. The volume of work was too great, especially after freelance work started arriving on a regular basis. I eventually made the hard decision to terminate my first internship in December of 2024 and another one in January of 2025.

It was a real burden to leave those internships and, more importantly, the people I worked with. Strong relationships were built—especially at my first company, where I felt deeply connected to the team. But sometimes, moving forward requires taking hard steps. Looking back now, I believe it was a necessary part of the journey, almost as if it was all planned to happen that way. Where I am standing today wouldn’t have been possible without those steps. I still carry immense gratitude for those two companies—fittlyf.com and Bio Clutch (which was then known as Blastoserve Scientific)—as they were the ones who took a chance on me and gave me my first real exposure to working on live projects.

Over time, I worked on a wide range of projects, including bombaytaxico.com, fittlyf.com, abtestinghub.com, 40god.com, bluedive.in, thebrokershub.in, tiktikglobal.com, and many others. Some projects were mobile applications, while others involved proof-of-concept builds, bug fixes, and full-fledged platform development. My core tech stack included React, Django, Next.js, and Express.js. In addition to coding projects, I also handled CMS-based tasks involving WordPress, Odoo, and Wix for simpler needs.

The difficulty level varied greatly. E-commerce platforms were relatively easier to build, whereas certain customized applications posed significant challenges. However, these projects allowed me to grow technically and gain a deeper understanding of managing client expectations.

Interestingly, even my physical workspace evolved along with my journey. My system that once had just one screen eventually expanded to two screens, and then three—and maybe even more in the future. Each additional screen mirrored my increasing workload, multitasking capabilities, and the professional scale of my freelancing operations.

Freelancing taught me one of life’s most valuable lessons: time is money. Every second wasted is an opportunity lost. But it also taught me the importance of not sacrificing my health and sleep for more work and income. Burnout is real, and long-term success is only possible with a healthy mind and body.

I learned how essential it is to estimate project timelines accurately. A single misjudgment can lead to overlapping deadlines and stress. To manage better, I now set fixed hours for each project, allowing myself enough time for focused work without burnout. Managing multiple projects simultaneously is an art that requires discipline, planning, and clarity.

Another important lesson was the power of selling. Convincing a client that you can meet—or exceed—their expectations is a skill in itself. Good communication, confidence, and a clear project roadmap are all essential. I gradually became better at explaining my capabilities, showing past work, and ensuring clients felt secure in trusting me with their projects.

In the early days, I undercharged because I lacked experience, didn’t know how to price correctly, and felt underconfident. But with time and successful deliveries, I began charging fair, competitive rates that matched my skills and the value I brought to the table.

One of the most challenging projects I undertook was for a German client—a football tournament management and streaming software called Der-Turniermanager. The project required intricate logic to manage tournament structures, match details, and live streaming features. What made it particularly difficult was the language barrier; the client struggled with English, which made requirement gathering a tough task.

We originally planned to complete the project within two months. However, communication gaps led to scope creep and missed timelines. We had to trim features and planned to roll them out in a later iteration. But due to simultaneous college pressure and other project obligations, I could no longer dedicate focused energy to this already-complicated project. The codebase had become messy from hasty patchwork aimed at meeting deadlines.

Eventually, the client and I mutually agreed to end the project. I was paid fairly for the completed portion, but it was still a tough experience. It was the first time I had to drop a project due to timeline issues. That failure taught me the importance of crystal-clear requirements, realistic timelines, and maintaining clean code throughout the lifecycle. These lessons made me a stronger developer and better project planner.

Each project I undertook resulted in favorable comments, higher revenue, and new projects. With time, I not only developed technically but also as an individual. I became a better communicator, learned discipline, and perfected time management. I grew stronger and better at managing disappointments.

When 2025 rolled in, I deliberately stepped back from freelancing and prioritized studies. It wasn't a decision I wanted to make, particularly after gaining so much traction—but I knew I had to. I needed to take a break, take stock, and put some time into the theoretical basis behind everything I do.

But make no mistake: this is not the end of my freelancing chapter—just an intermission. A stronger, smarter comeback is already on the horizon. With sharper skills, deeper knowledge, and a renewed sense of purpose, I’ll be returning to the freelance world not just as a developer, but as a force to be reckoned with.

This experience has taught me more than I can possibly enumerate. I've learned to think like a businessperson, deliver like a developer, and communicate like a leader—skills that any technology company would find valuable. And when I come back, it will be with a refined vision, a stronger foundation, and a renewed passion to leave an imprint on the world of tech.