Why I Stopped Taking Every Client Who Came My Way

Ammar Manzar

Why I Stopped Taking Every Client Who Came My Way

When I started my freelance journey, my answer to every single client inquiry was an automatic “yes.“

It didn’t matter what the project was, whether or not I was an expert in it, whether the client’s project seemed easy or difficult, or whether the budget was low or high none of that mattered to me. In the beginning, my only focus was volume. I would simply start the conversation and gather their requirements. That was my workflow at the time.

Why I Stopped Taking Every Client Who Came My Way

When I started, I believed that if I worked this way, I would secure a massive volume of projects. I thought it would help me gain rapid experience while bringing in consistent cash flow. For a brief period, the response was positive, and I was satisfied with the momentum.

Then, the system stopped working. And the way it broke is a lesson every developer and freelancer needs to hear before repeating the same mistakes.

The Project I Should Have Never Said Yes To

One day, a client approached me with a graphic design and layout project. They explained the requirements, we agreed on the pricing, and I started working on it.

However, there was a major structural flaw I didn’t recognize at the time. The client hadn’t clearly defined the full scope of the project, and I failed to ask for detailed requirements. Because of that, I didn’t fully understand how extensive the work actually was. As development progressed, the project turned out to be far more complex than our initial agreement. It required excessive revisions, additional design elements, and significantly more time than estimated.

By the end, the amount of labor I had invested was completely out of proportion to what I was being paid. I finished it to honor my commitments, but the whole time I was thinking: this is not worth it. I’m not making money here. I’m losing time that could have gone toward core development.

When it was done, I handed it over, collected the payment, and told myself: this is the last time I let this happen.

That project was a turning point. Not because the final delivery was a disaster the client was fine but because it made me realize I had zero operational system for deciding what work to accept and what to reject. I was just saying yes to everything and hoping it worked out.

When I Tried to Work Outside My Area

Around the same time, I was taking projects across different sectors not just web development, which was where my actual core skills were strongest. If something came my way and it seemed remotely doable, I’d take it.

A few times, that strategy backfired badly.

There were projects where I realized midway through that I genuinely wasn’t the right person for the job. I tried my best, but the output wasn’t what the client deserved. I lost clients over it. More importantly, I damaged professional trust that would have been very hard to rebuild.

People around me kept offering the same advice: just get the money, just deliver something, the client doesn’t need to know you’re figuring it out as you go. That advice sounds practical. In reality, it is how you quietly destroy your market reputation.

After those experiences, I made a firm decision: I would only take projects where I could genuinely deliver elite-tier work. If something was outside my expertise, I’d refer the client elsewhere rather than take their money and underdeliver. That felt like the right operational standard for both parties.

The Client I Had to Walk Away From Mid-Project

The hardest situation I faced was with a client from an organization that required a full website rebuild. Their legacy site was running on an outdated version of WordPress that couldn’t even be updated securely anymore. The project had a large scope and real technical complexity, so I priced it accordingly. They agreed to the terms without hesitation.

But once development started, a core issue surfaced: they didn’t actually want to let me work.

I had placed an under-construction page on the front end so I could build the architecture without constant interruptions. They demanded it live immediately so they could monitor every step. The moment I made it visible, the interference started. Every element, every decision, every micro-change became a battleground of constant oversight. My concentration was completely broken, and project velocity dropped dramatically.

Roughly 45% through the project, I had to make a hard call. I told them directly that I couldn’t continue. Their management style made it impossible to produce stable work. I asked them to pay me strictly for the portion I had completed and to find someone else for the remainder.

Beyond the daily interference, the root cause was that they had never provided their requirements in writing. Everything had been verbal. That made scope management impossible and disagreements inevitable.

That conversation was uncomfortable. But walking away was the correct decision. I knew that if I kept going, the final result would reflect badly on my technical standards regardless of how hard I tried, because the operating conditions made good engineering impossible.

The Client Who Scammed Me: What I Learned About Trust

The Client Who Scammed Me And What I Learned About Trust

I need to mention this incident because it fundamentally changed how I operate.

A client came to me through a close friend’s recommendation. Because of that personal connection, I treated the engagement differently than normal. I didn’t ask my standard vetting questions. I didn’t get clear written requirements. I even skipped taking an advance deposit because he came through someone I trusted.

