I met with a potential client today and part of their opening gambit was how they were looking for revolutionary work delivered within a tight timescale, and if the work could be done at a reduced rate then they’d be able to send a load more work our way.
Let me distill this for you. They were saying that they wanted work that was fast, good, and cheap. And if the work was fast, good, and cheap enough, the reward would be the offer of more work that is fast, good, and cheap.
This was the shortest pitch I’ve ever been in. I tried to explain the value in creating a nurturing ecosystem where all parties benefit and grow from their relationship, and they wholeheartedly agreed… as long as the work was fast, good, and cheap. It was time for a sharp exit.
Let me be clear about this, these people are evil and their work is poison.
It’s not unusual to encounter people like this, I know I’ve met plenty over the years. Let me be clear about this, these people are evil and their work is poison. They are douchebags of the highest calibre, and they are infinitely more toxic than even the strokers that run out on you without paying their invoice.
The first thing to understand is that it is impossible to create work that is fast, good, and cheap—from your perspective. If you do work that is cheap and fast, it is inevitable that it will not be of as high quality if you had more time or budget.
The first thing to understand is that it is impossible to create work that is fast, good, and cheap
The accurate, but overly simple deduction when considering the fast, good, and cheap trifecta is that it is only possible to deliver on two. If you agree to deliver fast, good, and cheap then something will have to give, and it’s never the value of the job, as the type of clients that push you into accepting fast, good, and cheap never agree to an increase in fee under any circumstances.
This leaves you with fast and good. If you’re determined to hold onto fast (or more likely are being forced to be fast) then you will be left with two options. The first option is to sacrifice the quality of the work in order to meet the deadline, and often you will get away with this as making the best of a bad situation.
But if your client knows her stuff, you won’t be able to cut corners when it comes to quality. This is the worst-case scenario, with you being held to deliver a quality of work within an unreasonable timescale. Something has to give, and the only option you have left is price, resulting in you having to invest more than planned on a job that already had a low profit margin, often to the point of you making a loss on the job.
This kind of work is easy to find, but it will emotionally and financially destroy you.
Now you are paying a client to do work you grudge, within a timescale that delays you from working on other, more profitable projects. This kind of work is easy to find, but it will emotionally and financially destroy you. It takes courage to decline new work, but recognising that it is better to do no work, than toxic work, is vital to your happiness and prosperity.
I mentioned above that this is an over simplification, and by this I refer to both the analogue, and relative nature of the three factors. Delivering ‘good enough’ can be the difference between a job being delivered fast and cheap enough. When good enough is perceived as ‘not doing one’s best’ it is shameful, but this is a fallacy.
This was ludicrous—we’d paid a supremely talented illustrator to create something nobody would ever see.
I distinctly remember our creative director waxing lyrical about the architectural illustrations that Russell Bell did for us for The Chicago Spire, and how if you could zoom in far enough you could even see the coin slots on the pool tables. This was ludicrous—we’d paid a supremely talented illustrator to create something nobody would ever see.
The analogue nature of the quality of your work means there are shades of grey between good and bad. Add to this that you are likely to be more critical than your client of what is good, and we can see that there is a point on the good/bad sliding scale where increasing the quality of the work will have no discernible effect on the client, and will either make you too expensive or unprofitable.
Simply put, if you need to work weekends to meet a client’s tight deadline it just can’t be cheap.
This allows us to bring logic into play. If we set a lower limit on the quality of work we are prepared to create, i.e. we are not prepared to do bad work, then we can see that the only variables are the speed and the price. Simply put, if you need to work weekends to meet a client’s tight deadline it just can’t be cheap.
If, on the other hand, your client is prepared to wait until you have some down time between other projects then by all means cut them some slack on your fees. For what it’s worth, I’ve found the clients that are flexible with timings have proved to be the most rewarding to work with, and the most likely to become long term partners in that nurturing relationship.
As for the pricks I met with today, their project is very appealing and I would love to have it in the portfolio. As a result some poor fool will take them on, but at the end of the day they will all end up hating each other, and the parasitical client will move on to find their next victim.
Good riddance.

