<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Robert Dempsey - Latest Comments in When To Say NO To A Project</title><link>http://adsblog.disqus.com/</link><description></description><atom:link href="https://adsblog.disqus.com/when_to_say_no_to_a_project/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Fri, 12 Dec 2008 09:42:01 -0000</lastBuildDate><item><title>Re: When To Say NO To A Project</title><link>http://blog.adsdevshop.com/2008/06/05/when-to-say-no-to-a-project/#comment-20756217</link><description>&lt;p&gt;@&lt;a href="#comment-7285" rel="nofollow noopener" target="_blank" title="#comment-7285"&gt;Paul Klipp&lt;/a&gt;: Hi Paul, you make a great point. Working with customers who have a long-term vision and a plan to make it happen increase the chances for success, and our satisfaction with what we create.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Robert Dempsey</dc:creator><pubDate>Fri, 12 Dec 2008 09:42:01 -0000</pubDate></item><item><title>Re: When To Say NO To A Project</title><link>http://blog.adsdevshop.com/2008/06/05/when-to-say-no-to-a-project/#comment-20756216</link><description>&lt;p&gt;At some point, our company got to the point where demand was much higher than we could possibly supply without lowering our standards and I began turning down or re-directing most of our prospects. More than anything else these days, I am looking for projects likely to succeed in the market and I find that the management team is more important than the idea for evaluating the chances of a project being successful. So now after discussing the project, I ask to review the marketing plan and to meet the management team before I take on a project. Because while all projects pay, we're not really in it for the money, are we? Nothing beats the satisfaction of hundreds of thousands of satisfied users clicking away at your work.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">paulklipp</dc:creator><pubDate>Fri, 12 Dec 2008 09:31:35 -0000</pubDate></item><item><title>Re: When To Say NO To A Project</title><link>http://blog.adsdevshop.com/2008/06/05/when-to-say-no-to-a-project/#comment-20756215</link><description>&lt;p&gt;Great post, and I agree, the notion of taking equity for investment is just one that takes careful consideration.&lt;/p&gt;&lt;p&gt;Here are some others that we consider:&lt;/p&gt;&lt;p&gt;* is the project from scratch, or have framework or architecture decisions already been made leading to "lock-in"&lt;/p&gt;&lt;p&gt;* what is the ongoing relationship? is the project likely to require maintenance? is the client willing to commit to a reasonable contract for that or do they want to be free and clear but be able to call you any time they need a "tweak"&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">cschultz</dc:creator><pubDate>Mon, 16 Jun 2008 10:09:10 -0000</pubDate></item><item><title>Re: When To Say NO To A Project</title><link>http://blog.adsdevshop.com/2008/06/05/when-to-say-no-to-a-project/#comment-20756214</link><description>&lt;p&gt;@Chris Scott: I think your last point is tricky. After all, you're not an investor.&lt;/p&gt;&lt;p&gt;We have a customer that was going to sell herbs/spices via a website. I thought it would be a total failure. ' Cause after all, who buys spices from a website?&lt;/p&gt;&lt;p&gt;But now, a year later, it's a big success!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Leon Bogaert</dc:creator><pubDate>Sun, 15 Jun 2008 06:09:57 -0000</pubDate></item><item><title>Re: When To Say NO To A Project</title><link>http://blog.adsdevshop.com/2008/06/05/when-to-say-no-to-a-project/#comment-20756213</link><description>&lt;p&gt;Great additions Chris, thanks.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Robert Dempsey</dc:creator><pubDate>Fri, 06 Jun 2008 12:59:47 -0000</pubDate></item><item><title>Re: When To Say NO To A Project</title><link>http://blog.adsdevshop.com/2008/06/05/when-to-say-no-to-a-project/#comment-20756212</link><description>&lt;p&gt;Clients that talk about how bad their last developer was or mention their lawsuit against them. Don't think you'll be any different when they're done w/you.&lt;/p&gt;&lt;p&gt;Clients that want you to sign an onerous NDA before they'll tell you anything. I'm all for NDAs, but if you can't explain the basics to me w/out one that signals you either don't trust me or will be a total PITA. Either way...&lt;/p&gt;&lt;p&gt;Clients that ask you to do trade-out for their product/service or equity. I'm a developer not an investor. Also, this tells me that you don't have any money and couldn't convince anyone to give you any.&lt;/p&gt;&lt;p&gt;Projects that I don't feel will be successful. I want a challenge as well as something that I'm proud to point out when I'm done. I also want to be able to point to it in 6 months to a year and have the client doing well and still be in business.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Scott</dc:creator><pubDate>Thu, 05 Jun 2008 16:15:18 -0000</pubDate></item></channel></rss>