How to Get Fewer Freelance Clients
Tags: freelancing, consulting
Published: 2018-09-24 17:30:08

---
title: How to Get Fewer Freelance Clients
published: true
tags: freelancing, consulting
canonical_url: https://raddevon.com/articles/how-to-get-fewer-freelance-clients/
cover_image: https://thepracticaldev.s3.amazonaws.com/i/yv9dtvt9ztk4t2qx5pih.jpg
---
					
**Your first job as a freelance web developer is to stop people from hiring you.** That’s right. It’s _not_ to convert every lead into a client. Your freelance services aren’t like toilet paper or some other commodity. You don’t just want to sell them to as many people as possible. You want to sell your services to only **the right people**, but how do you know if the lead in front of you is one of the right people?

## Why Kill Deals?
				
Disqualifying clients is good for you _and_ for your clients. To understand why, let’s imagine what <b>an ideal project</b> looks like. Here are the 10 pieces of an ideal project:
<ol>
<li>A prospect comes to you with <b>a pressing business need</b>.</li>
<li>They have a <b>clear idea of the result</b> they want.</li>
<li>Timing is important for the project, and <b>the right time is now</b>.</li>
<li>Solving this problem will either <b>make or save them lots of money</b>.</li>
<li>
<b>You understand</b> the problem.</li>
<li>
<b>You are capable</b> of solving the problem.</li>
<li>
<b>The client will pay</b> what you ask.</li>
<li>You <b>build</b> the solution.</li>
<li>The client <b>pays</b>.</li>
<li>The solution <b>delivers the desired result</b>.</li>
</ol>

As a freelance web developer, you’re in a choice position. <b>There’s far more work to be done than you could ever do.</b> That means, you don’t need to capture everything. You need to capture only these ideal projects. Here’s how you can control for this <i>before</i> the project begins.

## What makes an Ideal client?

Since you only want to take on ideal clients, you’ll need <b>some criteria</b> to help you determine which jobs to take. You’ll want to customize these to your own freelance practice, but here are a few to get you started.

### Is the problem real?

<i>“I need a new web site.”</i><br>Not a problem.<br><i>“I need my web site to work on mobile.”</i><br>Not a problem.<br><i>“60% of the visitors to my online store use a mobile devices, but my site isn’t mobile responsive. I need a new responsive web site so I can convert those visitors at a higher rate.”</i><br>Bingo.</p>
<p>Client conversations often start out with something like the first two examples. We can sometimes steer them to something more like the last example. This is critical to building an ideal project. Without <b>a real problem</b> (the first piece of an ideal project), we don’t know if this project is <b>timely</b> (the third piece), and we can’t <a href="/articles/the-most-valuable-skill-for-web-developers/">figure out <b>a real solution</b></a> (the second piece). Without understanding the desired result, we can’t know if the solution we build <b>actually works</b> (the last piece).</p>
<p>Businesses spend money either to make <i>more</i> money or to spend <i>less </i>money over the long-term. They have obstacles preventing them from making more or spending less, and the budget for a solution is intended to overcome those obstacles. If you’re a trusted problem solver, they may come to you with the problems first. If you’re seen as a web developer, they’re more likely to come to you with a solution they’ve worked out in their head, asking you to simply build it.</p>
<p>Even if they <i>don’t</i> tell you what their ultimate goal is (i.e. the pressing business need), <b>they’re still going to evaluate success in the project against whatever metric they have in their head</b>. You need to get that problem out into the open so that you can</p>
<ul>
<li>gauge if the proposed solution will solve it</li>
<li>determine if the solution is feasible within the budget</li>
<li>steer the client in the right direction if either of the first two is a problem</li>
<li>focus your time and energy on making sure that problem is solved</li>
</ul>

###Is the problem Valuable?

<p>If the problem isn’t valuable (the fourth piece of an ideal project), you’re no longer an asset; <b>you’re a liability</b>. You’re someone the business feels it <i>has</i> to hire for one reason or another.</p>
<p>There is no “home run” because the benefits to the business’s bottom line are minimal. That’s going to affect <b>how much they’re willing to pay you</b> (the seventh piece) and <b>how much they respect you</b>. That’s going to affect how they perceive the outcome. It’s going to affect <b>whether they decide to come to you for more work</b> in the future.</p>
<p>Besides that, if you’re pricing your projects based on the value, <b>a project with <i>no</i> clear value won’t fit into that paradigm</b>. If the project means $0 to the company, what can you charge them for it? Even if it’s worth $500/year to them, what can <i>you</i> charge that would allow you to earn a decent rate? It’s just not enough room to work with.</p>
<p><i>If you’re new to value-based pricing, I highly recommend a free ebook called <a href="https://www.freshbooks.com/blog/breakingthetimebarrier">Breaking the Time Barrier</a>. It’s a great introduction for people who are used to billing for time.</i></p>

