<?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: Assigning Value</title>
	<atom:link href="http://startupfiance.com/2010/assigning-value/feed/" rel="self" type="application/rss+xml" />
	<link>http://startupfiance.com/2010/assigning-value/</link>
	<description>Infinitely engaged to a serial entrepreneur, and becoming one of my own.</description>
	<lastBuildDate>Thu, 29 Dec 2011 07:13:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Big Sis</title>
		<link>http://startupfiance.com/2010/assigning-value/comment-page-1/#comment-889</link>
		<dc:creator>Big Sis</dc:creator>
		<pubDate>Sat, 27 Feb 2010 18:33:38 +0000</pubDate>
		<guid isPermaLink="false">http://startupfiance.com/?p=747#comment-889</guid>
		<description>Giving some thought to the question, I would offer the following.  I don&#039;t think it&#039;s wrong to offer a &quot;sliding scale&quot; of pricing, however, it should depend on the system that you are using.  The company I work for certainly offers a &quot;sliding scale&quot; although we don&#039;t call it that.  We price our services based on several factors, such as, what is the long term value of the client, what particular services they are requesting, how easy/hard of a client they are to deal with (i.e. do they pay promptly, are they clear about what they want or change their minds throughout the process), etc.  With that being said, you also want to give yourself several bottom line price levels for what your time is worth either per hour or per project.  As you are thinking about how to price a project you should think about this and other questions, &quot;Is the particular assignment fairly routine, or does it demand a certain level of expertise that fewer people possess?&quot;  Don&#039;t sell yourself short just because of someone&#039;s &quot;perceived&quot; inability to pay.  I guess all that being said, you need to evaluate each particular project based on those factors (and others that you value) and price each project.  I wouldn&#039;t make the prices wildly different per job, but certainly adjustable.  Hope that helps or at least gives you another opinion.</description>
		<content:encoded><![CDATA[<p>Giving some thought to the question, I would offer the following.  I don&#8217;t think it&#8217;s wrong to offer a &#8220;sliding scale&#8221; of pricing, however, it should depend on the system that you are using.  The company I work for certainly offers a &#8220;sliding scale&#8221; although we don&#8217;t call it that.  We price our services based on several factors, such as, what is the long term value of the client, what particular services they are requesting, how easy/hard of a client they are to deal with (i.e. do they pay promptly, are they clear about what they want or change their minds throughout the process), etc.  With that being said, you also want to give yourself several bottom line price levels for what your time is worth either per hour or per project.  As you are thinking about how to price a project you should think about this and other questions, &#8220;Is the particular assignment fairly routine, or does it demand a certain level of expertise that fewer people possess?&#8221;  Don&#8217;t sell yourself short just because of someone&#8217;s &#8220;perceived&#8221; inability to pay.  I guess all that being said, you need to evaluate each particular project based on those factors (and others that you value) and price each project.  I wouldn&#8217;t make the prices wildly different per job, but certainly adjustable.  Hope that helps or at least gives you another opinion.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

