RFPs: How to get what you want

Allison Manley

As someone who works in Sales and Marketing, I see and read a lot of RFPs. And I’ve seen it all: ones that are 50+ pages long but give no information, to ones just a few pages long that outline everything needed.

RFPs, or “requests for proposals,”can be daunting to write. Whether it’s nonprofit, corporate, or whatever, your organization likely only embarks on a large project once every few years, and you aren’t writing RFPs very often. And depending on your organization’s legal or procurement department, you may need to include a lot of additional language. Where do you start? What do you include? How do you give vendors the information they need so you can get the information you need back from them?

In this session, I’ll give you my feedback of what makes a good RFP that gets you the most thorough response.

This session will cover the following:

— best practices on the sales process

— what to include, and what to avoid, in your RFP

— why asking for spec work is a bad idea

— how to get responses back from vendors that give you a good comparison between them



This session is good for clients who are about to enter the RFP process, and sales teams that are looking to improve their responses to RFPs.

https://www.midcamp.org/topic/rfps-how-get-what-you-want

Drupal is a registered trademark of Dries Buytaert.