Hi Dani,

I see a lot of RFPs and while there's nothing all that weird (I guess) about sharing list-wide, I am going to attach a recent and par-for-course RFP individually, off list.  Most folks generate one from templates in a book or off example sites, so they all tend to look the same.

I wanted to take the chance to reply to the crowd, though, because -- well, there's no easy way to say this -- web designers worth their salt hate and often outright refuse to respond to RFPs. If you want to attract the right people to work with you on your project, I think it's important to take consider the advice big web-industry publications and thought leaders give:

"Unsolictied RFPs: Just Say, No!" (http://www.uxmatters.com/mt/archives/2009/04/unsolicited-rfps-just-say-no.php)

"RFPs: The Least Creative Way to Hire People" (http://alistapart.com/article/rfps-the-least-creative-way-to-hire-people) 

"Saying No to RFPs" ( http://chrislema.com/saying-no-to-rfps/ )

"Why we won't answer a website design RFP" (http://www.gorilla76.com/why-we-wont-answer-a-website-design-rfp/)

"Why your website RFP is probably wrong" (https://boagworld.com/digital-strategy/website-rfp/) 

RFP Advice From the Front Lines (http://cognition.happycog.com/article/rfp-advice-from-the-front-lines) - spoiler: "Avoid All RFPs Don't Google RFP. Don't do a search."

"Why you should never provide free design in an RFP response" (http://blog.invisionapp.com/free-design-rfp-response/) 
	
So, the reality is that your hands may be tied and as part of a larger organization you have to write an RFP. Read the above and write your RFP with that in mind. Let me summarize, though:

1.) Do not ask / solicit free design advice or uniquely detailed processes as part of your response requirements. Designers / agencies have processes and they can provide an overview, but specific-to-you answers are premature, well rehearsed falsehoods, and - of course - free work.

2.) Do not require a minimum word or page count. As per Chris Lema: "the RFP invites companies that specialize in responding to them, and those may not make the best development shops. But they will certainly invite more expensive shops - which may (or may not) fit your budget."

3.) Loudly invite questions regarding the RFP

Most of the articles above have really good advice for organizations required to send RFPs. Follow them. These days there are a few alternatives I like, namely "Project Evaluations":

Stop Writing Project Proposals (http://www.smashingmagazine.com/2012/02/stop-writing-project-proposals/) 

Rather than solicit for whole designs, solicit for evals (or allow respondents to offer a quote and a pitch for an eval) that may or may not lead to a full redesign project. This may help answer questions or pinpoint problems, user needs, and the like, which can then help you craft a much more focused RFP down the road because you know what you want, how to articulate it, what's good, and what's been recommended so far. 

Anyway, I'll send you a recent RFP off-list so you have something follow.

Have a good one,

Michael Schofield / @schoeyfield / www.libux.co 

-----Original Message-----
From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of Dani Brecher Cook
Sent: Monday, December 07, 2015 7:31 PM
To: [log in to unmask]
Subject: [CODE4LIB] Examples of Library Website Design RFP?

Dear Code4Lib community,

My library is in the preliminary stages of preparing an RFP to outsource the coding of a redesign of our main library website, using a TBD CMS. Have any of you recently done anything like this, and, if so, would you be willing/able to share your RFP with us as an example? We've found some generic samples online, but it would be great to see some library-specific proposals.

Thanks so much for considering,

Dani 
[log in to unmask]