He scammed me. He took the completed work, refused to pay, and disappeared.

The lesson wasn’t to stop trusting people. The lesson was that a referral never replaces a strict business process. A client coming through a personal contact still needs to go through the exact same evaluation pipeline as any other lead: clear requirements, locked budget, timeline agreements, and a formal written contract. Good people can still have poor intent, or simply turn out to be toxic clients. The source of the introduction doesn’t change operational risk.

Now, when a referred client approaches me, they go through the exact same verification process as everyone else. No shortcuts, no assumed trust, no exceptions.

How I Evaluate Every Project Now

Before accepting any project today, every lead must pass a strict set of criteria:

  1. Are the requirements clear? If a client can’t explain what they need in specific terms, or if they change their description constantly during discussions, it’s a red flag that will compound once development begins.

  2. Is the budget realistic? I take time to explain the value of what I deliver and why I charge my rates. If the budget is genuinely too low, I explore breaking the project into phases. If that fails, I pass. Undercharging leads to operational resentment, rushed code, and a substandard deliverable.

  3. How is their communication? A client who is clear, responsive, and respectful during initial discovery will generally remain professional throughout the project lifecycle. Evasive or chaotic communication upfront predicts a worse experience post-contract.

  4. Is the timeline reasonable? Unrealistic deadlines create panic. Panic creates rushed code, and rushed code breaks production. I always confirm that deadlines are viable before committing.

  5. Does it match my core expertise? If the answer is no, I refer the client to someone better suited. I do not experiment at the client’s expense.

Red Flags I Watch For in Early Conversations

Experience has made me quick at identifying indicators of a dysfunctional project:

  • A client who cannot define their requirements or shifts parameters constantly is scope creep waiting to happen. I now enforce direct technical discovery early.

  • A budget that completely disconnects from the scope is a warning sign, especially when the client refuses to discuss adjustments. Someone wanting enterprise work for minimal capital is signaling how the entire execution phase will unfold.

  • Clients who demand everything be built before issuing any financial commitment present an unnecessary risk. Advance deposit policies exist to filter out operational friction.

  • Clients who micro-manage every micro-step rather than trusting the execution process reliably lead to stalled velocity, exhausted patience, and unsatisfactory outcomes.

What Happened After I Became More Selective

What Happened After I Became More Selective

The immediate result was a short-term dip in income. When you start turning down incoming projects that you previously would have accepted out of desperation, workflow decreases temporarily. That transition was uncomfortable, especially when financial stability wasn’t fully locked in.

However, the secondary effect was transformative: the clients I did retain were vastly superior.

Better clients meant clear communication, reasonable expectations, fewer revision cycles, and deep mutual respect for my time and process. Projects became genuinely engaging to engineer.

Those clients returned for repeat operations. They referred their peers. They understood that the digital assets I built carried real market value. The technical quality of my work improved because I finally had the space to focus properly instead of constantly firefighting chaotic situations.

Looking back, working with fewer but higher-caliber clients has produced vastly superior income, technical quality, and peace of mind than accepting every incoming lead ever did.

Final Thoughts

Operating without an initial mentor means every lesson must be learned through real projects, real mistakes, and real financial consequences.

Being selective is not arrogance. It is core professionalism. Knowing your technical boundaries, being honest about your limits, and protecting your operational time makes you better at the work you actually commit to.

The goal is not to manage as many clients as possible. The goal is to do great work, consistently, for clients who value it. That combination builds a sustainable agency. Taking every project from every client regardless of how they treat you or whether it fits your core stack only builds burnout.

You don’t have to learn those boundaries the hard way. I already did.

If you are a freelancer or agency founder trying to figure out when to start being selective, the answer is simple: earlier than you think. Start by asking better questions in your first client conversations, and pay attention to what the answers actually reveal about your future operations.

 

About the Ammar Manzar

I'm Ammar Manzar software engineer, founder of CubeCod Technologies, and someone who has spent 5+ years building websites, freelancing, and learning digital business the hard way. I only write about what I have personally built, tested, or used. Nothing else.

Leave a Comment