<?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"
	>
<channel>
	<title>Comments on: Hourly vs. Fixed Pricing</title>
	<atom:link href="http://freelanceswitch.com/money/hourly-vs-fixed-pricing/feed/" rel="self" type="application/rss+xml" />
	<link>http://freelanceswitch.com/money/hourly-vs-fixed-pricing/</link>
	<description>Freelance Advice and Freelance Jobs - FreelanceSwitch</description>
	<pubDate>Wed, 03 Dec 2008 06:35:28 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Luke</title>
		<link>http://freelanceswitch.com/money/hourly-vs-fixed-pricing/#comment-30659</link>
		<dc:creator>Luke</dc:creator>
		<pubDate>Wed, 19 Nov 2008 16:24:19 +0000</pubDate>
		<guid isPermaLink="false">http://freelanceswitch.com/money/hourly-vs-fixed-pricing/#comment-30659</guid>
		<description>@Adrian I think that if you're charging flat rate, you're taking on the risk. If you take on the risk, you should also be able to accept the benefits. Some jobs you will be eating the extra hours, some jobs there might be some hours left; it will balance itself out. It might be a good PR move to charge less than you've quoted, but the client has agreed to the price and they see it as being worth what you quoted. Charge the full amount unless you need to grease the wheels.</description>
		<content:encoded><![CDATA[<p>@Adrian I think that if you&#8217;re charging flat rate, you&#8217;re taking on the risk. If you take on the risk, you should also be able to accept the benefits. Some jobs you will be eating the extra hours, some jobs there might be some hours left; it will balance itself out. It might be a good PR move to charge less than you&#8217;ve quoted, but the client has agreed to the price and they see it as being worth what you quoted. Charge the full amount unless you need to grease the wheels.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrian Rodriguez</title>
		<link>http://freelanceswitch.com/money/hourly-vs-fixed-pricing/#comment-29527</link>
		<dc:creator>Adrian Rodriguez</dc:creator>
		<pubDate>Mon, 20 Oct 2008 18:17:10 +0000</pubDate>
		<guid isPermaLink="false">http://freelanceswitch.com/money/hourly-vs-fixed-pricing/#comment-29527</guid>
		<description>Let's say I charge $20/hr and I quote a project for $400 which is equal to 20 work hours, but I finish in 15. Would it be a smart thing to just ask for the actual price? Should I tell the client that it's the way I price and if I go over 20 hours should I charge for the quote or continue charging?</description>
		<content:encoded><![CDATA[<p>Let&#8217;s say I charge $20/hr and I quote a project for $400 which is equal to 20 work hours, but I finish in 15. Would it be a smart thing to just ask for the actual price? Should I tell the client that it&#8217;s the way I price and if I go over 20 hours should I charge for the quote or continue charging?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason</title>
		<link>http://freelanceswitch.com/money/hourly-vs-fixed-pricing/#comment-23988</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Sun, 22 Jun 2008 15:48:42 +0000</pubDate>
		<guid isPermaLink="false">http://freelanceswitch.com/money/hourly-vs-fixed-pricing/#comment-23988</guid>
		<description>Hey, this is an old posting, but it provides some very good insight. I have a model similar to Pawel's above, I usually charge by the project, with the cost averaging out to the number of hours I would put in anyway. However, I do have a clause in the agreement that details the amount of revisions and adjustments the client has so they won't be stomping you with new ideas or changes every week, expecting to pay the original price. I had to learn that the hard way, but so far this hybrid of sorts has worked out well for me.</description>
		<content:encoded><![CDATA[<p>Hey, this is an old posting, but it provides some very good insight. I have a model similar to Pawel&#8217;s above, I usually charge by the project, with the cost averaging out to the number of hours I would put in anyway. However, I do have a clause in the agreement that details the amount of revisions and adjustments the client has so they won&#8217;t be stomping you with new ideas or changes every week, expecting to pay the original price. I had to learn that the hard way, but so far this hybrid of sorts has worked out well for me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#187; What You Should Charge &#38; Why You Should Stick Your Price :: Blog Archive :: Positive Space :: Discussions on Culture, Design, Technology, &#38; Music ::</title>
		<link>http://freelanceswitch.com/money/hourly-vs-fixed-pricing/#comment-15958</link>
		<dc:creator>&#187; What You Should Charge &#38; Why You Should Stick Your Price :: Blog Archive :: Positive Space :: Discussions on Culture, Design, Technology, &#38; Music ::</dc:creator>
		<pubDate>Tue, 05 Feb 2008 03:52:13 +0000</pubDate>
		<guid isPermaLink="false">http://freelanceswitch.com/money/hourly-vs-fixed-pricing/#comment-15958</guid>
		<description>[...] Resources:  Freelance Switch Rates Calculator  Coroflot Design Salary Survey   9 Factors to Consider When Determinging Your Price Hourly vs. Fixed Pricing 7 Tips on Quoting Freelance Projects   Posted By: [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Resources:  Freelance Switch Rates Calculator  Coroflot Design Salary Survey   9 Factors to Consider When Determinging Your Price Hourly vs. Fixed Pricing 7 Tips on Quoting Freelance Projects   Posted By: [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Virtually yours, &#187; Blog Archive &#187; Freelance Races: Charging hourly vs. Flat Rates</title>
		<link>http://freelanceswitch.com/money/hourly-vs-fixed-pricing/#comment-14813</link>
		<dc:creator>Virtually yours, &#187; Blog Archive &#187; Freelance Races: Charging hourly vs. Flat Rates</dc:creator>
		<pubDate>Mon, 14 Jan 2008 04:24:32 +0000</pubDate>
		<guid isPermaLink="false">http://freelanceswitch.com/money/hourly-vs-fixed-pricing/#comment-14813</guid>
		<description>[...] recently stumbled upon a great article titled Hourly vs. Fixed Pricing over at Freelance Switch. There is a pretty decent discussion of the topic in the article&#8217;s [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] recently stumbled upon a great article titled Hourly vs. Fixed Pricing over at Freelance Switch. There is a pretty decent discussion of the topic in the article&#8217;s [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Corporate Blogging Weblog &#187; Honorare in der PR-Branche</title>
		<link>http://freelanceswitch.com/money/hourly-vs-fixed-pricing/#comment-10629</link>
		<dc:creator>Corporate Blogging Weblog &#187; Honorare in der PR-Branche</dc:creator>
		<pubDate>Fri, 02 Nov 2007 16:20:57 +0000</pubDate>
		<guid isPermaLink="false">http://freelanceswitch.com/money/hourly-vs-fixed-pricing/#comment-10629</guid>
		<description>[...] Hourly vs. Fixed Pricing [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Hourly vs. Fixed Pricing [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mcdave.net &#187; links for 2007-08-15</title>
		<link>http://freelanceswitch.com/money/hourly-vs-fixed-pricing/#comment-6360</link>
		<dc:creator>mcdave.net &#187; links for 2007-08-15</dc:creator>
		<pubDate>Wed, 15 Aug 2007 06:24:24 +0000</pubDate>
		<guid isPermaLink="false">http://freelanceswitch.com/money/hourly-vs-fixed-pricing/#comment-6360</guid>
		<description>[...] » Hourly vs. Fixed Pricing (tags: freelance business tips work pricing) [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] » Hourly vs. Fixed Pricing (tags: freelance business tips work pricing) [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: arun</title>
		<link>http://freelanceswitch.com/money/hourly-vs-fixed-pricing/#comment-1404</link>
		<dc:creator>arun</dc:creator>
		<pubDate>Mon, 07 May 2007 17:32:35 +0000</pubDate>
		<guid isPermaLink="false">http://freelanceswitch.com/money/hourly-vs-fixed-pricing/#comment-1404</guid>
		<description>get me those freelancers contacts. i can hire them and give some work and pay money from my wallet and i will also ask that is it your hourly rate</description>
		<content:encoded><![CDATA[<p>get me those freelancers contacts. i can hire them and give some work and pay money from my wallet and i will also ask that is it your hourly rate</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pawel</title>
		<link>http://freelanceswitch.com/money/hourly-vs-fixed-pricing/#comment-1286</link>
		<dc:creator>Pawel</dc:creator>
		<pubDate>Sat, 05 May 2007 20:37:41 +0000</pubDate>
		<guid isPermaLink="false">http://freelanceswitch.com/money/hourly-vs-fixed-pricing/#comment-1286</guid>
		<description>I usually charge per project. In fact it slowly becomes a standard in Ireland anyways. The price is based on projected time that will be required to complete work and of course the hourly rate, although I have different rates for different tasks, so the client gets a breakdown. I ALWAYS sign a contract with the client and require 30% upfront, otherwise I do not even start thinking of the project. Also in the contract I have cancellation clause, which states the percentage of the remaining fee (after the upfront) that the client has to pay prior to project cancellation (there are 3 different rates due to different reasons for cancellation). The contract also states that I allow for 2 corrections / revisions, anything above that not due to designers fault will be charge at hourly rate (defined in the contract).
I guess that covers me totally and the client also knows what they are standing on. Then what's left to do is a good time management on the project ...</description>
		<content:encoded><![CDATA[<p>I usually charge per project. In fact it slowly becomes a standard in Ireland anyways. The price is based on projected time that will be required to complete work and of course the hourly rate, although I have different rates for different tasks, so the client gets a breakdown. I ALWAYS sign a contract with the client and require 30% upfront, otherwise I do not even start thinking of the project. Also in the contract I have cancellation clause, which states the percentage of the remaining fee (after the upfront) that the client has to pay prior to project cancellation (there are 3 different rates due to different reasons for cancellation). The contract also states that I allow for 2 corrections / revisions, anything above that not due to designers fault will be charge at hourly rate (defined in the contract).<br />
I guess that covers me totally and the client also knows what they are standing on. Then what&#8217;s left to do is a good time management on the project &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mave</title>
		<link>http://freelanceswitch.com/money/hourly-vs-fixed-pricing/#comment-1285</link>
		<dc:creator>mave</dc:creator>
		<pubDate>Sat, 05 May 2007 18:31:53 +0000</pubDate>
		<guid isPermaLink="false">http://freelanceswitch.com/money/hourly-vs-fixed-pricing/#comment-1285</guid>
		<description>I generally charge hourly and bill bi-weekly. 

1] at the beginning of a project, I give the client an estimate of the hours (and therefore cost) to complete the project. they are made aware that I am charging hourly, so that anything above the estimated # of hours will be billed hourly. 

2] during the course of the work, I regularly update them on where we are at in terms of hours, and what is left. I warn them if any delays or changes in scope are likely to affect the # of hours it takes. if they accept this change in cost, we move forward with the changes.

3] invoices are payable within 7 days of receipt. for new clients or slow payers, a deposit (based on a percentage of total # of estimated hours) is required before work can start.

in the rare cases when I do work fixed-rate (and that generally only happens for a] retainers and really large, long-term projects or b] clients who are working with a fixed budget), I always ask for some $ up front. even in the case of fixed-rate pricing, I am still billing based on hours spent. I'm just calculating beforehand how many hours it will take.

I have tried so many different billing methods over the years, and this one is by far the best balance between giving clients something to budget a project with, and giving me assurance that I will be paid for what I do. I am not a bank, willing/able to extend credit to clients for work being done, and that's what it basically amounts to if I work now and get paid later.

this method also puts the responsibility for scope change squarely where it belongs: with the client. they are made aware, throughout the course of the project, exactly how each change in the plan will affect the price. over time, if the client is a regular, it means that a client learns to rein him/herself in, and it also means they develop a real sense of the value of my time and effort. clients become more efficient, waste less of my time, and have a greater respect for what exactly goes into what I do.

as for "the honesty model", I think that is a given when working for an hourly rate. we charge for what we did. rarely - rarely will that be less than what was estimated for (clients love to expand projects as they go along), but when it does happen, of course the client is charged for actual hours spent. and in reference to the hints about "time management" and "being forced to work efficiently", are we seriously sitting here implying that those who charge hourly are going to waste project time? I take exception to the idea that freelancers need to be "made honest" in terms of hours they charge for or how hard/fast they work. something about that really turns me off. we are professionals, not schoolchildren.

if anything, I think the opposite is far more common: giving clients a lot more than they paid for. I think most freelancers are too client-driven, and don't think enough about protecting their own interests. we habitually under-bid and under-charge. we regularly put in more hours than we bill for, just so we can add that "extra touch" that will wow the client and make the project more portfolio-worthy. we are ridiculously accommodating, and bend over backwards to give the client whatever he/she wants, regardless of how tricky it is to plan, execute and bill for. if anything, we need to learn how to protect our interests and draw fair boundaries around how we work so that our bank accounts and schedules aren't adversely impacted by the way we work.</description>
		<content:encoded><![CDATA[<p>I generally charge hourly and bill bi-weekly. </p>
<p>1] at the beginning of a project, I give the client an estimate of the hours (and therefore cost) to complete the project. they are made aware that I am charging hourly, so that anything above the estimated # of hours will be billed hourly. </p>
<p>2] during the course of the work, I regularly update them on where we are at in terms of hours, and what is left. I warn them if any delays or changes in scope are likely to affect the # of hours it takes. if they accept this change in cost, we move forward with the changes.</p>
<p>3] invoices are payable within 7 days of receipt. for new clients or slow payers, a deposit (based on a percentage of total # of estimated hours) is required before work can start.</p>
<p>in the rare cases when I do work fixed-rate (and that generally only happens for a] retainers and really large, long-term projects or b] clients who are working with a fixed budget), I always ask for some $ up front. even in the case of fixed-rate pricing, I am still billing based on hours spent. I&#8217;m just calculating beforehand how many hours it will take.</p>
<p>I have tried so many different billing methods over the years, and this one is by far the best balance between giving clients something to budget a project with, and giving me assurance that I will be paid for what I do. I am not a bank, willing/able to extend credit to clients for work being done, and that&#8217;s what it basically amounts to if I work now and get paid later.</p>
<p>this method also puts the responsibility for scope change squarely where it belongs: with the client. they are made aware, throughout the course of the project, exactly how each change in the plan will affect the price. over time, if the client is a regular, it means that a client learns to rein him/herself in, and it also means they develop a real sense of the value of my time and effort. clients become more efficient, waste less of my time, and have a greater respect for what exactly goes into what I do.</p>
<p>as for &#8220;the honesty model&#8221;, I think that is a given when working for an hourly rate. we charge for what we did. rarely - rarely will that be less than what was estimated for (clients love to expand projects as they go along), but when it does happen, of course the client is charged for actual hours spent. and in reference to the hints about &#8220;time management&#8221; and &#8220;being forced to work efficiently&#8221;, are we seriously sitting here implying that those who charge hourly are going to waste project time? I take exception to the idea that freelancers need to be &#8220;made honest&#8221; in terms of hours they charge for or how hard/fast they work. something about that really turns me off. we are professionals, not schoolchildren.</p>
<p>if anything, I think the opposite is far more common: giving clients a lot more than they paid for. I think most freelancers are too client-driven, and don&#8217;t think enough about protecting their own interests. we habitually under-bid and under-charge. we regularly put in more hours than we bill for, just so we can add that &#8220;extra touch&#8221; that will wow the client and make the project more portfolio-worthy. we are ridiculously accommodating, and bend over backwards to give the client whatever he/she wants, regardless of how tricky it is to plan, execute and bill for. if anything, we need to learn how to protect our interests and draw fair boundaries around how we work so that our bank accounts and schedules aren&#8217;t adversely impacted by the way we work.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
