Toxic Clients

I have been talking around a similar topic a few times lately with some of my business partners so I was curious to read Seth Godin's post on Toxic Employees. This paragraph caught my eye ...

"Managers can hire the non-toxic, re-assign the toxic and be really clear with themselves that they're willing to pay almost any price to keep toxic employees away from everyone else."

I especially liked the bit about being willing to pay almost any price to keep toxic employees away from everyone else. As a small development shop that doesn't at yet have employees I am more interested in this idea as it applies to Toxic Clients.

I am making some kind of resolution around the idea of Toxic Clients and being willing to pay almost any price to avoid them. Notice ALMOST any price. I guess if I am starving I might bend but in conversation of late I have mused as to what the design/development world would e like if more providers simply refused to work with toxic clients.

Don't say you don't know who they are. I am convinced that there are usually so e tell tale signs. Just wondering if I am game to stick to my guns and say "Thanks but no thanks"

Comments
Chris's Gravatar Godin is a pimp.

His latest post in practical terms is simple supply and demand. High demand for talent and low supply means you have to work with less passionate people. High demand for clients and low supply means you're up 'til 2AM working on a project that pays half of what you're worth.

The solution to both is easy in theory, hard in practice.
# Posted By Chris | 8/1/07 11:35 PM
Matt's Gravatar you guys should formularise it - take out the emotion - like:

if currentBankBalance is less than currentRentOwed and prospective job is worth more than currentRentOwed then acceptJob = true

Ok, a bit simple and missing a few key variable like "timeTakenForClientToPay" and "scopeCreep", but I think its got legs.
# Posted By Matt | 8/3/07 9:59 AM