I just had to do that very thing today – had a dry spell recently due to one thing or another and in the midst of it all I received a poisonous offer of work that, whilst it would have paid very well, would very likely have given me an embolism as it was, in their own words, ‘a shitty mess’.
It does take balls to turn stuff down, especially when you need some work – usually in that situation you end up taking on some crappy job, only to be immediately offered something good from another client (which you now don’t have the time to do).
Good post and a good lesson for seasoned and fresh freelancers alike.
BTW, what’s with the ‘you must fill in your name and email’ message when submitting? I saw a FOTB talk you did a few years ago deploring the need for people to leave their details
Good for you Chris! And the anonymous submissions referred to my contact form. I don’t mind people talking to me from the shadows, but when posting comments for the world to read I find asking for credentials goes a little way to keeping out the crazies.
Reading this makes my stomach turn from bad memories. If anyone was to tell me this when I started my own company 10 years ago, I’m not sure I would have listened. One can only hope that not everyone needs to learn this the hard way like me (and I suspect maybe you).
But as I wrote in my post FOTB session email to you: Doing charitable work for free will most likely be a very positive experience. It doesn’t even have to be a good cause other than keeping yourself busy when starting up or during slow periods. If the client is prepared to pay, but cannot pay full rate (and the project is small enough), tell them you’ll do it for free! The working invironment will most likely be good like you wouldn’t believe and you’ll both profit from it intellectually. Also clients seem to better handle the separation of free and full charge and that there is nothing in between.
Absolutely Øyvind, it’s better to work for free for a good client than to work at a loss for bad client.
A fourth factor to consider is creative freedom. Some of my most successful projects have been for clients that have given me creative freedom in lieu of budget. When a client puts their trust in you like this, you’re given the opportunity to put a new direction in your portfolio, or add a new skill to your toolset.
I’ve met a few clients like that. Like you said, short conversations. From recruiters too: usually hear things like “clients don’t want remote workers” (which I am – funny I’m still in business?) and “the market won’t bear more than $50 per hour for your level of experience” (I charge twice that) “and we need [3 mo project] in the next three weeks. When can you start?”. Um, never? Have a nice day!
Hoss, we deal with these potential clients in voice-overs all the time. Thank God for my agents who are skilled in only playing the game with clients that understand the mutual benefits of paying for quality and the, ironically, the goodwill that surrounds a long term relationship as a result.
When someone lowballs me on the “promise” of future work, I always tell them that I’d be happy to give discounts to existing valued (i.e., returning) customers, but not on the “possibility” of returning customers.
Everyone knows the rule about fast, good, and cheap:
You can only have two.
Bonus: http://clientsfromhell.net/
Let me guess, this was probably sub-contracting for an agency that had already got the job, right?
I learned from bitter experience to cut out these blood suckers and pitch directly to end clients. As a flash freelancer with 10 years in the game I’ve found it’s actually not that hard (at the moment) to find customers who have ideas/projects they want realised in Flash, but are unsure who to approach. They know if they go to a high profile agency the price is likely to be prohibitive.
For some reason most freelance programmers are scared of doing sales. They prefer someone else to find the customers, so they can just sit and do the fun stuff.
It’s unfortunate, because the best projects seem to come out of a direct dialog between designer and end customer, and not only does this give the best results, it is cheaper for the customers, and offers the programmer/designer (whatever you prefer to call flashers) a higher wage.
If you can build relationships with just a handful of end customers, and deliver something good at a reasonable price, soon you don’t need to look for work, it finds you.
Another approach I’ve had success with is to dream up the project first, something I really want to do, then think about which customer might benefit from it and send them a mail, maybe with a demo. This is my favorite way of working, as it keeps me motivated and the clients happy.
As far as pricing goes, I have several strategies depending on circumstances. For non-specific flash programming I charge $200 an hour. These are jobs for cash, plain and simple. This might be upgrading an existing system to AS3, or setting up a video service, something boring and non-creative.
For project work, if I instigate it, I think more about ROI than hourly rate. For example something that sells a product is likely to have a huge economic value for the customer, so there’s an opportunity to earn extra cash and then treat yourself to a conference or a software/hardware upgrade.
Then there’s re-usablity. I would definitely do a project for less than it’s worth (calculated by hourly rate) if I can see that I can sell the same solution again and again.
This might all sound obvious, but somehow it’s still taken years to understand and use effectively.
I have and do use the lovely phrase, “You can have it good, cheap and fast, choose 2″, but as I’ve gotten older and had more kids I avoid the “fast” option, i.e. working 14 hrs a day for 2 weeks to make some otherwise impossible deadline.
Oops, didn’t mean to write a novel, I obviously think about this subject more than i realised
Flashers are in demand. It’s your time. Don’t be exploited, clients want new and exciting stuff, but they’ll never find you, you have to find them.
Not only you are right, but I love the way you present your rants visually.
Absolutely agree 100%.
My current major project is with a client (former colleague) who’s flexible on timing, and basically we just get in touch every week or two to make sure we’re on the same page.
I imagine the kind of jobs where it’s someone you’ve worked with before, works out best.
The great thing is, even while we’re taking extra time on the right things, his competitors are running scared because he’s so good at selling, and because I let him know what’s feasible or not technically, we always overdeliver, whereas whoever they’re contracting to is top-heavy and probably has overworked, underpaid employees not putting out their best.
To The point;
however, I have found that working with people I know is not good – in fact, I would rather not do so. Most of these people expect free work and of the highest possible quality. Then they dont act professionally and expect you to treat them well because you knew them.
So I would strongly sugggest not working with people you know OR if you do so, be very cautious.
Incredible. When I saw this, I thought it was legacy post from three years ago. Did these people not pay attention the first time you said this?!
If I wasn’t dealing with this sort of thing consistently myself, I’d say over-reaction, as it is, I might bookmark this post and just fwd it to some people as an eye-opener.
Pingback: Fast, good, cheap | Hoss Gifford. « Mike Cane's xBlog
@Hoss: Excellent post, filled with the insight clearly learned from experience. By the way, the expression is “worst-case scenario”, not “worse case scenario”.
@Hugh: Freelancers may have read similar advice years ago, but *clients* aren’t reading articles like this. Many years from now, toxic clients will still be trying to get free or cheap work from us.
Thanks Allen, I’m stickler for grammar and it irks me no end to miss things like that. Fixed now though.
And you’re right, the insight here was learned the hard way.
Can I add a missing ‘n’ into my post please! Otherwise I might have aN embolism
Fixed. The attention to grammatical detail around here makes me proud.
Fast, good, or cheap. Pick two! I love the project triangle, it helps articulate a reality that developer’s experience which client’s frequently fail to recognize, or respect. Too many person’s believe they need their idea realized yesterday, when in fact if their idea has true merit, it will catch on, today, next month, or a year from now. If you have the budget to hire a larger staff for serious rapid development, do it, just don’t expect rapid development to translate to long-term stability & ease of refactoring.
Pingback: Some clients are evil and their work is toxic | Smash Company
Great article, but can I make one suggestion? You may want to play with the leading on your article to make it a bit more readable. I understand your design goal and style with the site, but at least for the body copy it would help a lot. It’s really tight and difficult to make out word shape given that you chose a font with a large x-height.
One more thing.
Add the “cursor:pointer” property to your post comment button.
Muy preciso. Hace poco terminé una relación de años con un cliente que siempre alegaba ser pobre y que quería tenerme como su empleado de rápido, bueno y barato. Siempre decía frases como: Pero verdad que es fácil… Pero verdad que lo haces rápido.
Google translation.
Very accurate. I recently finished a long relationship with a client who always claimed to be poor and he wanted me as his employee, fast, good and cheap. He always said things like: “But really it’s easy … But you do really fast.
There is definitely a difference between what the buyer perceives and what the seller perceives when it comes to value of work and time. It’s as true in Wal-Mart when we scoff at the price of some gadget we think is useless as it is when someone tries to lowball a developer.
The reality is that a lot of people want, but they don’t want badly enough to pay for things. I’m glad to see your post on this, and would love to see a universal scoff back at this sort of attempt. It’s the few devs who fall for it that allow the “toxic” clients to keep in business.
I completely agree with your statements and have been railing against people who ignore this axiom for years. You incorrectly used ‘an’ for ‘a’ before
“…we’d paid an supremely talented illustrator…”
I suspect you may have changed your adjective to supreme from something with a different sound. (ex. an extremely)
Remember, using a or an depends on the sound that begins the next word. So…
a + singular noun beginning with a consonant: a boy; a car; a bike; a zoo; a dog
an + singular noun beginning with a vowel: an elephant; an egg; an apple; an idiot; an orphan
a + singular noun beginning with a consonant sound: a user (sounds like ‘yoo-zer,’ i.e. begins with a consonant ‘y’ sound, so ‘a’ is used); a university; a unicycle
In some cases where “h” is pronounced, such as “historical,” use an:
An historical event is worth recording.
In writing, “a historical event” is more commonly used.
Well spotted, and bonus points for correct suspicions on cause of my error—Russell started life in my post as an extremely talented illustrator and I later upgraded him to a supremely talented illustrator.
My faith in humanity is restored by the attention to detail being shown by readers of this site.
Keep it coming.
Pingback: Fast, good, cheap | Martin Džubák
Beautiful. Just beautiful.
I’ve been trying to find the words for my overwhelmingly depressing experiences moving away from my current job and toward taking life by the balls.
Thankfully, I can take away that not every business transaction is like this, and that the triad–cost, quality, and time–is not some unique affliction borne only by me.
Thanks for this.
@Allen I was specifically referring to a talk I saw Hoss give at Flash on the Beach years ago. I can attest that clients aren’t reading this. If they are, their reaction is; “I can’t see why I can’t have it good, fast AND cheap.”
Bravo on an excellent article. This is something I try to explain to clients, and I often tend to drop that kind altogether. I like how they are usually (at least in the local business atmosphere) rather straightforward with their requests for cheap-good-fast, and thus are easy to identify and drop immediately (while warning all my friends who are in the same business).
They are not worth my time, efforts, or nerves.
90% of the clients I’ve met were like this. To make it worse they’ll always find someone that will take their project and they know it. If we don’t get united and spread the word to the new designers out there this will never stop.
Spot on with your comments and this interesting conundrum firmly exists outside of the design world as well, I work for a hosting company and we face this battle daily.
I always thnk it’s very interesting that they expect this from you, but take their own sweet time to pay their invoices.
Great post. Thanks.
http://www.fastngoodncheap.com is currently available. Some fun to be had there! No?
Pingback: Fast, good, cheap. « Antti Akonniemi
Pingback: Fast, Good, Cheap « walkbywalk