<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Instigator Blog - Latest Comments in Top 10 Reasons Why Proposals Fail</title><link>http://instigatorblog.disqus.com/</link><description>Focused on startups, customer development, Lean Startup and entrepreneurship.</description><atom:link href="https://instigatorblog.disqus.com/top_10_reasons_why_proposals_fail/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Sat, 29 Nov 2008 06:46:43 -0000</lastBuildDate><item><title>Re: Top 10 Reasons Why Proposals Fail</title><link>https://www.instigatorblog.com/top-10-reasons-why-proposals-fail/2007/02/07/#comment-8053473</link><description>&lt;p&gt;I think about this all the time and wrote about one angle a little recently - the angle being that a lot of salespeople are great at relationship selling (face-to-face) yet hate actually putting pen to paper and writing.&lt;/p&gt;&lt;p&gt;Many really good salespeople do all the things you mention in a sales call, but fail to do it in the actual proposal. Many are just uncomfortable writing, some want to be just customer facing and there are many more reasons.&lt;/p&gt;&lt;p&gt;Well structured, persuasive proposals are usually produced as a team effort and someone who is reading this thinking "I need to write a proposal and don't know where to start" should really get some input from an experienced salesperson who is a good writer too. There is a skill and technique in a good sales call and having the same impact in your proposal sometimes requires a different input entirely.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">James England</dc:creator><pubDate>Sat, 29 Nov 2008 06:46:43 -0000</pubDate></item><item><title>Re: Top 10 Reasons Why Proposals Fail</title><link>https://www.instigatorblog.com/top-10-reasons-why-proposals-fail/2007/02/07/#comment-2383376</link><description>&lt;p&gt;Marijn - That's great advice. If you can, call the contact for the RFP to get some inside information / have your questions answered. I would suggest you have a list of questions you want answered, so you're not just trying to schmooze the person on the phone. An d so you don't waste the opportunity to get the information and details you need.&lt;/p&gt;&lt;p&gt;I'm really not a fan of RFPs but if you're going to respond to them, then calling the contact to establish some amount of relationship, understanding and getting your questions answered can definitely help.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Benjamin Yoskovitz</dc:creator><pubDate>Tue, 16 Sep 2008 08:33:06 -0000</pubDate></item><item><title>Re: Top 10 Reasons Why Proposals Fail</title><link>https://www.instigatorblog.com/top-10-reasons-why-proposals-fail/2007/02/07/#comment-2358323</link><description>&lt;p&gt;Another personal one I would like to add: the person who writes the proposal doesn't contact the prospect!&lt;br&gt;I know that when I contact the prospect by phone, I get a tons of useful info that is not in their RFP! Especially which parts they think is important, or which problem they try to solve..&lt;/p&gt;&lt;p&gt;pingback from &lt;a href="http://marijnsomers.blogspot.com/2008/09/top-10-reasons-why-proposals-fail.html" rel="nofollow noopener" target="_blank" title="http://marijnsomers.blogspot.com/2008/09/top-10-reasons-why-proposals-fail.html"&gt;http://marijnsomers.blogspo...&lt;/a&gt;&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">marijn</dc:creator><pubDate>Mon, 15 Sep 2008 08:37:25 -0000</pubDate></item><item><title>Re: Top 10 Reasons Why Proposals Fail</title><link>https://www.instigatorblog.com/top-10-reasons-why-proposals-fail/2007/02/07/#comment-1646286</link><description>&lt;p&gt;I'm in the process of pursuing new contracts so this is a helpful blog.  Thanks!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Civil Site Design</dc:creator><pubDate>Thu, 14 Aug 2008 09:40:36 -0000</pubDate></item><item><title>Re: Top 10 Reasons Why Proposals Fail</title><link>https://www.instigatorblog.com/top-10-reasons-why-proposals-fail/2007/02/07/#comment-1646288</link><description>&lt;p&gt;I have been guilty of a few of these myself.  Proposals are tough.  I hired a wonderfully talented professional to do a proposal for us for what would have been a great job.  The proposal was perfect, beautiful, a work of art.  We didn't get the job.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bhicks</dc:creator><pubDate>Fri, 25 Jul 2008 09:36:53 -0000</pubDate></item><item><title>Re: Top 10 Reasons Why Proposals Fail</title><link>https://www.instigatorblog.com/top-10-reasons-why-proposals-fail/2007/02/07/#comment-1646289</link><description>&lt;p&gt;"They’re not selling benefits. Proposals that miss out on #2 and focus too much on #3 invariably aren’t selling benefits. If you’re not selling benefits you’re sunk. And for the love of everything that is holy, spell these out as clearly as possible. "&lt;/p&gt;&lt;p&gt;I absolutely agree with the statement.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Eva</dc:creator><pubDate>Sun, 22 Jun 2008 08:49:23 -0000</pubDate></item><item><title>Re: Top 10 Reasons Why Proposals Fail</title><link>https://www.instigatorblog.com/top-10-reasons-why-proposals-fail/2007/02/07/#comment-1646290</link><description>&lt;p&gt;Arguably the biggest one for me is that proposals aren't selling benefits. if one would just start harping on that, you'll definitely see success.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Kelvin Chan</dc:creator><pubDate>Mon, 26 May 2008 21:33:55 -0000</pubDate></item><item><title>Re: Top 10 Reasons Why Proposals Fail</title><link>https://www.instigatorblog.com/top-10-reasons-why-proposals-fail/2007/02/07/#comment-1646287</link><description>&lt;p&gt;I agree completely with points 2 and 3. In my role I continually see engineers writing proposals/ requirements that end up filled with neat ideas while missing the mark on the customer's needs.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike</dc:creator><pubDate>Mon, 07 Apr 2008 15:51:43 -0000</pubDate></item><item><title>Re: Top 10 Reasons Why Proposals Fail</title><link>https://www.instigatorblog.com/top-10-reasons-why-proposals-fail/2007/02/07/#comment-1646283</link><description>&lt;p&gt;I have seen the same thing as well. People forget some of the simple little things that would land it, and its all the technobabble mumbo jumbo that people get caught up in. Just go back to root basics. That simple.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">BZ Sponger</dc:creator><pubDate>Thu, 27 Dec 2007 17:23:27 -0000</pubDate></item><item><title>Re: Top 10 Reasons Why Proposals Fail</title><link>https://www.instigatorblog.com/top-10-reasons-why-proposals-fail/2007/02/07/#comment-1646285</link><description>&lt;p&gt;Jurriann - Glad you enjoyed the post. I'm sure this is the first time I've had anything translated into Dutch.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ben Yoskovitz</dc:creator><pubDate>Mon, 24 Sep 2007 09:48:12 -0000</pubDate></item><item><title>Re: Top 10 Reasons Why Proposals Fail</title><link>https://www.instigatorblog.com/top-10-reasons-why-proposals-fail/2007/02/07/#comment-1646284</link><description>&lt;p&gt;Great article! Thanx, i translated it in dutch &amp;amp; put it on &lt;a href="http://www.bligg.nl" rel="nofollow noopener" target="_blank" title="www.bligg.nl"&gt;www.bligg.nl&lt;/a&gt;, and on &lt;a href="http://www.bobex.nl" rel="nofollow noopener" target="_blank" title="www.bobex.nl"&gt;www.bobex.nl&lt;/a&gt;.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jurriaan</dc:creator><pubDate>Mon, 24 Sep 2007 06:42:21 -0000</pubDate></item><item><title>Re: Top 10 Reasons Why Proposals Fail</title><link>https://www.instigatorblog.com/top-10-reasons-why-proposals-fail/2007/02/07/#comment-1646282</link><description>&lt;p&gt;Great advice, I would simply add, it is important to keep things simple.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">pete</dc:creator><pubDate>Sun, 09 Sep 2007 17:41:09 -0000</pubDate></item><item><title>Re: Top 10 Reasons Why Proposals Fail</title><link>https://www.instigatorblog.com/top-10-reasons-why-proposals-fail/2007/02/07/#comment-1646281</link><description>&lt;p&gt;Well said!&lt;/p&gt;&lt;p&gt;I hate reading proposals like those too.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mark</dc:creator><pubDate>Fri, 31 Aug 2007 14:09:35 -0000</pubDate></item><item><title>Re: Top 10 Reasons Why Proposals Fail</title><link>https://www.instigatorblog.com/top-10-reasons-why-proposals-fail/2007/02/07/#comment-1646279</link><description>&lt;p&gt;Brad - I like that approach. We know that everyone reading a proposal goes down to the end to see price + timeline anyway, so might as well put it in a 1-page summary at the front.&lt;/p&gt;&lt;p&gt;Thanks for stopping by and commenting.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ben Yoskovitz</dc:creator><pubDate>Wed, 08 Aug 2007 09:37:50 -0000</pubDate></item><item><title>Re: Top 10 Reasons Why Proposals Fail</title><link>https://www.instigatorblog.com/top-10-reasons-why-proposals-fail/2007/02/07/#comment-1646280</link><description>&lt;p&gt;Excellent advice! One other thing I like to do is add an "executive summary page" that highlights the key benefits, cost and ROI. Even a twenty-page proposal on a complex product or service can usually be boiled down to a page or less. Maybe that's the best place to start writing a proposal...?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brad Shorr</dc:creator><pubDate>Wed, 08 Aug 2007 09:20:39 -0000</pubDate></item><item><title>Re: Top 10 Reasons Why Proposals Fail</title><link>https://www.instigatorblog.com/top-10-reasons-why-proposals-fail/2007/02/07/#comment-1646278</link><description>&lt;p&gt;Proposals are sales letters, so the rules and best practices applied to proposals can apply to sales letters - both long and short...&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ben Yoskovitz</dc:creator><pubDate>Tue, 05 Jun 2007 09:17:18 -0000</pubDate></item><item><title>Re: Top 10 Reasons Why Proposals Fail</title><link>https://www.instigatorblog.com/top-10-reasons-why-proposals-fail/2007/02/07/#comment-1646277</link><description>&lt;p&gt;Seems there is hardly any difference between a proposal and a long sales letter.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">free</dc:creator><pubDate>Tue, 05 Jun 2007 03:32:08 -0000</pubDate></item><item><title>Re: Top 10 Reasons Why Proposals Fail</title><link>https://www.instigatorblog.com/top-10-reasons-why-proposals-fail/2007/02/07/#comment-1646276</link><description>&lt;p&gt;This is great. Thank you. Sounds like tips from a great copywriter.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">rebecca</dc:creator><pubDate>Fri, 30 Mar 2007 12:15:26 -0000</pubDate></item><item><title>Re: Top 10 Reasons Why Proposals Fail</title><link>https://www.instigatorblog.com/top-10-reasons-why-proposals-fail/2007/02/07/#comment-1646275</link><description>&lt;p&gt;Good post - thanks!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chad Ledford</dc:creator><pubDate>Wed, 28 Mar 2007 14:49:59 -0000</pubDate></item><item><title>Re: Top 10 Reasons Why Proposals Fail</title><link>https://www.instigatorblog.com/top-10-reasons-why-proposals-fail/2007/02/07/#comment-1646274</link><description>&lt;p&gt;Great post, Ben.&lt;/p&gt;&lt;p&gt;The same 10 points could be applied to any number of situations in the modern workplace as they are all examples of ways to practice "principles-based business."&lt;/p&gt;&lt;p&gt;Make sure whatever you are working on is: &lt;br&gt;-Audience Centric&lt;br&gt;-As Simple As Possible&lt;br&gt;-Valuable Enough For All Involved&lt;br&gt;-Real / Genuine / Authentic&lt;br&gt;-At Least As Good As It Should Be&lt;br&gt;-In Some Way Remarkable&lt;/p&gt;&lt;p&gt;Thanks, -Adam&lt;/p&gt;&lt;p&gt;&lt;a href="http://www.BadSlacks.com" rel="nofollow noopener" target="_blank" title="www.BadSlacks.com"&gt;www.BadSlacks.com&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Adam Brucker</dc:creator><pubDate>Mon, 12 Mar 2007 19:49:28 -0000</pubDate></item><item><title>Re: Top 10 Reasons Why Proposals Fail</title><link>https://www.instigatorblog.com/top-10-reasons-why-proposals-fail/2007/02/07/#comment-1646272</link><description>&lt;p&gt;Ben, great, blunt tips here.  With the help of Mark Silver(&lt;a href="http://HeartofBusiness.com" rel="nofollow noopener" target="_blank" title="HeartofBusiness.com"&gt;HeartofBusiness.com&lt;/a&gt;) and Dawud Miracle &lt;a href="http://HealthyWebDesign.com" rel="nofollow noopener" target="_blank" title="HealthyWebDesign.com"&gt;HealthyWebDesign.com&lt;/a&gt;) I have a fledgling website and blog site, both still in development.  Your information is realistic and to the point.  Thank you.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Stuart Baker</dc:creator><pubDate>Wed, 21 Feb 2007 07:20:27 -0000</pubDate></item><item><title>Re: Top 10 Reasons Why Proposals Fail</title><link>https://www.instigatorblog.com/top-10-reasons-why-proposals-fail/2007/02/07/#comment-1646273</link><description>&lt;p&gt;I highly recommend the book "The One Page Proposal" by Patrick Riley. It provides a great framework that applies many of the ideas outlined here. It's really changed the way I write proposals, although they're not always one page.&lt;/p&gt;&lt;p&gt;Great post.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">dpickett</dc:creator><pubDate>Tue, 20 Feb 2007 09:18:14 -0000</pubDate></item><item><title>Re: Top 10 Reasons Why Proposals Fail</title><link>https://www.instigatorblog.com/top-10-reasons-why-proposals-fail/2007/02/07/#comment-1646251</link><description>&lt;p&gt;Ethan - email it to me, I'll take a look.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ben Yoskovitz</dc:creator><pubDate>Tue, 13 Feb 2007 23:20:42 -0000</pubDate></item><item><title>Re: Top 10 Reasons Why Proposals Fail</title><link>https://www.instigatorblog.com/top-10-reasons-why-proposals-fail/2007/02/07/#comment-1646250</link><description>&lt;p&gt;I love this post.  I have read it at least 5 times   since it was posted.  As a new startup we began  working on creating and fine tuning our standard proposal document about two weeks before this post.  This has been our check list to compare against.&lt;/p&gt;&lt;p&gt;So where do I send it for a little review ;)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ethan Giffin</dc:creator><pubDate>Tue, 13 Feb 2007 23:16:40 -0000</pubDate></item><item><title>Re: Top 10 Reasons Why Proposals Fail</title><link>https://www.instigatorblog.com/top-10-reasons-why-proposals-fail/2007/02/07/#comment-1646252</link><description>&lt;p&gt;Patrick - adding to your quote is a good way of covering scope creep and your own inability to quote accurately (which most people have a problem with.) Everything takes longer than you think it will...&lt;/p&gt;&lt;p&gt;But I do agree with the "a la carte" approach - break up deliverables and costs.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ben Yoskovitz</dc:creator><pubDate>Mon, 12 Feb 2007 22:02:37 -0000</pubDate></item></channel></rss>