<?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: Two Things You Should Never Tell Clients</title>
	<atom:link href="http://cathystucker.com/two-things-you-should-never-tell-clients/feed" rel="self" type="application/rss+xml" />
	<link>http://cathystucker.com/two-things-you-should-never-tell-clients</link>
	<description>Wisdom &#38; Whimsy from the Idea Lady</description>
	<lastBuildDate>Mon, 07 May 2012 19:27:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Steve</title>
		<link>http://cathystucker.com/two-things-you-should-never-tell-clients/comment-page-1#comment-403</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Wed, 03 Jun 2009 21:50:11 +0000</pubDate>
		<guid isPermaLink="false">http://cathystucker.com/two-things-you-should-never-tell-clients#comment-403</guid>
		<description>Thanks for the great post!  I am very close to starting an online business and never even thought about not telling clients how much time jobs take.  Very good insight.</description>
		<content:encoded><![CDATA[<p>Thanks for the great post!  I am very close to starting an online business and never even thought about not telling clients how much time jobs take.  Very good insight.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lori</title>
		<link>http://cathystucker.com/two-things-you-should-never-tell-clients/comment-page-1#comment-388</link>
		<dc:creator>Lori</dc:creator>
		<pubDate>Tue, 21 Apr 2009 13:52:58 +0000</pubDate>
		<guid isPermaLink="false">http://cathystucker.com/two-things-you-should-never-tell-clients#comment-388</guid>
		<description>Cathy thank you for your advice, I know now that I give too much information and often undercharge way too often.</description>
		<content:encoded><![CDATA[<p>Cathy thank you for your advice, I know now that I give too much information and often undercharge way too often.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brandon</title>
		<link>http://cathystucker.com/two-things-you-should-never-tell-clients/comment-page-1#comment-141</link>
		<dc:creator>Brandon</dc:creator>
		<pubDate>Sun, 24 Aug 2008 23:28:10 +0000</pubDate>
		<guid isPermaLink="false">http://cathystucker.com/two-things-you-should-never-tell-clients#comment-141</guid>
		<description>When looking at different pricing models for my business, I have considered hourly rates for my consulting, but hated being limited in such a way, especially when what people are paying for, often, is expertise. It may take you 10 hours or 1 hour to come up with a solution, depending upon your level of expertise. One shouldn&#039;t be penalized because they may have more.</description>
		<content:encoded><![CDATA[<p>When looking at different pricing models for my business, I have considered hourly rates for my consulting, but hated being limited in such a way, especially when what people are paying for, often, is expertise. It may take you 10 hours or 1 hour to come up with a solution, depending upon your level of expertise. One shouldn&#8217;t be penalized because they may have more.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cathy Stucker</title>
		<link>http://cathystucker.com/two-things-you-should-never-tell-clients/comment-page-1#comment-137</link>
		<dc:creator>Cathy Stucker</dc:creator>
		<pubDate>Fri, 22 Aug 2008 20:57:32 +0000</pubDate>
		<guid isPermaLink="false">http://cathystucker.com/two-things-you-should-never-tell-clients#comment-137</guid>
		<description>@Phil, I know that there may be times when you have no choice but to give some kind of hourly rate, but I would avoid it whenever possible. For example, perhaps the ongoing support work could be on some kind of retainer or other flat rate. 

The less clients know about your internal rate calculations the better. Get them focused on the value of the results you provide.</description>
		<content:encoded><![CDATA[<p>@Phil, I know that there may be times when you have no choice but to give some kind of hourly rate, but I would avoid it whenever possible. For example, perhaps the ongoing support work could be on some kind of retainer or other flat rate. </p>
<p>The less clients know about your internal rate calculations the better. Get them focused on the value of the results you provide.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil</title>
		<link>http://cathystucker.com/two-things-you-should-never-tell-clients/comment-page-1#comment-136</link>
		<dc:creator>Phil</dc:creator>
		<pubDate>Fri, 22 Aug 2008 20:49:45 +0000</pubDate>
		<guid isPermaLink="false">http://cathystucker.com/two-things-you-should-never-tell-clients#comment-136</guid>
		<description>Sounds like good advice, but I don&#039;t think its practical... Most of the time the work cannot be defined well enough to estimate it with any accuracy (what client can tell you what they really want with clarity?). And what do you do for open-ended ongoing support work (which is very common). Estimating fixed bid software work is near impossible unless everything is crystal clear in definition. Even then, there&#039;s always too much unknown that creeps in. Estimating accurately also takes a lot of time and effort. You also have the problem of disagreements on what &quot;finished&quot; means.</description>
		<content:encoded><![CDATA[<p>Sounds like good advice, but I don&#8217;t think its practical&#8230; Most of the time the work cannot be defined well enough to estimate it with any accuracy (what client can tell you what they really want with clarity?). And what do you do for open-ended ongoing support work (which is very common). Estimating fixed bid software work is near impossible unless everything is crystal clear in definition. Even then, there&#8217;s always too much unknown that creeps in. Estimating accurately also takes a lot of time and effort. You also have the problem of disagreements on what &#8220;finished&#8221; means.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kris</title>
		<link>http://cathystucker.com/two-things-you-should-never-tell-clients/comment-page-1#comment-129</link>
		<dc:creator>Kris</dc:creator>
		<pubDate>Fri, 15 Aug 2008 00:30:30 +0000</pubDate>
		<guid isPermaLink="false">http://cathystucker.com/two-things-you-should-never-tell-clients#comment-129</guid>
		<description>I absolutely agree with your points.  The difficulty I have faced over the years, is that my competitors are not as professional - they will provide hours worked or planned for the project, they also provide a ridiculous hourly rate, and therefore an equally ridiculous project price.  While I can develop a strategy to overcome this with clients I&#039;ve worked with before; it is much more difficult when quoting on work with clients whom you may have met, but who don&#039;t know or understand the value you bring.  They compare the dollars and go for the lowest bid!  Afterwards, I&#039;ve had some come back to me for work.  But I wonder if the effect is that they are lowering the bar on prices overall - as consultants, project managers, etc.  we look like we&#039;re overcharging!</description>
		<content:encoded><![CDATA[<p>I absolutely agree with your points.  The difficulty I have faced over the years, is that my competitors are not as professional &#8211; they will provide hours worked or planned for the project, they also provide a ridiculous hourly rate, and therefore an equally ridiculous project price.  While I can develop a strategy to overcome this with clients I&#8217;ve worked with before; it is much more difficult when quoting on work with clients whom you may have met, but who don&#8217;t know or understand the value you bring.  They compare the dollars and go for the lowest bid!  Afterwards, I&#8217;ve had some come back to me for work.  But I wonder if the effect is that they are lowering the bar on prices overall &#8211; as consultants, project managers, etc.  we look like we&#8217;re overcharging!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Candy</title>
		<link>http://cathystucker.com/two-things-you-should-never-tell-clients/comment-page-1#comment-127</link>
		<dc:creator>Candy</dc:creator>
		<pubDate>Wed, 13 Aug 2008 13:30:17 +0000</pubDate>
		<guid isPermaLink="false">http://cathystucker.com/two-things-you-should-never-tell-clients#comment-127</guid>
		<description>Cathy,

Thanks for the info - I&#039;m just starting out and had not heard that before. It makes a lot of sense!

Regards,
Candy</description>
		<content:encoded><![CDATA[<p>Cathy,</p>
<p>Thanks for the info &#8211; I&#8217;m just starting out and had not heard that before. It makes a lot of sense!</p>
<p>Regards,<br />
Candy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Old Welsh Guy</title>
		<link>http://cathystucker.com/two-things-you-should-never-tell-clients/comment-page-1#comment-126</link>
		<dc:creator>Old Welsh Guy</dc:creator>
		<pubDate>Tue, 12 Aug 2008 22:22:17 +0000</pubDate>
		<guid isPermaLink="false">http://cathystucker.com/two-things-you-should-never-tell-clients#comment-126</guid>
		<description>How true is that! 

Just last week, I wrote a &#039;Dear John&#039; to one of my clients because they demanded to know  how many hours I had worked on their site last month. 

I politely told them fist that the number of hours was not a deliverable, the deliverables were set out in the schedule of works. 

They replied demanding they had a right to know how many hours I spent working on their site. I sent them back an email that listed the volume of hours i WOULD have worked had i not have invested in bespoke software built around my specific knowledge, that allowed me to work faster and do multiple tasks at once. 

Oh &amp; my final line was &#039;As you insisted on there being no long term contract between us, I now consider our agreement to be at an end&#039;. 

They were on the phone apologising within the hour, Turns out they had argued with their developer and vented their frustration on me. Ah well it backfired as I am no longer doing their work for them.</description>
		<content:encoded><![CDATA[<p>How true is that! </p>
<p>Just last week, I wrote a &#8216;Dear John&#8217; to one of my clients because they demanded to know  how many hours I had worked on their site last month. </p>
<p>I politely told them fist that the number of hours was not a deliverable, the deliverables were set out in the schedule of works. </p>
<p>They replied demanding they had a right to know how many hours I spent working on their site. I sent them back an email that listed the volume of hours i WOULD have worked had i not have invested in bespoke software built around my specific knowledge, that allowed me to work faster and do multiple tasks at once. </p>
<p>Oh &amp; my final line was &#8216;As you insisted on there being no long term contract between us, I now consider our agreement to be at an end&#8217;. </p>
<p>They were on the phone apologising within the hour, Turns out they had argued with their developer and vented their frustration on me. Ah well it backfired as I am no longer doing their work for them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brett Slater</title>
		<link>http://cathystucker.com/two-things-you-should-never-tell-clients/comment-page-1#comment-125</link>
		<dc:creator>Brett Slater</dc:creator>
		<pubDate>Tue, 12 Aug 2008 21:50:50 +0000</pubDate>
		<guid isPermaLink="false">http://cathystucker.com/two-things-you-should-never-tell-clients#comment-125</guid>
		<description>Outstanding advice... As a freelancer who does a lot of jobs that take anywhere from 15 minutes to 15 days, coming up with a viable pricing structure isn&#039;t always easy... And hourly rates do tend to spook some clients.  Thanks!</description>
		<content:encoded><![CDATA[<p>Outstanding advice&#8230; As a freelancer who does a lot of jobs that take anywhere from 15 minutes to 15 days, coming up with a viable pricing structure isn&#8217;t always easy&#8230; And hourly rates do tend to spook some clients.  Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David West</title>
		<link>http://cathystucker.com/two-things-you-should-never-tell-clients/comment-page-1#comment-124</link>
		<dc:creator>David West</dc:creator>
		<pubDate>Tue, 12 Aug 2008 21:28:55 +0000</pubDate>
		<guid isPermaLink="false">http://cathystucker.com/two-things-you-should-never-tell-clients#comment-124</guid>
		<description>Some good points Cathy.  We dodge the &quot;how long will it take&quot; question by quoting time only on points that we have control over - such as how long it will take us to do an initial design. We can not predict how many revisions a client will ask for or when the client will have their content ready for their new site.

Cheers.  David</description>
		<content:encoded><![CDATA[<p>Some good points Cathy.  We dodge the &#8220;how long will it take&#8221; question by quoting time only on points that we have control over &#8211; such as how long it will take us to do an initial design. We can not predict how many revisions a client will ask for or when the client will have their content ready for their new site.</p>
<p>Cheers.  David</p>
]]></content:encoded>
	</item>
</channel>
</rss>

