<?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: Charging Project Pricing Versus Hourly Rates</title>
	<atom:link href="http://buildinternet.com/2009/06/charging-project-pricing-versus-hourly-rates/feed/" rel="self" type="application/rss+xml" />
	<link>http://buildinternet.com/2009/06/charging-project-pricing-versus-hourly-rates/</link>
	<description>Web Design, Development, and Business</description>
	<lastBuildDate>Sat, 18 May 2013 16:53:48 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Alia Crittendon</title>
		<link>http://buildinternet.com/2009/06/charging-project-pricing-versus-hourly-rates/comment-page-1/#comment-33852</link>
		<dc:creator>Alia Crittendon</dc:creator>
		<pubDate>Wed, 28 Mar 2012 18:16:16 +0000</pubDate>
		<guid isPermaLink="false">http://buildinternet.com/?p=3553#comment-33852</guid>
		<description><![CDATA[This means superb. Exactly how in order to grab livlier in relation to diving]]></description>
		<content:encoded><![CDATA[<p>This means superb. Exactly how in order to grab livlier in relation to diving</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Louis Vuitton Monogram Multicolore Watercolor Speedy White M95752 Canada</title>
		<link>http://buildinternet.com/2009/06/charging-project-pricing-versus-hourly-rates/comment-page-1/#comment-33757</link>
		<dc:creator>Louis Vuitton Monogram Multicolore Watercolor Speedy White M95752 Canada</dc:creator>
		<pubDate>Tue, 27 Mar 2012 00:37:04 +0000</pubDate>
		<guid isPermaLink="false">http://buildinternet.com/?p=3553#comment-33757</guid>
		<description><![CDATA[The new Zune browser is surprisingly good, but not as good as the iPod&#039;s. It works well, but isn&#039;t as fast as Safari, and has a clunkier interface. If you occasionally plan on using the web browser that&#039;s not an issue, but if you&#039;re planning to browse the web alot from your PMP then the iPod&#039;s larger screen and better browser may be important.]]></description>
		<content:encoded><![CDATA[<p>The new Zune browser is surprisingly good, but not as good as the iPod&#8217;s. It works well, but isn&#8217;t as fast as Safari, and has a clunkier interface. If you occasionally plan on using the web browser that&#8217;s not an issue, but if you&#8217;re planning to browse the web alot from your PMP then the iPod&#8217;s larger screen and better browser may be important.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bowen</title>
		<link>http://buildinternet.com/2009/06/charging-project-pricing-versus-hourly-rates/comment-page-1/#comment-33150</link>
		<dc:creator>Bowen</dc:creator>
		<pubDate>Fri, 24 Feb 2012 07:05:44 +0000</pubDate>
		<guid isPermaLink="false">http://buildinternet.com/?p=3553#comment-33150</guid>
		<description><![CDATA[Highly amusing.]]></description>
		<content:encoded><![CDATA[<p>Highly amusing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jenni</title>
		<link>http://buildinternet.com/2009/06/charging-project-pricing-versus-hourly-rates/comment-page-1/#comment-30082</link>
		<dc:creator>Jenni</dc:creator>
		<pubDate>Thu, 21 Jul 2011 01:08:13 +0000</pubDate>
		<guid isPermaLink="false">http://buildinternet.com/?p=3553#comment-30082</guid>
		<description><![CDATA[I usually use the project pricing system with my clients.
Thank you for your great post.]]></description>
		<content:encoded><![CDATA[<p>I usually use the project pricing system with my clients.<br />
Thank you for your great post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad Maver</title>
		<link>http://buildinternet.com/2009/06/charging-project-pricing-versus-hourly-rates/comment-page-1/#comment-15125</link>
		<dc:creator>Brad Maver</dc:creator>
		<pubDate>Thu, 07 Oct 2010 05:21:42 +0000</pubDate>
		<guid isPermaLink="false">http://buildinternet.com/?p=3553#comment-15125</guid>
		<description><![CDATA[Great Post. Very useful information in here. Thanks for sharing!]]></description>
		<content:encoded><![CDATA[<p>Great Post. Very useful information in here. Thanks for sharing!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Berthold</title>
		<link>http://buildinternet.com/2009/06/charging-project-pricing-versus-hourly-rates/comment-page-1/#comment-12781</link>
		<dc:creator>Berthold</dc:creator>
		<pubDate>Wed, 14 Apr 2010 07:37:49 +0000</pubDate>
		<guid isPermaLink="false">http://buildinternet.com/?p=3553#comment-12781</guid>
		<description><![CDATA[Well you started out nicely laying out the pros of hourly rates, but towards the end you became a lot less verbose. I&#039;d like to take the liberty and fill in the blanks:

Hourly Rates
 
#designer
   + you will always get paid for your time on the project
   - your processes are more transparent, inviting the client to call you out on time wasted, even if you didn&#039;t

#client
   + good control over expenses, can stop you at any time if budget is tight
    - *will* feel the need to control how much time you spent to make sure they get their money&#039;s worth, essentially having to manage you (bad! They will apply their processes to your work, which most likely won&#039;t fit and will lead to conflict)

Project

#designer
   + it&#039;s easy to manage, you can be as efficient as you want and make a killing in hourly rates if you&#039;re good
   - unexpected issues are your problem, and may cause you to actually lose money on the project (if it gets too bad, you should renegotiate with the client. Be curteous, they don&#039;t owe you anything. You miscalculated.)

# client
   + it&#039;s easier to manage. They have a fixed budget and a fixed result.
   - it&#039;s harder for them to understand how the charge breaks down, and unless they a) get told what you do for their money and how long it will take and b) understand what value they get in the website they receive (more customers) they will try and negotiate until they undercut your bare minimum. Be verbose, and don&#039;t give in.

As mentioned before, ideally you&#039;d want to combine both systems - offer a flat rate but also tell the customer what is included and how they benefit from it all. Your estimates will get better and better with every project that you complete, provided you keep a running record of time spent and compare that vs. the target time for your hourly rate. You will also develop a keen sense on how long different processes should take you, and when you start running over/under budget.]]></description>
		<content:encoded><![CDATA[<p>Well you started out nicely laying out the pros of hourly rates, but towards the end you became a lot less verbose. I&#8217;d like to take the liberty and fill in the blanks:</p>
<p>Hourly Rates</p>
<p>#designer<br />
   + you will always get paid for your time on the project<br />
   &#8211; your processes are more transparent, inviting the client to call you out on time wasted, even if you didn&#8217;t</p>
<p>#client<br />
   + good control over expenses, can stop you at any time if budget is tight<br />
    &#8211; *will* feel the need to control how much time you spent to make sure they get their money&#8217;s worth, essentially having to manage you (bad! They will apply their processes to your work, which most likely won&#8217;t fit and will lead to conflict)</p>
<p>Project</p>
<p>#designer<br />
   + it&#8217;s easy to manage, you can be as efficient as you want and make a killing in hourly rates if you&#8217;re good<br />
   &#8211; unexpected issues are your problem, and may cause you to actually lose money on the project (if it gets too bad, you should renegotiate with the client. Be curteous, they don&#8217;t owe you anything. You miscalculated.)</p>
<p># client<br />
   + it&#8217;s easier to manage. They have a fixed budget and a fixed result.<br />
   &#8211; it&#8217;s harder for them to understand how the charge breaks down, and unless they a) get told what you do for their money and how long it will take and b) understand what value they get in the website they receive (more customers) they will try and negotiate until they undercut your bare minimum. Be verbose, and don&#8217;t give in.</p>
<p>As mentioned before, ideally you&#8217;d want to combine both systems &#8211; offer a flat rate but also tell the customer what is included and how they benefit from it all. Your estimates will get better and better with every project that you complete, provided you keep a running record of time spent and compare that vs. the target time for your hourly rate. You will also develop a keen sense on how long different processes should take you, and when you start running over/under budget.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jamie</title>
		<link>http://buildinternet.com/2009/06/charging-project-pricing-versus-hourly-rates/comment-page-1/#comment-7034</link>
		<dc:creator>Jamie</dc:creator>
		<pubDate>Sat, 08 Aug 2009 17:26:54 +0000</pubDate>
		<guid isPermaLink="false">http://buildinternet.com/?p=3553#comment-7034</guid>
		<description><![CDATA[Well, I&#039;m not a freelancer, but here&#039;s how it works at my company: we give clients a quote, which is usually a range (for example, $7500 - $10,000). Then we bill hourly for work, maintaining a spreadsheet that details how we spend the time. When it&#039;s time to bill the client, the project manager usually plays with the spreadsheet a bit depending on a number of factors. For example, if the bottom end of the quote is $7500 but we only bill $5000, he&#039;ll bump it up to within the quote range. If the client is especially difficult, he may also bump it up, and so on. 

So, I think the best solution is a mix of both. Seasoned web developers know how approximately how long a particular project will take. That&#039;s why we give a quote. Then, the client knows the range of the final bill, but they can still get an hour-by-hour breakdown of the work (which clients love to see, in my experience).
.-= Jamie´s last blog ..&lt;a href=&quot;http://jamienay.com/blog/personal/i-am-still-alive/&quot; rel=&quot;nofollow&quot;&gt;I am still alive&lt;/a&gt; =-.]]></description>
		<content:encoded><![CDATA[<p>Well, I&#8217;m not a freelancer, but here&#8217;s how it works at my company: we give clients a quote, which is usually a range (for example, $7500 &#8211; $10,000). Then we bill hourly for work, maintaining a spreadsheet that details how we spend the time. When it&#8217;s time to bill the client, the project manager usually plays with the spreadsheet a bit depending on a number of factors. For example, if the bottom end of the quote is $7500 but we only bill $5000, he&#8217;ll bump it up to within the quote range. If the client is especially difficult, he may also bump it up, and so on. </p>
<p>So, I think the best solution is a mix of both. Seasoned web developers know how approximately how long a particular project will take. That&#8217;s why we give a quote. Then, the client knows the range of the final bill, but they can still get an hour-by-hour breakdown of the work (which clients love to see, in my experience).<br />
.-= Jamie´s last blog ..<a href="http://jamienay.com/blog/personal/i-am-still-alive/" rel="nofollow">I am still alive</a> =-.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bathrobewarrior</title>
		<link>http://buildinternet.com/2009/06/charging-project-pricing-versus-hourly-rates/comment-page-1/#comment-6800</link>
		<dc:creator>Bathrobewarrior</dc:creator>
		<pubDate>Sun, 02 Aug 2009 03:20:39 +0000</pubDate>
		<guid isPermaLink="false">http://buildinternet.com/?p=3553#comment-6800</guid>
		<description><![CDATA[Excellent advice!  :)
.-= Bathrobewarrior´s last blog ..&lt;a href=&quot;http://www.bathrobewarrior.com/blog/2009/7/2/some-tips-on-images-for-the-web.html&quot; rel=&quot;nofollow&quot;&gt;Some tips on images for the web&lt;/a&gt; =-.]]></description>
		<content:encoded><![CDATA[<p>Excellent advice!  :)<br />
.-= Bathrobewarrior´s last blog ..<a href="http://www.bathrobewarrior.com/blog/2009/7/2/some-tips-on-images-for-the-web.html" rel="nofollow">Some tips on images for the web</a> =-.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clay S</title>
		<link>http://buildinternet.com/2009/06/charging-project-pricing-versus-hourly-rates/comment-page-1/#comment-5623</link>
		<dc:creator>Clay S</dc:creator>
		<pubDate>Mon, 29 Jun 2009 16:02:29 +0000</pubDate>
		<guid isPermaLink="false">http://buildinternet.com/?p=3553#comment-5623</guid>
		<description><![CDATA[Great post!  Project pricing is our preferred method as well, and I think it works out well for both us and our clients.  We&#039;re bound to produce a final deliverable and it also eliminates any guesswork or suspicion on their end, where they worry if we&#039;re charging too many hours, etc.  We also try to even avoid charging hourly for support and try to cover that cost with a monthly licensing fee.  About a year ago, I wrote a post on our approach to billing and service that you might find interesting: http://www.newmediacampaigns.com/page/when-companies-dont-fear-customer-support-everybody-wins
.-= Clay S´s last blog ..&lt;a href=&quot;http://feedproxy.google.com/~r/newmediacampaigns/~3/Eh6zAe2DySc/moving-your-script-tags-the-quickest-way-to-improve-site-performance&quot; rel=&quot;nofollow&quot;&gt;Moving your script tags: The quickest way to improve site performance&lt;/a&gt; =-.]]></description>
		<content:encoded><![CDATA[<p>Great post!  Project pricing is our preferred method as well, and I think it works out well for both us and our clients.  We&#8217;re bound to produce a final deliverable and it also eliminates any guesswork or suspicion on their end, where they worry if we&#8217;re charging too many hours, etc.  We also try to even avoid charging hourly for support and try to cover that cost with a monthly licensing fee.  About a year ago, I wrote a post on our approach to billing and service that you might find interesting: <a href="http://www.newmediacampaigns.com/page/when-companies-dont-fear-customer-support-everybody-wins" rel="nofollow">http://www.newmediacampaigns.com/page/when-companies-dont-fear-customer-support-everybody-wins</a><br />
.-= Clay S´s last blog ..<a href="http://feedproxy.google.com/~r/newmediacampaigns/~3/Eh6zAe2DySc/moving-your-script-tags-the-quickest-way-to-improve-site-performance" rel="nofollow">Moving your script tags: The quickest way to improve site performance</a> =-.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Project Pricing vs Hourly Rates &#124; Design Shack</title>
		<link>http://buildinternet.com/2009/06/charging-project-pricing-versus-hourly-rates/comment-page-1/#comment-5552</link>
		<dc:creator>Project Pricing vs Hourly Rates &#124; Design Shack</dc:creator>
		<pubDate>Thu, 25 Jun 2009 08:00:40 +0000</pubDate>
		<guid isPermaLink="false">http://buildinternet.com/?p=3553#comment-5552</guid>
		<description><![CDATA[[...] View Post [...]]]></description>
		<content:encoded><![CDATA[<p>[...] View Post [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using memcached
Database Caching using memcached
Object Caching 411/440 objects using disk: basic

Served from: buildinternet.com @ 2013-05-19 01:41:49 -->