- Shopping Bag ( 0 items )
Praise for Request for Proposal
“Bud Porter-Roth is an expert in the field of preparing RFPs, and we could not have successfully completed our project without his skill and knowledge. This book is a clear guide to an otherwise complex and difficult process. If you can’t hire Bud Porter-Roth to write your RFP, then you should buy this book.”
—Lori Deibel, Manager, Library Services
“This book is priceless. It is a must for a novice writing an RFP.”
—Doris Lopez, Senior Systems Engineer, O-Cedar Brands, Inc.
“This book brings a structure to a process that is too often unstructured. There have been no standards (outside of government) that I know of that apply to RFP preparation. I also believe that vendors (sellers) would welcome a more uniform and consistent style of RFP.”
—Frank Tillman, API Systems Group
“This book provides overall coverage on a subject that deserves some real guidance. I like very much the sentiment concerning the RFP as the basis for a team and the idea that the RFP is the beginning, not the end. His emphasis on the need for clarity in the RFP and for measurable requirements needs to be heard and understood by many within the target audience. He takes an excellent position on ‘Why Write an RFP’.”
—Patricia Oberndorf, SEI
“This book is well written and insightful. It provides good information on what makes a good requirement, how proposals are evaluated, and what precautions to take to prevent early elimination.”
“Just a note to tell you thank you for providing some tips on how to structure an RFP. I work for a small company who does not have a specific template for this purpose and found your guidance a very useful starting point.”
Despite its importance as an initial step in the development of major technical projects, the Request for Proposal (RFP) process rarely receives the professional attention it deserves. Used by government agencies and by private corporations to solicit proposals from contractors and vendors, the RFP document is the foundation for a successful project. A clearly written and properly organized RFP clarifies technical goals, communicates administrative and financial expectations, and sets the tone for good communication and a trusting and productive relationship between customer and contractor.
This experience-based handbook offers a systematic, comprehensive, and professional approach to writing RFPs. It guides you step-by-step—from initial planning to selecting the winning proposal—through the RFP process, demonstrating the most effective ways of structuring the document and expressing technical, administrative, and financial requirements. Request for Proposal: A Guide to Effective RFP Development focuses on the major goals of the RFP process—to elicit high-quality responses from potential contractors and promote effective communication between the client and the chosen vendor.
You will be able to:
In addition, this book includes several templates you can adapt for your own organization’s RFP efforts. Request for Proposal gives numerous examples of both effective and poorly-written RFP requirements that illustrate the author’s points and provide solid advice to help you avoid common pitfalls and implement best practices.
For anyone with the responsibility of writing RFPs or responding to them, this book is are source you will want to keep close at hand.
1. Introduction to Writing RFPs.
What is Presented in this RFP Book?
Different Types of RFPs.
Request for Information (RFI).
Request for Proposal (RFP).
Why Write an RFP?
RFP Development and Preparation.
RFP Project Development.
Reviewing the RFP.
Anatomy of an RFP.
Project Overview and Administrative Information.
Supplier Qualifications and References.
Contracts and License Agreements Section.
The Importance of the RFP from a Contract Perspective.
2. RFP Planning and Preparation.
PreRFP Planning Considerations.
Technology and Supplier Education.
The Project Acquisition Budget.
Post-RFP Planning Considerations.
Project Development and Implementation.
Additional Post-RFP Activities.
3. RFP Administration Requirements Section Introduction.
How to use this Chapter.
Anatomy of an Administration Section.
Supplier and Supplier Reference Information.
Company Confidential Information.
Intent to Bid.
Proprietary Information Notice.
Supplier Confidential Information.
RFP Questions and Answers.
Responding to Supplier Questions.
RFP Reference Library.
Proposal Format Requirements.
The Cover Letter or Transmittal Letter.
The Executive Summary Required in Proposals.
Pricing Section (Cost Section).
Best and Final Offers.
Informational Paragraphs in the Administrative Section.
Definition of Requirements.
Production Environment for Hardware and Software Products.
Errors or Omissions in Proposals.
Proposal Evaluation Criteria.
Proposal Costs and Expenses.
Notifying Winning and Losing Suppliers.
What Should Not Appear in the Administrative Section.
4. RFP Technical Requirements Section.
Writing Requirements for the Technical Section.
Definition of a Requirement.
Who Writes Requirements?
How Do Suppliers Recognize Requirements in Your RFP?
What Is the Difference between Specifications and Requirements?
Requirements can Be Written as Questions, Statements, or Narrative Description.
Qualities of Well Written Requirements.
Requirements Must Reflect Real Products or Solutions.
Requirements Must Be Unambiguous.
Requirements Must Not Use Subjective Terms.
Requirements Must Be Measurable.
Requirements Must Be Meaningful.
Requirements Must Be Complete.
Requirements Must Not Include the Solution.
Requirements Must Not Include Unnecessary Characteristics.
Developing Technical Requirements.
Anatomy of a Technical Section.
Current Business Environment.
Current Technical Environment.
Proposed Technical Environment.
A Note on Hardware Requirements.
A Note on System Software Requirements.
5. Management Requirements Section.
Writing Requirements for the Management Section.
Examples of Poorly Written Requirements.
Anatomy of a Management Section.
Site Preparation Plan and Personnel Responsibilities.
Project Staffing Requirements.
Roles and Responsibilities.
Design, Development, and Implementation.
Project Change Control.
Delivery and Installation.
System Maintenance and Support.
Supplier Issues and Concerns.
Anatomy of a Pricing Section.
Custom Software Development.
Project Implementation and Management Services.
Maintenance and Support.
Other Costs Not Specifically Requested.
Organizing the Price Section.
Other Pricing Notes.
Contracts and License Agreements Section.
Fixed Price Contract.
Time and Materials (T&M).
Associated Contract Considerations.
Evaluation of Price Proposals.
7. Evaluation Guidelines.
The Evaluation Team.
Evaluation Criteria in the RFP.
Getting Started Evaluating Proposals.
Requests for Clarification.
Other Considerations for the Evaluation Team.
Anatomy of an Evaluation Section.
Oral Presentations and Demonstrations.
The Evaluation Process.
Second Round of Evaluations.
Developing the Scoring Methodology.
Appendix A. Administrative Information.
Appendix B. Supplier Information.
Appendix C. Proposal Preparation Instructions.
Appendix D. Budget Planning and Investment Analysis.
Appendix E. Nondisclosure Agreement.
Appendix F. Proprietary Notice.
Appendix G. Notice of Intent to Bid.
Appendix H. Questions and Answers.
Appendix I. Compliance Matrix.
Appendix J. Preliminary Evaluation Checklist.
Appendix K. RFP Reverse Planning Calendar. 0201775751T12102001
For many years, I wrote sales proposals in response to a request for proposal (RFP). As a vendor, I responded to both well written and poorly written RFPs and found that there was no consistency among them either in the structure or the quality of information. Several times I was stumped as to what the subject of the RFP was, and after several rounds of questions and answers, I determined that the company issuing the RFP was also stumped—they had neglected to do their homework properly and could not properly define their requirements.
After becoming a consultant, I began writing RFPs on behalf of my clients. As I wrote them, I tried not to make the same mistakes I had seen as a vendor and began to develop a structure and organization methodology for writing RFPs. I began to write and speak to customers and at conferences about writing RFPs and what makes a good RFP. Time after time I was approached by people in the audience who asked if I had additional material. Frequently, I was asked to recommend a book that would provide some guidance. But the literature is very slim on this subject, and I could find no “general” guide to writing RFPs.
This book aims to fill that gap, bringing order and stability to the process of writing RFPs for those who are new to it, as well as reaffirming effective practices for veterans. I have included ideas from the best RFPs and share what I have learned from poorly written RFPs. Three major themes run through this book:
An RFP is not the end of the project, but rather the start of a new phase in the project. While the general requirements for a project have already been defined, quite often the real requirements are not understood until well after the RFP is released, a contract is awarded, and the project development begins. Sometimes it takes two or three iterations of the requirements development process before both companies fully understand the problem they are trying to solve or the products they hope to use to overcome these difficulties:
We can only shape the path as we are cutting its course through the forest.Many requirements of a system become known only as the system develops. This is especially true for a system that makes use of multiple commercial products, since their interactions will have a substantial influence on the system’s eventual design.
—David J. Carney.Quotations from Chairman David. Pittsburgh: Carnegie Mellon University, 1998. Sponsored by the U.S. Department of Defense.
While this book is directed toward the computer system project, the disciplines of gathering requirements, organizing and writing an RFP, and interacting with suppliers during and after the RFP has been issued can be applied in many other contexts. The material in this book can therefore be used, with some adjustments, to write RFPs for many industries. However, this book does not cover every type of application for every project; some parts may not apply to your specific needs.
All of the following material, including the sample RFP paragraphs, should be considered as a starting point and guideline for your own RFP. While the book provides you with a general format and general language, it is up to you to build upon this base of information and these examples. In the commercial world there are no rulebooks or laws that force you to write an RFP in a certain manner, and the federal government’s Federal Acquisition Regulations (FARs) still leave room to be creative.
So within reason, be creative and include the requirements in your RFP that will make your project successful for both you and the chosen supplier.
Vendors do not have unlimited time and resources. When your RFP is complete, take a moment to look at it from a vendor’s point of view and consider whether it is fair or if you are asking for too much. Remember that if you succeed in your bid, the vendor will become your partner. Successful business relationships are built on foundations of fairness and mutual respect. To bully or cajole a vendor into reducing pricing or including free services is to impair your relationship from the beginning. As Andrew Carnegie once said about J. P. Morgan, “Mr. Morgan buys his partners; I grow my own.”Columbia Dictionary of Quotations. New York: Columbia University Press, 1995.
In my experience writing RFPs, I have worked with all kinds of people from all types of companies and departments. I find that many companies do not have RFP writing guidelines, procedures, or support and rely on company history and previously written RFPs as source materials. If there is no previous history in writing RFPs, a company may turn to consultants for help or ask vendors for copies of RFPs that can be used. I have been asked many times if I could send someone a “good” RFP as an example.
People who have been assigned to write an RFP but have not written one before and, perhaps, have little history and support to draw upon will find this book invaluable. A suggested outline, a wealth of examples, and good solid advice will guide you from starting the project to signing the contract.
People who have previously written RFPs will find that this book adds to their existing knowledge by providing some fresh examples for developing technical and management requirements.
Request for Proposal has been written for people in many different commercial industries as well as federal, state, and local government workers who need guidance, procedures, and direction. People who should read this book include the following:
After reading this book, the reader will be able to do the following:
There is no prerequisite for reading this book&8212;you do not need to be a senior IT manager or a certified purchasing agent. The text provides a standard format for the recommended sections in an RFP and includes examples for each section, as well as examples of how to write the technical and nontechnical requirements for each section.
The text also provides guidelines for evaluating proposals and selecting a winning vendor once proposals have been received. Evaluation guidelines include evaluating technical and management content as well as pricing.
As with any endeavor this large, many people have provided help, constructive criticism, encouragement, and support. I would like to thank all of the reviewers who took the time to review and comment on the manuscript. The finished book is much better as a result of their efforts.
Ralph Young has been especially helpful in providing detailed suggestions and encouragement and in graciously agreeing to write the foreword. Thank you, Ralph.
Special thanks go to Addison-Wesley for publishing this book and to my editor, Debbie Lafferty, for her professionalism, great suggestions and attitude, and lots of behind-the-scenes hard work that I will never know about.
Finally, my wife Anne and daughter Lizzie endured many early mornings, late nights, and missed weekends as I toiled away writing and revising the manuscript. Their support helped make this book possible.
Mill Valley, California
Posted August 22, 2003
How do you write an RFP? How long does it take? How much will it cost? Can you send me an example? Are there RFP software programs that you can use? How many people do I need to write it? How many vendors should I send it to? How do you evaluate proposals? These are only a few of the questions that this book answers, and why I wrote this book. All companies, large or small, must eventually write an RFP. Since I started writing RFPs for companies, I have learned that there is very little corporate history for writing RFPs, that the players change all the time, Purchasing may or may not have a role, and that each department writes its own RFP. In other words, I have learned by doing because there were no teachers, books, or seminars. This book provides you with the basic format, guidelines, and, in many cases, the actual materials for an RFP. The book will not write your RFP for you, but it will help you to write a better RFP, evaluate proposals, and answer many of your questions about RFPs. I wish this book had been available fifteen years ago - and now it is. Bud Porter-Roth Porter-Roth Associates...Was this review helpful? Yes NoThank you for your feedback. Report this reviewThank you, this review has been flagged.
Posted April 3, 2003
This book gives a lot of examples of how to write a proposals and the results of what happens when a proposal is not clear. Helped me to re-think how to word requirements in my proposal. If you have not written proposals before or have not received the responses you expected this book will really help you.Was this review helpful? Yes NoThank you for your feedback. Report this reviewThank you, this review has been flagged.
Posted September 4, 2009
No text was provided for this review.