<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Reader Poll: Top Reasons to Let a Client Go</title>
	<atom:link href="http://www.toprankblog.com/2007/01/reader-poll-top-reasons-to-let-a-client-go/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.toprankblog.com/2007/01/reader-poll-top-reasons-to-let-a-client-go/</link>
	<description>Grow your business with TopRank Online Marketing tips, articles, &#38; experts interviews on social media, digital PR &#38; search engine marketing.</description>
	<lastBuildDate>Sun, 21 Mar 2010 23:39:37 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Marc Ohmann</title>
		<link>http://www.toprankblog.com/2007/01/reader-poll-top-reasons-to-let-a-client-go/#comment-56492</link>
		<dc:creator>Marc Ohmann</dc:creator>
		<pubDate>Fri, 05 Jan 2007 20:46:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.toprankblog.com/2007/01/reader-poll-top-reasons-to-let-a-client-go/#comment-56492</guid>
		<description>We don&#039;t lose many clients but when we do it&#039;s because of items 1 (Client is too difficult to work with) and 2 (The engagement is not profitable for your agency).

I have found the most important aspect of a quality relationship is keeping value and goals in the forefront.  We won&#039;t start a project anymore without actual conversion goals being spelled out.  We have found it is far too difficult to measure success or failure later on without clearly defined goals.  We also keep value in clear view.  What is the value of X daily visitors to your site and Y conversions?  Focusing on value generally squelches any expense complaints from purchasing. 

