BNET Insight

Sales Machine

A, Always. B, Be. C, Closing.

Ten Gaffes of Proposal Writing

February 16th, 2007 @ 9:34 am

6 Comments

Categories: Pitches, Sales Tips

Tags: Dumb, Proposal, Geoffrey James

I hate proposals. And from what I hear from other sales pros, I’m hardly alone. It’s a pain in the tuchus to provide reams of paperwork just to get somebody to buy something. Nonetheless, proposals are the grist of the business world; very few big decisions get made without them.

The other day, I happened to be chatting about proposal-writing with Tom Sant, a guy who makes his living helping companies learn how to write better proposals. As you might expect, he had a lot to say, but I think that his advice can be boiled down into ten dumb things that people do when writing proposals. Avoid these mistakes, and your proposal may actually produce results:

  • Gaffe #1. Treat the proposal as an information packet.
    Why it’s dumb:
    A proposal is a sales document, not a data sheet. It should define the problems or opportunity and then present a workable solution or plan. Period.
  • Gaffe #2. Write a proposal targeted for someone who doesn’t know you.
    Why it’s dumb:
    Your proposal will go straight to the circular file cabinet unless you’ve established yourself as credible to the decision-maker.
  • Gaffe #3. Make the “executive summary” a summary of the proposal’s contents.
    Why it’s dumb:
    An executive briefing summarizes basic issues and the reasons the customer should buy.
  • Gaffe #4. Bloat up the executive summary.
    Why it’s dumb:
    Here’s the rule of thumb: a single page executive summary for any proposal less than 50 page, with half-a-page added for every additional 25 pages.
  • Gaffe #5. Fail to understand what the customer values.
    Why it’s dumb:
    The proposal must address the concerns of different decision-makers. For instance, engineers want technology; accountants want ROI.
  • Gaffe #6. Focus on the product rather than the customer.
    Why it’s dumb:
    Nobody is interested in the history of you or your product. Make the proposal about how you’ll solve the customer’s problems.
  • Gaffe #7. Forget to edit paragraphs lifted from other proposals.
    Why it’s dumb:
    If you cut and paste from an earlier proposal, there may be references to a previous customer – probably a competitor of this customer. Ouch.
  • Gaffe #8. Ignore the customer’s outline.
    Why it’s dumb:
    If the customer gave you a template (even one that’s weird or awkward) use it. If you don’t, they’ll assume you can’t follow simple instructions.
  • Gaffe #9. Explain costs in the executive summary.
    Why it’s dumb:
    Emphasize your “value proposition,” like increased productivity or reduced operating costs rather than how much money you want them to spend.
  • Gaffe #10. Pad the proposal with meaningless jargon.
    Why it’s dumb:
    Phrases like “next generation,” “state-of-the-art” and “leading edge” don’t mean crap. Delete them.

This Blog's Best Post: The Ultimate Cold Calling Tool

 
Reply to Story

BNET TalkbackShare your ideas and expertise on this topic

Subscribe to this discussion via Email or RSS

  •  
    1

    stephenh@...

    02/21/07 | Report as spam

    Good pointers

    An excellent article. Some very useful points indeed that make a lot of sense. Thank you for making it available

  •  
    2

    t.armstrong@...

    02/27/07 | Report as spam

    My Justification

    I have spent the whole day on V1 draft of a Tender <ocument. Thank you for providing a sanity check. A colleague suggested I should just cut and paste the generic yada yada into the <ocument.

    Cheers Todd

  •  
    3

    paul@...

    02/27/07 | Report as spam

    Ten Gaffes of Proposal Writing

    Just a comment to note I think there is a distinct difference in approach between a tender and a proposal. A proposal should be one where the prospects concerns are totally understood, and the provider's remedies are fully and uniquely articulated. It's no use doing a proposal if not - you'll usually end up as 'cannon fodder'. Tenders (especially public bodies) are notorious - no matter how good you make a proposal you'll usually end up disappointed if you haven't got to the influencers and used charm and sales persuasion! Unfortunately it's getting more and more difficult to get quality time with prospects. And there's another interesting thread....

  •  
    4

    littul@...

    02/27/07 | Report as spam

    Great pointers, but...

    I agree with the bullet points, but more often than not I have seen that in addition to stating the problem and the solution in business terms, you will need to insert some "information" about the technology and "how" the relevant technology and your product will solve the problem - which could go against the "information packet" approach in your article. We actually end up putting architecture diagrams etc on almost all our proposals because IT is almost always an important stakeholder for what we do.

  •  
    5

    mneveu@...

    02/28/07 | Report as spam

    Nice job from the Real World

    For once, someone with "real world" (whatever that means) experience provides things not-to-do with your precious proposal. In my job, I read proposals all the time - and my guidelines go right down the list in the same fashion as explained in the blog. I look for facts, not rhetoric. I look for brevity where it is needed, and technical explanation where it is appropriate. If the sales/executive portion of the proposal doesn't tell me why they should get my business within the first 100 words - they've often lost my interest in lieu of the competitor who can.

    nice job:-)

  •  
    6

    info@...

    04/11/07 | Report as spam

    Very Dumb Indeed...

    what's worse is that they will never stop making those mistakes.

Please add your comment:

  1. You are currently: a Guest |
  2.  

Basic HTML tags that work in comments are: bold (<b></b>), italic (<i></i>), underline (<u></u>), and hyperlink (<a href></a)

advertisement

Blogger Profiles

  • Blogger Thumbnail Geoffrey James Geoffrey James has sold and written hundreds of features, articles and columns for national publications including Wired, Men's Health, Business 2.0, SellingPower, Brand World, Computer Gaming World, CIO, The New York Times and (of course) BNET. He is the author of seven books, including Business Wisdom of the Electronic Elite (translated into seven languages and selected by four book clubs), and The Tao of Programming (widely quoted on the Web as a "canonical book of... more »

advertisement
  • Click Here
  • Click Here
  • Click Here
advertisement