###Can I help with this (and will I enjoy it)?

<p>If you don’t have the particular skill you need to help the prospective client, it’s <b>OK to pass on the work</b>. This will actually earn you <b>more trust</b> with the client, particularly if you can act as a resource and <b>help them find someone to solve the problem</b>. If you <i>do</i> refer the work to someone else, when <i>that</i> person comes upon work that’s in <i>your</i> wheelhouse, they’ll want to return the favor.</p>
<p>This doesn’t mean you shouldn’t <b>take on jobs that will require you to bring on other people</b> with different skillsets. That’s fine. If someone wants to build a marketing site, and you plan to code it yourself while hiring a designer and a copywriter, go for it!</p>
<p>This also doesn’t mean you shouldn’t <b>stretch yourself</b> when you take on new work. Maybe you find a <a href="https://vuejs.org/">Vue</a> gig. You’re not familiar with Vue, but it’s otherwise similar to other work you’ve done. Do it! You’ll learn Vue as you go.</p>
<p>I’d simply caution you not to take every single job just because it landed in your lap or because it has a big budget attached to it. If you personally have no skills to offer toward a solution, it’s not the right job. Even if you’re overseeing the work, you’re less likely to oversee a success than if you’re working on a project where you yourself can deliver a great solution (the sixth piece of an ideal project).</p>
<p>Optional criteria: make sure the work is something you <i>want</i> to do with some<i>one</i> you want to do it for. The happier <i>you</i> are, the greater the chance for success and the greater the chance the client will tell their friends and come back.</p>

### Will this client pay?

<p>Nothing is more demoralizing than doing work you don’t get paid for. Companies are making money on the back of your work. You should too. So, how can you tell if your client is actually going to pay (the ninth piece of an ideal project)?</p>
<p>The best proxy for whether a client will pay is to <b>have them pay something up-front</b>. You can ask for the entire payment up-front, or you can get a partial payment with the remainder coming due later. Make sure the pre-payment is more than a token amount. This will give you some operating capital while you complete the job, but <b>it also shows the client is serious about the work</b>.</p>
<p>The next best way to tell they’re going to pay is to <b>have them sign a contract</b>. Let them know you mean business and spell out the expectations on both sides, compensation being one of them.</p>
<p>If you find a prospect who balks on the contract or on pre-paying, leave them behind. This is a red-flag that they won’t pay later either.</p>

## The Cost of Bad Projects

<p>You may think you can still take all the work, enjoy the ideal projects, and just power through the bad ones. That may be true, but you’re ignoring the <b>opportunity cost</b>. Opportunity costs are the opportunities you miss by taking less-than-ideal ones. It’s literally <b>a cost in terms of <i>opportunity</i></b> instead of a cost in terms of <i>money</i>, which is how we usually think of costs.</p>
<p>What happens when you’re loaded up with bad projects and an ideal one comes along? <b>You’re going to lose the chance to take on the ideal project</b> because your resources are tied up in the bad one. That’s not a place you want to be, and gigs aren’t so scarce that you should ever <i>have</i> to be there.</p>
<p>You’ll need to overcome a psychological barrier to get comfortable with this. Think of it this way: if someone offered to fill your availability with <b>nothing but ideal projects</b>, how much would you be willing to pay for that? Got something in your head? OK, great.</p>
<p>Now, imagine you’re going to pay <i>yourself</i> that same amount to get you nothing but ideal projects. When you turn down bad projects waiting for the ideal ones, that’s probably going to leave some small gaps in your workload that represent the time you were disqualifying clients. That time that’s no longer billable, <b>that is the pay you’re paying to <i>yourself</i></b> to get only the ideal jobs.</p>
<p>You’ll soon find yourself reaping the benefits of <b>happier clients</b>, <b>greater job satisfaction</b>, and <b>more profit</b>. Learning to turn away work is a difficult transition to make, but it’s one that pays off in every aspect of your web development business.</p>

_I help people leave their 💩 jobs to become web developers over at [RadDevon.com](https://raddevon.com/). If you liked this article, hit the site to find more stuff like it!_