<?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: Tips on the Structure and Timing of Payments for Web Site Projects</title>
	<atom:link href="http://www.webdesignfromscratch.com/business/payment-timing-structure-tips/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.webdesignfromscratch.com/business/payment-timing-structure-tips/</link>
	<description>Your complete web design guide</description>
	<lastBuildDate>Fri, 10 Feb 2012 14:36:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Ben Hunt</title>
		<link>http://www.webdesignfromscratch.com/business/payment-timing-structure-tips/#comment-5148</link>
		<dc:creator>Ben Hunt</dc:creator>
		<pubDate>Thu, 21 Apr 2011 09:17:20 +0000</pubDate>
		<guid isPermaLink="false">#comment-5148</guid>
		<description>Hi Jeana. 4 payments of 25% would mean there&#039;s less commitment up-front, and your revenue will come through slower. The general principle is that you should be paid (mostly) up-front for each phase of work, which limits your exposure. If a client is committed to the project, they should not object. But it also encourages you to keep working hard. To get paid too much up-front would create less incentive. So it&#039;s a balancing act.

The way we have it set up, the client would get the PSD artwork if they walked away at the end of the design phase (i.e. having paid 50%), so we would be covered.

Regarding refunding of payments, we never made this explicit in proposals, although it may have been in our Ts &amp; Cs. These days, as we are only taking on one web project per month, we are now requesting explicitly non-refundable deposits from clients who wish to book us for a particular calendar month.</description>
		<content:encoded><![CDATA[<p>Hi Jeana. 4 payments of 25% would mean there&#8217;s less commitment up-front, and your revenue will come through slower. The general principle is that you should be paid (mostly) up-front for each phase of work, which limits your exposure. If a client is committed to the project, they should not object. But it also encourages you to keep working hard. To get paid too much up-front would create less incentive. So it&#8217;s a balancing act.</p>
<p>The way we have it set up, the client would get the PSD artwork if they walked away at the end of the design phase (i.e. having paid 50%), so we would be covered.</p>
<p>Regarding refunding of payments, we never made this explicit in proposals, although it may have been in our Ts &#038; Cs. These days, as we are only taking on one web project per month, we are now requesting explicitly non-refundable deposits from clients who wish to book us for a particular calendar month.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeana</title>
		<link>http://www.webdesignfromscratch.com/business/payment-timing-structure-tips/#comment-5102</link>
		<dc:creator>Jeana</dc:creator>
		<pubDate>Mon, 18 Apr 2011 21:44:08 +0000</pubDate>
		<guid isPermaLink="false">#comment-5102</guid>
		<description>I&#039;ve been using a similar method, but with 4 payments of 25%, but I&#039;ve noticed a lot of scope creeping problems at wrap-up.  I&#039;m sure that using your method would help with that!  I&#039;m curious about how you deal with the &quot;design assets&quot;.  We also use the end of the design phase as a milestone and payment point (2nd 25% payment), but I&#039;ve never stopped to think about what we would do if someone pulled out of the project at that point.  Would we hand over the PSD files and call it even?  Also, I&#039;ve never placed any conditions in my agreement about the down payment or installments being non-refundable.  Is that something you would recommend?  Thanks for the article!  It was nice to get some outside perspective on this for a change. :)</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been using a similar method, but with 4 payments of 25%, but I&#8217;ve noticed a lot of scope creeping problems at wrap-up.  I&#8217;m sure that using your method would help with that!  I&#8217;m curious about how you deal with the &#8220;design assets&#8221;.  We also use the end of the design phase as a milestone and payment point (2nd 25% payment), but I&#8217;ve never stopped to think about what we would do if someone pulled out of the project at that point.  Would we hand over the PSD files and call it even?  Also, I&#8217;ve never placed any conditions in my agreement about the down payment or installments being non-refundable.  Is that something you would recommend?  Thanks for the article!  It was nice to get some outside perspective on this for a change. <img src='http://www.webdesignfromscratch.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PAUL TRAPANI</title>
		<link>http://www.webdesignfromscratch.com/business/payment-timing-structure-tips/#comment-4160</link>
		<dc:creator>PAUL TRAPANI</dc:creator>
		<pubDate>Sat, 12 Feb 2011 00:21:37 +0000</pubDate>
		<guid isPermaLink="false">#comment-4160</guid>
		<description>This is exactly the type of guideline I was looking for to write up my own payment structure for clients.  Everything in this article is short and to the point, perfect.  Thank you for posting it!</description>
		<content:encoded><![CDATA[<p>This is exactly the type of guideline I was looking for to write up my own payment structure for clients.  Everything in this article is short and to the point, perfect.  Thank you for posting it!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lisa</title>
		<link>http://www.webdesignfromscratch.com/business/payment-timing-structure-tips/#comment-3354</link>
		<dc:creator>Lisa</dc:creator>
		<pubDate>Wed, 01 Sep 2010 15:26:52 +0000</pubDate>
		<guid isPermaLink="false">#comment-3354</guid>
		<description>Another lesson I learned is make sure you define your scope and make it part of the official contract. I recently had a client that I did a double-don&#039;t...didn&#039;t have a contract and the scope wasn&#039;t clearly defined. Every day even though the client had launched their site, they came back for more modifications. Eventually I became the bad guy because I had to eventually say &quot;no&quot; and draw the line to say the project was delivered &quot;beyond the original scope&quot; and everything else was an enhancement. It was an expensive lesson on my part because of the hundreds of hours I put into the site (yes hundreds) with the scope-creeping and walked away feeling I truly wasn&#039;t compensated.</description>
		<content:encoded><![CDATA[<p>Another lesson I learned is make sure you define your scope and make it part of the official contract. I recently had a client that I did a double-don&#8217;t&#8230;didn&#8217;t have a contract and the scope wasn&#8217;t clearly defined. Every day even though the client had launched their site, they came back for more modifications. Eventually I became the bad guy because I had to eventually say &#8220;no&#8221; and draw the line to say the project was delivered &#8220;beyond the original scope&#8221; and everything else was an enhancement. It was an expensive lesson on my part because of the hundreds of hours I put into the site (yes hundreds) with the scope-creeping and walked away feeling I truly wasn&#8217;t compensated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lisa</title>
		<link>http://www.webdesignfromscratch.com/business/payment-timing-structure-tips/#comment-3353</link>
		<dc:creator>Lisa</dc:creator>
		<pubDate>Wed, 01 Sep 2010 15:17:24 +0000</pubDate>
		<guid isPermaLink="false">#comment-3353</guid>
		<description>This is great information! I really like your approach to the payment schedule and am considering adopting it myself. I usually do 50/50 - 50% at sign-up and 50% just before launch, but as you pointed out, you get some clients that keep making more demands and modifications, and it begins to feel like a never-ending project where you never see your compensation for the time you invest. 

I&#039;d be curious to read about your approach to scope changes and maintenance.</description>
		<content:encoded><![CDATA[<p>This is great information! I really like your approach to the payment schedule and am considering adopting it myself. I usually do 50/50 &#8211; 50% at sign-up and 50% just before launch, but as you pointed out, you get some clients that keep making more demands and modifications, and it begins to feel like a never-ending project where you never see your compensation for the time you invest. </p>
<p>I&#8217;d be curious to read about your approach to scope changes and maintenance.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

