Request for Proposal: A Guide to Effective RFP Development

Paperback | December 21, 2001

byBud Porter-roth

not yet rated|write a review
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 it is an offer from the supplier to form a team with you and to jointly solve a problem.As a team, both sides stand to benefit from the relationship, but the project itself is the real winner. 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. A Word of Encouragement 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. A Word of Caution 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. Who Should Read This Book? 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 Proposalhas 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: information technology IT managers asked to write or manage an RFP business unit managers who may not have dedicated IT support and find that they need to write an RFP purchasing managers who provide RFP oversight for their company federal, state, and local government IT and business managers who need to supplement their internal guidelines consultants who are responsible for writing RFPs or helping their clients write RFPs university and college professors looking for primary or supplemental course material After reading this book, the reader will be able to do the following: organize the RFP project effort outline each RFP section develop, write, and review requirements technical, management, and pricing pre-screen a vendor list selecting only the best vendors for the project set up the evaluation criteria for evaluating vendor proposals select the best solution based on objective evaluation criteria prepare for the post-RFP activities such as site visits and reference checks, plan and schedule implementation activities, and put in place project management plans There is no prerequisite for reading this book 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. Acknowledgments 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. Bud Porter-RothMill Valley, California bud@rfphandbook.com http://www.rfphandbook.com 0201775751P12102001

Pricing and Purchase Info

$55.70 online
$74.99 list price (save 25%)
In stock online
Ships free on orders over $25
HURRY, ONLY 1 LEFT!

From the Publisher

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 ...

From the Jacket

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 th...

Bud Porter-Roth is a technology consultant who specializes in helping clients develop and write effective RFPs, evaluate vendor proposals, and implement joint projects. As a result of hisreal-world expertise, Mr. Porter-Roth frequently writes and lectures on RFPs. He is also the author of Proposal Development: How to Respond and Win t...
Format:PaperbackPublished:December 21, 2001Publisher:Pearson EducationLanguage:English

The following ISBNs are associated with this title:

ISBN - 10:0201775751

ISBN - 13:9780201775754

Customer Reviews of Request for Proposal: A Guide to Effective RFP Development

Reviews

Extra Content

From the Author

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: Quality of information is paramount to getting good proposal responses. Only if your requirements are well formed and complete will suppliers have enough information to write quality proposals. Presentation, structure, and organization are all necessary if suppliers are to understand how to read your RFP and respond to it in a productive manner. Without a structured and organized RFP, vendors will find it difficult to write proposals, and you will find it difficult to evaluate them. An RFP is much more than a request to buy a product; it is an offer from the supplier to form a team with you and to jointly solve a problem.As a team, both sides stand to benefit from the relationship, but the project itself is the real winner. 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. A Word of Encouragement 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. A Word of Caution 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. Who Should Read This Book? 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: information technology (IT) managers asked to write or manage an RFP business unit managers who may not have dedicated IT support and find that they need to write an RFP purchasing managers who provide RFP oversight for their company federal, state, and local government IT and business managers who need to supplement their internal guidelines consultants who are responsible for writing RFPs or helping their clients write RFPs university and college professors looking for primary or supplemental course material After reading this book, the reader will be able to do the following: organize the RFP project effort outline each RFP section develop, write, and review requirements&8212;technical, management, and pricing prescreen a vendor list selecting only the best vendors for the project set up the evaluation criteria for evaluating vendor proposals select the best solution based on objective evaluation criteria prepare for the postRFP activities such as site visits and reference checks, plan and schedule implementation activities, and put in place project management plans 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. Acknowledgments 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 AddisonWesley for publishing this book and to my editor, Debbie Lafferty, for her professionalism, great suggestions and attitude, and lots of behindthescenes 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. Bud PorterRoth Mill Valley, California bud@rfphandbook.com http://www.rfphandbook.com 0201775751P12102001

