<?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: Scheduling Gig Challenges	</title>
	<atom:link href="https://jessewarden.com/2008/09/scheduling-gig-challenges.html/feed" rel="self" type="application/rss+xml" />
	<link>https://jessewarden.com/2008/09/scheduling-gig-challenges.html</link>
	<description>Software &#124; Fitness &#124; Gaming</description>
	<lastBuildDate>Wed, 12 Nov 2008 18:12:45 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Daryl James		</title>
		<link>https://jessewarden.com/2008/09/scheduling-gig-challenges.html/comment-page-1#comment-134582</link>

		<dc:creator><![CDATA[Daryl James]]></dc:creator>
		<pubDate>Wed, 12 Nov 2008 18:12:45 +0000</pubDate>
		<guid isPermaLink="false">http://jessewarden.com/?p=1285#comment-134582</guid>

					<description><![CDATA[Jesse, in my humble experience, it comes down to the quality of the leads.  Because it&#039;s always a struggle to balance between getting the work and doing the work, I have been trying different systems for the &quot;getting&quot; part.  Right now, I&#039;ve been successful developing relationships through oDesk.  There&#039;s no upfront cost (only a % for managing the process), and I&#039;ve personally experienced a greater than 70% follow-through on the bids I put out there (I was tired of spending tons of time bidding just for people who are &quot;shopping prices&quot; and wasting my time...but so far, I haven&#039;t had seen that here).  I want to be upfront in that I work with oDesk, and you are welcome to check out my profile there (same name).  It&#039;s definitely helped me to even out my freelance workload.]]></description>
			<content:encoded><![CDATA[<p>Jesse, in my humble experience, it comes down to the quality of the leads.  Because it&#8217;s always a struggle to balance between getting the work and doing the work, I have been trying different systems for the &#8220;getting&#8221; part.  Right now, I&#8217;ve been successful developing relationships through oDesk.  There&#8217;s no upfront cost (only a % for managing the process), and I&#8217;ve personally experienced a greater than 70% follow-through on the bids I put out there (I was tired of spending tons of time bidding just for people who are &#8220;shopping prices&#8221; and wasting my time&#8230;but so far, I haven&#8217;t had seen that here).  I want to be upfront in that I work with oDesk, and you are welcome to check out my profile there (same name).  It&#8217;s definitely helped me to even out my freelance workload.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Deb		</title>
		<link>https://jessewarden.com/2008/09/scheduling-gig-challenges.html/comment-page-1#comment-125225</link>

		<dc:creator><![CDATA[Deb]]></dc:creator>
		<pubDate>Thu, 25 Sep 2008 21:15:14 +0000</pubDate>
		<guid isPermaLink="false">http://jessewarden.com/?p=1285#comment-125225</guid>

					<description><![CDATA[Anyone in the Seattle area with strong Flash/AS3 skills interested in a 6 month contract?  dtamburri@gmail.com]]></description>
			<content:encoded><![CDATA[<p>Anyone in the Seattle area with strong Flash/AS3 skills interested in a 6 month contract?  <a href="mailto:dtamburri@gmail.com">dtamburri@gmail.com</a></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Joeflash		</title>
		<link>https://jessewarden.com/2008/09/scheduling-gig-challenges.html/comment-page-1#comment-124682</link>

		<dc:creator><![CDATA[Joeflash]]></dc:creator>
		<pubDate>Sun, 21 Sep 2008 04:28:16 +0000</pubDate>
		<guid isPermaLink="false">http://jessewarden.com/?p=1285#comment-124682</guid>

					<description><![CDATA[I can&#039;t purport to be an expert at balancing steady freelance work, but I&#039;ve learned a few things that seem to have worked well for me in the last few years.

1) Pay yourself first. I learned this from a good friend of mine David Stiller, and it works like a charm. When I get a cheque, I take off what I need to live, and bank the rest into an &quot;income account.&quot; During the lean weeks I pay myself from the account as if I&#039;m getting paid for client work. The ups and downs of freelancing income level out, and I can concentrate on getting steady work not to afford rent this month, but to boost the median average of my &quot;pay&quot;.

2) Most of my work comes from clients emailing me, either through google, lists or word of mouth, fortunately. If I&#039;m on a gig, I don&#039;t tell prospective clients  yes or no; I give them a &quot;conditional yes.&quot; Ideally this will result in a few potentials in the queue by the time one contract ends, so a few weeks before that contract is over, I contact the potentials I&#039;ve been in conversation with and ask them to get serious: whichever one signs on the dotted line first wins. Using this strategy (and due to the prosperity of the market, no doubt) I find I actually have to schedule down time.

3) I don&#039;t take on contracts less than one month, preferably not less than three months. So I don&#039;t have to play the game &quot;should I take longer or the shorter project?&quot; It also means I don&#039;t take on much creative agency or Flash work like I used to (higher pressure, shorter deadlines) -- it pre-qualifies the more serious clients, and allows me to do more Flex app dev projects.

4) I never quote a flat rate. Been burned too many times, so I don&#039;t do it. Flat rates can get you into bidding wars and crap like that, and I don&#039;t need the hassle. But getting paid by the hour comes with a commitment to the client for regular communication, status reports, spec implementation timelines, and the like, so the client knows I won&#039;t build their app like a highway construction crew ;) I also indicate a weekly range, like 30-40 hours per week, which gives their bean counters a chance to do the math.

5) If I have down time I write articles or tutorials for which I get paid, and I also use this as learning time. So it&#039;s good filler and allows me to keep an income flow during lulls. (Books are another story ;)]]></description>
			<content:encoded><![CDATA[<p>I can&#8217;t purport to be an expert at balancing steady freelance work, but I&#8217;ve learned a few things that seem to have worked well for me in the last few years.</p>
<p>1) Pay yourself first. I learned this from a good friend of mine David Stiller, and it works like a charm. When I get a cheque, I take off what I need to live, and bank the rest into an &#8220;income account.&#8221; During the lean weeks I pay myself from the account as if I&#8217;m getting paid for client work. The ups and downs of freelancing income level out, and I can concentrate on getting steady work not to afford rent this month, but to boost the median average of my &#8220;pay&#8221;.</p>
<p>2) Most of my work comes from clients emailing me, either through google, lists or word of mouth, fortunately. If I&#8217;m on a gig, I don&#8217;t tell prospective clients  yes or no; I give them a &#8220;conditional yes.&#8221; Ideally this will result in a few potentials in the queue by the time one contract ends, so a few weeks before that contract is over, I contact the potentials I&#8217;ve been in conversation with and ask them to get serious: whichever one signs on the dotted line first wins. Using this strategy (and due to the prosperity of the market, no doubt) I find I actually have to schedule down time.</p>
<p>3) I don&#8217;t take on contracts less than one month, preferably not less than three months. So I don&#8217;t have to play the game &#8220;should I take longer or the shorter project?&#8221; It also means I don&#8217;t take on much creative agency or Flash work like I used to (higher pressure, shorter deadlines) &#8212; it pre-qualifies the more serious clients, and allows me to do more Flex app dev projects.</p>
<p>4) I never quote a flat rate. Been burned too many times, so I don&#8217;t do it. Flat rates can get you into bidding wars and crap like that, and I don&#8217;t need the hassle. But getting paid by the hour comes with a commitment to the client for regular communication, status reports, spec implementation timelines, and the like, so the client knows I won&#8217;t build their app like a highway construction crew ;) I also indicate a weekly range, like 30-40 hours per week, which gives their bean counters a chance to do the math.</p>
<p>5) If I have down time I write articles or tutorials for which I get paid, and I also use this as learning time. So it&#8217;s good filler and allows me to keep an income flow during lulls. (Books are another story ;)</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Zack Jordan		</title>
		<link>https://jessewarden.com/2008/09/scheduling-gig-challenges.html/comment-page-1#comment-123426</link>

		<dc:creator><![CDATA[Zack Jordan]]></dc:creator>
		<pubDate>Mon, 15 Sep 2008 14:33:07 +0000</pubDate>
		<guid isPermaLink="false">http://jessewarden.com/?p=1285#comment-123426</guid>

					<description><![CDATA[I actually haven&#039;t run into a dry spell since I went freelance last year, but I know that&#039;s just because the market is so hot right now for AS developers.  My main problem is continual overbooking- mainly because everything sounds like so much &lt;em&gt;fun&lt;/em&gt;.  When a client calls me and wants an app that will do all these awesome things, I often find myself getting extremely optimistic about what I can accomplish during the timeframe given.  And then of course I end up killing myself with multiple simultaneous projects.

So I guess the skill of saying no is just as important as the skill of finding work.]]></description>
			<content:encoded><![CDATA[<p>I actually haven&#8217;t run into a dry spell since I went freelance last year, but I know that&#8217;s just because the market is so hot right now for AS developers.  My main problem is continual overbooking- mainly because everything sounds like so much <em>fun</em>.  When a client calls me and wants an app that will do all these awesome things, I often find myself getting extremely optimistic about what I can accomplish during the timeframe given.  And then of course I end up killing myself with multiple simultaneous projects.</p>
<p>So I guess the skill of saying no is just as important as the skill of finding work.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: erikbianchi		</title>
		<link>https://jessewarden.com/2008/09/scheduling-gig-challenges.html/comment-page-1#comment-122246</link>

		<dc:creator><![CDATA[erikbianchi]]></dc:creator>
		<pubDate>Tue, 09 Sep 2008 06:54:29 +0000</pubDate>
		<guid isPermaLink="false">http://jessewarden.com/?p=1285#comment-122246</guid>

					<description><![CDATA[A few things I have done that had helped when i was doing more consultation:

1) temp agencies almost 98% of the time fall through

2) stable work only came from people I knew or had worked with in the past on other gigs

3) if it sounds to good to be true . . . 

4) get a company to market yourself and find you work for a fee (so worth it)

-erik]]></description>
			<content:encoded><![CDATA[<p>A few things I have done that had helped when i was doing more consultation:</p>
<p>1) temp agencies almost 98% of the time fall through</p>
<p>2) stable work only came from people I knew or had worked with in the past on other gigs</p>
<p>3) if it sounds to good to be true . . . </p>
<p>4) get a company to market yourself and find you work for a fee (so worth it)</p>
<p>-erik</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
