Every seller that writes proposals in response to federal or state/local government RFPs should ask for copies of all the proposals submitted. Are you?
Including your client’s logo in your proposal can be risky. Resist the temptation.
When reviewing a proposal, it’s better to remove unnecessary things than it is to add more words. Be concise.
When responding to RFPs, true success comes from saying, proactively, two years ahead of time, “I want that contract, and here’s how I plan to go win it.”
When writing proposals, use a single space after a period.
If you respond to every RFP you receive, you’re wasting resources.
Calculating the right kind of success ratios as part of your RFP selling effort can offer great insight into where you’re doing well and where you might be falling short.
A satirical look at the overuse of superlatives in business writing. It really is the best article ever written on the topic.
A proposal is a sales document, not an informational document. Include the necessary information, but make it persuasive.
When writing proposals, say what needs to be said. No more. You can say more if you want, but it just makes your proposal longer and less likely to be read.
Reacting to RFPs doesn’t work. If you don’t have a relationship with the client before the RFP is issued, it is unlikely you are going to win.
If you add just one more comma at the end of a list, you will make your writing clearer.
You should always include a cover letter when you send a proposal. It’s good business etiquette, it’s polite, and there’s no reason not to.