Read from the Book

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: Quality of information is paramount to getting good proposal responses. Only if your requirements are well formed and complete will suppliers have enough information to write quality proposals. Presentation, structure, and organization are all necessary if suppliers are to understand how to read your RFP and respond to it in a productive manner. Without a structured and organized RFP, vendors will find it difficult to write proposals, and you will find it difficult to evaluate them. An RFP is much more than a request to buy a product; it is an offer from the supplier to form a team with you and to jointly solve a problem.As a team, both sides stand to benefit from the relationship, but the project itself is the real winner. 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. A Word of Encouragement 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. A Word of Caution 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. Who Should Read This Book? 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: information technology (IT) managers asked to write or manage an RFP business unit managers who may not have dedicated IT support and find that they need to write an RFP purchasing managers who provide RFP oversight for their company federal, state, and local government IT and business managers who need to supplement their internal guidelines consultants who are responsible for writing RFPs or helping their clients write RFPs university and college professors looking for primary or supplemental course material After reading this book, the reader will be able to do the following: organize the RFP project effort outline each RFP section develop, write, and review requirements&8212;technical, management, and pricing pre-screen a vendor list selecting only the best vendors for the project set up the evaluation criteria for evaluating vendor proposals select the best solution based on objective evaluation criteria prepare for the post-RFP activities such as site visits and reference checks, plan and schedule implementation activities, and put in place project management plans 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. Acknowledgments 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. Bud Porter-Roth Mill Valley, California bud@rfphandbook.com http://www.rfphandbook.com 0201775751P12102001

Table of Contents



1. Introduction to Writing RFPs.

Introduction.

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.

Evaluation Criteria.

Reviewing the RFP.

Anatomy of an RFP.

Project Overview and Administrative Information.

Technical Requirements.

Management Requirements.

Supplier Qualifications and References.

Suppliers' Section.

Pricing Section.

Contracts and License Agreements Section.

Appendices.

RFP Activities.

Pre­RFP Activities.

Identifying Suppliers.

Qualifying Suppliers.

RFP Activities.

Post­RFP Activities.

The Importance of the RFP from a Contract Perspective.

Conclusion.



2. RFP Planning and Preparation.

Introduction.

Pre­RFP Planning Considerations.

Project Organization.

Project Organization.

Project Schedule.

Technology and Supplier Education.

Budget Development.

The Project Acquisition Budget.

Post-RFP Planning Considerations.

Project Development and Implementation.

Additional Post-RFP Activities.

Conclusion.



3. RFP Administration Requirements Section Introduction.

How to use this Chapter.

Anatomy of an Administration Section.

RFP Overview.

Supplier and Supplier Reference Information.

Company Confidential Information.

Intent to Bid.

Proprietary Information Notice.

Supplier Confidential Information.

Subcontracting.

RFP Contacts.

RFP Questions and Answers.

Responding to Supplier Questions.

RFP Reference Library.

RFP Schedule.

Pre­Proposal Conference.

Proposal Format Requirements.

The Cover Letter or Transmittal Letter.

The Executive Summary Required in Proposals.

Pricing Section (Cost Section).

Best and Final Offers.

Alternate Proposals.

Compliance Matrix.

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.

Product Demonstrations.

Notifying Winning and Losing Suppliers.

Proposal Debriefing.

What Should Not Appear in the Administrative Section.

Conclusion.



4. RFP Technical Requirements Section.

Introduction.

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.

Illustrating 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.

Application Requirements.

Conclusion.

Suggested Readings.



5. Management Requirements Section.

Introduction.

Writing Requirements for the Management Section.

Examples of Poorly Written Requirements.

Anatomy of a Management Section.

Project Plan.

Project Schedule.

Site Preparation Plan and Personnel Responsibilities.

Project Staffing Requirements.

Roles and Responsibilities.

Design, Development, and Implementation.

Project Change Control.

Delivery and Installation.

Testing.

System Maintenance and Support.

Training.

Documentation.

Standards.

Project Cutover.

Supplier Issues and Concerns.

Conclusion.



6. Pricing.

Introduction.

Anatomy of a Pricing Section.

Introduction.

Hardware.

System Software.

Application Software.

Custom Software Development.

Consumables.

Project Implementation and Management Services.

Maintenance and Support.

Training.

Documentation.

Other Costs Not Specifically Requested.

Organizing the Price Section.

Validating Prices.

Other Pricing Notes.

Contracts and License Agreements Section.

Fixed Price Contract.

Time and Materials (T&M).

Associated Contract Considerations.

Evaluation of Price Proposals.

Conclusion.



7. Evaluation Guidelines.

Introduction.

The Evaluation Team.

Evaluation Considerations.

Evaluation Criteria in the RFP.

Getting Started Evaluating Proposals.

Requests for Clarification.

Other Considerations for the Evaluation Team.

Anatomy of an Evaluation Section.

Technical Evaluation.

Management Evaluation.

Price Evaluation.

Oral Presentations and Demonstrations.

The Evaluation Process.

Introduction.

Preliminary Evaluation.

Second Round of Evaluations.

Detailed Evaluations.

The Shortlist.

Developing the Scoring Methodology.

Evaluation Report.

Conclusion.



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