We have also moved towards being very clear with customers who are overly price conscious that there probably isn&#039;t a good fit between our companies.  And try an go our separate ways before the relationship spirals into an actual firing.</description>
		<content:encoded><![CDATA[<p>We don&#8217;t lose many clients but when we do it&#8217;s because of items 1 (Client is too difficult to work with) and 2 (The engagement is not profitable for your agency).</p>
<p>I have found the most important aspect of a quality relationship is keeping value and goals in the forefront.  We won&#8217;t start a project anymore without actual conversion goals being spelled out.  We have found it is far too difficult to measure success or failure later on without clearly defined goals.  We also keep value in clear view.  What is the value of X daily visitors to your site and Y conversions?  Focusing on value generally squelches any expense complaints from purchasing. </p>
<p>We have also moved towards being very clear with customers who are overly price conscious that there probably isn&#8217;t a good fit between our companies.  And try an go our separate ways before the relationship spirals into an actual firing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Essential Keystrokes &#187; Friday&#8217;s Food for Thought</title>
		<link>http://www.toprankblog.com/2007/01/reader-poll-top-reasons-to-let-a-client-go/#comment-56470</link>
		<dc:creator>Essential Keystrokes &#187; Friday&#8217;s Food for Thought</dc:creator>
		<pubDate>Fri, 05 Jan 2007 19:25:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.toprankblog.com/2007/01/reader-poll-top-reasons-to-let-a-client-go/#comment-56470</guid>
		<description>[...] Which leads me to the article I was looking for earlier - Reader Poll: Top Reasons to Let a Client Go by Lee Odden. More food for thought. [...]</description>
		<content:encoded><![CDATA[<p>[...] Which leads me to the article I was looking for earlier &#8211; Reader Poll: Top Reasons to Let a Client Go by Lee Odden. More food for thought. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Elements of Successful Client Relationships &#187; Online Marketing Blog</title>
		<link>http://www.toprankblog.com/2007/01/reader-poll-top-reasons-to-let-a-client-go/#comment-56416</link>
		<dc:creator>Elements of Successful Client Relationships &#187; Online Marketing Blog</dc:creator>
		<pubDate>Fri, 05 Jan 2007 14:50:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.toprankblog.com/2007/01/reader-poll-top-reasons-to-let-a-client-go/#comment-56416</guid>
		<description>[...] A marketing blog about the intersection of social media, search marketing and online public relations.     Home&#160; About&#160; Resources&#160; Archives&#160; Subscribe&#160; Contact&#160;    &#171; Reader Poll: Top Reasons to Let a Client Go [...]</description>
		<content:encoded><![CDATA[<p>[...] A marketing blog about the intersection of social media, search marketing and online public relations.     Home&nbsp; About&nbsp; Resources&nbsp; Archives&nbsp; Subscribe&nbsp; Contact&nbsp;    &laquo; Reader Poll: Top Reasons to Let a Client Go [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lee Odden</title>
		<link>http://www.toprankblog.com/2007/01/reader-poll-top-reasons-to-let-a-client-go/#comment-56410</link>
		<dc:creator>Lee Odden</dc:creator>
		<pubDate>Fri, 05 Jan 2007 14:17:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.toprankblog.com/2007/01/reader-poll-top-reasons-to-let-a-client-go/#comment-56410</guid>
		<description>I think up front due diligence, setting proper expectations, communication and account management are the most precursors to whether an agency/client relationship works out or not. 

Char, you make a good point about responsiveness. In the search marketing industry, I&#039;ve seen stats that say all SEO recommendations are NOT implemented by clients about 60% of the time. That&#039;s a huge number, but it doesn&#039;t dig into the details, like whether SEO recommendations are even possible or whether the cost of implementation outweighs the potential benefit.</description>
		<content:encoded><![CDATA[<p>I think up front due diligence, setting proper expectations, communication and account management are the most precursors to whether an agency/client relationship works out or not. </p>
<p>Char, you make a good point about responsiveness. In the search marketing industry, I&#8217;ve seen stats that say all SEO recommendations are NOT implemented by clients about 60% of the time. That&#8217;s a huge number, but it doesn&#8217;t dig into the details, like whether SEO recommendations are even possible or whether the cost of implementation outweighs the potential benefit.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Balazs Balint</title>
		<link>http://www.toprankblog.com/2007/01/reader-poll-top-reasons-to-let-a-client-go/#comment-56409</link>
		<dc:creator>Balazs Balint</dc:creator>
		<pubDate>Fri, 05 Jan 2007 14:08:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.toprankblog.com/2007/01/reader-poll-top-reasons-to-let-a-client-go/#comment-56409</guid>
		<description>Oh, sorry. The end of my comment is missing. Here you are!

...Than you have to multiply the probability of the scenarios with the present value of the expected profit (of course you have to take into consideration of the risk sensitivity of your company). Than add the profits of the two parts of your portfolio, and you will get the present value of your profit. If it is below your minimal profit expectations, you have to reject the client relationship, otherwise you have to start (or continue) it. Isn&#039;t it simple?

Of course the modell is simple. But it is very hard to evalute future scenarios. The only thing I tried to explain, that it is a mistake to decide about a client considering one special factor of the relationship. For instance I do not send a client becouse it is hard to work with him. If he pays my &#039;difficulties&#039; I continue the hard work with him. On the aother hand I tend to work for share- if the profit is high enough, and the risk is low enough for me, why not?</description>
		<content:encoded><![CDATA[<p>Oh, sorry. The end of my comment is missing. Here you are!</p>
<p>&#8230;Than you have to multiply the probability of the scenarios with the present value of the expected profit (of course you have to take into consideration of the risk sensitivity of your company). Than add the profits of the two parts of your portfolio, and you will get the present value of your profit. If it is below your minimal profit expectations, you have to reject the client relationship, otherwise you have to start (or continue) it. Isn&#8217;t it simple?</p>
<p>Of course the modell is simple. But it is very hard to evalute future scenarios. The only thing I tried to explain, that it is a mistake to decide about a client considering one special factor of the relationship. For instance I do not send a client becouse it is hard to work with him. If he pays my &#8216;difficulties&#8217; I continue the hard work with him. On the aother hand I tend to work for share- if the profit is high enough, and the risk is low enough for me, why not?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Balazs Balint</title>
		<link>http://www.toprankblog.com/2007/01/reader-poll-top-reasons-to-let-a-client-go/#comment-56403</link>
		<dc:creator>Balazs Balint</dc:creator>
		<pubDate>Fri, 05 Jan 2007 13:55:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.toprankblog.com/2007/01/reader-poll-top-reasons-to-let-a-client-go/#comment-56403</guid>
		<description>I think the poll implicitly suggest to think that client reliationships are qiute similar to each other. Of course, everybody knows that they are not. If you think as a manager, every business activity including client relationships has to be evaluated by risk and profitability, acknowledging that the other party evaluates the same things. Let&#039;s suppose that there is no difficulties with the payments (otherwise the risk factor of the evaluation becomes too high, so most companies cant&#039;t afford to continue such a relationship. Late payments just cause less profitability). 

If you think about the client relationship just as an order the only important thing is that your work have to be payed. 

If you think about the client relationship as an investment (reference, long term relationship, widening range of services you will deliver later) than your portfolio (remember- every business activity is an investment, just like T-Bonds) consist of two parts: The first part is payed immedietly, and without risk (ideally). The other part of the portfolio consist of references, good-will growth, more orders (approving that the client&#039;s business also grows) (probably with greater profit-ratio), etc.</description>
		<content:encoded><![CDATA[<p>I think the poll implicitly suggest to think that client reliationships are qiute similar to each other. Of course, everybody knows that they are not. If you think as a manager, every business activity including client relationships has to be evaluated by risk and profitability, acknowledging that the other party evaluates the same things. Let&#8217;s suppose that there is no difficulties with the payments (otherwise the risk factor of the evaluation becomes too high, so most companies cant&#8217;t afford to continue such a relationship. Late payments just cause less profitability). </p>
<p>If you think about the client relationship just as an order the only important thing is that your work have to be payed. </p>
<p>If you think about the client relationship as an investment (reference, long term relationship, widening range of services you will deliver later) than your portfolio (remember- every business activity is an investment, just like T-Bonds) consist of two parts: The first part is payed immedietly, and without risk (ideally). The other part of the portfolio consist of references, good-will growth, more orders (approving that the client&#8217;s business also grows) (probably with greater profit-ratio), etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Kelm - Brokerblogger</title>
		<link>http://www.toprankblog.com/2007/01/reader-poll-top-reasons-to-let-a-client-go/#comment-56372</link>
		<dc:creator>Bill Kelm - Brokerblogger</dc:creator>
		<pubDate>Fri, 05 Jan 2007 11:18:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.toprankblog.com/2007/01/reader-poll-top-reasons-to-let-a-client-go/#comment-56372</guid>
		<description>Lee, my take on the reasons you outlined above is basically &quot;An ounce of prevention...&quot;:

#  Client is too difficult to work with - avoidable unless SEM is dealing with a change in management &amp; contacts.
# Your agency oversold and cannot deliver - avoidable if expectations are set realistically.
# The engagement is not profitable for your agency - avoidable if a 6 mo. to 1 yr. contract is signed with fair pricing to both buyer and seller.
# The client</description>
		<content:encoded><![CDATA[<p>Lee, my take on the reasons you outlined above is basically &#8220;An ounce of prevention&#8230;&#8221;:</p>
<p>#  Client is too difficult to work with &#8211; avoidable unless SEM is dealing with a change in management &amp; contacts.<br />
# Your agency oversold and cannot deliver &#8211; avoidable if expectations are set realistically.<br />
# The engagement is not profitable for your agency &#8211; avoidable if a 6 mo. to 1 yr. contract is signed with fair pricing to both buyer and seller.<br />
# The client</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mitch</title>
		<link>http://www.toprankblog.com/2007/01/reader-poll-top-reasons-to-let-a-client-go/#comment-56279</link>
		<dc:creator>Mitch</dc:creator>
		<pubDate>Fri, 05 Jan 2007 02:13:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.toprankblog.com/2007/01/reader-poll-top-reasons-to-let-a-client-go/#comment-56279</guid>
		<description>I had to fire a client once because we couldn&#039;t communicate.  Well, she couldn&#039;t communicate, and I wasn&#039;t Kreskin.  Too bad also, because she could have been worth lots of cash down the line.</description>
		<content:encoded><![CDATA[<p>I had to fire a client once because we couldn&#8217;t communicate.  Well, she couldn&#8217;t communicate, and I wasn&#8217;t Kreskin.  Too bad also, because she could have been worth lots of cash down the line.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Char</title>
		<link>http://www.toprankblog.com/2007/01/reader-poll-top-reasons-to-let-a-client-go/#comment-56266</link>
		<dc:creator>Char</dc:creator>
		<pubDate>Fri, 05 Jan 2007 01:26:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.toprankblog.com/2007/01/reader-poll-top-reasons-to-let-a-client-go/#comment-56266</guid>
		<description>All of the reasons above are valid reasons for letting a client go. I have let a client go (gradually over time) for a combination of slow, then no-pay; ridiculous turn around time expectations and poor client effort.

Actually, poor client involvement is another reason to release a client. I can&#039;t help a client if they are unresponsive, don&#039;t know what they want or need, and expect me to pull things out of thin air. If I ask them for a vital piece of their web site copy, input or other information and they can&#039;t meet their own self-imposed deadlines, it does not bode well for the project.</description>
		<content:encoded><![CDATA[<p>All of the reasons above are valid reasons for letting a client go. I have let a client go (gradually over time) for a combination of slow, then no-pay; ridiculous turn around time expectations and poor client effort.</p>
<p>Actually, poor client involvement is another reason to release a client. I can&#8217;t help a client if they are unresponsive, don&#8217;t know what they want or need, and expect me to pull things out of thin air. If I ask them for a vital piece of their web site copy, input or other information and they can&#8217;t meet their own self-imposed deadlines, it does not bode well for the project.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
